- From: kcoyle via GitHub <sysbot+gh@w3.org>
- Date: Thu, 25 Oct 2018 05:14:14 +0000
- To: public-dxwg-wg@w3.org
@nicholascar "Also, any specialised ontology of another is a profile carrying forward entailments from the base spec." Here I think we need to carefully define what we mean by "entailment". The meaning I was using was the actual axiomatic usage in RDF, which is effected in code. This kind of entailment adds triples to the graph. In a non-RDF environment, it would add some code to existing code, as in your example of placing new terms in a hierarchy. I do not use "entailment" to mean intellectual or semantic "carry-over", such as re-using dct:title without further definition because your community knows very well what it means. I agree with @agreiner in her concerns about "cascading" profiles, and I think that the profiles that we see in the wild support her view that a stand-alone profile is what most people are comfortable with. For that reason, I think that any entailments inherent in the ontology need to be clearly spelled out - in part so that people can understand if they need them. This is my worry about "profileOf" - one could say that DCAT-AP is a profileOf DCAT, yet DCAT-AP does not allow any code entailments from DCAT, AFAIK. If "profileOf" means that there are entailments, then it would not be correct for DCAT-AP to use that. Yet it seems quite natural to consider DCAT-AP a profile of DCAT. So the definition and implications of the use of "profileOf" are very important and need to be spelled out. Can a stand-alone profile be a profileOf something? What is the algorithm for entailment of profileOf? In ODRL it means (as I understand it) to carry forward ALL properties of the base profile. I don't think that's what we mean since we say that profiles can select properties from a variety of base vocabularies. So what exactly is the effect of profileOf on the content of the profile? -- GitHub Notification of comment by kcoyle Please view or discuss this issue at https://github.com/w3c/dxwg/issues/486#issuecomment-432917154 using your GitHub account
Received on Thursday, 25 October 2018 05:14:16 UTC