ontologies not in import closure if owl:imports <iri> does not match <iri> a owl:Ontology

[tgbugs]

If the ontology iri (ie <iri> a owl:Ontology) does not match that of the owl:imports <iri> when loading a local copy from a catalog.xml then the ontology will not be included in the import closure and will not be included for reasoning.

To reproduce this git clone https://github.com/SciCrunch/NIF-Ontology.git; cd NIF-Ontology; checkout uri-switch and open NIF-Ontology/ttl/nif.ttl in protege using the Open... option in the file menu.

Viewing the Ontology imports pane in the Active ontology tab of protege will show the imported iri without any additional information. When the reasoner is run any axioms from the mismatched iri cases will not be included. Axioms from the mismatched iri cases will not appear unless you switch to the Show all loaded ontologies option under View.

The work around I use is to patch the import chain of all my ontologies when I want to reason and have the <iri> a owl:Ontology iris in my catalog point to the local copy. See the patch and the catalog I use to fix the issue (note on the usage).

See also #629 (comment)

[gpotdevin]

I can confirm both the issue and workaround stated above.

[malte3d]

Can confirm this bug is still present and the workaround stated above still works.

However, based on the research i did for actual solutions to fix the core problem, it is not in Protege itself, but in the way the OWL API library handles the import resolution. So this most likely has to fixed in https://github.com/owlcs/owlapi

[vChavezB]

I am not sure if it entirely the same issue as in #1181 but if yes try appling the patch I provide in #1181 (comment)

[vChavezB]

issue should be solved with release 5.6.4