- From: Michael Steidl via GitHub <sysbot+gh@w3.org>
- Date: Fri, 07 Jul 2017 09:37:42 +0000
- To: public-poe-archives@w3.org
nitmws has just labeled an issue for https://github.com/w3c/poe as "Vocab": == Role of the ODRL Common Vocabulary == This issue started in the discussion of #202: Properties taking the role of a short-cut may be added to a Policy. And [Compact Policy](https://w3c.github.io/poe/model/#composition-compact) of the IM tells, that Rules have to check the policy level for properties which should replicated to the Rule. This raises the question: how can a receiver of a Policy know what property found at the policy-level is - because there is no earmark like "this is a sub-property of relation" in a policy serialised as JSON or XML. A suggested approach was: all properties which are relevant for a policy must be defined by either the [ODRL Core Vocabulary](http://w3c.github.io/poe/vocab/#vocab-core) or by the profile applied to this policy. A note in this discussion added that the search by a Rule for applicable properties should include the properties of the [ODRL Common Vocabulary](http://w3c.github.io/poe/vocab/#vocab-common). By my view this does not fit. I see this as a general question: what properties and what instances/individuals of a class are defined as "may be applied to an ODRL policy with a specific profile" and which not. A receiver of such a policy has to expect only defined properties and instances and can adjust an ODRL processor accordingly. I support the approach outlined above: any used property or instance of an ODRL class must be defined * by the ODRL Core Vocabulary OR * by a vocabulary of the applied profile * all other properties and instances can be considered as unknown. Under this condition the ODRL Common Vocabulary has only the role of an informal suggestion to profile-makers what they can adopt for their specific profile. But using a property defined by the Common Vocabulary without an adoption of it by the applied profile should make this property unknown/invalid. See https://github.com/w3c/poe/issues/210
Received on Friday, 7 July 2017 09:37:48 UTC