Closed zednis closed 9 years ago
Same issue with dco:hasPeople
.
Side question - does this basically break VIVO forms for annotation properties? If annotation properties cannot have domains or ranges then are they basically invisible on VIVO forms?
dco:dcoId
and dco:hasLatitude
also exhibit this issue.
dco:hasLatitude
a owl:FunctionalProperty , owl:AnnotationProperty , owl:DatatypeProperty ;
rdfs:label "latitude (decimal)"@en-US .
dco:dcoId
a owl:FunctionalProperty , owl:AnnotationProperty , owl:DatatypeProperty ;
rdfs:domain dco:Object ;
rdfs:label "DCO ID"@en-US ;
rdfs:range xsd:anyURI ;
rdfs:subPropertyOf owl:topDataProperty , dco:dcoId .
removed owl:AnnotationProperty from dco:dcoId, dco:hasLatitude, dco:inOrganization, dco:hasPeople
dco:inOrganization
is defined as both anowl:AnnotationProperty
andowl:ObjectProperty
.According to the OWL spec the OWL-DL profile defines annotation and object properties as disjoint and annotation properties are not allowed in property axioms (range, domain, subclass, inverseOf)
from http://www.w3.org/TR/owl-ref/#Header
from dco.ttl
I think we should remove the assertion of type
owl:AnnotationProperty
fordco:inOrganization
.