[poe] ODRL Validation/Validation issues

nitmws has just created a new issue for https://github.com/w3c/poe:

== ODRL Validation/Validation issues ==
Going over the [ODRL Validation](https://www.w3.org/2016/poe/wiki/Validation) document, 1.2 Validation section I noticed:

1. I suggest to follow the spelling of classes and properties in the IM: classes starting with uppercase characters (Rule, Constraint, Duty), properties with lowercase characters. That's a big issue as we have names of classes and properties where only the case of the first characters is making the difference: Duty - duty.
1. Use of plural: I suggest to use, primarily in the headers, the singular of classes, properties etc. Why: it is not clear if the raised issue applies to each item of the pluralised things or to the set of all of them. Example: "... rules must have exactly one assignee" (does that mean: the 20 rules in a policy must have the same single assignee?)  should be replaced by "... each rule must have exactly one assignee".
2. How to check what kind of class is referenced by a property
"Policies must have at least one rule" does this check by testing if one of the properties odrl:permission, odrl:prohibition, or odrl:obligation exist. But what if they reference an instance of the Action and not the Rule class? (Note: in my ODRL testground I expand the JSON-LD IM examples with @context to JSON-LD without context - by https://www.npmjs.com/package/jsonld - and this expanded JSON-LD does not show the type of the value referenced by e.g. odrl:permission.)
3. Headers "Source and AssetCollections" and "Source and PartyCollections" : append "... with refinements" as this is the essential part
4. re "Constraints must have exactly one rightOperand" - more a question: the IM [defines as value of rightOperand](http://w3c.github.io/poe/model/#constraint-class) a single item or a list of items. Does SHACL understand a list as a single thing?
5. *:DATATYPE: I guess this must be *:datatype



Please view or discuss this issue at https://github.com/w3c/poe/issues/261 using your GitHub account

Received on Monday, 18 September 2017 07:00:58 UTC