-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extract produces strangeness -> OBO Graph error #1184
Comments
The header appears to be the main issue. |
@caufieldjh the |
<?xml version="1.0"?>
<rdf:RDF xmlns="http://www.w3.org/2002/07/owl#"
xml:base="http://www.w3.org/2002/07/owl"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:obo="http://purl.obolibrary.org/obo/"
xmlns:owl="http://www.w3.org/2002/07/owl#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:xml="http://www.w3.org/XML/1998/namespace"
xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:terms="http://purl.org/dc/terms/"
xmlns:oboInOwl="http://www.geneontology.org/formats/oboInOwl#">
<Ontology/>
</rdf:RDF> translates to this Turtle: _:Bcaf351a4X2DfbbfX2D465cX2Db7e5X2Dc4aa153dec17 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/2002/07/owl#Ontology> . |
I played around with this a bit: This converts from owl to obojson without issue. <?xml version="1.0"?>
<rdf:RDF xmlns="http://www.w3.org/2002/07/owl#"
xml:base="http://www.w3.org/2002/07/owl"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:obo="http://purl.obolibrary.org/obo/"
xmlns:owl="http://www.w3.org/2002/07/owl#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:xml="http://www.w3.org/XML/1998/namespace"
xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:terms="http://purl.org/dc/terms/"
xmlns:oboInOwl="http://www.geneontology.org/formats/oboInOwl#">
<owl:Ontology rdf:about="http://purl.obolibrary.org/obo/phenio.owl">
</owl:Ontology> This does not - it raises a <?xml version="1.0"?>
<rdf:RDF xmlns="http://www.w3.org/2002/07/owl#"
xml:base="http://www.w3.org/2002/07/owl"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:obo="http://purl.obolibrary.org/obo/"
xmlns:owl="http://www.w3.org/2002/07/owl#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:xml="http://www.w3.org/XML/1998/namespace"
xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:terms="http://purl.org/dc/terms/"
xmlns:oboInOwl="http://www.geneontology.org/formats/oboInOwl#">
<owl:Ontology rdf:about="http://purl.obolibrary.org/obo/phenio.owl">
<Ontology/> Omitting the Should including the |
Your second snippet is malformed XML. You can either use It's much easier to work with OWL functional syntax, or possibly Turtle if you need an RDF syntax. With these you have a better chance of seeing what elements are in your ontology. With RDF/XML you are simultaneously dealing with XML wellformedness along with the very complicated XML-to-RDF mapping. RDF/XML is basically the worst format. |
I have had that issue as well and made a corresponding obographs issue here: geneontology/obographs#100 As this is not a ROBOT issue after all, lets move discussions there. |
Hi robotniks. I'm facing a challenge in converting OWL to obojson, but only for an extracted subset. Starting with
phenio.owl
, I remove any problematic annotations (like"<rdfs:comment></rdfs:comment>"
) then userobot convert
to get the corresponding json. This works without issue. But when I start withphenio-test.owl
, which is the result ofrobot extract --method MIREOT --input phenio.owl --branch-from-term "UPHENO:0084945" --output phenio-test.owl
, I get an OBO GRAPH ERROR. Could there be some annotation error introduced in the course of the extraction? How could I find out where it is, if so?One bit of weirdness - the extracted product has a mangled header. It's missing the whole owl:Ontology block.
This is what the
phenio.owl
header looks like:And here's
phenio-test.owl
:This is all with v1.9.5.
@matentzn
The text was updated successfully, but these errors were encountered: