canvas 2d context
Encrypted Media Extensions
HTML 5 spec
HTML 5: The Markup Language
HTML WG website
HTML5 differences from HTML4
HTML5 Spec - PR Blockers
Media Source Extensions
pre-LC1 alt techniques
pre-LC1 authoring guide
pre-LC1 HTML 5 spec
Erika Doyle Navara
Philippe Le Hégaret
Joshue O Connor
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):
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."
>>> 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
Add notes (no markup allowed, URIs get automatically hyperlinked):
Mike Smith and Ian Hickson discussed coordinating this work with the IETF
Seems worth point out that ACTION-38 is broadly looking at all charter+scope issues.
The Working Group agreed to the following resolution by consensus:
** RESOLUTION: WebSocket is out of scope for HTML5. **