Open rob-metalinkage opened 5 years ago
from @rob-metalinkage:
The rationale for a subproperty is that we can then add a property chain axiom to clarify the intent.
:specifiedBy rdf:type owl:ObjectProperty ;
rdfs:domain :ResourceDescriptor ;
rdfs:range dct:Standard ;
skos:definition "The base specification that defines the role of the related resource" ;
skos:usageNote "This property allows a client to determine which base specification declared
the requirement or other role for this particular resource, allowing
implementations to flatten inheritance hierarchies for clients do not need
to traverse a graph to locate all requirements. Implementations are responsible
for determining if and how to use this property, and may choose some appropriate
subset of resources. This property provides an optional inverse for the property
hasResource"@en ;
owl:propertyChain (
:specifiedBy :hasResource
) ;
rdfs:label "specified by" .
In the discussion on w3c/dxwg#857 @nicholascar detailed the PROF semantics for the inheritance link (https://github.com/w3c/dxwg/issues/857#issuecomment-557945066) .
But if that definition is still up-to-date, I find it has inconsistencies, which should probably be addressed here. More precisely, there's a contradiction between three elements:
Proposal: replace
isInhertiedFrom
with a more general property that allows anyResourceDescriptor
to directly indicate theProfile
that defines theResourceRole
of this resource.