You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to parse the OpenEnergyOntology (https://openenergy-platform.org/ontology/oeo) the RDF parser skips over ~80 components and returns a different set of components each time. I.e. the following test fails and diff is different on each run. Unfortunately, I couldn't make out a pattern yet.
The error does seem to be related to the OEO; other (large) ontologies in RDF/XML do not produce this error. Also, other parsers don't produce this error.
The text was updated successfully, but these errors were encountered:
@b-gehrke are the skipped components always the same, or do they also differ from run to run? If they were always the same, do they belong to a particular class of components, i.e. all annotations or all axioms?
By looking through OEO, I see that e.g. at line 51873 there is the following axiom:
Could you verify whether this axiom gets skipped or if it is parsed properly?
My hypothesis is that the parser is not handling axioms declared in this way correctly.
The skipped axioms are not always the same (e.g. the SubClassAxiom in line 9217 is sometimes parsed, sometimes not). I attached a list of three different runs which contain the missing axioms (compared the XML version).
The DisjointClasses axiom you mentioned are indeed always missing. Additionally, EquivalentClasses axioms and some trivial declarations are often not included (e.g. line 341, declaration of annotation property "IAO:0000115").
When trying to parse the OpenEnergyOntology (https://openenergy-platform.org/ontology/oeo) the RDF parser skips over ~80 components and returns a different set of components each time. I.e. the following test fails and
diff
is different on each run. Unfortunately, I couldn't make out a pattern yet.The error does seem to be related to the OEO; other (large) ontologies in RDF/XML do not produce this error. Also, other parsers don't produce this error.
The text was updated successfully, but these errors were encountered: