Re: RfC: LCWD of Web Socket API; comment deadline October 21

2012-02-07 Thread Michael[tm] Smith
Julian Reschke , 2012-02-01 12:25 +0100: > On 2012-01-03 13:39, Arthur Barstow wrote: > >On 12/29/11 8:48 AM, ext Julian Reschke wrote: > >>I note that > >> > >>claims this was addressed but it was not. > >> > >>(In the meantime

Re: RfC: LCWD of Web Socket API; comment deadline October 21

2012-02-01 Thread Julian Reschke
On 2012-01-03 13:39, Arthur Barstow wrote: On 12/29/11 8:48 AM, ext Julian Reschke wrote: I note that claims this was addressed but it was not. (In the meantime the reference additionally is out-of-date as RFC 6455 has been

Re: RfC: LCWD of Web Socket API; comment deadline October 21

2012-01-03 Thread Arthur Barstow
On 12/29/11 8:48 AM, ext Julian Reschke wrote: I note that claims this was addressed but it was not. (In the meantime the reference additionally is out-of-date as RFC 6455 has been published a few days later, and not waiti

Re: RfC: LCWD of Web Socket API; comment deadline October 21

2011-12-29 Thread Julian Reschke
On 2011-09-30 10:26, Julian Reschke wrote: On 2011-09-29 18:28, Arthur Barstow wrote: On September 29, aLCWD of Web Sockets API was published: http://www.w3.org/TR/2011/WD-websockets-20110929/ Please send all comments to public-webapps@w3.org by October 21. The reference for the Websocket Pr

Re: Spec changes for LCs and later maturity levels [Was: Re: RfC: LCWD of Web Socket API; comment deadline October 21]

2011-11-02 Thread Julian Reschke
On 2011-10-14 15:14, Julian Reschke wrote: On 2011-10-11 00:30, Ian Hickson wrote: On Sun, 9 Oct 2011, Arthur Barstow wrote: On 10/7/11 8:32 AM, ext Julian Reschke wrote: As far as I recall, we agreed in the IETF WG that parsing of web socket URIs should work exactly the same way as for any ot

Re: Spec changes for LCs and later maturity levels [Was: Re: RfC: LCWD of Web Socket API; comment deadline October 21]

2011-10-14 Thread Julian Reschke
On 2011-10-11 00:30, Ian Hickson wrote: On Sun, 9 Oct 2011, Arthur Barstow wrote: On 10/7/11 8:32 AM, ext Julian Reschke wrote: As far as I recall, we agreed in the IETF WG that parsing of web socket URIs should work exactly the same way as for any other URI scheme. It appears that the API spec

Reminder: RfC: LCWD of Web Socket API; comment deadline October 21

2011-10-14 Thread Arthur Barstow
Original Message Subject:RfC: LCWD of Web Socket API; comment deadline October 21 Resent-Date:Thu, 29 Sep 2011 16:29:15 + Resent-From: Date: Thu, 29 Sep 2011 12:28:29 -0400 From: ext Arthur Barstow To: public-webapps On September 29, aLCWD of Web

Re: Spec changes for LCs and later maturity levels [Was: Re: RfC: LCWD of Web Socket API; comment deadline October 21]

2011-10-10 Thread Ian Hickson
On Sun, 9 Oct 2011, Arthur Barstow wrote: > On 10/7/11 8:32 AM, ext Julian Reschke wrote: > > As far as I recall, we agreed in the IETF WG that parsing of web socket URIs > > should work exactly the same way as for any other URI scheme. It appears > > that the API spec now tries to override this, a

Re: Spec changes for LCs and later maturity levels [Was: Re: RfC: LCWD of Web Socket API; comment deadline October 21]

2011-10-09 Thread Arthur Barstow
On 10/7/11 8:32 AM, ext Julian Reschke wrote: As far as I recall, we agreed in the IETF WG that parsing of web socket URIs should work exactly the same way as for any other URI scheme. It appears that the API spec now tries to override this, and this looks problematic to me. On 10/7/11 9:30 AM

Re: RfC: LCWD of Web Socket API; comment deadline October 21

2011-10-07 Thread Ian Hickson
On Fri, 7 Oct 2011, Arthur Barstow wrote: > > Would you please elaborate on this change? Elaborate in what way? -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just ta

Re: RfC: LCWD of Web Socket API; comment deadline October 21

2011-10-07 Thread Arthur Barstow
Hi Hixie, In [1], Julian asks about Web Socket API rev 1.247 [2], the change that adds the Parsing WebSocket URLs section (CVS comment "Revert the part of r5409 that removed the URL parsing algorithms, since it's no longer defined in the protocol spec. (whatwg r6632)"). Would you please elab

Re: Spec changes for LCs and later maturity levels [Was: Re: RfC: LCWD of Web Socket API; comment deadline October 21]

2011-10-07 Thread Julian Reschke
On 2011-10-07 13:55, Arthur Barstow wrote: Hi Julian, All - I changed the subject to reflect the general process-related issue here. I will respond separately to the WebSocket specifics ... WebApps has always used the Edit First, Review Second process, as documented in our [WorkMode] document.

Spec changes for LCs and later maturity levels [Was: Re: RfC: LCWD of Web Socket API; comment deadline October 21]

2011-10-07 Thread Arthur Barstow
On 10/5/11 3:15 AM, ext Julian Reschke wrote: On 2011-09-29 18:28, Arthur Barstow wrote: On September 29, aLCWD of Web Sockets API was published: http://www.w3.org/TR/2011/WD-websockets-20110929/ Please send all comments to public-webapps@w3.org by October 21. I just noted that as of yesterd

Re: RfC: LCWD of Web Socket API; comment deadline October 21

2011-10-05 Thread Anne van Kesteren
On Wed, 05 Oct 2011 09:15:45 +0200, Julian Reschke wrote: What's the Webapps WG's procedure to manage changes during LC? We have another Last Call. -- Anne van Kesteren http://annevankesteren.nl/

Re: RfC: LCWD of Web Socket API; comment deadline October 21

2011-10-05 Thread Julian Reschke
On 2011-09-29 18:28, Arthur Barstow wrote: On September 29, aLCWD of Web Sockets API was published: http://www.w3.org/TR/2011/WD-websockets-20110929/ Please send all comments to public-webapps@w3.org by October 21. I just noted that as of yesterday, the API spec contains the custom URI parsi

Re: Biblio references and authors Re: RfC: LCWD of Web Socket API; comment deadline October 21

2011-09-30 Thread Marcos Caceres
On Friday, September 30, 2011 at 11:45 AM, Julian Reschke wrote: > On 2011-09-30 10:37, Marcos Caceres wrote: > > > > > > On Friday, September 30, 2011 at 10:26 AM, Julian Reschke wrote: > > > > > On 2011-09-29 18:28, Arthur Barstow wrote: > > > > On September 29, aLCWD of Web Sockets API wa

Re: Biblio references and authors Re: RfC: LCWD of Web Socket API; comment deadline October 21

2011-09-30 Thread Julian Reschke
On 2011-09-30 10:37, Marcos Caceres wrote: On Friday, September 30, 2011 at 10:26 AM, Julian Reschke wrote: On 2011-09-29 18:28, Arthur Barstow wrote: On September 29, aLCWD of Web Sockets API was published: http://www.w3.org/TR/2011/WD-websockets-20110929/ Please send all comments to publ

Re: Biblio references and authors Re: RfC: LCWD of Web Socket API; comment deadline October 21

2011-09-30 Thread Anne van Kesteren
On Fri, 30 Sep 2011 10:37:24 +0200, Marcos Caceres wrote: Might be good if we stop including the name of authors in the references (because they do tend to change quite a bit over time). The reference document is hyperlinked, so what is the use case for including the author in a reference?

Biblio references and authors Re: RfC: LCWD of Web Socket API; comment deadline October 21

2011-09-30 Thread Marcos Caceres
On Friday, September 30, 2011 at 10:26 AM, Julian Reschke wrote: > On 2011-09-29 18:28, Arthur Barstow wrote: > > On September 29, aLCWD of Web Sockets API was published: > > > > http://www.w3.org/TR/2011/WD-websockets-20110929/ > > > > Please send all comments to public-webapps@w3.org > > (m

Re: RfC: LCWD of Web Socket API; comment deadline October 21

2011-09-30 Thread Julian Reschke
On 2011-09-29 18:28, Arthur Barstow wrote: On September 29, aLCWD of Web Sockets API was published: http://www.w3.org/TR/2011/WD-websockets-20110929/ Please send all comments to public-webapps@w3.org by October 21. The reference for the Websocket Protocol (WSP) needs an updated author list.

RfC: LCWD of Web Socket API; comment deadline October 21

2011-09-29 Thread Arthur Barstow
On September 29, aLCWD of Web Sockets API was published: http://www.w3.org/TR/2011/WD-websockets-20110929/ Please send all comments to public-webapps@w3.org by October 21.