A numeric ordering is a kind of systematic ordering, with a couple of important attributes: (1) what the origin is – zero or one, typically, and (2) whether it is from low to high or high to low. Typically numeric orderings of collections use positive integers, but there could be other kinds of ordering that use, for example, alphabetical with numerals and/or distinctions by rank, such as A.1.1.

There may also be utility in having the notion of 'position', such as a position in an ordered list, or position of a term in a text.

We have not captured this clearly in the ontology and should.

Currently we've mapped MVFEntry to SKOS Concept, and it should be Vocabulary Entry to SKOS Concept. Likewise, the mapping between MVF Concept System to ConceptSystem should be to Vocabulary in MVF.

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.

This represents a generalization as in UML or OWL, at the metamodel level rather than at the UML model level. This may be confusing to users and so an explanatory note is needed to help. Note that the ramifications of this are at the instance level - one instance of an MVF entry may be a generalization of another instance of an MVF entry.

The same is true of the additional relationship, which is context, where notes and examples would also be helpful.

While the definition of MVF entry and that of SKOS concept appear to be the same, there are differences in how SKOS is used. That may, in fact mean we should consider mapping to MVF Vocabulary Entry instead.

Regardless, it would be useful to provide a discussion in the specification about the possibility, depending on the application.

One example of this is hasNumericValue. It is currently declared to be functional, but could be the parent property for several properties of some class. In this case, the resulting ontology could be logically inconsistent if the values are not the same (and even if they are, by coincidence, that's still a problem). Other properties that are also declared as functional should be reviewed for the same issue.

This would assist in alignment with SysML v2, but more importantly allows alignment of some quantity value with a more general measurement reference rather than only a measurement unit, for representation of IU in pharma, for example.

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.