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
According to Manchester syntaxIRI := fullIRI | abbreviatedIRI | simpleIRI. So IRI can be abbreviated IRI. But if we represent Range field of AnnotationPropertyFrame as abbreviated IRI then it can't be parsed by OWL API (tried with version 4.5.20).
Exapmle
If we transform BDO into Manchester syntax with Protege we can see next AnnotationPropertyFrame in result:
The point is that if some tool generates .omn file with IRI in abbreviated form (which is allowed according to OWL standard) it becomes inconsistent with OWL API.
The text was updated successfully, but these errors were encountered:
Problem description
According to Manchester syntax
IRI := fullIRI | abbreviatedIRI | simpleIRI
. SoIRI
can be abbreviatedIRI
. But if we representRange
field ofAnnotationPropertyFrame
as abbreviated IRI then it can't be parsed by OWL API (tried with version 4.5.20).Exapmle
If we transform BDO into Manchester syntax with Protege we can see next AnnotationPropertyFrame in result:
If we change
Range
field tothen it can't be parsed with OWL API.
The point is that if some tool generates
.omn
file with IRI in abbreviated form (which is allowed according to OWL standard) it becomes inconsistent with OWL API.The text was updated successfully, but these errors were encountered: