Multiple Vocabulary Facility Avatar
  1. OMG Specification

Multiple Vocabulary Facility — Open Issues

  • Acronym: MVF
  • Issues Count: 13
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

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:

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:

The constraint on vocabulary entry stating that it denotes exactly 1 MVF entry is incorrect

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

    While typically one would associate a vocabulary entry with only one MVF entry, this does not allow for cases when a vocabulary includes more entries than are mapped to MVF entries. Thus, one could have terms that either are not needed or have yet to be mapped, and the restriction would result in wrong results (or a rule that exercises the restriction could do so).

    The restriction in the MVF ontology should be modified to 'max 1' from exactly 1, and the redundant restriction in the ISO 1087 ontology that says 'min 0' should be eliminated.

  • Reported: MVF 1.0b2 — Wed, 19 Jun 2024 18:45 GMT
  • Updated: Wed, 19 Jun 2024 18:45 GMT

Need an extension in the terminology science ontology for numeric ordering

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

    A numeric ordering is a kind of systematic ordering, with a couple of important attributes: (1) what the origin is – zero or one, typically, and (2) whether it is from low to high or high to low. Typically numeric orderings of collections use positive integers, but there could be other kinds of ordering that use, for example, alphabetical with numerals and/or distinctions by rank, such as A.1.1.

    There may also be utility in having the notion of 'position', such as a position in an ordered list, or position of a term in a text.

    We have not captured this clearly in the ontology and should.

  • Reported: MVF 1.0b2 — Thu, 7 Mar 2024 20:09 GMT
  • Updated: Fri, 12 Apr 2024 18:20 GMT

In the mapping ontology between SKOS-XL and MVF, the mappings need adjustment

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

    Currently we've mapped MVFEntry to SKOS Concept, and it should be Vocabulary Entry to SKOS Concept. Likewise, the mapping between MVF Concept System to ConceptSystem should be to Vocabulary in MVF.

  • Reported: MVF 1.0b2 — Fri, 19 Jan 2024 19:44 GMT
  • Updated: Fri, 12 Apr 2024 18:20 GMT

Consider adding more contextual properties to vocabulary entry

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

    Investigate whether this should be on vocabulary, vocabulary entry, both, and/or possibly on a more general element as well.

    There may also be an impact on the ontology, depending on the resolution.

  • Reported: MVF 1.0b2 — Fri, 19 Jan 2024 19:36 GMT
  • Updated: Fri, 12 Apr 2024 18:19 GMT

Include a note to explain the use of generalization and context between MVFEntries

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

    This represents a generalization as in UML or OWL, at the metamodel level rather than at the UML model level. This may be confusing to users and so an explanatory note is needed to help. Note that the ramifications of this are at the instance level - one instance of an MVF entry may be a generalization of another instance of an MVF entry.

    The same is true of the additional relationship, which is context, where notes and examples would also be helpful.

  • Reported: MVF 1.0b2 — Fri, 19 Jan 2024 19:15 GMT
  • Updated: Fri, 12 Apr 2024 18:19 GMT

The mapping from SKOS Concept to MVF Entry may need further review

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

    While the definition of MVF entry and that of SKOS concept appear to be the same, there are differences in how SKOS is used. That may, in fact mean we should consider mapping to MVF Vocabulary Entry instead.

    Regardless, it would be useful to provide a discussion in the specification about the possibility, depending on the application.

  • Reported: MVF 1.0b2 — Fri, 8 Mar 2024 19:18 GMT
  • Updated: Fri, 8 Mar 2024 19:18 GMT

Additional mapping capabilities between MVF entries would be useful

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

    This might be a new area of exploration, and could apply beyond MVF entries in the context of MVF.

    Currently the metamodel reflects SKOS-like relations such as broader and narrower, but more is needed for certain applications.

    It would be useful to have a non-normative annex demonstrating how one could do this as a starting point for MVF users.

  • Reported: MVF 1.0b2 — Fri, 19 Jan 2024 19:21 GMT
  • Updated: Fri, 9 Feb 2024 19:26 GMT