W3C home > Mailing lists > Public > www-tag@w3.org > July 2011

Re: Revised HTML/XML Task Force Report

From: Robin Berjon <robin@berjon.com>
Date: Thu, 14 Jul 2011 13:18:06 +0200
Cc: "www-tag@w3.org List" <www-tag@w3.org>
Message-Id: <C6F2C34C-3046-48D4-8D22-4B90C4F30403@berjon.com>
To: Larry Masinter <masinter@adobe.com>
On Jul 14, 2011, at 01:09 , Larry Masinter wrote:
> # XHTML requires element names to be lowercase, not XML.  In retrospect,
> # it would've made more sense for XHTML to require uppercase elements, as
> # this is how HTML parsers are supposed to normalize (and why Firebug,
> # etc. present the DOM using uppercase regardless of HTML/XHTML).  This
> # would have led to lots less script breakage for us application/xhtml+xml
> # die-hards.
> So why can't 'application/xhtml5+xml' (i.e., some other MIME type) use uppercase elements?

What would that accomplish that putting an HTML parser at the front of your XML processing pipeline won't achieve far more cheaply and without requiring tinkering with undeployed media types?

Robin Berjon - http://berjon.com/ - @robinberjon
Received on Thursday, 14 July 2011 11:18:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:39 UTC