SuzyUK - 11:05 am on Mar 9, 2007 (gmt 0)

By all means bring on the next wave of HTML but give us ways to verify that applications have met compliance so we know where the flaws are in advance and don't spin our wheels fighting cross-platform issues.

Isn't that what XHTML transitional 'validation' has all been about? - nothing to do with serving the "correct" mime-type or whether or not pages validated XHTML1.1 strict or required XML - was it not simply a way to be "next step" ready while still getting on with the day job - e.g. lowercase tags and attributes, quoted attributes, closed elements etc.. all of these are important in other languages used in application building - why not HTML

This group will maintain and produce incremental revisions to the HTML specification, which includes the series of specifications previously published as XHTML version 1

Will HTML5 will be no more (apart from some new elements perhaps) than XHTML1 with the namespace and content-type doing the rest?

If they adopt the WhatWG working draft [whatwg.org] then it seems so

interesting times are ahead no doubt and Good to see ALL the majors involved :)

[edited by: SuzyUK at 11:08 am (utc) on Mar. 9, 2007]