Allow stricter parsing/saving of ontologies, fixing profile violations. about owlapi HOT 8 CLOSED

Same issue with this ontology:

http://bioportal.bioontology.org/ontologies/3198

from owlapi.

It looks like the ontology has a property named rdf:Description and this is confusing the parser.

from owlapi.

Interesting ... that gives me a potential work around. Thanks @matthewhorridge

from owlapi.

rdf:Description with the same standard expansion for rdf? Among other things, that's use of reserved vocabulary :-)
Can you run the profile violation tool on it? It might report other fixes that need to be applied.
Thanks for the report.

from owlapi.

The grammar seems to state that rdf:Description is not allowed as a property URI:

http://www.w3.org/TR/REC-rdf-syntax/#propertyElementURIs

from owlapi.

The use of rdf:Description in the ontology seems to match the common usage of rdfs:comment, if you need an alternative.

from owlapi.

Confirmed, the profile check for OWL 2 DL reports the property name as reserved vocabulary.
For backwards compatibility this is not treated as an error - it should, IMHO, but we do not want to break all the tools which rely on being able to load slightly invalid ontologies.
We have plans to enable stricter parse and output modes in version 4. This will allow to fix issues as the one described here.
Turning this into a feature request as a reminder.

from owlapi.

OWLProfileViolation now comes with a fix method, that provides the changes required to make the violation go away. Use with care, as sometimes the fix is to drop the axiom.

from owlapi.