I’m going to make a bold prediction. Long after you and I are gone, HTML will still be around.

Much of the excitement we’ve seen so far about HTML5 has been for the new APIs: local storage, application cache, Web workers, 2-D drawing and the like. But let’s not overlook that **HTML5 brings us 30 new elements to mark up documents and applications**, boosting the total number of elements available to us to over 100.

Ich habe glaube ich noch keinen einzigen Talk über HTML5 gehalten, in dem ich nicht auf diese Karte des HTML5-Universums zurückgegriffen habe

»This piece of information makes building an HTML5 compatibility shim for IE7 far easier than had previously been assumed.«

By Heydon Pickering. Nobody wants them, but Heydon is a purist and explains it beautifully. Whatever you call them — blocks, boxes, areas, regions — we’ve been dividing our Web pages into visible sections for well over a decade. The problem is, we’ve never had the right tools to do so. While our interfaces look all the world like grids, the underlying structure has been cobbled together from numbered headings and unsemantic helper elements; an unbridled stream of content at odds with its own box-like appearance.

The blockquote, cite and q elements are very useful… especially if they are used for the purposes for which they were intended. Together with the other HTML writing elements, you have a full and rich set of markup elements with which to start treating your content. Mit footer zur Kennzeichnung der Quelle. Coole Idee.

Yesterday Steve Faulkner made me aware that the W3C had changed the HTML 5.2 specification to reflect the common interpretation of the element, much to their credit.

»For the last few years, the HTML5 specification has included a warning about the lack of implementations and has suggested that the document outline algorithm not be relied upon to convey heading semantics to users. Recently this has been taken a step further. Now the HTML 5.1 specification  requires developers to use h1-h6 to convey document structure. The simple reason for this change is that the HTML5 document outline is not implemented and despite efforts to get it implemented, the general response from user agent developers has not been enthusiastic. «