Smashing Magazine has a cool “cheat sheet” for those interested in the ongoing development of HTML 5. Of interest is what’s being excluded and what’s new, as well as the length of time it’s html5-logogoing to take before HTML 5 is completely supported:

XHTML is dead, long live HTML 5! According to W3C News Archive, XHTML 2 working group is expected to stop work end of 2009 and W3C is planning to increase resources on HTML 5 instead. And even although HTML 5 won’t be completely supported until 2022, it doesn’t mean that it won’t be widely adopted within the foreseeable future.

Part of the “completely supported” should include, if necessary, application infrastructure: load balancing, acceleration, caching, and security. Because these types of infrastructure solutions are not only aware of content but rely upon it as actionable data for decision making processes it’s important to consider early how changes to the specification might impact that application infrastructure.

One of the big changes in HTML 5 that leaps out in terms of infrastructure is that it’s getting more granular about content. Rather than being limited to the generic or tags, for example, HTML 5 thus far includes