Closed IgorRodchenkov closed 9 years ago
Also discovered that INOH BioPAX has the following issues:
Another type of problem - there are many TemplateReactions that have a Complex as the value of the 'template' property, which is apparently wrong. There can be only values/objects of Dna, Rna, RnaRegion or DnaRegion type; other types get ignored by the Paxtools' parser (and another BioPAX/OWL parser might simply fail short).
(Note: INOH BioPAX RDF/XML files were created somehow ignoring such critical errors; data files that contain illegal use of OWL properties are simply impossible to write with Paxtools Java library.) Example INOH files that have this sort of errors are, e.g., BMP2_signaling_TGF-beta_MV.owl ("id1354461388_Transcription"), FGF8_Mouse.owl ("id814152498_Transcription" and several more.
This cannot be fixed with Paxtools; perhaps the Validator could do (with some new code added there); could be fixed with a custom script, based on regex or RDF tools... Ideally, this must be addressed by the data Ca provider, INOH.
Addition. After some analysis (with Gary B.), we've decided to remove all such illegal TemplateReaction objects that have a "gene" Complex (of two DNAs - coding and responsive el.) as 'template' from the model. These are hardly useful for public, for there are no standard gene/sequence identifiers (there are xrefs to INOH and IGS ontology that cannot be found any more, and DnaReferences are trivial, with name 'Dna' and no xrefs...)
Also, e.g., in BMP2_signaling_TGF-beta_MV.owl, Pathway has pathwayOrder (steps) but no pathwayComponent values. Shall we copy reactions from the listed steps to pathwayComponent?
Ok, we've done what we could. Closing the issue for now (let's re-open if we gonna need to do more, later).
We downloaded and saved most (if not all) of the INOH v4 data for future use/fix here.
http://inoh.hgc.jp (
www.inoh.org
is not properly resolved anymore - domain name has been probably lost...)INOH BioPAX L3 looks good in general (there are warnings reported by the biopax-validator); let's fix the following in the cleaner:
http://www.inoh.org (MolecularRoleOntology)
" to "IMR" (http://www.ontobee.org/browser/index.php?o=IMR)? (this ontology/db is not in MIRIAM, nor obofoundry.org, but can be seen at http://www.berkeleybop.org/ontologies/imr.owl, http://inoh.hgc.jp/ontologies/MoleculeRoleOntology.obo, and the OWL URIs are still resolved (e.g., http://purl.obolibrary.org/obo/IMR_0702625).http://www.inoh.org (EventOntology)
" - that could be called "IEV"(http://www.ontobee.org/browser/index.php?o=IEV, http://www.berkeleybop.org/ontologies/iev.owl, http://inoh.hgc.jp/ontologies/EventOntology.obo) ontology (IEV_1234567 ids)...