This has actually been a long standing issue. There are places in the code where the first Ontology resource found in an OntModel is taken as the associated ontology, but this could be any of the other Ontology resources referenced by the model, for example via import.
This issue is related with #354 , where part of the issue was solved (thus allowing the registration iself to complete) but stills the contents of the registered ontology has wrong associations.
The task here is to review and fix this whole handling (in particular, in calls to JenaUtil2.getOntology(OntModel) and replace them with retrieval of the Ontology for the concrete associated URI.
This has actually been a long standing issue. There are places in the code where the first Ontology resource found in an OntModel is taken as the associated ontology, but this could be any of the other Ontology resources referenced by the model, for example via import.
This issue is related with #354 , where part of the issue was solved (thus allowing the registration iself to complete) but stills the contents of the registered ontology has wrong associations.
The task here is to review and fix this whole handling (in particular, in calls to
JenaUtil2.getOntology(OntModel)and replace them with retrieval of the Ontology for the concrete associated URI.