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
I encountered the problem that a valid OWL DL ontology can be classified as not belonging to the profile if language tags are used. The following is a minimal example, defining a single data relation:
Using the class OWL2DLProfile(), I wrongly get a violation report for the OWL DL profile. The issue seems to be that the object of the data relation is parsed as rdfs:langString in OWLLiteralImplPlain (line 44). However, this type of string is not allowed according to the OWL DL standard.
I am not sure if this is a problem of incorrect parsing or conflicting standards. The RDF standard (3.3; third element) sounds like the parsing is correct.
For reproduction, here is a minimal program that demonstrates the behavior:
OWLOntologyDocumentSource source = new FileDocumentSource(ontFile, new FunctionalSyntaxDocumentFormat());
OWLOntologyManager manager = OWLManager.createOWLOntologyManager();
ont = manager.loadOntologyFromOntologyDocument(source);
OWLProfileReport profileReport = new OWL2DLProfile().checkOntology(ont);
List<OWLProfileViolation> violations = profileReport.getViolations();
The text was updated successfully, but these errors were encountered:
I encountered the problem that a valid OWL DL ontology can be classified as not belonging to the profile if language tags are used. The following is a minimal example, defining a single data relation:
Using the class
OWL2DLProfile()
, I wrongly get a violation report for the OWL DL profile. The issue seems to be that the object of the data relation is parsed asrdfs:langString
in OWLLiteralImplPlain (line 44). However, this type of string is not allowed according to the OWL DL standard.I am not sure if this is a problem of incorrect parsing or conflicting standards. The RDF standard (3.3; third element) sounds like the parsing is correct.
For reproduction, here is a minimal program that demonstrates the behavior:
The text was updated successfully, but these errors were encountered: