On 25/04/13 21:30, Joshua TAYLOR wrote:
On Thu, Apr 25, 2013 at 2:24 PM, Ian Dickinson <[email protected]> wrote:
On 25/04/13 18:27, Joshua TAYLOR wrote:
On Thu, Apr 25, 2013 at 11:46 AM, David Jordan <[email protected]>
wrote:
I am writing a little performance benchmark test to ascertain the
overhead in determining whether a given update is a valid. It was
recommended before on this forum that the best way to do this
efficiently is create a new OntModel A, have it import the
associated ontology, then perform the few updates in this new
OntModel A, and then call A.validate().isValid().
Is an imported model simply a submodel, added by just calling the
add method? I don’t see any specific method for importing a model,
but some documentation suggests that a submodel is an imported
model.
OntModels can have submodels, which are added with
OntModel#addSubModel [1]. However, OWL ontologies can also import
other ontologies via owl:imports, and this is a different concept
than OntModel and submodels.
Not really. Sub-models are what OntModel uses to keep track of imports. An
ontology with imported ontologies is a composite document, sub-models are
the composite pattern analogue of that for OntModels.
If you read an ontology into an OntModel, and that ontology owl:imports
another ontology, the import will end up in a sub-model. Or you can add a
sub-model directly using the Java API. Either way, you end up with the same
composite model structure.
Sorry, I should have been clearer about what I meant by "different
concept." The way that Jena OntModels handle owl:imports makes use of
submodels, but use of submodels alone doesn't imply that an
owl:imports relationship is being established.
Sorry, I see what you mean. Yes, that's exactly right.
Ian
