Adding an import does not load the imported ontology about owlapi HOT 4 CLOSED

There is a distinction between adding an imports declaration to an ontology and physically trying to load an (imported) ontology. I think we should keep this clean separation. It allows manipulating of imports declarations/statments without doing heavy weight parsing (i.e. ImportsDeclarations being "lightweight" statements).

from owlapi.

Yeah I figured that, but I think it might be useful to provide some sort of option to enable it for those who might want to do it.

from owlapi.

If adding an imports declaration parses/loads an ontology into a manager, then would removing the declaration unload it? If it didn't there would be some sort of asymmetry, but doing this seems yucky. The current solution is simpler... i.e. let the client decide what to do.

from owlapi.

Closed this as unnecessary. Client code which requires a new import to be available immediately for querying should load the imported ontology in the manager and not rely on automatic loading. The reverse applies for removed import directives: they do not unload the ontologies.

from owlapi.