ISSUE-64: Web Sockets API: in scope? requirement? coordination
web-sockets-scope-req
Web Sockets API: in scope? requirement? coordination
- State:
- CLOSED
- Product:
- HTML Principles/Requirements
- Raised by:
- Dan Connolly
- Opened on:
- 2008-12-02
- Description:
- 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.
]] - Related Actions Items:
- No related actions
- Related emails:
- Re: CfC: declare WebSockets out of scope (from mjs@apple.com on 2009-09-23)
- CfC: declare WebSockets out of scope (from mjs@apple.com on 2009-09-09)
- minutes for 2009-09-03 telcon (from mike@w3.org on 2009-09-05)
- Agenda for HTML WG telcon 2009-08-20 - Accessibility TF, HTML5 Test Suite, etc (from mjs@apple.com on 2009-09-01)
- {minutes} HTML WG telcon 2009-08-27 (from annevk@opera.com on 2009-08-27)
- {agenda} HTML WG telcon 2009-08-27 *PLEASE-READ* (from rubys@intertwingly.net on 2009-08-26)
- ISSUE-64: web-sockets-scope-req - suggest closing on 2009-09-03 (from mjs@apple.com on 2009-08-20)
- Re: ISSUE-64: web-sockets-scope-req (from mike@w3.org on 2009-03-27)
- Re: ISSUE-64: web-sockets-scope-req (from mike@w3.org on 2009-03-27)
- Re: ISSUE-64: web-sockets-scope-req (from rsayre@mozilla.com on 2009-03-26)
- ISSUE-64: web-sockets-scope-req (from rsayre@mozilla.com on 2009-03-26)
Related notes:
Mike Smith and Ian Hickson discussed coordinating this work with the IETF
http://krijnhoetmer.nl/irc-logs/whatwg/20081211#l-43
Seems worth point out that ACTION-38 is broadly looking at all charter+scope issues.
Shawn Medero, 8 Jan 2009, 18:15:31The Working Group agreed to the following resolution by consensus:
** RESOLUTION: WebSocket is out of scope for HTML5. **
Display change log
