It’s just data

HTML5 Update

Two significant events happened this week in the portions of the W3C where I happen to frequent.

First, the HTML Working Group published a new Working Draft.  Mark Pilgrim published a excellent overview of the changes.  This wasn’t exactly an uncontentious event, it included first resolving 5 separate issues and then resolving whether or not to include issue markers in the published draft.  The initial decision on that final question was to NOT include issue markers, but if you look closely issue markers are present as the problem that people had with issues markers themselves was addressed, due in part to a first installment of a cleanup of the issues list itself by Maciej and by the automation of the inclusion of issue markers done by James Graham.  Ian adopted the approach and Manu approved of the results.

Second, Chris Wilson stepped down as co-chair, and was immediately replaced by Paul Cotton of Microsoft and Maciej Stachowiak of Apple.  I hope I last as long as Chris did, and look forward to working with Paul and Maciej.

Pivotal issues include ARIA, Canvas Accessibility, RDFa and Distributed ExtensibilityNormative Language Reference and HTML Versioning are potential sleeper items, the former is essentially an epistemological question, and the TAG is on the case for the latter one.

A lot of people are working hard to get to the point where we hopefully can have a Last Call this year with the prior concurrence not only the WHATWG, but also including Microsoft and the related Working Groups inside of the W3C including the WAI and SW communities.

Sam Ruby: HTML5 Update

Sam Ruby: HTML5 Update Thu 27 Aug 2009 at 19:31Two significant events happened this week in the portions of the W3C where I happen to frequent.First, the HTML Working Group published a new Working Draft.  Mark Pilgrim pub... vantguarde W3C , HTML...

Excerpt from はてなブックマーク - Bookmayuk - お気に入り at

It seems the main line of thought was, “I like the idea of highlighting the issues, but it shouldn’t be added to the public spec.”
Everything turned out remarkably well!

Posted by Michael Kozakewich at

What’s the problem with ARIA exactly? It seems to be integrated into HTML 5 already.

Posted by Ms2ger at

Ms2ger: my understanding is that there is a lot of unanswered questions.  Also, what appeared in the document was with pretty much zero rationale, and PF/WAI is working on feedback.

Posted by Sam Ruby at

What is it with these specifications and going ludicrously far beyond what people want and is practical to implement? People want an animated form of PNG, so what gets produced is MNG which tries to do everything animated possible. People want a vector graphics format for the internet, instead we get SVG which was apparently designed to also be a Flash-killer, so that the most popular open source browser still doesn’t support it in IMG tags or as an image format in CSS because the developers are getting hung up over security implications. The HTML5 approach proves that these lessons have still not been learned: it’s trying to be a document format and a web application toolkit and god knows what else all in one.

Posted by andy at

Interesting. Aside from ARIA this list seems to reflect most of the concerns I recently wrote about.

Good luck to you, Paul, and Maciej as you move HTML 5 to Last Call.

Posted by Shelley at

Add your comment