Re: [poe] Role of the ODRL Common Vocabulary and of Profiles

Considering "what makes a processor conforming to a Profile" I had a wider look at the section 4 [ODRL Profiles](https://w3c.github.io/poe/model/#profile)
* a simple issue in ODRL Purpose Profile: to the list of things which can be extended by Profile the instances of Action should be added, I guess they will have a key role in Profiles.
* What is a Profile allowed to define:
  * 4.1 tells: "... An ODRL Profile directly and explicitly serves their communities needs by **specifying only the terms they wish to support** in ODRL expressions. ...." - this allows also to exclude terms defined by the IM - is that ok?
  * 4.3 tells: "An ODRL Profile extends the ODRL Information Model classes, properties, and instances in the following ways: ..."
  * Conclusion: we need consistence - "extending" seems to be ok, "excluding" is unclear (and at least I'm not supporting it as it will be hard to draw a line between excluding IM parts and spoiling the IM. The only alternative I see is that the IM defines which things may be excluded by a Profile.)
* As said above I suggest to have **a normative sub-section in section 4**:
  * Head: ODRL Profile Definitions and Conformance
  * Content: (not supporting any "exclusion", see above)
An ODRL Profile must not overrule the ODRL Information Model.
An ODRL Profile may extend the ODRL Information Model classes, properties, and instances by defining subclasses, sub-properties and new instances.
An ODRL Processor may conform to an ODRL Profile, in this case it has to conform to the Information Model and in addition to the definitions of the Profile. If an ODRL Processor does not conform to the ODRL Profile, then it may continue processing the Policy expression, but it should not assume it has interpreted the Policy expression correctly.


-- 
GitHub Notification of comment by nitmws
Please view or discuss this issue at https://github.com/w3c/poe/issues/210#issuecomment-315012522 using your GitHub account

Received on Thursday, 13 July 2017 08:42:07 UTC