Versions Compared

Key

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

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

...

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 provides the ontology organization rules for topics, sub-topics, and modules in publication (a reference to topic/domain structure document). All content within a topic MUST be released with a common version. The version of one topic does not constrain another topic’s version.

...

A module MUST represent an ontology resource without a specific representation. A file is a module encoded in a specific representation. A given HTTPS HTTP server delivers an ontology in multiple representations, for example, OWL XML, RDF Schema, Turtle, or JSON-LD. In an HTTPS request, the desired representations are specified in the HTTPS header. The server evaluates the HTTPS header and delivers the ontology given the available representationsSee Section 14 of IETF RFC 2616 for HTTP/1.1 Accept header use and HTTP/1.1 server requirements.

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

...

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

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

...

Old notes for reference…

IRI Structural Rules in the following order

  • Authority: www.industrialontologies.org

  • Top: /ontology

  • Topic areas are lowercase with no punctuation or separation:

    • /supplychain

    • /foundation

  • Versioned IRI:

    • Release date after highest level topic area

    • Date format: YYYYMMDD

    • /supplychain/20210601

    • /foundation/20210601/meta

  • File-name Upper Camel Case with no punctuation: AnnotationVocabulary

    • Uppercase first letter of each word, no separation

    • All acronyms are spelled out

      • Exceptions like RADAR, words appearing in the dictionary

  • Class and properties separated from path with a /

    • /ontology/foundation/meta/AnnotationVocabulary/usageNote

  • Class name Upper Camel Case:

    • Uppercase first letter of each word, no separation

    • All acronyms are spelled out

      • Exceptions like RADAR, words appearing in the dictionary

  • Object property Lower Camel Case:

    • Lowercase first letter, uppercase each following word

    • All property names MUST be verb or verb phrase

    • hasParticipant

  • Data properties and annotation names Lower Camel Case

    • Lowercase first letter, uppercase each following word

    • Verb phrase starting with has

    • hasTag

    • hasDateValue

  • Annotation properties

    • Lowercase first letter, uppercase each following word

    • usageNote

    • adaptedFrom

  • Versioned and unversioned forms MUST be provided.

Examples

  • Unversioned: /ontology/foundation/meta/AnnotationVocabulary/usageNote

  • Versioned: /ontology/foundation/20210601/meta/AnnotationVocabulary/usageNote

  • /ontology/supplychain/

...