MVF 1.1b1 RTF Avatar
  1. OMG Issue

MVF11 — Bad restriction in ontology

  • Key: MVF11-20
  • Status: open  
  • Source: Adaptive ( Mr. Pete Rivett)
  • Summary:

    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>

  • Reported: MVF 1.0 — Fri, 28 Mar 2025 23:33 GMT
  • Updated: Fri, 28 Mar 2025 23:33 GMT