Very good discussion posted by Stephen Shankland about new HTML specification (HTML5), W3C, WHATWG and few very important persons involved in development of new specification for HTML5. I have found the post very interesting and useful for all those who are related to web development.
He discussed about state of HTML5, its readiness to come fully to developers, W3C takes on new features on HTML5 and what is going on within W3C and WHATWG. He also discusses about the differences appearing between two bodies - W3C and WHATWG. Along with all the above, he also talks about the key players in whole of episode.
Few interesting paragraphs from there:
Those producing the specification show an HTML governance process that can be stormy, fractious, and far from settled down.
The W3C released the most recent version, 4.01, an eternity ago, in 1999. When the W3C pursued an incompatible, and largely unsuccessful alternative called XHTML 2 and refused to amend HTML, browser makers Opera Software, Mozilla, and Apple formed the WHATWG to make their advancements regardless.
Where developers will find specification for HTML5 - at W3C site or WHATWG?
You know lots of features of HTML5 are already in market and many are ready to come. So, W3C want to be a part of it.
The World Wide Web Consortium's return to HTML standardization after years of absence has produced tensions with the more informal Web Hypertext Application Working Group (WHATWG) that shouldered the HTML burden during that absence.
This is the sad reality of spec writing: if the implementers disagree with what the spec says, they'll do what they want, and the spec becomes just a very dry form of science fiction.
"Ian is a very capable person, but he believes that the best, quickest way to create a specification is if one person makes all the decisions about what is in a specification. Ian also has strong, rather inflexible, opinions about the future of the Web, and the future of HTML. One person with such strong, inflexible opinions, and with virtually unlimited control over the HTML5 specification contents, is not a good thing," Powers said.
Hickson has garnered plenty of respect as he's tackled Herculean tasks--for one example, see his 23,000-word attempt to assess and respond to more than 620 e-mails concerning mathematical text and Scalable Vector Graphics in HTML. But he's also raised hackles.
"They have as much power as I do," Hickson said. "Seriously--the spec is licensed under a completely open license, anyone can take it and edit it and have the same level of 'control' as I do. All they have to do is do a better job in the eyes of the browser vendors."
There are many interesting paragraphs on HTML5, W3C and people around them.
Read the complete story here: Growing pains afflict HTML5 standardization