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.

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.

This is an object property that was eliminated from the commons collections ontology, so in order to maintain consistency, it needs to be moved to the MVF ontology.

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.