Updated with new release Version IRI

Votes

Overview

The IRI structure of the IOF references the OWL documents providing a versioned and not-versioned form. The latter form will always refer to the latest released version of the documents. For the IRI syntax, please refer to RFC 3987 from The Internet Engineering Task Force (IETF).

This document provides the normative requirements for all IRIs created in the IOF for consistency and usability. An English language class and property naming scheme was selected after considering a numerical identity scheme to facilitate the use of the ontologies. The following sections define the rules for constructing the IRI and version IRI per OWL 2 specifications (reference below).

The following rules MUST be followed when reviewing this document, these are taken from IETF RFC 2119 (simplified):

1. MUST: This word means that the definition is an absolute requirement of the specification.

2. MUST NOT: This phrase means that the definition is an absolute prohibition of the specification.

3. 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.

4. 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.

5. 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.

Protocol and Authority

All IOF IRIs MUST be resolvable and refer to a resource that can be retrieved from the internet. The form of the IRI MUST specify the protocol as HTTPS and the authority MUST be a domain administered and owned by the IOF or its parent organization. The IOF MUST choose a single authority for all ontologies released by the IOF. The authority spec.industrialontologies.org is used for illustrative purposes only. When decided, this document MUST be revised with the normative authority.

• For the given IRI: https://spec.industrialontologies.org/ontology/supplychain

• The protocol: https

• The authority: spec.industrialontologies.org

• The development authority: dev.industrialontologies.org

The authority MUST be a domain administered and owned by the IOF or its parent organization. The IOF MUST choose a single authority for all ontologies released by the IOF. The authority MUST be spec.industrialontologies.org unless it is not possible due to technical reasons.

IRI Path

In accordance with IETF RFC 3987, the Path component of the IRI MUST immediately follow the authority starting with a forward-slash (/), and the Path parts MUST be separated by forward-slashes (/). The first part of the Path is referred to as the Path Root.

• For the given IRI: https://spec.industrialontologies.org/ontology/supplychain

• The path component: /ontology/supplychain

IRI Path Root

The IRI Path Root MUST be /ontology. The Root provides the ability to have documentation and other supporting resources referenced in alternate Root resources, such as /documentation or /references. The IOF MUST designate each root resource for a specified use.

• For the given IRI: https://spec.industrialontologies.org/ontology/supplychain

• The root part: /ontology

Topic Area

A topic represents a domain or area of concern addressed by one or more working groups. The topic organizes sub-topics and modules. The IOF will provide the ontology organization rules for topics, sub-topics, and ontologies in a future publication. All content within a topic MUST be released with a common version. The version of one topic does not constrain another topic’s version.

The topic areas MUST form the path part of the IRI. The topic areas MUST be all lower case with no separation or punctuation between words. All acronyms MUST be spelled out, except for words defined in the dictionary like radar (RADAR) always given in lowercase. The following are examples of topic areas:

• https://spec.industrialontologies.org/ontology/supplychain

• https://spec.industrialontologies.org/ontology/foundation

• https://spec.industrialontologies.org/ontology/productionprocess

IRI and Version IRI

IOF ontologies MUST provide a non-version IRI (referred to as the IRI) and version IRI in the RDF/XML serialized OWL file.

Development and release version IRIs differ where development ontologies are stamped using a year, month, and day (date version) as opposed to the release version IRIs composed of a year and a increasing number (numeric version). All ontologies released together MUST have the same year and number.

Development IRI

The development version IRI MUST use the date of the version in YYYYMMDD form, such as 20210601 for June 1, 2021. When a versioned IRI is formed, the date MUST appear after the topic. In the following examples, the sub-topic area is given to illustrate the placement of the version (see next section: Sub-Topic). Development ontologies are versioned based on dates.

All versions in GitHub use the development IRI. The publication and release process replaces the version IRI.

The non-versioned IRI MUST always reference the latest released version of the ontology.

• Versioned IRI: https://dev.industrialontologies.org/ontology/supplychain/20220821/meta

• Non-Versioned IRI: https://dev.industrialontologies.org/ontology/supplychain/meta

Public Release IRI

The publicly released version IRI MUST use a numeric version formed with the release year and a monotonically increasing number NN in YYYYNN form, such as 202202 for the second release in 2022. If the IOF releases every quarter, NN represents the quarter when the ontology was released. When a versioned IRI is formed, the version MUST appear after the topic. In the following examples, the sub-topic area is given to illustrate the placement of the version (see next section: Sub-Topic). All IOF ontologies part of a release MUST share a common numeric version.

This version IRI will be automatically changed during the release and publication process. The version IRI in GitHub will not be changed by the publication process.

