1. OMG Mailing List
  2. Commons Ontology Library (Commons) 1.3 RTF

Open Issues

  • Issues not resolved
  • Name: cmns-rtf
  • Issues Count: 17

Issues Summary

Key Issue Reported Fixed Disposition Status
COMMONS13-14 Commons silently changes the semantics of dct:description Commons 1.2b1 open
COMMONS13-13 Annotation Vocabulary missing discussion of labeling policy Commons 1.2b1 open
COMMONS13-12 Annotation Vocabulary has incomplete definitions from SKOS Commons 1.2b1 open
COMMONS13-11 The documents ontology is missing the notion of a document part Commons 1.2b1 open
COMMONS13-10 Need to augment the locations ontology to cover sites and facilities, or create a new ontology for these concepts Commons 1.2b1 open
COMMONS13-2 The quantities and units ontology does not allow representation of unitless quantity values Commons 1.1b1 open
COMMONS12-2 The quantities and units ontology does not allow representation of unitless quantity values Commons 1.1b1 open
COMMONS13-1 Need an ontology representing multidimensional arrays COMMONS 1.0b2 open
COMMONS12-1 Need an ontology representing multidimensional arrays COMMONS 1.0b2 open
COMMONS12-5 Several properties in the quantities and units ontology are overly constrained MVF 1.0b2 open
COMMONS12-3 The quantities and units ontology is missing the concept of a measurement reference MVF 1.0b2 open
COMMONS12-9 Several OMG and external ontology efforts need to be able to talk about registration authorities MVF 1.0b2 open
COMMONS12-10 Several OMG and external processes need concepts for describing regulatory authorities MVF 1.0b2 open
COMMONS12-11 Certain OMG processes need additional structured collection definitions MVF 1.0b2 open
COMMONS12-13 Clean up a few issues with the Locations ontology Commons 1.1 open
COMMONS12-7 The definition of aspect needs refinement Commons 1.1 open
COMMONS12-8 Several processes and external projects need definitions for organizations, and related to that, locations MVF 1.0b2 open

Issues Descriptions

Commons silently changes the semantics of dct:description

  • Status: open  
  • Source: Adaptive ( Mr. Pete Rivett)
  • Summary:

    The definition in Commons Annotation Vocabulary is not a mere copy of what's in DCT with the documented addition of making it a owl:AnnotationProperty, but adds the triple :
    <rdfs:subPropertyOf rdf:resource="&skos;note"/>
    That may or may not be a good idea but it adds a dependency and it's a significant change that should be flagged.
    In fact, given that SKOS itself makes use of DCT, that makes for a somewhat undesirable circular dependency though not formally stated.

    If an aim is some sort of unification then maybe skos:definition should be made a subProperty of dct:description.

  • Reported: Commons 1.2b1 — Sun, 10 Nov 2024 20:28 GMT
  • Updated: Fri, 15 Nov 2024 19:49 GMT

Annotation Vocabulary missing discussion of labeling policy

  • Status: open  
  • Source: Adaptive ( Mr. Pete Rivett)
  • Summary:

    Little best practice or guidance is given in either the spec or the ontology. By the fact that they're included it seems that skos:prefLabel and skos:altLabel are recommended. However they're not actually used in this or any of the other Commons ontologies.
    Commons itself provides an alternative with its Designations ontology. And OMG provides a strong capability in MVF.

    Users of Commons should be warned about the anti-pattern use of rdfs:label as the primary in conjunction with skos:altLabel which makes it impossible, with reasoning enabled, to return only the primary (since skos:altLabel; is a subProperty of rdfs:label)

  • Reported: Commons 1.2b1 — Sun, 10 Nov 2024 20:08 GMT
  • Updated: Sun, 10 Nov 2024 20:42 GMT

Annotation Vocabulary has incomplete definitions from SKOS

  • Status: open  
  • Source: Adaptive ( Mr. Pete Rivett)
  • Summary:

    The definitions taken from SKOS seem altered and incomplete.
    For example here is the official definition from SKOS RDF file for altLabel. The Commons version changes the label (using "tag" instead of "label") and omits the comments, one of which is the important (informal) disjointness constraint, and example.

    <rdf:Description rdf:about="#altLabel">
    <rdfs:label xml:lang="en">alternative label</rdfs:label>
    <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2004/02/skos/core"/>
    <skos:definition xml:lang="en">An alternative lexical label for a resource.</skos:definition>
    <skos:example xml:lang="en">Acronyms, abbreviations, spelling variants, and irregular plural/singular forms may be included among the alternative labels for a concept. Mis-spelled terms are normally included as hidden labels (see skos:hiddenLabel).</skos:example>
    <!-- S10 -->
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#AnnotationProperty"/>
    <!-- S11 -->
    <rdfs:subPropertyOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#label"/>
    <!-- S12 (not formally stated) -->
    <rdfs:comment xml:lang="en">The range of skos:altLabel is the class of RDF plain literals.</rdfs:comment>
    <!-- S13 (not formally stated) -->
    <rdfs:comment xml:lang="en">skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties.</rdfs:comment>
    <!-- For non-OWL aware applications -->
    <rdf:type rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
    </rdf:Description>

  • Reported: Commons 1.2b1 — Sun, 10 Nov 2024 19:56 GMT
  • Updated: Sun, 10 Nov 2024 20:09 GMT

