W3C has now expressed its wishes for recommending HTML5 specifications. Which means that HTML5 would come across as an all-inclusive, complete standard by 2014 end. And it would be subsequently bringing out HTML5.1 in 2016 end.
This new plan would have HTML working group create an HTML5 Candidate Recommendation (CR) by 2012 end; containing just those elements that are stable, specified and are implemented in actual browsers. So, all the things that are debatable would not make it to this specification. It also plans to get rid of the stuff that is known to give interoperability troubles among current implementations. The CR would be the foundation of the HTML5 spec.
In sync with this, an HTML5.1 draft would also be created. It would incorporate things right from HTML5.0 CR to each of the things that won’t be put to use in 2014. Again the same process would be followed, elements that are unstable would be gotten rid of, so as to prepare an HTML 5.1 CR. This will create room for an HTML 5.2 draft. And likewise the same pattern would be adopted in version 5.3, 5.4 and ahead.
The earlier speculations showed a different picture altogether, where HTML5 was not getting finished till 2022 (nearly a decade from now). While the CR was supposed to be delivered around this time, the coming 10 years would have gone into creating a wide-spread test suite to permit conformity testing of implementations. The HTML5.1 would be smaller, since many technologies (like WebSockets and Web Workers) which were at one point under the HTML5 family, have now separated and become particular specifications. It would have less strict testing requirements too.
The standardization of HTML5 has been a fussy topic so far, along with adulation and disagreements, it has seen people warring over separate point of views.
The new move by W3C also admitted that ‘this disagreement has made the scenario quite bitter’ and that the Working group will have to pull up its socks to deal with it. W3C also expressed that the new plan also wasn’t exactly welcomed by everyone. Certain Working group people were in fact unsatisfied with the projected handling of their specific skills.
To the web developers, there won’t be much of a difference, as they’re already familiar with working from draft specs on everyday basis. Its foremost result would be that those things that are viewed as proper for insertion in HTML 5 shall obtain a better test suite. And successively, that would assist the browser developers discover any left out inconsistencies and bugs.
The fact that HTML5 would be finally seeing the light of the day sooner is a big development in itself. As with such opposition and uproar, reaching a consensus had seemed an improbability.
Ajeet Yadav is a seasoned Technical Writer with http://www.xhtmljunction.com/