After additional review, RTF members suggested that a better name for the ontology would be roles and compositions. Other feedback identified a typo, suggested that we add the notion of independent identity in the definition of composition for clarification, and remove the functional axiom on the property isPlayedBy, which might overly constrain its utility.

Rename the new composites ontology and revise definitions per additional RTF discussion

The resolution to this issue depends on the resolution to COMMONS-11-4, adding a new Composites ontology, and revises the results of that resolution, including renaming and moving the sections in the specification as well as renaming the ontology, per further RTF discussion.

Note that the change barred version of the document does not reflect the original sections (i.e., adding and then deleting 8.5, for ease of managing the resulting document in LibreOffice.

In pharmaceuticals and other industries, products are often composed of other things. The 'recipe' for manufacturing a product includes various ingredients, which are roles that substances, components. or other things take on in the context of that product.

Further, there are cases where the composition of some product is context specific. Product documentation may be jurisdictionally defined due to regulatory constraints, for example. The representation of some ingredients in certain pharmaceutical products, including the way these elements are described on packaging, is jurisdiction specific, even thought the product itself has exactly the same composition via exactly the same manufacturing processes world wide.

A general pattern for this kind of composition would be quite useful for a number of domain areas and is a good candidate for inclusions in the Commons library.

Augment the Commons library with an ontology defining compositions and roles

Introduce a new ontology representing composition and role as classes and relationships between them for use in addressing the requirements outlined in the issue description

Currently we have an explicit date period, but not explicit time period, which is needed for PPMN, among other processes. This is also required for Robotics.

Added a number of properties to the Dates and Times ontology related to start and end time

The resolution to this issue adds two classes to the ontology: TimePeriod and ExplicitTimePeriod, and a number of properties, including a general purpose hasTime property as well as hasDateOfIssuance, hasEnd, hasEndTime, hasStart, hasStartTime, and hasTimePeriod, per request of two task forces, Robotics Service Ontology (RoSO) and Pedigree and Provenance Metamodel and Notation (PPMN).

Note: in the text revisions, under item 5, there are no sections labeled i and n because solitaire turned them into odd emojis.

A preliminary quantities and units ontology was developed for FIBO for use with commodities. Several other groups at OMG need this ontology, as do external users of the Commons library. The ontology should be mappable to the SysML v2 library so that we can generate the individuals in that library for use in knowledge graph applications. It should also be consistent, to the degree possible, with the latest changes to the VIM, with BIPM requirements, and with ISO 11240 for use in the pharmaceutical domain.

There is a dependency in the quantities and units ontology on a small documents ontology, to provide the reference documentation for certain units. This ontology is relatively small, however, and can easily be mapped to other ontologies defining documents.

Introduce two new ontologies, a documents ontology and a quantities and units ontology that depends on it

Several OMG task forces and other external industry groups in pharmaceuticals, manufacturing, finance and others, there is a widely recognized need for a well-designed ontology supporting quantities and units. While a number of ontologies exist that claim to fill this gap, few are well designed and some have moved away from OWL in order to meet other demands. Within OMG, the healthcare, finance, robotics, and retail task forces all have requirements for a quantities and units ontology. Given the latest advances in SysML, such an ontology should align well with the library of quantities and units in SysML v2 so that the equivalent reference content in RDF/OWL can be automatically generated.

The ontologies included in this resolution fill that need, although they are limited to scalar quantities at this juncture. The RTF intends to create a new arrays / vectors / tensors ontology and a companion quantities and units extension to support tensor and vector quantities over the coming months. Most applications do not need that level of sophistication however, and thus the RTF has determined that submission of the scalar version should happen sooner than later to fulfill requirements of other task forces.

A situation is a complex, typically time-bound, setting, state of being, or relationship that is relatively stable for some period of time. An ontology defining such situations, including the complex property chains that link the actors and undergoers in such situations to the roles that they play is essential in finance, pharma, retail, robotics, and many other industries.

A well-tested ontology that describes these patterns would be a useful addition to the Commons library. In addition, this ontology (and the new composition ontology on which it depends) is urgently needed for the Robotics Service Ontology (RoSO), whose planned revised submission is planned for September 2023.

Note that the resolution of this issue requires the ontology added under COMMONS-11-4.

Augment the Commons library with an ontology defining parties and situations

The parties and situations ontology defines concepts including agent and agent role, party and party role, situation - which is a state of affairs / reified relationship that holds for some period of time, and other related roles and relations that are commonly required across many domains.

Note that the resolution to this issue depends on resolutions to COMMONS-11-1, COMMONS-11-3, and COMMONS-11-8 have been applied first, and that sections have been renumbered and organized alphabetically by ontology name prior to applying this resolution.

This is needed for representation of tensor and vector quantities for the quantities and units ontology, and for representation of certain machine learning algorithms, among other requirements.

Development of an ontology for Arrays, Tensors and Vectors

This issue will take more time and thoughtful effort to resolve, and the task force agreed to defer it as well as this aspect of quantities and units to the next revision.The new quantities and units ontology supports scalar quantities, which is what most users, including robotics, retail, and finance, need. The tensor and vector aspects are primarily used in specific disciplines of engineering.