Should all owl:imports refer to versioned IRIs?

[Jamie-SA]

I think we have a couple of places in the repo with imports that look like owl:imports <https://w3id.org/semanticarts/ontology/gistCore> ;. I think we'd want them to reference the versioned IRI of an ontology, such as owl:imports <https://w3id.org/semanticarts/ontology/gistCoreX.x.x> ;.

[rjyounes]

Yes, agreed.

[rjyounes]

Mark agrees.
Boris: Temporarily yes. But would like to see a more flexible import paradigm where the import uses an unversioned IRI, but there is a dependency on some exact version, version greater than, versions x-y, etc. Like Maven, Python dependencies. These would be attached to the ontology itself. It's descriptive but validated by a query.

Rebecca: Would like to have the versionIRI added during the release bundling, since people will be looking for it.
Boris: Yes.

Michael: will add issue to add gist versions and gist operators - possibly in a sub-gist.

DECISION: For now, add owl:imports <https://w3id.org/semanticarts/ontology/gistCoreX.x.x> ; to all the small ontologies that are released with gistCore: gistPrefixDeclarations, gistSubClassAssertions, and gistValidationAnnotations. gistMediaTypes is already correct.

@dylan-sa I am guessing the change to gistSubClassAssertions requires a change to the script, so adding you as an assignee.