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
The HTTP specification, in section 14.17 Content-Type, says The Content-Type entity-header field indicates the media type of the entity-body sent to the recipient.
The HTML 5 specification specifies an algorithm for determining content types based on widely deployed practices and software.
To the extent these specifications overlap, the IETF HTTP Working Group has a right of review.
Re: Proposed Design Principles updated ("don't break the web" vs respecting MIME types)
review of content type rules by IETF/HTTP community
suggestions for default character encoding section
Add notes (no markup allowed, URIs get automatically hyperlinked):
The design seems somewhat stable within the HTML WG... haven't seen much new information lately... main concern at this point is coordination with IETF HTTP WG, TAG, etc.
Data found during Google Chrome development:
hmm... I wonder how this got closed; I don't remember any sort of "any objections?" message/poll. I think I would have objected to the current editor's draft.
not sure how/why this got closed; changing back to RAISED
[DanC]: note http://trac.tools.ietf.org/wg/httpbis/trac/ticket/155
"If referencing an unstable external spec is an issue, we can raise that separately."
seems like unnecessary churning. This "issue" has all the history, and moving the specs around in the IETF don't warrent closing one issue and raising another.