An organization ontology that covers formal organizations, legal entities, and organization membership is essential for the ongoing retail ontology effort, for development of an ontology for the emerging PPMN standard, and others.

Note that representation of domicile requires the concept of a geopolitical entity, which the task force agrees belongs in a more general locations ontology. Thus, a locations ontology is also needed as part of a resolution for this issue.

Add new locations and organizations ontologies to the Commons library

The resolution to this issue affects both the specification document and machine readable files. It adds one property to the designators ontology and incorporates two additional ontologies, one describing locations, which is needed for several processes: the Retail Industry Ontology, the RoSO ontology for robotics, a planned revision to the Multiple Vocabulary Facility (MVF), and a planned update to LCC, as well as external efforts, and an organizations ontology, also needed for the RIO ontology and external work.

1. County and FederalCapitalArea should be subclasses of CountrySubdivision

2. FederalState should have synonyms rather than this in the note "variously referred to as a state, province or canton".

3. Several annotations on geographic region identifier and a few other concepts need clarification

Cleaned up a few issues identified in the locations ontology during review

These include adjusting the class hierarchy for consistent representation of country subdivisions as well as minor adjustments to definitions

Rather than classifying 'something' an aspect should classify a set or group of things - at a higher metalevel than 'quality' in BFO, for example. This impacts the Classifiers ontology, in which Aspect is defined.

Clarified the definition of the Aspect class

Revised metadata to be current and revised the definition from

'characteristic or feature that can be used to dimensionalize, filter, or subset something'

to

'characteristic or feature that can be used to dimensionalize, filter, or a class, collection, or set of things'

Requirements range from retail to finance and health care, where certain constructs, such as identifiers, are registered with specific authorities, and understanding who has registered a particular identifier is essential to the definition of that identifier.

Coverage should include definitions for registration authority, registrar (which could be a person or organization, and may or may not be part of the same organization as the authority), a registered identifier, which should be modeled as a contextual identifier, the registry and some registration scheme.

Note that the resolution to this issue depends on Commons-1.2-8, including properties in the organizations ontology.

Add a new ontology covering registration authorities to the Commons library

Requirements range from retail to finance, government, pharmaceuticals, and health care, where certain constructs, such as identifiers, are registered with specific authorities, and understanding who has registered a particular identifier is essential to the definition of that identifier.

The OMG's FIGI standard, for example, allows for a single registration authority (RA), which is Bloomberg LP, but enables multiple registrars to act on behalf of the RA. Today registrars include Bloomberg LP as well as Kaiko.

Coverage should include definitions for registration authority, registrar (which could be a person or organization, and may or may not be part of the same organization as the authority), a registered identifier, which should be modeled as a contextual identifier, the registry and some registration scheme.

Note that the resolution to this issue depends on the resolutions in Ballot #3, Commons-1.2-8, including properties in the organizations ontology.

One example of this is hasNumericValue. It is currently declared to be functional, but could be the parent property for several properties of some class. In this case, the resulting ontology could be logically inconsistent if the values are not the same (and even if they are, by coincidence, that's still a problem). Other properties that are also declared as functional should be reviewed for the same issue.

Revised the quantities and units ontology to remove unnecessary constraints

1. Revised the quantities and units ontology to remove functional declarations on a number of properties. These constraints caused reasoning errors when any of the properties, such as hasNumericValue, were used as the superproperty of more than one subproperty on the same class (concept).
2. Eliminated circular restrictions on system of quantities, system of units and added links back to the appropriate system from the quantity or unit
3. Revised the license to include the copyrights and full text, added Airbus, Ontogenesis Solutions

This would assist in alignment with SysML v2, but more importantly allows alignment of some quantity value with a more general measurement reference rather than only a measurement unit, for representation of IU in pharma, for example.

Add measurement reference to the quantities and units ontology

The resolution to this issue involves:
1. Adding a new measurement reference class, which is a subclass of the union of measurement procedure, measurement unit, and reference material, though not equivalent because there may be other related concepts
2. Adding / replacing the superclass for measurement procedure, measurement unit, and reference material with measurement reference as appropriate,
3. Adding measurement reference as the parent for measurement scale, corresponding with SysML v2, and
4. Adding a new property, has measurement reference, and making has measurement unit a subproperty of has measurement reference

Note that the metadata required for this revision has been applied to the resolution for Commons12-5 and thus the resolution to this issue depends on the resolution to Commons12-5.

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.

Significant research is required to complete this ontology and related work on tensor and vector quantities

The work to complete this resolution requires testing with the SysML v2 library of quantities and units, and may ultimately result in additional changes to the approach taken to represent quantities in general. This has been a significant effort to date, including a number of contributors who created the corresponding artifacts for SysML v2. We believe more care needs to be taken to test any resulting ontology and reference library, which is planned over the coming months.

Because some of the other work on the Commons 1.2 specification was more urgently needed, we elected to defer this until the Commons 1.3 RTF.

There is a gap in the quantities and units ontology whereby we cannot represent counts of things, which do not necessarily have units, nor can we properly represent ratio values, which may involve scalar quantity values that do not have units. There is also a challenge in representing ratio values more generally, since there is no numeric value representing the ratio on the class.

The issue of unitless measures should be addressed in the context of the work we are doing with tensors and vectors

There is ongoing good work on an ontology for tensors and vectors, with planned revisions for tensor and vector quantities planned for the Commons 1.3 RTF due to the amount of work involved. This issue should be resolved in conjunction with that one in case there are relevant related revisions.

These include tax authorities for retail applications, banking regulators in finance, other regulators for manufacturing and engineering applications. A small ontology that supports the definition of regulatory authorities, including their jurisdiction, would be quite useful for these kinds of applications and is needed for the emerging retail industry ontology.

Augment the Commons library with an ontology for regulatory agencies to support retail, manufacturing, and other applications

The primary use cases for regulatory agencies in retail are for tax authorities, but for retail pharmaceuticals, there is also a requirement to be able to represent medicines regulatory agencies and related governmental stakeholder, for example. A small ontology that supports the definition of regulatory authorities, including their jurisdiction, would be quite useful for these kinds of applications and is needed for the emerging retail industry ontology.

Note that the resolution to this issue depends on the resolutions in Ballot #3, Commons-1.2-8, including properties in the organizations ontology.

Definitions of certain kinds of structured collections, including sets, lists, and some ordered collections are not well defined in OWL. A small ontology that includes definitions for these elements is needed for retail and other OMG work in progress.

Augment the Commons library with a small ontology for structured collections

Definitions of certain kinds of structured collections, including sets, lists, and some ordered collections are not well defined in OWL. Examples of ordered collections include chronologically ordered collections and indexed collections. A small ontology that includes definitions for these elements is needed for retail and other OMG work in progress.

Note that the resolution to this issue depends on the resolutions in Ballot #3, Commons-1.2-8, including properties in the organizations ontology.