In previous years finding information regarding the state of HTML5 was a tiresome and daunting task; however as time progressed the specification of HTML5 became more easily accessible.
Who's Behind HTML5?
A simple way to understand the concept of HTML is to understand the two main players working toward enriching the World Wide Web. The WHATWG (Web Hypertext Application Technology Working Group) creates HTML5 specification using the process called “commit then review.” The WHATWG group has summarized steps on how to participate in the development of HTML 5. The second group is the W3C (World Wide Web Consortium) which is an organization where members of top technological organizations and the public work together to ensure web standards. The W3C uses it's HTML working group as taking specification and putting it through its process of “review then commit” format.
Whats Next in HTML5?
Perhaps the most confusing issue for web designers diving into the waters of HTML5 is getting an answer to the question, “when will it be ready?” If you are not a fan of reading specifications or feel overwhelmed with the overall process; the best way to fully grasp the concept of HTML5 is by using the actual markup. By using HTML5 today has its benefits such as: cleaner markup, new form input types, a great selling point for future clients as not many designers have migrated from HTML4. However, HTML5 does have its benefits there are also some adverse effects in implementing HTML5 at an early date. Firstly, the specifications are not complete and are subject to change. Secondly, not all major browsers support certain elements of current HTML5 markup thus making cross-browser testing difficult and harder to correct in multiple browsers.
The date many expect on the release date of HTML5 is 2012. The date is suggested as the specification's due date will become a “candidate recommendation.” For those not in the industry; that means “done and ready for use.” However, the true due date is not when both organization agree on finalized language, but when browsers start supporting the new HTML5 markup.
For instance observe the browser support for CSS3. Whether “killing” an outdated browser is what calls for new technology (think IE6 for web development) then it would be quite difficult to declare a date that the language is ready for use. HTML5 should not be seen as a “revolution” but more as an a evolution. As browsers start supporting the language is a good indication as to when you can start implementing HTML5 in your next project.