As someone working on the HTML 5 specification I thought it made sense to convert my weblog into valid HTML 5.
Nearly.
It is not quite valid in a few spots:
- I’m still using the “ IE hack to prevent the image toolbar feature from kicking in. I believe that’s still useful and I don’t clearly understand why the spec prevents me from doing it. Sean Fraser was confused too, posted about it and got Ian’s attention (scan the comments on Sean’s post). Update: Highly unlikely this will be part of HTML 5.
- My use of the footnotes feature in PHP Markdown Extra causes an issue because it utilizes a
revattribute onanchorelements.revis currently missing from the HTML 5 working draft but I believe that was done because not enough research had been done to support including it at the time. I’ve started a dialog with the maintainer of the PHP implementation of Markdown (Michel Fortin) in hopes of proposing a solution to the W3C HTML Working Group. - Anywhere I’ve just blindly embedded the YouTube cut & paste code has a problem. YouTube doesn’t automatically insert the
dataandtypeattributes on theirelements and that's a validation error. Given all of the issues withI think forcingdataandtypeis a good thing but the requirement does seem to fly against the “pave the cowpaths” design decision of HTML 5. Then again embedded YouTube videos hardly have any lasting meaning since I suspect many of these embedded uses will disappear with age in a very short period of time.
Though I’m about a year behind my swedish cohort my implementation makes use of the more experimental tags like ,, ,, and “ where possible. I’ll keep tweaking the format over time because there’s no way I’ve interpreted the spec 100% correctly.