Version History
Version | Date | Comment | Lead Editor | Contributors |
|---|---|---|---|---|
0.1 | 2024-04-05 | First version | ||
0.2 | 2024-05-15 | Revision to add references | ||
0.3 | 2024-07-18 | Added Protege instructions |
...
MUST: This word means that the definition is an absolute requirement of the specification.
MUST NOT: This phrase means that the definition is an absolute prohibition of the specification.
SHOULD: This word means that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications MUST be understood and carefully weighed before choosing a different course.
SHOULD NOT: This phrase means that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label.
MAY: This word means that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item.
Syntax
According to the OWL 2 Web Ontology Language Document Overview (Second Edition), the primary exchange syntax for OWL 2 is RDF/XML. Therefore, every IOF ontology MUST be serialized in the RDF/XML syntax, using more specific rules explained in the subsequent sections.
Base IRI
According to XML Base, W3C Recommendation., 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. 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
Every IOF ontology MUST NOT declare a default namespace to ensure that no XML element is inadvertently put into the wrong namespace.
...
In order to ensure that no XML element is inadvertently put into the wrong namespace, every IOF ontology MUST NOT declare a default namespace.
What to do in Protégé
We need to prescribe what is required in Protégé to make things work correctly for a new ontology. Every time an ontology is created using Protégé, it defaults to the wrong behavior. We need instructions on changing options for the default namespace and base to ensure the serializer works properly and is serialized consistently.
...
Ontology Namespace Prefix
Every ontology MUST define a short, unique, meaningful, ontology-namespace prefix, like the ones found on lines 2-4, above.
Tools
Every local git repository (i.e., the one on your computer) that pushes changes to the IOF GitHub repository MUST have the EDM Council RDF Toolkit installed, such that every time an RDF/XML file is committed, that file will be automatically rewritten to conform to the policies in this document. The instructions for installing that toolkit can be found at that link.
What to do in Protégé
Protégé always saves an ontology with a default prefix of the ontology IRI, as shown in the following screen shot.
...
In order to fix this, , and, by default, violates the Ontology Namespace Prefix rule, above. In order to conform to the rules in this document, press the circle icon in the upper right and give that prefix a name and ??? TBD.
...
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 |
|