Commons Ontology Library / Scope

OMG GraphArch rendering of the Commons 1.3 formal specification

Scope

OMG GraphArch rendering of the Commons 1.3 formal specification

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

1. Scope§

1.1 Introduction§

The Commons Ontology Library is designed to provide a useful set of modeling constructs that are reusable in different modeling and data deployment environments with minimal commitments. It is intended to be extensible such that new ontologies and potentially other models (for example, UML models corresponding to the ontologies) can be added as cross-domain requirements present themselves. These requirements may come from other OMG standards efforts or potentially from external users of the library, for example, the Industrial Ontology Foundry (IOF) manufacturing community, EDM Council projects with the Pistoia Alliance IDMP pharmaceutical community, and others.

1.2 Criteria for Inclusion§

Ontologies and other models will be identified primarily by drawing on other work, although care must be taken to ensure that intellectual property and other legal rights are addressed, and that standardization is desired by the user community. Oversight for curation of the library will be managed by the Commons revision task force (RTF) via the normal OMG process. The minimum criteria identified to date for inclusion include: (1) the need for the same set of concepts with the same semantics across multiple specifications and/or domain areas, such as manufacturing, finance and/or retail, (2) a clear set of use cases, competency questions, and test cases that can help limit the scope for a given ontology and provide the basis for regression testing, (3) reusability in their own right with minimal dependencies on other ontologies with the possible exception of other Commons ontologies, and (4) that the ontologies meet minimal requirements for metadata, logical consistency, and serialization (e.g., RDF/XML and Turtle serialized OWL, for OWL ontologies).

1.3 Overview§

The Commons Ontology Library of ontologies specified herein covers:

(1) Annotations

  • A reusable set of declarations for commonly used annotation properties from the Dublin Core Metadata Initiative (DCMI) Terms1 and the Simple Knowledge Organization System (SKOS)2, so that these vocabularies can be reused without importing either.
  • Additional annotation properties that provide metadata for documentation that is not explicitly available in either Dublin Core or SKOS.

(2) Collections:

  • Collections – commonly used concepts for arrangements and schemes for organizing information and collections of things, such as structured collections that may be organized according to some scheme and related very high-level mereology relations to enable association of things with such collections and schemes.
  • Structured Collections – an extension to collections that defines chronologically and indexed collections as well as sets and lists.

(3) Roles and Compositions:

  • The notion of a composition that can be used, for example to relate something, such as a product or recipe, to its ingredients or constituents, and/or to the roles such constituents play in the composition, and optionally to some context, such as a jurisdiction, in which the composition is relevant.
  • The concept of a role, supporting the representation of participants in compositions, situations, and relationships, as well as properties that link the role to something that plays that role, that links something to a role it has (e.g., a role that is pertinent to a situation or composition), as well as inverses that enable role traversal in a graph.

(4) Designations:

  • Designators - commonly used concepts for naming, derived in part from the patterns defined in ISO 1087 for terminology work and ISO 11179-3, Metadata Registries. The top-level designators ontology includes several very high-level semiotic relationships, including defines, describes, and denotes for associating designators with the concepts they reference.
  • Contextual Designators – an extension to the designators ontology to incorporate applicable dates and times and facilitate the inclusion of other context that is commonly needed, derived in part from the patterns defined in ISO 11179-3, Metadata Registries.
  • Codes and Code Sets - commonly used concepts for describing codes, including standardized codes such as ISO language, country, and other code sets, the North American Industry Classification System (NAICS) codes, and custom code sets that many organizations develop for various purposes, derived from the patterns specified in ISO 11179-3, Metadata Registries.
  • Identifiers - commonly used concepts for describing identifiers and the identification schemes that define them, such as various national and international identifiers for legal entities, financial instruments, and the like, derived from the patterns specified in ISO 11179-3, Metadata Registries.
  • Contextual Identifiers – an extension to the contextual designators and identifiers ontologies covering concepts for describing more complex identifiers, including those that apply for some period of time as well as those that are structured and include other codes or identifiers.
  • Languages – High-level concepts defining languages, including natural as well as formal languages, based on a number of standards including but not limited to ISO 639 as well as the language element of the Language Tag specified in BCP 47 (RFC 4646, RFC 4647). The concept of a language is included here to normalize definitions across the Application Programming Interfaces for Knowledge Platforms (API4KP), Distributed Ontology, Model, and Specification Language (DOL), Languages, Countries, and Codes (LCC), and Multiple Vocabulary Facility (MVF) standards to support interoperability, and for use in other OMG and external ontology projects.

