Open GoogleCodeExporter opened 8 years ago
Thank you for your detailed bug report! I can confirm that I was able to
reproduce this problem.
Further analysis has revealed that this version of FMA is not a valid OWL 2
ontology. Specifically, there are three axioms with the empty
ObjectIntersectionOf:
SubClassOf(<http://purl.org/sig/ont/fma/fma256019>
ObjectSomeValuesFrom(<http://purl.org/sig/ont/fma/attributed_part>
ObjectIntersectionOf()))
SubClassOf(<http://purl.org/sig/ont/fma/fma242199>
ObjectSomeValuesFrom(<http://purl.org/sig/ont/fma/attributed_part>
ObjectIntersectionOf()))
SubClassOf(<http://purl.org/sig/ont/fma/fma63841>
ObjectSomeValuesFrom(<http://purl.org/sig/ont/fma/attributed_constitutional_part
> ObjectIntersectionOf()))
According to the OWL 2 specification, ObjectIntersectionOf should have at least
two class expressions as parameters:
http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Intersection_of_Class_Expres
sions
I am not really sure why OWL API accepts such ontologies. Perhaps to be
backward compatible with OWL 1, in which such expressions are probably allowed.
You can test if your ontology is compatible with OWL 2 by, e.g., converting it
to OWL 2 functional-style syntax and loading it again via OWL API (in general,
OWL 2 functional-style or OWL 2 XML syntax are more stable and easier to parse
by OWL API than OWL 2 RDF XML syntax). For this ontology the OWL API functional
style parser would return an error.
Coincidently, this issue has been already fixed in the next development version
of ELK (0.5.0-SNAPSHOT). If there will be some further urgent problems, I might
consider fixing this problem in the 0.4.x branch and release a new minor
version. For now, I would just recommend fixing this problem in the ontology
directly, perhaps also notifying the developers of FMA.
Best regards,
Yevgeny
Original comment by ykazako...@gmail.com
on 31 May 2015 at 9:11
Original issue reported on code.google.com by
leechuck2@gmail.com
on 24 May 2015 at 11:40