Open nicholascar opened 5 years ago
Also: w3c/dxwg#844, w3c/dxwg#796, w3c/dxwg#661, w3c/dxwg#644, w3c/dx-prof#8, w3c/dxwg#507, w3c/dx-prof#2
As I'm (trying) to read one of the issues related to this one, I would like to beg for some narrowing of the scope of this issue: can we restrict to prof:isProfileOf
(and maybe its relation with dcterms:conformsTo
), not prof:isInheritedFrom
? At least not until we've sorted out the former. Talking about "inheritance" will bring a lot of discussion, so if we can avoid it (and I believe we can, for prof:isProfileOf
) it would make our life much easier.
there's been also some related discussion in w3c/dxwg#698
I think that prof:isProfileOf and dct:conformsTo could be accepted as long as the definitions don't bring in inheritance. I think that's what the connection is here and what has derailed us in the past. If we can agree on some simple definitions I think we could nail this one. I don't, however, know how this affects the rest of the document. As soon as we get the review copy, we should keep this in mind while reading.
Narrowing scope, as requested by @aisaac by changing title.
@nicholascar I would suggest to keep 'transitivity intentions' in the title, as it shows where we want to bring clarification.
And to clarify my earlier comment, I think it's fine if our discussions bring us to agree on semantics that some could label with the word 'inheritance'. It's just that we should not explicitly seek to label it as inheritance, ourselves, as this is too controversial/vague for here.
The now closed issue w3c/dxwg#698 included a some suggestions have they been implemented? If not it's worth putting them here.
@aisaac does the inclusion of the axiom in the ED cover off on this Issue? In adding it, we did review the hierarchy and, with the inclusion of the axiom, we are now explicit about what inferences can be drawn from the use of prof:isProfileOf`.
This issue supersedes several redundant issues to motivate a complete review of PROF's hierarchy transitivity.