In this blog, I will discuss the next HTML specifications created by the Web Hypertext Application Technology Working Group (WHATWG) and the World Wide Web Consortium (W3C) called HTML5. HTML5 is also referred to Web Applications 1.0 or X/HTML 5.
The official answer to what is the technology is (by the W3C): “HTML5 is a new version of HTML and XHTML. The HTML5 draft specification defines a single language that can be written in HTML and XML. It attempts to solve issues found in previous iterations of HTML and addresses the needs of Web Applications, an area previously not adequately covered by HTML” [1].
The WHATWG began work on the HTML5 specifications in June of 2004 with the name Web Applications 1.0. This group was created by members of the Opera, Mozilla, and Apple groups. These browser developers did not agree with the path of XHTML and W3C’s lack of concern in HTML. Also WHATWG believed W3C had an ‘apparent disregard for the needs of real-world authors.’ The main reason they wanted to develop HTML5 was to replace proprietary plug-ins such as Adobe Flash Player. By developing the new HTML specifications browsers could handle images and video correctly without relying on third party plug-ins.
The W3C finally jumped on the HTML5 bandwagon once they saw the direction it was going. The W3C initially did not want to join because they believed one person making all the decision can be bad. They figured this person would be Ian Hickson, of Google, and one of the leaders of WHATWG. Hickson’s rebuttal to this was: “They have as much power as I do. 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.” The W3C created their first HTML5 working draft in January 2008.
Today Ian Hickson is the editor for the HTML specifications on both W3C and WHATWG teams. Also, both groups participate in creating specifications and managing HTML5.
Most websites on the World Wide Web today were created in an earlier version of HTML; however a few sites have been created with HTML5. Upgrading to HTML5 is as simple as changing the doctype element on current Web pages. Some developers have already changed this element even though HTML5 is not complete. Their reasoning is HTML4 is still supported but this change will allow a developer to use and validate the new elements. The new starting tagline for HTML5 is simply <!DOCTYPE html>, which appears to be much shorter that the earlier versions of HTML.
Another great item in HTML5 is developers will not need to throw away the markup they already know. Web applications that work with HTML4 should still work with HTML5. Ian Hickson states, “If we required browsers to refuse those documents, then you couldn’t browse over 90% of the Web,” referring to putting an end to the “tag soup”.
Some of the new features are: <nav> for website a navigation block; <header> and <footer> for a header and footer block; <audio> and <video> tags have also been added to work similar to the current img tag. In addition to the previously mentioned tag lines there are now new API’s. Some examples are: A canvas element, timed media playback, offline storage database, document editing, drag-and-drop, sliders, and date pickers.
For a list of all the new features, check out: http://diveintohtml5.org/peeks-pokes-and-pointers.html
One of the new attributes I am most excited about is the HTML5 video element. Currently Adobe’s Flash Player is the most widely used embedded video software on the internet and many browsers now come with the Flash Player already installed. HTML5 video is intended to become the new standard in a way to play videos, but there has been some debate on which video formats to support. Once this technology is developed it should put an end to the required third-party proprietary software.
Some items that already work with HTML5 are: draw on a canvas, play video, design better forms, build web applications that work offline and the new HTML is supported in Firefox, Safari, Chrome, Opera. Microsoft’s Internet Explorer 9 should support these features as well.
There is also a possibility of HTML5 including more accessibility features such as incorporating voice recognition and speech synthesis interfaces within Web pages. Another feature in the draft, I believe will be helpful, is the scoped stylesheet which allows a <style> element to be put in the document itself with the content. This would allow only that content to by styled in that manner. Also, most developers would find the new <datagrid> tag useful. This tag would allow a tree view list control for AJAX-backed data stores.
The future of HTML5 is questionable. I do not mean by it will fail but on when the final version will be released. Some predict it could take up to 2022 to have all of the specifications done. I assume if it does take that long the new features will roll into place just as soon as they are finished, on-the-fly.
Examples of HTML5 in use today can be found here: http://html5demos.com/
Certifications:
I was unable to find anyone who offers HTML5 certifications as of yet. I am sure once it has been fully implemented and the final version released, there will be many certification schools.
Sources:
[1] – http://html5.org/
http://en.wikipedia.org/wiki/HTML5
http://en.wikipedia.org/wiki/HTML5_video
http://diveintohtml5.org/introduction.html
http://xhtml.com/en/future/conversation-with-x-html-5-team/
http://www.computerworld.com/s/article/9183841/HTML5_may_help_Web_pages_talk_listen
http://wiki.whatwg.org/wiki/FAQ
http://inventorspot.com/articles/html5_being_developed_replace_need_proprietary_flash_plugins_37356
http://www.dharne.com/blog/2010/04/06/the-5-most-important-features-of-html5/
http://www.itwriting.com/blog/2353-the-two-specifications-of-html-5-0-what-wg-vs-w3c.html
http://www.satya-weblog.com/2010/06/fight-between-whatwg-w3c-fight-html5-specification.html