I am reading up on Pathways Commons as well as their BioPax java tool. The first question that comes to mind when reading this is - why come up with a new data format (the OWL format), when tab-delimited files work fine?
It seems to me that the simplest way to exchange data is in a set of tab-delimited files from a reliable database, and an ER diagram that explains the relations between these files (soon to be tables). DBSNP did a good job with this, for instance, as they provide a vast set of tables that allow you, if you are interested, to create a partial local copy from a limited set.
So if we are to complicate the exchange of data with a new format, requiring a Java tool to extract data, what new advantages does it bring to justify the loss of straightforwardness?
And seeing how PathwayCommons provides both OWL files and tab-delimited files, what is the best way to create a local copy in a relational database? They advocate the OWL format in their README file, but it would seem a bit simpler to use the tab-delimited files.
Keep in mind I'm a programmer and not a biologist! Thanks for any feedback.
Did you read about the OWL format and the rationale behind it? http://www.w3.org/TR/2004/REC-owl-features-20040210/#s1.2 and http://www.w3.org/TR/owl2-overview/ OWL wasn't just something Pathway Commons came up with but it is a standard format for ontologies recommended by the w3c
Ah, I see, thanks.
Did you try to recreate the OWL file from the TSV file and macthing ER diagram using a program you wrote. Did that work?