The slow normalization W3C blamed the WHATWG decided to support a continuous version of the HTML5 specification.
Not sure HTML5 needed this schism, especially as we remember the difficulties already encountered if only at the level of codecs to use for audio and video tags of language. The separation between the WHATWG and the W3C is not really a surprise at the time of the growing adoption of HTML5.
In 2004, the Working Group WHATWG (Web Hypertext Application Technology Working Group) has initiated the HTML5 specification. Work taken by the W3C in 2007 as a base with a view to developing a Web standard.
The WHATWG distances himself vis-à-vis W3C, clearly exasperated by the slowness of the W3C standardization which translates into reality through different lenses.
The WHATWG focuses on the development of a canonical description of HTML and related technologies, that is to say, correct errors as we find them, add new features as they become necessary and viable, and follow their implementation, says Ian Hickson.
Passed by Opera Software and Google today, the author Acid2 and Acid3 tests, and Web Applications 1.0 (HTML5 would become) points out that contrary W3C efforts are focused on creating a snapshot as developed the venerable W3C process.
This process is very thorough and explains the slow blamed by the WHATWG. The W3C believes that HTML5 will be a recommendation in 2014. Supported and pushed by vendors like Mozilla, Google, Apple and Opera Software, the WHATWG wants more responsiveness.
The WHATWG and HTML announcement Living Standard, a continuous version of the HTML5 specification. This model was actually already in place for several months. For its part, the W3C will continue to work for a version of HTML5 stopped with version numbers.
Both versions are likely to increase confusion around HTML5 implementations with different browsers, even if it is in fact already happening. A little puzzle in perspective for developers.
Revenue in the race of modern Web browsers since version 9 with the adoption of several standards and HTML5, Internet Explorer could suffer from this confusion. This falls badly for Microsoft Windows approach 8 and IE10 for running applications
