On Friday, I opened up my mailbox and was pretty stoked to find that my copy of HTML5 for Web Designers by Jeremy Keith had finally arrived, just over two weeks after having ordered it (pretty good coming from the U.S. to Canada). I immediately sat down and started reading it, and finished it up yesterday. There’s a lot of really great material packed into those few short pages and I’m not going to try to dissect it all here.
Instead, I want to consider just one important aspect of this new HTML5 technology: the form of the code.
Prior to HTML5, the evolution of markup for the web had started taking its lead from XML (extensible markup language), which, though it is infinitely extensible through user defined tags, is also extremely and rigidly structured. So, after HTML 4.01, we had XHTML 1.0 which was identical to HTML 4.01 in terms of the tags that it supported, but which instituted an XML syntax, attempting to remove some of the looseness that tended to permeate different documents across the web.
Now, for XHTML to be considered valid, the tags all had to be in lower case, all tags had to be closed (according to the order in which they were opened) and all attributes value had to be contained in proper quotation marks. From my perspective, the benefits of this were several:






