The purpose is to reflect the equivalent of package ownership in a source model: the name should better reflect that.

This might be a new area of exploration, and could apply beyond MVF entries in the context of MVF.

Currently the metamodel reflects SKOS-like relations such as broader and narrower, but more is needed for certain applications.

It would be useful to have a non-normative annex demonstrating how one could do this as a starting point for MVF users.

Investigate whether this should be on vocabulary, vocabulary entry, both, and/or possibly on a more general element as well.

There may also be an impact on the ontology, depending on the resolution.

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

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.