- From: simon via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Jul 2017 05:57:38 +0000
- To: public-poe-archives@w3.org
@nitmws: > And: what does "understanding a Profile" mean? > [..] > "understanding a Profile": I think this is like "being able interpret all classes, properties and entities as defined by the ODRL Information Model (simon: s/Information Model/Profile/ ?)". while "_being able interpret all classes, properties and entities as defined by ..._" is slightly less ambiguous than "_must understand the Profile_", there's still no clear-cut definition of what "being able to interpret" actually means.. It's about **conformance**, as actually already stated in [Section 4.3:](https://w3c.github.io/poe/model/#profile-requirements) > In an ODRL Policy, the profile property is used to indicate the identifier (IRI) of **the ODRL Profile ~~for~~ to which the Policy expression** (simon: ODRL Policy==Policy expression?) **conforms to.** however, for the remainder of the paragraph "conform to" was - for whatever reason - substituted by "understand": > This property is OPTIONAL, but if the property appears, then any ODRL consuming system that supports/implements the given profile MUST **understand** the identified ODRL Profile. If an ODRL consuming system does not **understand** the ODRL Profile, then it MAY continue processing the Policy expression, but it SHOULD NOT assume it has interpreted the Policy expression correctly. 1. better: s/understand/conform to/ 2. the first sentence needs to be reworked -- GitHub Notification of comment by simonstey Please view or discuss this issue at https://github.com/w3c/poe/issues/210#issuecomment-314979086 using your GitHub account
Received on Thursday, 13 July 2017 05:57:52 UTC