-
Key: MVF-4
-
Status: closed
-
Source: Thematix Partners LLC ( Mrs. Elisa F. 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
-
Disposition: Resolved — MVF 1.0
-
Disposition Summary:
Added profile with MVEntry and MVFEnabledElement stereotypes
The proposed UML profile includes two stereotypes
MFEntry applies to any Element. Adds a 'semanticReference' anyUri that can be used to link the UML element to an external semantic descriptor. Useful for those models that need the MVF 'concepts' but not the MVF 'terms'
MVFEnabledElement also applies to any Element. Adds an 'mvfEntry' reference which can be used to associate an (instance of) MVFEntry, which in turn can be linked to the other MVF entities
See the attached document, MVF Profiles.odt, for the revised text of this resolution. The new clause should be included in the document immediately following the clause specifying the metamodel.
-
Updated: Mon, 2 Oct 2023 12:57 GMT
-
Attachments:
- MVF Profiles.odt 40 kB (application/vnd.oasis.opendocument.text)
- MVFProfile.png 16 kB (image/png)
- MVFProfile.xmi 5 kB ()
MVF — Need a profile for the MVF metamodel in order to better integrate with various other UML profiles and tools
- Key: MVF-4
- OMG Task Force: Multiple Vocabulary Facility (MVF) 1.0 FTF