ODRL Validator document - communication considerations

Hi Victor,

thanks for your work on an ODRL Validator (and Evaluator) and creating the
document at https://www.w3.org/2016/poe/wiki/Validation

 

Looking into that document raised for me some issues regarding how to
communicate ODRL related to the IM of the CR:

*	A key issue from my point of view is that the IM shows all examples
only in JSON-LD, while the Validator doc shows only Turtle syntax. A person
who reads the IM will get familiar with the JSON-LD syntax - and its
specialities - and it may be hard to transform this quickly into Turtle in
the reader's head.
*	Question: could we recommend a web service for translating JSON-LD
into Turtle to support such readers?
*	Terminology: (goal: using the same terms in the IM and the Validator
document)

*	Normalization 3: Applying inheritance rules
The IM does not use the term "inheritance rules" but "inheritance mechanism"
- is it ok, to adopt that?
*	Normalization 4. Interiorizing policy-level properties
This section is about IM section 2.7.1. headlined "Compact Policy" and this
is included "It is RECOMMENDED that compact ODRL Policies be expanded to
atomic Policies when being processed for conformance."
I suggest to name this section 4: "Expanding Compact Policies"
*	Normalization 5. Expanding from compound to irreducible Rules
Section 2.7 in the IM names the target of expanding compounded properties
the "atomic equivalent".
- the target "Rules" in the current heading is wrong, this IM section only
talks about properties.
- I suggest to name this section 5: "Expanding compound Rule properties to
atomic equivalents"

 

That's all, thanks for considering.

 

Best,

Michael