Additional Information
OMG GraphArch rendering of the Commons 1.3 formal specification
- Copyright © 2024-2025, Adaptive Analytics, Inc.
- Copyright © 2022-2025, agnos.ai U.K. Ltd.
- Copyright © 2024-2025, Airbus Group
- Copyright © 2024-2025, Boeing
- Copyright © 2024-2025, Dassault Systèmes
- Copyright © 2024-2025, DEKonsult
- Copyright © 2022-2026, EDM Council, Inc. d/b/a EDM Association
- Copyright © 2024-2025, 88Solutions
- Copyright © 2022-2025, Federated Knowledge, LLC
- Copyright © 2024-2025, GfSE e.V.
- Copyright © 2024-2025, Mayo Clinic
- Copyright © 2022-2025, OntoAge
- Copyright © 2024-2025, Ontogenesis Solutions, LLC
- Copyright © 2023-2025, Pistoia Alliance
- Copyright © 2024-2025, ProSTEP iViP Association
- Copyright © 2024-2025, Raytheon Technologies
- Copyright © 2022, QuoteWell, Inc.
- Copyright © 2024-2025, Sparx Systems Pty Ltd
- Copyright © 2022-2025, Stardog Union
- Copyright © 2022-2025, Thematix Partners LLC
- Copyright © 2022-2025, University of North Florida
- Copyright © 2022-2025, Working Ontologist
- Copyright © 2022-2026, Object Management Group, Inc.
USE OF SPECIFICATION – TERMS, CONDITIONS & NOTICES
The material in this document details an Object Management Group specification in accordance with the terms, conditions and notices set forth below. This document does not represent a commitment to implement any portion of this specification in any company's products. The information contained in this document is subject to change without notice.
LICENSES
The companies listed above have granted to the Object Management Group, Inc. (OMG) a nonexclusive, royalty-free, paid up, worldwide license to copy and distribute this document and to modify this document and distribute copies of the modified version. Each of the copyright holders listed above has agreed that no person shall be deemed to have infringed the copyright in the included material of any such copyright holder by reason of having used the specification set forth herein or having conformed any computer software to the specification.
Subject to all of the terms and conditions below, the owners of the copyright in this specification hereby grant you a fully-paid up, non-exclusive, nontransferable, perpetual, worldwide license (without the right to sublicense), to use this specification to create and distribute software and special purpose specifications that are based upon this specification, and to use, copy, and distribute this specification as provided under the Copyright Act; provided that: (1) both the copyright notice identified above and this permission notice appear on any copies of this specification; (2) the use of the specifications is for informational purposes and will not be copied or posted on any network computer or broadcast in any media and will not be otherwise resold or transferred for commercial purposes; and (3) no modifications are made to this specification. This limited permission automatically terminates without notice if you breach any of these terms or conditions. Upon termination, you will destroy immediately any copies of the specifications in your possession or control.
PATENTS
The attention of adopters is directed to the possibility that compliance with or adoption of OMG specifications may require use of an invention covered by patent rights. OMG shall not be responsible for identifying patents for which a license may be required by any OMG specification, or for conducting legal inquiries into the legal validity or scope of those patents that are brought to its attention. OMG specifications are prospective and advisory only. Prospective users are responsible for protecting themselves against liability for infringement of patents.
GENERAL USE RESTRICTIONS
Any unauthorized use of this specification may violate copyright laws, trademark laws, and communications regulations and statutes. This document contains information which is protected by copyright. All Rights Reserved. No part of this work covered by copyright herein may be reproduced or used in any form or by any means--graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval systems--without permission of the copyright owner.
DISCLAIMER OF WARRANTY
WHILE THIS PUBLICATION IS BELIEVED TO BE ACCURATE, IT IS PROVIDED "AS IS" AND MAY CONTAIN ERRORS OR MISPRINTS. THE OBJECT MANAGEMENT GROUP AND THE COMPANIES LISTED ABOVE MAKE NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH REGARD TO THIS PUBLICATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF TITLE OR OWNERSHIP, IMPLIED WARRANTY OF MERCHANTABILITY OR WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE OR USE. IN NO EVENT SHALL THE OBJECT MANAGEMENT GROUP OR ANY OF THE COMPANIES LISTED ABOVE BE LIABLE FOR ERRORS CONTAINED HEREIN OR FOR DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, RELIANCE OR COVER DAMAGES, INCLUDING LOSS OF PROFITS, REVENUE, DATA OR USE, INCURRED BY ANY USER OR ANY THIRD PARTY IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
The entire risk as to the quality and performance of software developed using this specification is borne by you. This disclaimer of warranty constitutes an essential part of the license granted to you to use this specification.
RESTRICTED RIGHTS LEGEND
Use, duplication or disclosure by the U.S. Government is subject to the restrictions set forth in subparagraph (c) (1) (ii) of The Rights in Technical Data and Computer Software Clause at DFARS 252.227-7013 or in subparagraph (c)(1) and (2) of the Commercial Computer Software - Restricted Rights clauses at 48 C.F.R. 52.227-19 or as specified in 48 C.F.R. 227-7202-2 of the DoD F.A.R. Supplement and its successors, or as specified in 48 C.F.R. 12.212 of the Federal Acquisition Regulations and its successors, as applicable. The specification copyright owners are as indicated above and may be contacted through the Object Management Group, 9C Medway Road, PMB 274, Milford, MA 01757, U.S.A.
TRADEMARKS
CORBA®, CORBA logos®, FIBO®, Financial Industry Business Ontology®, FINANCIAL INSTRUMENT GLOBAL IDENTIFIER®, IIOP®, IMM®, Model Driven Architecture®, MDA®, Object Management Group®, OMG®, OMG Logo®, SoaML®, SOAML®, SysML®, UAF®, Unified Modeling Language®, UML®, UML Cube Logo®, VSIPL®, and XMI® are registered trademarks of the Object Management Group, Inc.
For a complete list of trademarks, see: https://www.omg.org/legal/tm_list.htm. All other products or company names mentioned are used for identification purposes only, and may be trademarks of their respective owners.
COMPLIANCE
The copyright holders listed above acknowledge that the Object Management Group (acting itself or through its designees) is and shall at all times be the sole entity that may authorize developers, suppliers and sellers of computer software to use certification marks, trademarks or other special designations to indicate compliance with these materials.
Software developed under the terms of this license may claim compliance or conformance with this specification if and only if the software compliance is of a nature fully matching the applicable compliance points as stated in the specification. Software developed only partially matching the applicable compliance points may claim only that the software was based on this specification but may not claim compliance or conformance with this specification. In the event that testing suites are implemented or approved by Object Management Group, Inc., software developed using this specification may claim compliance or conformance with the specification only if the software satisfactorily completes the testing suites.
OMG’s Issue Reporting Procedure
All OMG specifications are subject to continuous review and improvement. As part of this process, we encourage readers to report any ambiguities, inconsistencies, or inaccuracies they may find by completing the Issue Reporting Form listed on the main web page https://www.omg.org, under Specifications, Report a Bug/Issue (https://issues.omg.org/issues/create-new-issue).
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.
| Construct | Description | Notation |
|---|---|---|
| Boolean Connectives and Enumeration | ||
| intersection | The intersection of two classes consists of exactly those individuals which are instances of both classes. | C∩D |
| union | The union of two classes contains every individual which is contained in at least one of these classes. | C∪D |
| enumeration | An enumeration defines a class by enumerating all its instances. | oneOf (i1, i2, i3, … in) |
| Property Restrictions | ||
| universal quantification | Universal 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 quantification | Existential 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 value | Individual 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 cardinality | Cardinality (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 cardinality | Maximum 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 cardinality | Minimum 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 classes | Two classes are considered equivalent if they contain exactly the same individuals. | ≡C |
| disjoint classes | Disjointness means that membership in one class specifically excludes membership in another. | ¬C |
| Property Axioms | ||
| complex role inclusions | Role 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).