Multiple Vocabulary Facility Avatar
  1. OMG Specification

Multiple Vocabulary Facility — Open Issues

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

Issues Descriptions

The MVF ontology is missing the class "MVFElement"


Need a profile for the MVF metamodel in order to better integrate with various other UML profiles and tools

  • Key: MVF-4
  • Status: open  
  • Source: Thematix Partners LLC ( Elisa Kendall)
  • Summary:

    As a convenience for UML modelers or modelers using other profiles, a profile for MVF would allow UML tool users to apply MVF without requiring other changes to tools.

    This would require both the profile itself as a machine readable file and documentation for it in the MVF specification. An optional compliance point should be added to cover the new profile.

  • Reported: MVF 1.0b1 — Fri, 27 Jan 2023 19:32 GMT
  • Updated: Wed, 31 May 2023 00:02 GMT
  • Attachments:

The property, hasMVFEntry, is used too broadly in the MVF ontology

  • Key: MVF-2
  • Status: open  
  • Source: Thematix Partners LLC ( Elisa Kendall)
  • Summary:

    hasMVFEntry is a property used to relate an element in any model to a corresponding MVF entry. It corresponds to the property ElementEntry in the metamodel. That property has a UML Element in its domain, which cannot be modeled in the ontology, but a note is needed on the property hasMVFEntry to state as much. It should only have one subproperty, corresponding to the property ElementCurrentEntry in the metamodel, however. The property relating a vocabulary entry to an MVF entry should be a separate property, and the narrower/broader properties should not be subproperties of hasMVFEntry.

  • Reported: MVF 1.0a1 — Fri, 13 Jan 2023 19:28 GMT
  • Updated: Thu, 25 May 2023 00:05 GMT
  • Attachments:

anyURI should not be a class

  • Key: MVF-15
  • Status: open  
  • Source: agnos.ai UK Ltd ( Pete Rivett)
  • Summary:

    It should be a PrimitiveType with an xsdType of anyURI

  • Reported: MVF 1.0a1 — Mon, 15 May 2023 20:43 GMT
  • Updated: Thu, 25 May 2023 00:05 GMT
  • Attachments:

The property, isRelatedTo, on which the MVF ontology depends has been removed from Commons and must be re-created in the MVF ontology


Clarify uri vs refrence vs externalReference

  • Key: MVF-6
  • Status: open  
  • Source: Mayo Clinic ( Davide Sottara)
  • Summary:

    The terms may be confusing, and implementers may 'misplace' important pieces of information

    'uri' is meant to be an 'individual/instance' URI, that identifies the entity represented by the MVF element
    (e.g. an individual Community - mapped by a mvf:Community, or an individual Concept - mapped by a mvf:MVFEntry)

    'externalReference', which only applies to MVFEntry, may be better called 'semanticReference', and be exepcted to resolve to a definitional resource such as an ontology (class/expression)

    'reference' seems to hold more descriptive/informative links such as web pages or other web resources.
    Maybe it could be called 'descriptiveReference' - in contrast with 'semanticReference'?

  • Reported: MVF 1.0b1 — Fri, 31 Mar 2023 18:42 GMT
  • Updated: Fri, 19 May 2023 00:01 GMT
  • Attachments:

XMI document is missing class "MVFEntry"

  • Key: MVF-5
  • Status: open  
  • Source: Mayo Clinic ( Davide Sottara)
  • Summary:

    According to the UML diagram in the spec (page 15), there should be a root abstract class "MVFEntry"

    This class is missing from the XMI document posted on the OMG website, though the XMI contains (dangling) Generalization references

  • Reported: MVF 1.0a1 — Fri, 31 Mar 2023 18:29 GMT
  • Updated: Fri, 19 May 2023 00:01 GMT
  • Attachments:

UML Profile for MVF

  • Key: MVF-7
  • Status: open  
  • Source: Mayo Clinic ( Davide Sottara)
  • Summary:

    From a usability standpoint,
    at the date this issue is raised, not all UML tools support MVF natively.
    In particular, the tools would miss the mvf:ElementEntry and mvf:CurrentElementEntry links from a mof:Element to an mvf:MVFEntry

    As a workaround, one could define a UML profile that provides the necessary associations

  • Reported: MVF 1.0a1 — Fri, 31 Mar 2023 18:47 GMT
  • Updated: Fri, 19 May 2023 00:01 GMT

The published XMI should be generated as Canonical XMI

  • Key: MVF-8
  • Status: open  
  • Source: Thematix Partners LLC ( Elisa Kendall)
  • Summary:

    MVF users have requested that the form of the XMI that is provided as a part of the MVF specification be canonical XMI.

  • Reported: MVF 1.0a1 — Fri, 14 Apr 2023 18:18 GMT
  • Updated: Fri, 19 May 2023 00:01 GMT

More examples are needed to demonstrate how to use MVF

  • Key: MVF-3
  • Status: open  
  • Source: Thematix Partners LLC ( Elisa Kendall)
  • Summary:

    There is an example in Annex B that is quite useful, but is not multilingual. Since we have said that MVF can be used to support multiple natural languages, we need at least one additional example to cover that use case. We might also include a broader example showing how to represent a general vocabulary in MVF, such as the AI PTF emerging vocabulary for artificial intelligence, to show how this can be done.

  • Reported: MVF 1.0a1 — Fri, 13 Jan 2023 19:35 GMT
  • Updated: Fri, 19 May 2023 00:01 GMT