Re: [poe] Systematic labeling of normative vs. informative

>1) Do you mean the examples in the Encoding section of the Vocab document?
>We state this: https://w3c.github.io/poe/vocab/#conformance
>

Ah, yes, indeed, I missed that. This takes care of the examples.

>2) I assume we need test cases for all serialisations  @philarcher1
>
>3) Yes, we have discussed this a lot. The proposal is that we ask implementors (again) which terms they use and document that (like we did the first time [1]). From that we can split the Vocab into normative/non-normative.
>
>Another option is to split the Vocab into **Core** (normative) and **Common** (non-normative) and only have the IM terms in the Core.
>So the spec says the IM is the core and the rest is all recommended terms.

I would day *this decision is urgent*. The CR (which, afaik, is planned after the F2F meeting) **must** contain something about this. Either we decide on what is and what is not normative or, at the minimum, we label all features that _may_ become informative as "at risk" in the document. If we do not do that, and we "downgrade" some features as informative later, that means we will be required to re-publish a CR at some point which may be a source of delays.

To take a specific example (I may be a bit pushy here) I could imagine _not_ to consider the RDF serializations in the documents as normative. The ODRL recommendation is the model and the vocabulary; the vocabulary is defined in RDF. *That* is is the new thing we bring to the table. The fact that the RDF content can be serialized in JSON-LD, Turtle, or anything else is not a feature this recommendation adds as something new, it is just the usage of existing Recommendations.

(The testing of the vocabulary will use some form of a serialization, but that is different. We should not test the serialization _itself_.

The XML serialization is something different: that is not an RDF one. The question is whether it would be widely used (I am not sure), ie, whether putting it out as a Recommendation adds a value over "just" publishing it either as a separate Note or as an informative appendix in the spec.


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

Received on Tuesday, 2 May 2017 08:30:50 UTC