Implement versioning ontology per issue 979

[rjyounes]

Fixes #979.

[rjyounes]

Putting into draft state - forgot to check documentation for necessary updates.

[rjyounes]

This can't be finalized until #983 is complete, since the versioning and ops files can't be downloaded so the checks fail.

[uscholdm]

Looks good, one wording suggestion.

[rjyounes]

Keeping in draft state until:

• Issue Issue 372 text datatype properties #989 has been merged.
• bundle.yaml runs versioning validation queries.
  • The queries should be put into a sub-module, but can do that later.

[rjyounes]

@sa-bpelakh @uscholdm Do you think it's necessary to state the version and dependencies in the ancillary ontologies as well as gistCore? It looks like a bit of overkill, and these ontologies are always versioned with gist and would likely not have dependencies different from gist's. On the other hand, for absolute correctness I suppose they are needed.

[pmcb55]

I'm just curious really - but in reference to 'absolute correctness' around dependencies, dependency ranges, and the like, did you folks look into PLOW? (As indeed, I think 'absolute correctness' is definitely a most worthy goal, as dependency issues have a very nasty habit of getting convoluted/unwieldy/nightmarish pretty quickly once out in the 'real-world'.)

[rjyounes]

Moved to 12.2.0

[rjyounes]

@sa-bpelakh: @uscholdm has raised the point that you should make sure this implementation doesn't clash with the new units and magnitudes model (shouldn't, because there is no dependency on gist, but worth checking).

[uscholdm]

This can't be finalized until #983 is complete, since the versioning and ops files can't be downloaded so the checks fail.

@rjyounes @Jamie-SA
The operators file can now be downloaded, so the import should work. However, the versioning ontology is not currently downloadable.

From Protege,

• loading https://w3id.org/semanticarts/ontology/operators1.0.0 from URL works.

• loading https://w3id.org/semanticarts/ontology/operators does not work "File not found".

• loading https://w3id.org/semanticarts/ontology/versioning1.0.0 from URL works, except that it cannot find the imported ontology: https://w3id.org/semanticarts/ontology/operators

• loading https://w3id.org/semanticarts/ontology/versioning does not work "File not found".

• loading https://w3id.org/semanticarts/ontology/gistCore13.0.0 from URL works

• loading https://w3id.org/semanticarts/ontology/gistCore results in loading gistCore13.0.0

Possible fixes (one or both):

• the versioning ontology needs to import v1.0.0 of the operators ontology
• make the import of https://w3id.org/semanticarts/ontology/operators work

The first fix is already implemented on the develop branch of the versioning ontology and should be ready for releasing a new version, 1.0.1 or 1.1.0. The only 'semantic' change is the explicit import of operators1.0.0 instead of operators.

QUESTION: do we have a consistent policy on what to do with loading ontologies from URL when using a 'main URI' vs. a versioned IRI? If so, then we should make the imports of the following work:

• https://w3id.org/semanticarts/ontology/operators
• https://w3id.org/semanticarts/ontology/versioning

[uscholdm]

Keeping in draft state until:

• Issue Issue 372 text datatype properties #989 has been merged.

@rjyounes This has now been merged.

[uscholdm]

@sa-bpelakh: @uscholdm has raised the point that you should make sure this implementation doesn't clash with the new units and magnitudes model (shouldn't, because there is no dependency on gist, but worth checking).

I checked, there is no conflict, as expected.