- From: Michael Steidl via GitHub <sysbot+gh@w3.org>
- Date: Mon, 07 Aug 2017 14:28:17 +0000
- To: public-poe-archives@w3.org
**Re Profile** * re 2.1 Policy Class * Now 1: A Policy MAY have none or one profile property ... Should be 1: A Policy MAY have **none, one or many** profile properties ... * Now 2: Use an ODRL Profile that declares the supported vocabulary expressed in the Policy. Should be 2: Use an ODRL Profile that declares the supported vocabulary **used by expressions** in the Policy. (Comment: a Policy does not express vocabularies.) * re 4. ODRL Profiles * Now 1: An ODRL Profile explicitly serves a communities needs by ... Should be 1: An ODRL Profile explicitly serves **community** needs by ... * Now 2: These terms may be defined explicitly or may be reused from the ODRL Common Vocabulary. Should be 2: These terms may be defined explicitly or may be **adopted** from the ODRL Common Vocabulary. (Comment: "adopted" clarifies more that a Profile needs an explicit statement to make a term of the Common Vocabulary part of it.) * Now 3: Additional Actions for Rules: ... of a Action Should be 3: Additional Actions for Rules: ... of **an** Action * open issue re "All new classes ... must also be defined as a skos:Concept": is there a need to create skos:Collection for all instanced of e.g. Actions, Left Operand ... defined by a Profile. (They are defined this way by the Core Vocabulary.) -- GitHub Notification of comment by nitmws Please view or discuss this issue at https://github.com/w3c/poe/issues/215#issuecomment-320679092 using your GitHub account
Received on Monday, 7 August 2017 14:28:21 UTC