(5) Classifiers:

  • Abstract concepts for representation of classification schemes that enable the classification of arbitrary concepts into hierarchies (or partial orders) for use in other ontologies, derived in part from the patterns defined in ISO 1087-1 for terminology work and ISO 11179-3, Metadata Registries.

(6) Locations:

  • Locations – Very high-level definitions of geographic region and geopolitical entity related concepts, including, but not limited to, countries, sub-country regions such as states and provinces, and municipalities, derived from a combination of ISO 3166, the UN M49 Region codes, Geonames, and other sources.
  • Sites and Facilities – High-level concepts related to facilities, both virtual and physical, including sites that provide the context for various facilities.

(7) Parties :

  • Parties and Situations – The concepts of agent, agent role, party, party role, and situation, which is a state of affairs or reified relationship that holds for some period of time, including lattice relations between the concepts driven by property chains that can be used to access the lattice from any perspective in the resulting graph.
  • Organizations – an extension of the parties and situations and locations ontologies that defines organization, legal entity, organization membership, and related identifiers, as well as service and service provider, designed to enable mapping to other organization ontologies such as the W3C Organizations ontology.
  • Business Authorizations – the concept of authorization from a business perspective, rather than security or access control viewpoint, as a situation or state of affairs, including related parties. This extension is needed to cover a range of requirements from retail, for example for defining digital signatures, as well as for banking and pharmaceuticals, for defining marketing and manufacturing authorizations for medicines.
  • Registration Authorities – a small ontology that extends organizations defining registration authorities, registrars, registration-specific identifiers and related identification schemes, modeled after patterns included in ISO/IEC 11179-3.
  • Regulatory Agencies – an extension of locations and organizations that specifies concepts including regulatory agencies, also known as regulatory authorities or regulators, and their jurisdictions.

(8) Quantities and Units:

  • Documents - a small documents ontology that can be mapped to others, such as FRBR, to support representation of references and reference documents required for documenting certain units.
  • Quantities and Units - an ontology defining scalar quantities and units, corresponding to the quantities and units library in SysML v2 covering the key concepts required for most domains, including but not limited to measurement scales, quantity kinds, dimensions, scalar quantities and scalar units.

(9) Time:

  • Dates and Times - commonly used temporal concepts that cover those most frequently needed across domains, with a focus on terminology that is used in business applications. It is designed to be mappable to other date and time ontologies and specifications, such as the W3C Time Ontology in OWL3, certain temporal elements in ISO Basic Formal Ontology4, time concepts defined in schema.org, and the OMG Date Time Vocabulary (DTV) specification, without the corresponding overhead, or in some cases, issues. The concepts were originally derived from a number of date and time standards including ISO 8601:2004 Representation of Dates and Times.
  • Mapping Dates and Times to OWL Time – an extension to the dates and times ontology to map it to the widely used W3C Time Ontology in OWL recommendation.

(10) Text Datatype:

  • A custom datatype that combines language tagged and plain string values. This text datatype is useful in cases where it is not clear whether string values will be tagged or not, but where it is anticipated that multilingual strings might be appropriate.

Each of these ontologies is defined below.

1.4 Metadata§

Annotations on concepts, properties, and individuals in this specification follow the general policies recommended by the OMG Architecture Board, including the use of (1) the Dublin Core Metadata Terms [Dublin Core], (2) the Simple Knowledge Organization System (SKOS) [SKOS], and (3) the annotation vocabulary included in the Commons Ontology Library. Every element in the ontologies defined in the Commons Ontology Library must have a label and definition, and in many cases, the source for the definitions, such as an ISO or other OMG standard, is referenced. Examples are also included as appropriate, along with other notes that may assist users in understanding and reusing the ontology.

1

Dublin Core Metadata Initiative (DCMI), DCMI Metadata Terms -- https://www.dublincore.org/specifications/dublin-core/dcmi-terms/

2

Simple Knowledge Organization System (SKOS) -- https://www.w3.org/TR/2009/REC-skos-reference-20090818/

Document provenance

Search this specification