W3C home > Mailing lists > Public > public-html-admin@w3.org > July 2014

Re: CfC: Request transition of HTML5 to Candidate Recommendation

From: Roy T. Fielding <fielding@gbiv.com>
Date: Wed, 16 Jul 2014 15:19:41 -0700
Cc: Paul Cotton <Paul.Cotton@microsoft.com>, Sam Ruby <rubys@intertwingly.net>, "public-html-admin@w3.org" <public-html-admin@w3.org>
Message-Id: <3939F473-D227-4119-8285-8BE6D8A077C6@gbiv.com>
To: Robin Berjon <robin@w3.org>
On Jul 16, 2014, at 1:22 PM, Robin Berjon wrote:

> On 16/07/2014 20:09 , Roy T. Fielding wrote:
>> That is not a stable link, let alone a stable document.  Did you read it
>> with CSS on?  I don't see why you are refusing to publish it as a WG product
>> first before calling for CR.
> I am not aware of any group having done that, ever. I'm not even sure I understand what you're asking for.

I think that I come from the time when W3C process was actually followed
because that's what was agreed to by the consortium members.

All you have to do is send the editor's draft to the Team to publish the
technical content as a WD (or as LCWD), replacing the current document in
TR space, before asking the working group to claim that the document has
been reviewed by the public and determined to be CR-mature and stable.
The side-effect of doing so is that the links in your issues that claim to
have fixed something noted in LC will actually point to a document that
has that fix, the version links at the top of the document will actually
reflect what changes have been made since LC, and the status of this
document section will not be absurdly incorrect.

The move from last WD to CR is supposed to be handled by the Pub team
automatically after Director approval -- there is no need for the WG
to review a make-believe CR published on some other website with a
false date and bad links, since there are not supposed to be any substantive
changes between the WD and CR.  If there are, it is a publication error
that can be immediately fixed.

Received on Wednesday, 16 July 2014 22:20:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:37:36 UTC