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

RE: Revised HTML/XML Task Force Report

From: Larry Masinter <masinter@adobe.com>
Date: Wed, 13 Jul 2011 12:39:37 -0700
To: "Eric J. Bowman" <eric@bisonsystems.net>
CC: "karld@opera.com" <karld@opera.com>, "nrm@arcanedomain.com" <nrm@arcanedomain.com>, "www-tag@w3.org" <www-tag@w3.org>, "ndw@nwalsh.com" <ndw@nwalsh.com>
Message-ID: <C68CB012D9182D408CED7B884F441D4D05CB12A152@nambxv01a.corp.adobe.com>
> I suppose there's some design pattern "SIFR" which produces pages
> that cannot be expressed in polyglot? 

> *Why* can't "SIFR" be served as application/xhtml+xml? 

> See points 1 and 5, here:

> http://www.w3.org/TR/xhtml1/#C_13

> HTML normalizes to uppercase, XML doesn't; SIFR relies on uppercase
> normalization, breaks otherwise.

It seems like this could be fixed by XML, HTML, or CSS.    If the price of convergence of HTML and XML is making some change like this ("xml2" = "xml except it normalizes to uppercase" ?)

Why is normalization part of the XML definition at all? Isn't this just an odd artifact of CSS?
Received on Wednesday, 13 July 2011 19:40:32 UTC

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