W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

Re: CfC: publish a Candidate Recommendation of WebSockets API; deadline Nov 9

From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 03 Nov 2011 16:40:56 +0100
Message-ID: <4EB2B608.9070009@gmx.de>
To: Anne van Kesteren <annevk@opera.com>
CC: Arthur Barstow <art.barstow@nokia.com>, public-webapps <public-webapps@w3.org>
On 2011-11-03 16:29, Anne van Kesteren wrote:
> On Thu, 03 Nov 2011 07:50:08 -0700, Julian Reschke
> <julian.reschke@gmx.de> wrote:
>> On 2011-11-03 05:22, 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/
>>> ...
>> That specification has a new section "Parsing Websocket URLs" which is
>> broken in that it references algorithms in other specs without saying
>> so (see Anne's explanation from yesterday).
> It does say so, right in the dependency section.
> ...

That section says:

"2.1 Dependencies

This specification relies on several other underlying specifications.


     Many fundamental concepts from HTML are used by this specification. 

     The IDL blocks in this specification use the semantics of the 
WebIDL specification. [WEBIDL]"

How is a reader supposed to know that "resolve a URL", printed in bold, 
refers to a very specific algorithm in the HTML spec?

Best regards, Julian
Received on Thursday, 3 November 2011 15:41:36 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 13:55:45 UTC