Multiple Vocabulary Facility Avatar
  1. OMG Specification

Multiple Vocabulary Facility — Open Issues

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

Issues Descriptions

The constraint in vocabulary entry that it denotes exactly one MVF entry is too narrow

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

    There may be cases that vocabularies may not have a relationship with an MVF entry. The constraint should be loosened to be [0..1].

  • Reported: MVF 1.0b1 — Fri, 14 Feb 2025 19:39 GMT
  • Updated: Fri, 14 Feb 2025 19:39 GMT

Having both a vocabulary entry and abbreviation class is redundant

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

    Both the metamodel and ontology include a class called abbreviation, which is a subclass of vocabulary entry. This seems redundant given that there is a constraint representing the notion of whether or not a given vocabulary entry is in fact an abbreviation.

  • Reported: MVF 1.0b1 — Fri, 14 Feb 2025 19:32 GMT
  • Updated: Fri, 14 Feb 2025 19:36 GMT

Property 'currentMVFEntry' changes the multiplicity, so it should be redefines not subsets

  • Key: MVF11-3
  • Status: open  
  • Source: Coventry University ( Mr. Stephen Powley)
  • Summary:

    The property 'currentMVFEntry' on the association ElementCurrentEntry changes the multiplicity from 0..* to 0..1, so it should be redefines not subsets (or the parent multiplicity needs to be changed)

  • Reported: MVF 1.0b1 — Wed, 7 Jun 2023 22:54 GMT
  • Updated: Sat, 2 Mar 2024 23:58 GMT