W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2012

CfC: publish Candidate Recommendation of Web Sockets API; deadline July 18

From: Arthur Barstow <art.barstow@nokia.com>
Date: Wed, 11 Jul 2012 09:11:52 -0400
Message-ID: <4FFD7B98.1010203@nokia.com>
To: public-webapps <public-webapps@w3.org>, Cameron McCormack <cam@mcc.id.au>
Yesterday Hixie closed several of the Web Sockets bugs mentioned in the 
e-mail below and he updated others. I think this now provides a basis to 
determine if we have consensus to publish a Candidate Recommendation. As 
such, this is a Call for Consensus to publish a Candidate Recommendation 
of Web Sockets.

I propose the CR be based on the May 24 LC [1] plus include:

1. The editorial patch for 17224 [2]

2. The patch [3] to remove the TreatNonCallableAsNull qualifier for some 
attributes. If anyone considers this change as substantive, please speak 
up. Cameron - what's your opinion on this?

Additionally:

* 12510 - as Hixie indicated in the bug, if anyone is willing to create 
a patch, please contact Hixie privately and please let me know of your 
intent

* 15829 - the CR will include a fix for this as was done for the LC

* 16927 - the CR will include a fix for this as was done for the LC

* Other bugs to remain open for v.next: 15209, 15210, 17073, 17264, 17685

* The CR's exit criteria be identical to the December 2011 CR.

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

Positive response is preferred and encouraged and silence will be 
considered as agreeing with the proposal. The deadline for comments is 
July 18 and all comments should be sent to public-webapps at w3.org.

-Thanks, AB

[1] 
http://dev.w3.org/cvsweb/html5/websockets/Overview.html.diff?r1=1.269;r2=1.270;f=h
[2] 
http://dev.w3.org/cvsweb/html5/websockets/Overview.html.diff?r1=1.268;r2=1.269;f=h
[3] http://www.w3.org/TR/2012/WD-websockets-20120524/


-------- Original Message --------
Subject: 	[websockets] Seeking comments on moving back to CR; deadline 
June 28
Resent-Date: 	Thu, 21 Jun 2012 14:29:06 +0000
Resent-From: 	<public-webapps@w3.org>
Date: 	Thu, 21 Jun 2012 10:28:31 -0400
From: 	ext Arthur Barstow <art.barstow@nokia.com>
To: 	public-webapps <public-webapps@w3.org>



Hi All,

I created a tracking document for the two comments and five bugs that
were submitted against the 24 May LCWD of Web Sockets (or in the
approximate time frame of that publication):
<http://www.w3.org/2008/webapps/wiki/Websockets-Comments-LC-24May2012>.

Below is my "take" on these bugs and comments. It would be good to get
this spec back to CR and hence closer toward the IP commitments that
will only be final when the spec reaches Recommendation.

Bugs:

* 17073 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=17073> - marked
as an Enhancement; don't include in the v1 CR

* 17224 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=17224> - this
looks like an Editorial bug to me as I stated in the bug. Assuming there
is consensus the text should be "unsolicited pongs", if Hixie can't fix
this before the v1 CR copy is created, I'll make this change in the v1 CR.

* 17262 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=17262> - Jonas'
view as expressed in
<https://www.w3.org/Bugs/Public/show_bug.cgi?id=17262#c13> seems
reasonable so I propose closing this with a resolution of WorksForMe.

* 17263 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=17263> -
send(ArrayBuffer), which was included in the December 2011 CR, has been
implemented and presumably must be supported by some browsers (e.g.
bc/legacy reasons). As such, it seems reasonable to fix this bug and
perhaps we could argue a new LCWD is not needed since it has already
been implemented.

* 17264 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=17264> - this
bug appears to be a rehash of bug 13104 which was Fixed in October 2011
so I propose closing this with a resolution of Duplicate.

Comments:

* LC-1
<http://lists.w3.org/Archives/Public/public-webapps/2012AprJun/0807.html> -
The 28-May-2012 reply by Takeshi Yoshino notes this is a Chrome bug and
not a spec bug. The 1-June-2012 reply by Simon Pieters indicates the
Protocol spec needs to be updated. As such, I don't think any changes
are needed for v1 of the spec.

* LC-2
<http://lists.w3.org/Archives/Public/public-webapps/2012AprJun/0880.html> -
This is an editorial bug and is already captured in Bug 12510. Ideally,
this bug would be fixed before the v1 CR branch is created. However, if
Hixie can't fix it before then and if no one else creates an acceptable
patch for Hixie, I don't support blocking the v1 CR for this.

Please send all comments by June 28.

-Thanks, AB
Received on Wednesday, 11 July 2012 13:12:34 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:53 GMT