Tuesday, April 10th, 2007

Proposal for the W3C to adopt HTML 5

Category: Editorial, HTML

Mozilla, Opera, and Apple have all come together to propose that the new HTML Working Group at the W3C adopt the HTML 5 work from WHATWG.

And before anyone shouts about patents, “Apple, Mozilla and Opera will agree to arrange a non-exclusive copyright assignment to the W3 Consortium”.

Considering the work that has been put into HTML 5, I think this proposal should be taken very seriously.

Here is the letter in full:

Dear HTML Working Group,

HTML5, comprising the Web Apps 1.0 and Web Forms 2.0 specifications,
is the product of many years of collaborative effort. It specifies
existing HTML4 markup and APIs with much clearer conformance criteria
for both implementations and documents. It specifies many useful
additions, in many cases drawing on features that have existed in
browser-based implementations for a long time. And it actively draws
on feedback from implementors and content authors. Therefore, we the
undersigned propose the following:

– that the W3C HTML Working Group adops the WHAT Working Group’s
HTML5 as the starting point for further HTML development
– that the W3C’s next-generation HTML specification is officially
named “HTML 5”
– that Ian Hickson is named as editor for the W3C’s HTML 5
specification, to preserve continuity with the existing WHATWG effort

If HTML5 is adopted as a starting point, the contents of the document
would still be up for review and revision, but we would start with
the existing text. A suitable next step might be a high-level review
of functionality added and removed relative to HTML4.01, followed by
focused discussion and review of individual topic areas, including
both content already in the spec and proposed new features.
Discussions should be guided by common principles along the lines of
<http://esw.w3.org/topic/HTML/ProposedDesignPrinciples>

If the group is agreeable to these proposals, Apple, Mozilla and
Opera will agree to arrange a non-exclusive copyright assignment to
the W3 Consortium for HTML5 specifications.

L. David Baron, Mozilla Foundation
Lars Erik Bolstad, Opera Software ASA
Brendan Eich, Mozilla Foundation
Dave Hyatt, Apple Inc.
HÃ¥kon Wium Lie, Opera Software ASA
Maciej Stachowiak, Apple Inc.

Posted by Dion Almaer at 1:14 pm
52 Comments

++++-
4.1 rating from 38 votes

52 Comments »

Comments feed TrackBack URI

I find the clean simplicity of HTML 5 much to my own liking. I write XHTML when I have to embed SVG and MathML, but otherwise I run with HTML 4.01 strict. I found I could get a validating HTML 5 page put together in under 30 seconds and without looking at reams of documentation. And the page displays in both IE7 and FireFox 2 – something the XHTML pages using an .xhtml extension and SVG fail to do (in IE7). HTML 5 simply works. Simple is better – may simpler carry the day.

Comment by Dana Lee Ling — September 21, 2007

All standards ultimately require you the designers, developers and programmers to support it. If you don’t want to support the proposed HTML5 spec, then don’t use it. Stick with XML-based specifications. Nobody is going to suddenly un-spec XHTML 1/2.

Frankly, it will be the browser developers that need to figure out how they are going to support all these different formats. Good luck and my sympathy to you folks (please make FF and IE work the same, without unexpected behaviours…).

All i ask is that the browser developers (all of them!) implement all these different specs to completion (dudes, I mean really finished, I can’t accept that, day jobs aside, some of the best developers in the world can only get 30-70% of the spec implemented).

Folks, I sincerely believe that if a developer is going to code bad, he/she is going to code bad whatever the language/spec (C, C++, C#, J#, Java, PHP, Perl, Python, HTML, XHTML, XML… there is bad code everywhere). And as long as we allow for margins of error (to err is human) somebody somewhere will exercise that margin (quirks mode anyone?).

Comment by Marcus Uy — October 28, 2007

Leave a comment

You must be logged in to post a comment.