Update OWL API to 4.5.26

[matentzn]

Resolves #1129

• docs/ have been added/updated (not necessary)
• tests have been added/updated
• mvn verify says all tests pass
• mvn site says all JavaDocs correct
• CHANGELOG.md has been updated

The last OWL API version (4.5.25) had some major issues with the way complex turtle axioms are written, see #1129. This version solves this problem.

[matentzn]

The necessity to add this was the only thing that was really important. @balhoff I wonder if you have an hypothesis why suddenly the id was necessary here to be added?

[matentzn]

or in other words, why suddenly the OWLAPI decided that in the presence of the

    <owl:AnnotationProperty rdf:about="http://www.geneontology.org/formats/oboInOwl#id"/>

Now the <rdfs:label>id</rdfs:label> was serialised out?

[balhoff]

I added it to this enum in my OWLAPI PR: https://github.com/owlcs/owlapi/pull/1099/files#diff-624125d6c0fdd02198cff3e52ece7ed9a49652cc11b4b68bf8a7970a9e35930dR58

[matentzn]

Excellent, thank you for the clarification.

[matentzn]

The following ontologies changed their DL profile status:

clo owl2_dl True False
ecto owl2_dl True False
envo owl2_dl True False
foodon owl2_dl True False
iceo owl2_dl True False
maxo owl2_dl True False
ngbo owl2_dl True False
obi owl2_dl True False
swo owl2_dl True False

[matentzn]

@balhoff suggests could be explained by owlcs/owlapi#1094

[matentzn]

(For the eternal records, the violations are all true positive violations, e.g.)

~/tools/robot validate-profile -I http://purl.obolibrary.org/obo/envo.owl --profile DL
OWL 2 DL Profile Report: Ontology and imports closure NOT in profile. The following violations are present:
Use of unknown datatype: rdfs:anyURI [Declaration(Datatype(rdfs:anyURI)) in OntologyID(OntologyIRI(<http://purl.obolibrary.org/obo/envo.owl>) VersionIRI(<http://purl.obolibrary.org/obo/envo/releases/2023-02-13/envo.owl>))]

PROFILE VIOLATION ERROR http://purl.obolibrary.org/obo/envo.owl violates profile DL
For details see: http://robot.obolibrary.org/validate-profile#profile-violation-error
Use the -vvv option to show the stack trace.
Use the --help option to see usage information.