This is implied in the semantics, but not made explicit in the syntax: since both import and ontology (and, to some extent, data-version) clause values end up being converted to ontology IRIs (either as an IRI describing the document itself, or an IRI referring to the imported resource) they should follow the same syntax, with the following semantics:
either as an fully qualified IRI, in which case it is used without any other transformation
or as an abbreviated form, in which case it is translated using a default URL;
for import and ontology: https://purl.obolibrary.org/obo/{ontology}.owl
for data-version: https://purl.obolibrary.org/obo/{ontology}/{data-version}/{ontology}.owl
The following rules could be used (to be discussed):
This is implied in the semantics, but not made explicit in the syntax: since both
import
andontology
(and, to some extent,data-version
) clause values end up being converted to ontology IRIs (either as an IRI describing the document itself, or an IRI referring to the imported resource) they should follow the same syntax, with the following semantics:import
andontology
:https://purl.obolibrary.org/obo/{ontology}.owl
data-version
:https://purl.obolibrary.org/obo/{ontology}/{data-version}/{ontology}.owl
The following rules could be used (to be discussed):
with
ipath-rootless
being defined in the IRI RFC.