Commons Ontology Library / Additional Information

OMG GraphArch rendering of the Commons 1.3 formal specification

Additional Information

OMG GraphArch rendering of the Commons 1.3 formal specification

USE OF SPECIFICATION – TERMS, CONDITIONS & NOTICES
OMG’s Issue Reporting Procedure

1. Additional Information§

1.1 Changes to Other OMG Specifications§

None.

1.2 Acknowledgments§

The following organization submitted this specification:

  • Thematix Partners LLC

The following companies and organizations are supporters of this specification:

  • 88solutions
  • Accurids GmbH
  • Adaptive, Inc.
  • agnos.ai U.K. Ltd
  • Airbus Group
  • Boeing
  • Dassault Systèmes
  • DEKonsult
  • EDM Council, Inc.
  • Federated Knowledge, LLC
  • Jackrabbit Consulting
  • Mayo Clinic
  • Micro Focus International Plc
  • Model Driven Solutions
  • OntoAge
  • Ontogenesis Solutions, LLC
  • OpenText Inc.
  • Pharmalex GmbH
  • Pistoia Alliance, Inc.
  • QuoteWell, Inc.
  • Raytheon Technologies (RTX)
  • Rensselaer Polytechnic Institute
  • Sparx Systems Pty Ltd
  • U. S. National Institute of Standards and Technology (NIST)
  • Wells Fargo Bank, N.A.
  • Working Ontologist

1.3 Intellectual Property Rights§

The Commons Ontology Library is available under the OMG’s Copyright and Non-Assertion Covenant (see https://www.omg.org/cgi-bin/doc.cgi?ipr for details). The individual ontologies are also licensed for use under the MIT open-source license agreement, available at https://opensource.org/licenses/MIT.

1.4 Application of the Commons Ontologies§

With respect to OMG standards, the ontologies included in the library are reused by the Multiple Vocabulary Facility (MVF) specification and an anticipated update of the Languages, Countries and Codes (LCC) specification. For LCC, they replace existing concepts that were needed for MVF derived from LCC. The ontologies are also used by the API4KP specification, the Financial Industry Business Ontology (FIBO), by the emerging Retail Industry Ontology (RIO), and by the Robotics Service Ontology specification.

In addition to their use in OMG standards, initiatives such as the Industrial Ontology Foundry (IOF), sponsored by the U.S. National Institute of Standards and Technology and a joint effort of the Pistoia Alliance and EDM Council for ontologies that facilitate identification of medicinal products (IDMP).

1.5 Notation§

The diagrams included herein are ODM-compliant UML diagrams. In other words, they conform to the UML Profiles for RDF and OWL specified in the OMG’s Ontology Definition Metamodel [ODM] Specification. This includes the set of UML stereotypes and graphical notation used in the diagrams provided.

The color scheme employed in these diagrams includes:

  • Basic OWL Classes: white for classes defined within the current (local) ontology, amber for classes defined within an imported (referenced) ontology
  • OWL Restriction Classes and other Class Expressions (unions, intersection, complements): green
  • OWL Object Properties: blue
  • OWL Data Properties: dark gray
  • OWL Datatypes: pink
  • OWL Individuals: light gray

These colors are provided for clarification purposes only and are non-normative.

For the library there is an “about” file, which provides metadata about the library, described below in tabular form. The ontologies themselves are documented as ODM-compliant UML models, aside from the “about” file, annotation vocabulary, and mapping ontology. Every ontology is expressed in RDF/XML-serialized OWL and Turtle-serialized OWL [OWL 2].

The notation used to represent description logic expressions (i.e., the expressions in the Parent columns in class tables containing ontology details) is consistent with the notation defined in the Description Logic Handbook [DL Handbook]. The notation used in this specification, representing a subset of OWL 2, is described in Table 6-1, below.

Description Logic Expressions Notation
ConstructDescriptionNotation
Boolean Connectives and Enumeration
intersectionThe intersection of two classes consists of exactly those individuals which are instances of both classes.C∩D
unionThe union of two classes contains every individual which is contained in at least one of these classes.C∪D
enumerationAn enumeration defines a class by enumerating all its instances.oneOf (i1, i2, i3, … in)
Property Restrictions
universal quantificationUniversal quantification is used to specify a class of individuals for which all related individuals must be instances of a given class (i.e., allValuesFrom in OWL).∀R.C, where R is the relation (property) and C is the class that constrains all values for related individuals
existential quantificationExistential quantification is used to specify a class as the set of all individuals that are connected via a particular property to at least one individual which is an instance of a certain class (i.e., someValuesFrom in OWL).∃R.C, where R is the relation (property) and C is the class that constrains some values of related individuals
individual valueIndividual value restrictions are used to specify classes of individuals that are related to one particular individual (i.e., hasValue in OWL).R.I, where R is the relation (property) and I is the individual
exact cardinalityCardinality (number) restrictions specify classes by restricting the cardinality on the sets of fillers for roles (relationships, or properties in OWL). Exact cardinality restrictions restrict the cardinality of possible fillers to exactly the number specified.= n R (for unqualified restrictions)
= n R.C (for qualified restrictions, i.e., including onClass or on DataRange)
maximum cardinalityMaximum cardinality restrictions restrict the cardinality of possible fillers to at most the number specified (inclusive).≤ n R (for unqualified restrictions)
≤ n R.C (for qualified restrictions)
minimum cardinalityMinimum cardinality restrictions restrict the cardinality of possible fillers to at least the number specified (inclusive).≥ n R (for unqualified restrictions)
≥ n R.C (for qualified restrictions)
Class Axioms
equivalent classesTwo classes are considered equivalent if they contain exactly the same individuals.≡C
disjoint classesDisjointness means that membership in one class specifically excludes membership in another.¬C
Property Axioms
complex role inclusionsRole inclusions allow [object] properties to be chained together in a sequence that is a subproperty of a higher-level property.R○R

Note that in the case of complex restrictions, where there are nested elements in parentheses, the “dot notation” used as a separator between a property and the role filler is replaced with the embedded parenthetical filler definition. A “role” from a description logic perspective is essentially a property in OWL, and the role “filler” is the class or individual that provides the value for that role in a given axiom (i.e., in a restriction or other logic expression).

Document provenance

Search this specification