MVF11 — Bad restriction in ontology

We need a new property to link MVFentry to its VocabularyEntries.
The problem is this bad restriction on MVFentry:
<owl:Restriction>
<owl:onProperty rdf:resource="&mvf;hasVocabularyEntry"/>
<owl:onClass rdf:resource="&mvf;VocabularyEntry"/>
<owl:minQualifiedCardinality rdf:datatype="&xsd;nonNegativeInteger">0</owl:minQualifiedCardinality>
</owl:Restriction>
However hasVocabularyEntry is specifically for linking with a Vocabulary. If used to link an MVFEntry with its VocabularyEntries then the MVFEntry will get inferred to be a VOcabulary due to the following::
<owl:ObjectProperty rdf:about="&mvf;isInVocabulary">
<rdfs:subPropertyOf rdf:resource="&cmns-col;isMemberOf"/>
<rdfs:label>is in vocabulary</rdfs:label>
<rdfs:range rdf:resource="&mvf;Vocabulary"/>
<owl:inverseOf rdf:resource="&mvf;hasVocabularyEntry"/>
<skos:definition>has containing vocabulary</skos:definition>
</owl:ObjectProperty>

Overly constraining inverse on property isInVocabulary

The resolution to this issue depends on the resolution to MVF11-15, to include all of the metadata changes made in Ballot 2.

The challenging restriction isn't the issue here (and doesn't exist). Currently, there is a link between MVF entry and vocabulary entry - an MVF entry 'is signified by' min 0 vocabulary entry. The inverse is on vocabulary entry, and after MVF11-15, states that a vocabulary entry denotes max 1 MVF entry.

However, to ensure that there are no issues in saying that a given vocabulary entry can occur in things other than vocabularies, we can relax the inverse on the property isInVocabulary.