The documents ontology is missing the notion of a document part

  • Status: open  
  • Source: Thematix Partners LLC ( Mrs. Elisa F. Kendall)
  • Summary:

    SBRM and other OMG processes need to be able to connect documents to the components therein. RTF members have requested that we add these terms to the documents ontology to facilitate mapping to other document ontologies as well as for extension purposes.

  • Reported: Commons 1.2b1 — Sat, 2 Nov 2024 19:26 GMT
  • Updated: Sat, 2 Nov 2024 19:26 GMT

Need to augment the locations ontology to cover sites and facilities, or create a new ontology for these concepts

  • Status: open  
  • Source: Thematix Partners LLC ( Mrs. Elisa F. Kendall)
  • Summary:

    Several OMG members have requested a general ontology that includes sites and facilities, which are currently modeled in FIBO, primarily for lending and asset management purposes, but they are also needed for retail and manufacturing. The relationship between a site and a facility is many to many, and modeling them for manufacturing as well as retail, energy, military, and other domain areas can be tricky. Having the general pattern that can be extended by any domain area would be very useful for extension purposes.

  • Reported: Commons 1.2b1 — Sat, 2 Nov 2024 19:21 GMT
  • Updated: Sat, 2 Nov 2024 19:21 GMT

The quantities and units ontology does not allow representation of unitless quantity values

  • Status: open  
  • Source: Thematix Partners LLC ( Mrs. Elisa F. Kendall)
  • Summary:

    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.

  • Reported: Commons 1.1b1 — Tue, 13 Feb 2024 21:34 GMT
  • Updated: Wed, 25 Sep 2024 22:59 GMT

The quantities and units ontology does not allow representation of unitless quantity values

  • Status: open  
  • Source: Thematix Partners LLC ( Mrs. Elisa F. Kendall)
  • Summary:

    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.

  • Reported: Commons 1.1b1 — Tue, 13 Feb 2024 21:34 GMT
  • Updated: Wed, 25 Sep 2024 22:59 GMT

Need an ontology representing multidimensional arrays

  • Status: open  
  • Source: Thematix Partners LLC ( Mrs. Elisa F. Kendall)
  • Summary:

    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.

  • Reported: COMMONS 1.0b2 — Fri, 14 Jul 2023 18:03 GMT
  • Updated: Wed, 25 Sep 2024 22:59 GMT

Need an ontology representing multidimensional arrays

  • Status: open  
  • Source: Thematix Partners LLC ( Mrs. Elisa F. Kendall)
  • Summary:

    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.

  • Reported: COMMONS 1.0b2 — Fri, 14 Jul 2023 18:03 GMT
  • Updated: Wed, 25 Sep 2024 22:59 GMT

Several properties in the quantities and units ontology are overly constrained

  • Status: open  
  • Source: Thematix Partners LLC ( Mrs. Elisa F. Kendall)
  • Summary:

    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.

  • Reported: MVF 1.0b2 — Sun, 18 Feb 2024 02:25 GMT
  • Updated: Mon, 16 Sep 2024 14:39 GMT
  • Attachments:

The quantities and units ontology is missing the concept of a measurement reference

  • Status: open  
  • Source: Thematix Partners LLC ( Mrs. Elisa F. Kendall)
  • Summary:

    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.

  • Reported: MVF 1.0b2 — Tue, 13 Feb 2024 22:01 GMT
  • Updated: Mon, 16 Sep 2024 14:39 GMT
  • Attachments:

Several OMG and external ontology efforts need to be able to talk about registration authorities

  • Status: open  
  • Source: Thematix Partners LLC ( Mrs. Elisa F. Kendall)
  • Summary:

    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.

  • Reported: MVF 1.0b2 — Mon, 5 Aug 2024 17:47 GMT
  • Updated: Mon, 16 Sep 2024 14:39 GMT
  • Attachments:

Several OMG and external processes need concepts for describing regulatory authorities

  • Status: open  
  • Source: Thematix Partners LLC ( Mrs. Elisa F. Kendall)
  • Summary:

    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.

  • Reported: MVF 1.0b2 — Mon, 5 Aug 2024 22:23 GMT
  • Updated: Mon, 16 Sep 2024 14:39 GMT
  • Attachments:

Certain OMG processes need additional structured collection definitions

  • Status: open  
  • Source: Thematix Partners LLC ( Mrs. Elisa F. Kendall)
  • Summary:

    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.

  • Reported: MVF 1.0b2 — Tue, 6 Aug 2024 15:26 GMT
  • Updated: Mon, 16 Sep 2024 14:39 GMT
  • Attachments:

Clean up a few issues with the Locations ontology

  • Status: open  
  • Source: Thematix Partners LLC ( Mrs. Elisa F. Kendall)
  • Summary:

    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

  • Reported: Commons 1.1 — Fri, 16 Aug 2024 18:15 GMT
  • Updated: Mon, 16 Sep 2024 14:39 GMT
  • Attachments:

The definition of aspect needs refinement

  • Status: open  
  • Source: Thematix Partners LLC ( Mrs. Elisa F. Kendall)
  • Summary:

    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.

  • Reported: Commons 1.1 — Fri, 12 Apr 2024 18:40 GMT
  • Updated: Mon, 16 Sep 2024 14:39 GMT
  • Attachments:

Several processes and external projects need definitions for organizations, and related to that, locations

  • Status: open  
  • Source: Thematix Partners LLC ( Mrs. Elisa F. Kendall)
  • Summary:

    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.

  • Reported: MVF 1.0b2 — Sun, 4 Aug 2024 01:11 GMT
  • Updated: Mon, 16 Sep 2024 14:39 GMT
  • Attachments: