- From: Ivan Herman via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Dec 2017 18:20:52 +0000
- To: public-poe-archives@w3.org
iherman has just labeled an issue for https://github.com/w3c/poe as "Vocab": == Dc:license vocabulary hijacking? == In section 3.5.2 of the vocab, on target policy, it says that `hasPolicy` has `dc:license` as a sub-property. This statement also appears in the ontology: ``` dct:license rdfs:subPropertyOf odrl:hasPolicy . ``` What this means is that if `dc:license` relates _any_ two instances in the world, then `odrl:hasPolicy` is also a valid relationship for those instances. That is referred to as "ontology hijacking", ie, imposing an extra constraint on a vocabulary item that is not under the control of this group. This should not be done. There are two possibilities: 1. This is an editorial oversight and it should say `hasPolicy subPropertyOf dct:license`. 2. This was the intention, but that should, in fact, be removed. (No. 1 makes sense to me.) A further question is either of those steps are taken, does that invalidate any of the implementations, i.e., does any of the implementations really make use of those terms? What about test cases? Obviously, the question is whether this is a substantive change or a honest but harmless mistake... (This question came up during the PR Transition discussion with the Director.) See https://github.com/w3c/poe/issues/286
Received on Tuesday, 19 December 2017 18:21:03 UTC