The non-versioned IRI MUST always reference the latest released version of the ontology.

• Versioned IRI: https://spec.industrialontologies.org/ontology/supplychain/202202/meta

• Non-Versioned IRI: https://spec.industrialontologies.org/ontology/supplychain/meta

OWL IRI Specification

The IRI specification is given in OWL 2 Web Ontology Language, Section 3.1 standard as follows:

Each ontology may have an ontology IRI, which is used to identify an ontology. If an ontology has an ontology IRI, the ontology may additionally have a version IRI, which is used to identify the version of the ontology. The version IRI may be, but need not be, equal to the ontology IRI. An ontology without an ontology IRI MUST NOT contain a version IRI.

Sub-Topic (Optional)

When specified, a sub-topic MUST appear after the version date in a versioned IRI or after the topic in a non-versioned IRI. For example, metadata associated with the supplychain ontology is placed under the smeta sub-topc. There MAY be multiple sub-topics for any topic. The sub-topic MUST be lowercase with no separation or punctuation between words. Sub-topics MAY have multiple ontologies.

The meta sub-topic area MUST be used for ontologies consisting solely of annotations properties. For example:

• IRI:

• https://spec.industrialontologies.org/ontology/core/meta/AnnotationVocabulary/

• Version IRI:

• https://spec.industrialontologies.org/ontology/core/20210601/meta/AnnotationVocabulary/

Ontology

An ontology is a set of related ontological classes, properties, and axioms encoded in a specific representation, such as RDF/XML, Turtle, or CLIF. A given HTTP server delivers an ontology in a serialization using the HTTP/1.1 Accept header of the request. See Section 14 of IETF RFC 2616. The serialized representation is referred to as an ontology file.

Following the topic and sub-topic resource locations, the ontology name MUST be given without extension as follows:

• https://spec.industrialontologies.org/ontology/core/meta/AnnotationVocabulary/

• https://spec.industrialontologies.org/ontology/core/domainindependent/Stasis/

  • The Stasis ontology of the domainindependent sub-topic of the core topic

• https://spec.industrialontologies.org/ontology/core/domainindependent/Stasis/Stasis

  • Class Stasis in the Stasis ontology of the domainindependent sub-topic of the core topic.

• https://spec.industrialontologies.org/ontology/core/domainindependent/Stasis/triggers

  • Object property triggers in the Stasis ontology of the domain independent sub-topic of the core topic.

• https://spec.industrialontologies.org/ontology/supplychain/SupplyChainReferenceOntology/SupplyChainShippingProcess

  • Class SupplyChainShippingProcess of the SupplyChainReferenceOntology ontology of the supplychain topic.

The ontology name MUST be in Upper Camel Case, each word capitalized with no separation between words. All acronyms MUST be spelled out except when in the dictionary, like RADAR.

The ontology name MUST NOT have any extensions in the IRI. The following parts of the IRI, class and property names, MUST be separated from the file name by a forward slash / and the IRI MUST end with a forward slash /. owl:imports rdf:resource reference MUST use the IRI with a trailing /.

• <owl:imports rdf:resource="<https://spec.industrialontologies.org/ontology/core/domainindependent/Stasis/>"/>

Class Names

Class names MUST be given in Upper Camel Case, each word capitalized, and no separation or punctuation between words. As with the module names, no acronyms MUST NOT occur except those in the dictionary, such as RADAR.

• /ontology/supplychain/SupplyChainReferenceOntology/SupplyChainShippingProcess

The versioned forms are as follows:

• /ontology/supplychain/20210621/SupplyChainReferenceOntology/SupplyChainShippingProcess

Property Names (Relations)

All property names MUST be in lower Camel Case, the first word lower case and each subsequent word capitalized with no separation or punctuation between words.

• /ontology/foundation/meta/AnnotationVocabulary/usageNote

• The versioned forms are as follows:

• /ontology/foundation/20210611/meta/AnnotationVocabulary/usageNote

Object Properties

All object property names MUST be verbs or a verb phrase. For example:

• hasParticipant

• participatesIn

Data Properties

A data property MUST be a verb phrase starting with is for boolean (true/false) or has for any other data type. The data property SHOULD end with Value.

Examples:

• hasTagValue

• hasDateValue

• isTransferable

Annotation properties

Must follow property capitalization rules and MUST be placed in the meta sub-topic area, as follows.

• .../ontology/foundation/20210611/meta/AnnotationVocabulary/usageNote

• .../ontology/foundation/20210611/meta/AnnotationVocabulary/adaptedFrom

TOB Vote: