swa66 - 9:37 am on Mar 29, 2013 (gmt 0)
is a contradio in terminis.
You need to be able to reference to a standard (even in plain writing), having it as a moving target is a bad idea.
A real standard (one that's not a moving target) is e.g. needed in contracts between a web developer and a site owner. You can't validate the work if the standard you agreed upon shifted (maybe or maybe not) during the work.
Standards are designed to create order in the chaos. What watwg is doing is create chaos cause the browser makers like it that way aparently.
The dtd for HTML 5
That's another of those "bright" ideas: they dot rid of that pesky dtd as it was enabling us to say "invalid" all too easy.
I'm no fan of the dumbing down, but whatwg is runninng the show for now and (x)html5 it is. So I'm sticking to try to make due with polyglot (x)html5. It's a pity though 3rd parties such as Google make their stuff like e.g. adsense so archaic that it still uses document.write after all these years (document.write is illegal in xml delivered html).
The tag soup promotion in the html5 specs and the attitude of everything is optional is just pain wrong. Sure the browser could accept things to be less than perfect and try to make it work anyway, but at least tell those crafting software that generates html or those that write html by hand how it should be (and there it *must* be as perfect as possible to allow the browsers as little room as possible to have to resort to guessing what was meant.
Anyway, html5 it is for now - till we can get some more enlightened people back at the helm and make html6 :)