Versions Compared

Old Version 2

changes.mady.by.user William Sobel

Saved on

compared with

New Version Current

changes.mady.by.user William Sobel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Updated with new release Version IRI

Version History

Version

Date

Comment

Lead Editor

Contributors

1

 2021-06-18

First version

William Sobel

Evan Wallace tschneider Farhad Ameri Chris Will Elisa Kendall Ana Correia Serm Kulvatunyou

2

2022-10

Updated authority from purl to spec and changed version IRI to YYYYNN.

William Sobel

Evan Wallace tschneider Jim Logan Barry Smith (Unlicensed) Arkopaul Sarkar Farhad Ameri Chris Will Stephen Kahmann Elisa Kendall Ana Correia Serm Kulvatunyou Milos Drobnjakovic Pawel Garbacz Melissa Weller

Votes

Member

Vote

1

William Sobel

YES

2

Farhad Ameri

 YES

3

Elisa Kendall

 YES

4

Chris Will

 YES

5

Dusan Sormaz

 YES

6

Walter Terkaj

 

7

Melinda Hodkiewicz

 YES

8

Rebecca Siafaka

 

9

Dimitris Kiritsis

YES

10

Serm Kulvatunyou

YES

11

Evan Wallace

 YES

12

Hedi Karray

 YES

13

Hyunmin Cheong

 

14

Jinzhi Lu

 YES

15

Ana Correia

 YES

16

tschneider

 YES

With reservations:

View file
nameIOF-IRI_StructureAndFormat_2022-02-121022-010924_Reservations-Schneider.pdf

17

Peter Denno

 YES

18

Alexandru Todor

 

19

Thomas Hanke

 

20

Total

YES: 14, NO: 0, No Response: 5

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

...

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 purlspec.industrialontologies.org is used for illustrative purposes only. When decided, this document MUST be revised with the normative authority.

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

  • The protocol: https

  • The authority: spec.industrialontologies.org

  • The development authority: purldev.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 purlspec.industrialontologies.org unless it is not possible due to technical reasons. Otherwise, the authority may begin with an alternative such as purl.industrialontologies.org or onto.industrialontologies.org.

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://purlspec.industrialontologies.org/ontology/supplychain

  • The path component: /ontology/supplychain

...

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

  • The root part: /ontology

...

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://purlspec.industrialontologies.org/ontology/supplychain

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

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

...

IOF ontologies MUST provide a non-version IRI (referred to as the IRI) and version IRI in the RDF/XML serialized OWL XML 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). All sub-topics and modules within a topic MUST share a common version date and be released together. 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://purldev.industrialontologies.org/ontology/supplychain/2021062120220821/meta

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

Public Release IRI

The development 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 that are 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://purlspec.industrialontologies.org/ontology/supplychain/202202/meta

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

...

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

  • IRI:

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

  • Version IRI:

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

...

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

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

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

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

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

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

  • https://purlspec.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://purlspec.industrialontologies.org/ontology/supplychain/SupplyChainReferenceOntology/SupplyChainShippingProcess

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

...

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

...