[Bug 12776] Define process for deciding whether a draft is REC-track or Note-track

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12776

--- Comment #14 from Michael[tm] Smith <mike@w3.org> 2011-06-20 06:53:39 UTC ---
(In reply to comment #13)
> Informative vs normative and REC vs Note are orthogonal dimensions.

Agreed. To be even more specific: A Note can contain statements that are
intended as normative requirements, and it's possible for a Rec to contain no
normative requirements at all, and to just be purely informative.

[...]
> It is certainly up to Editors (initially) and the Working Group (ultimately)
> whether a draft will include normative requirements. But it is also up to the
> Working Group whether a draft will proceed to Candidate Rec and beyond. It
> seems much better to decide this up front, in an orderly manner, than to go all
> the way to the point of being ready to go to CR and then having the CR
> resolution fail.
> 
> That is what this bug is about.

As I understand it, the background on this bug was that during the LC survey,
Lachlan stated that he believed a couple of drafts which are currently Working
Drafts should be made into Notes instead. And we have two other bugs open now
for those.

The reason Lachlan gave what that he does not want those documents to contain
any statements of normative requirements, and he mistakenly believes that the
way to ensure they don't have any normative requirements is to put them on the
"Note track".

But that's not going to achieve what Lachlan thinks its going to achieve; if
the documents are turned into Notes -- or if the group decides they are
destined to eventually become Notes -- that is not going to prevent the editors
of those documents from including statements of normative requirements in them.

So establishing a process in the decision policy for turning documents into
Notes is not going to solve the problem Lachlan wants fixed.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Monday, 20 June 2011 06:53:44 UTC