Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check of OWL 2 DL profile fails when using language tags #1158

Open
tobiaswjohn opened this issue Nov 27, 2024 · 0 comments
Open

Check of OWL 2 DL profile fails when using language tags #1158

tobiaswjohn opened this issue Nov 27, 2024 · 0 comments

Comments

@tobiaswjohn
Copy link

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:

Prefix(:=<http://www.example.org/reasonerTester#>)
Ontology(
  Declaration(DataProperty(:dataprop))
  Declaration(NamedIndividual(:a))
  
  DataPropertyAssertion(:dataprop :a "some string"@en)
)

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();
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant