...
According to TBD, the xml:base attribute of an XML element determines an IRI prefix to be prepended to every relative IRI used in any nested XML element. For example, the The following provides a fictitious example of how this mechanism works:
...
In order to ensure that the correct IRI is prepended to the value of every relative IRI in an IOF ontology, the xml:base attribute of the rdf:RDF XML element in every ontology file MUST have the ontology IRI as its value.
Default Namespace
...
According to TBD, the default namespace of an XML element determines the namespace of every nested XML element that does not have an explicit namespace. The following provides an example that is technically legal, but disallowed by this policy:
| Code Block |
|---|
<rdf:RDF xml:base="https://spec.industrialontologies.org/ontology/systemsengineering/SystemsEngineering/"
xmlns="http://www.w3.org/2002/07/owl#"
xmlns:iof-se="https://spec.industrialontologies.org/ontology/systemsengineering/SystemsEngineering/"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
>
<Ontology rdf:about="https://spec.industrialontologies.org/ontology/systemsengineering/SystemsEngineering/">
</Ontology>
<Class rdf:about="&iof-se;AbstractSyntax">
<rdfs:subClassOf rdf:resource="&iof-se;Syntax"/>
</Class>
</rdf:RDF> |
Note that the default namespace declaration on line 2 technically make the elements Ontology (lines 6 and 7) and Class (lines 9 and 11) into the fully qualified IRIs http://www.w3.org/2002/07/owl#Ontology and http://www.w3.org/2002/07/owl#Class, respectively.
In order to ensure that no XML element is inadvertently put into the wrong namespace, every IOF ontology MUST NOT declare a default namespace.
Voting
Member | Vote | Comments | |
|---|---|---|---|
| 1 | |||
| 2 | |||
| 3 | |||
| 4 | |||
| 5 | |||
| 6 | |||
| 7 | |||
| 8 | |||
| 9 | |||
| 10 | |||
| 11 | |||
| 12 | |||
| 13 | |||
| 14 | |||
| 15 | |||
| 16 | |||
| 17 | |||
| 18 | |||
| 19 | Total | YES: 0, NO: 0, No Response: 0 |
|