Closed brentzundel closed 5 years ago
@msporny Rubics are not normative unless they can have conformance, thus rubrics should not be in a charter
@nadalin wrote:
Rubics are not normative unless they can have conformance, thus rubrics should not be in a charter
It is perfectly reasonable for a WG to develop NOTEs or sections in a specification that are non-normative. Charters can call out the sort of work product that a WG is expected to produce, such as a set of rubrics, even if it is non-normative.
@msporny That would be part of a specification not a charter, if there is normative work this should be called out but I'm unaware of calling out non-normative work in a charter
@nadalin wrote:
That would be part of a specification not a charter, if there is normative work this should be called out but I'm unaware of calling out non-normative work in a charter
The Web Authentication Charter, which you co-Chair, calls out non-normative work in it's charter:
@msporny yes we did but that was POSIBLE work, please look at what we specified and we explicitly called these out as non-normative, these are, test suites, BCP, and protocol design. Not sure how rubrics would fit in, please explain.
@msporny, @brentzundel - I think the issue @nadalin is seeing here lies in a blur between "scope" and "deliverables" in the current document draft. "Deliverables" definitely can include NOTEs (or non-normative sections of SPECs) which may include rubrics, all of which are implicitly within "scope" (which might then not need to be called out quite so explicitly).
@TallTed Correct, please have a non-normative set of deliverables defined
@TallTed, @nadalin, @msporny - I added the rubric to the set of non-normative deliverables in 46de811
@msporny have my changes answered your concerns?
@msporny have my changes answered your concerns?
Hey @msporny your requested changes are blocking PR merge. @brentzundel's updates looked good; can you review/approve?
add requirement to charter for the WG to recommend a conformance rubric for method specs.