- From: Arthur Barstow <art.barstow@nokia.com>
- Date: Fri, 11 Nov 2011 09:00:43 -0500
- To: public-webapps <public-webapps@w3.org>
I created the following version of the spec as the basis of the CR: [1] http://dev.w3.org/html5/websockets/publish/CR-websockets-2011.html This version includes a fix for [13700] and I added a reference to HTML5's Parsing URLs section as requested by Julian. The only remaining bug is [12510]. This editorial bug was reopened after the CfC started. If anyone thinks those references are critical, they should please add a diff (based on [1]) to the bug and I will add them before the CR is published. [Given Doug and I are traveling next week, we must schedule and hold a Director's call for the CR and US national holidays at the end of the month, I don't expect the CR to get published for a few weeks, possibly December.] -AB [13700] http://www.w3.org/Bugs/Public/show_bug.cgi?id=13700 [12510] http://www.w3.org/Bugs/Public/show_bug.cgi?id=12510 On 11/3/11 12:22 AM, ext Arthur Barstow wrote: > During the October 31 meeting [1], there was agreement to publish a > Candidate Recommendation of the WebSockets API and this is a Call for > Consensus to do so: > > http://dev.w3.org/html5/websockets/ > > The remaining open editorial bug [13700] will be fixed before > publication. > > I propose the CR exit criteria is the same as our last CR (Progress > Events): > > [[ > To exit the Candidate Recommendation (CR) stage the following criteria > must have been met: > > 1. There will be at least two interoperable implementations passing > all test cases in the test suite for this specification. An > implementation is to be available (i.e. for download), shipping (i.e. > not private), and not experimental (i.e. intended for a wide > audience). The working group will decide when the test suite is of > sufficient quality to test interoperability and will produce an > implementation report (hosted together with the test suite). > > 2. A minimum of three months of the CR stage will have elapsed (i.e. > not until after DD MMM 2012). This is to ensure that enough time is > given for any remaining major errors to be caught. The CR period will > be extended if implementations are slow to appear. > ]] > > This CfC satisfies: a) the group's requirement to "record the group's > decision to request advancement" to CR; and b) "General Requirements > for Advancement on the Recommendation Track" as defined in the Process > Document: > > http://www.w3.org/2005/10/Process-20051014/tr.html#transition-reqs > > As with all of our CfCs, positive response is preferred and encouraged > and silence will be considered as agreeing with the proposal. The > deadline for comments is November 9 and all comments should be sent to > public-webapps at w3.org. > > -AB > > [1] http://www.w3.org/2011/10/31-webapps-minutes.html#item14 > [13700] http://www.w3.org/Bugs/Public/show_bug.cgi?id=13700 > >
Received on Friday, 11 November 2011 14:01:21 UTC