MVF 1.0 FTF Avatar
  1. OMG Issue

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

  • Key: MVF-2
  • Status: closed  
  • Source: Thematix Partners LLC ( Mrs. Elisa F. 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
  • Disposition: Resolved — MVF 1.0
  • Disposition Summary:

    Limit the usage of hasMVFEntry to correspond to its usage in the metamodel

    The resolution to this issue unwinds some circularity in restrictions and clarifies the meaning of hasMVFEntry to better reflect the metamodel.

  • Updated: Mon, 2 Oct 2023 12:57 GMT
  • Attachments: