There is no doubt about it, HTML5 is the technology buzzword in e-learning today, but we've found many people are still trying to understand exactly what it is, and what it can do for you.
So, what is HTML5?
HTML5 is the name used to refer to the current HTML standard. This standard defines many things, but at a high level it defines:
- New markup elements: These are tags that are new to the syntax of HTML.
- Deprecated and obsolete elements: These are tags that should not be used. Deprecated tags will cause a warning if a validation tool is used to verify the code, obsolete tags will cause code to fail validation completely.
- Microdata: This specifies a means for encoding machine-readable labels for the content of the document, which can be exposed in a variety of ways.
There are several other elements of the specification, but these are generally of interest to implementors (those who create and distribute web browsers) and web developers working to build web applications.
Some of the more technically-inclined may notice that CSS isn't mentioned at all, despite the fact that many browsers have newly added support for some very advanced features of that technology. While CSS is used in conjunction with HTML to produce web content, the language is in fact not a part of the HTML standard, but is instead driven by it's own standard. A working draft document on the W3C website describes the status of the modules for the next version, CSS3 http://www.w3.org/TR/css3-roadmap/.
What HTML5 isn't
We have been seeing a lot of confusion in the e-learning space, and much of that confusion seems to revolve around what HTML5 isn't. HTML5 is not:
Anyone who has been doing serious web development for the last few years knows this simply is not the case. We have been using all 3 of those technologies together to create interactive non-Flash content for years; there was nothing in the previous version of HTML that prevented us from doing so in any way.
- Different than HTML
This is another misconception that I've encountered, the idea that the HTML that has been powering the Web for these many years is somehow a different technology than HTML5. In fact, we've found that people assume any existing HTML content requires a significant effort to upgrade or port to HTML5. The truth is that HTML5 is simply the next version of the HTML standard, and with the exception of a few obsolete elements, the new standard includes everything from the last published standard (HTML 4.01). In fact, a quick example can demonstrate just how easy it is to update existing HTML content:
First, the 'old' HTML code:
&lt;!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4
&lt;TITLE&gt;My first HTML document&lt;/TITLE&gt;
Next, the HTML5 version:
&lt;TITLE&gt;My first HTML document&lt;/TITLE&gt;
Note the only difference between the 2 is the line starting with <!DOCTYPE. This identifies the type of document that follows, in the first example the document is identified as being HTML 4.01, in the second the new HTML declaration is used. After that, the code is completely identical. This is because the code is perfectly valid in either version of the standard, the most recent version of which can be seen at http://whatwg.org/html
The current version of the HTML standard is by no means complete. There are 2 places on the web one can view the HTML5 standard, http://whatwg.org/html and http://www.w3.org/TR/html5/, both of which make the point that the draft is not finished. Ian Hickson, the specification editor with the Web Hypertext Applications Technology Working Group, or WHATWG, nicely sums up the reason for the currently incomplete status in a blog post http://blog.whatwg.org/html-is-the-new-html5. In fact it is this ever-changing nature of the standard that prompted the WHATWG to decide to drop numbered versions from the standard, and instead declare the current HTML standard to be a living document. It is still correct to refer to HTML5 as the World Wide Web Consortium (W3C) is still working to create a 'snapshot' specification encompassing HTML5. The HTML5 specification is to be completed in 2014, at which point the W3C will begin working on the next snapshot, currently called HTML.next.
And as the HTML standard continues to evolve, dominKnow will evolve it's authoring technology right along with it.
What does this all mean?
At this point, you might be wondering what HTML5 means to you as an author of learning content. For many, the most exciting new additions are the <audio> and <video> tags. These tags allow web content authors to deliver audio and video files over the web without having to rely on browser plugins. This is especially exciting when developing content for mobile devices, where in many instances common browser plugins such as the Flash Player currently cannot run. While there is still some controversy over the exact format of the files that browsers should support, most mobile browsers use a common encoding format. An excellent dive into the world of the new native media tags can be found at http://www.diveintohtml5.com/video.html. These tags are supported on most of the modern mobile smartphone and tablet platforms, including Apple's iOS, Google's Android, HP's webOS and the latest version of RIM's Blackberry smartphone and their tablet operating systems.
The advancements in the latest specification of the HTML standard represent an exciting time for everyone involved with creating web content; we are seeing the means for producing ever more engaging and interactive content for our learners. However, it's important to know your audience, as those with older browsers won't have the ability to take advantage of these features. When planning your content, ensure there is a fallback in place for these browsers, so you're content will function for as wide an audience as possible.
These are just a few of the highlights in the new HTML standard. The important point to come away with from this is when evaluating new authoring technologies, simply asking for a 'yes' or 'no' answer on HTML5 as a whole is insufficient. It is important to understand what features are important to you as a developer, and to ask technology vendors about the support of those specific features.
With Claro, our next generation authoring tool, we're committed to taking advantage of as many new HTML features as we can, while still ensuring the content produced will continue to function in older browsers that may not support these new advancements.
Ryan McIlmoyl is Chief Software Architect at dominKnow