W3C home > Mailing lists > Public > public-html@w3.org > March 2009

Re: ISSUE-64: web-sockets-scope-req

From: Michael(tm) Smith <mike@w3.org>
Date: Fri, 27 Mar 2009 13:48:35 +0900
To: Rob Sayre <rsayre@mozilla.com>
Cc: public-html@w3.org
Message-ID: <20090327044834.GF6152@sideshowbarker>
OK, I've updated the text of the issue-64 description to read in full:

  Original issue description:
  [[
  IETF area directors have expressed concerns about network
  protocol specs buried in the HTML 5 specs.

  Is this something the WG supports as a requirement for this release?

  Who is interested in contributing test materials for web sockets?
  ]]

  Some clarifications (from Rob Sayre):
  [[
  http://lists.w3.org/Archives/Public/public-html/2009Mar/0653.html
  Something like Web Sockets is explicitly mentioned in the charter. 
  From section 2.1 of the charter:

  "The following features are expected to be obtained by integrating
  deliverables of the Web APIs Working Group
  <http://www.w3.org/2006/webapi/>. They are listed here so that they may be
  developed in the case where the Web APIs Working Group is not able to
  produce the specifications.

     * Data storage APIs.
     * Networking APIs for server-push, asynchronous two-way
       client-server communication, peer-to-peer communication, and
       client-side cross-domain communication.

  Note that some of the features mentioned above may be obtained by
  integrating deliverables of the Web APIs Working Group."
  ]]
  [[
  http://lists.w3.org/Archives/Public/public-html/2009Mar/0657.html
  [[
  >>> Web Sockets API: in scope?

  The charter places it in scope. No need for a question.

  An obnoxiously literal reading could exclude this capability as a hard
  requirement, but such a reading would also preclude accepting a solution
  developed in the IETF.

  I claim that the spirit of the charter assigns the HTML WG to develop a
  solution if an acceptable solution does not emerge from elsewhere in a
  timely fashion.
  ]]

Rob Sayre <rsayre@mozilla.com>, 2009-03-26 20:27 -0700:

>  On 3/26/09 8:10 PM, Michael(tm) Smith wrote:
> > Rob Sayre<rsayre@mozilla.com>, 2009-03-26 16:59 -0700:
> >
> >    
> >>   Something like Web Sockets is explicitly mentioned in the charter. I 
> >> would
> >>   like the issue updated to reflect this reality.
> >>      
> >
> > Updated in what way? Do you mean the text of the description field
> > should be changed? If so, do you have some proposed text?
> >    
> 
>  Here's some text from the issue:
> 
>  >>> Web Sockets API: in scope?
> 
>  The charter places it in scope. No need for a question.
> 
>  >>> requirement? coordination
>  >>> Is this something the WG supports as a requirement for this release? Who 
>  is interested in contributing test materials for web sockets?
> 
>  An obnoxiously literal reading could exclude this capability as a hard 
>  requirement, but such a reading would also preclude accepting a solution 
>  developed in the IETF.
> 
>  I claim that the spirit of the charter assigns the HTML WG to develop a 
>  solution if an acceptable solution does not emerge from elsewhere in a 
>  timely fashion.
> 
>  - Rob

-- 
Michael(tm) Smith
http://people.w3.org/mike/
Received on Friday, 27 March 2009 04:48:50 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:44 UTC