W3C home > Mailing lists > Public > public-html@w3.org > March 2010

(unknown charset) Re: Possible Conservative Proposal : no prefixes, but allow xmlns on a root element

From: (unknown charset) Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Mon, 22 Mar 2010 20:54:13 +0100
To: (unknown charset) Philip Taylor <pjt47@cam.ac.uk>
Cc: (unknown charset) "Ennals, Robert" <robert.ennals@intel.com>, "public-html@w3.org WG" <public-html@w3.org>, "Carr, Wayne" <wayne.carr@intel.com>
Message-ID: <20100322205413550980.d59582c7@xn--mlform-iua.no>
Philip Taylor, Mon, 22 Mar 2010 18:58:35 +0000:
> Ennals, Robert wrote:
>> [...]
>> *         If the browser encounters an unknown element with a default
>> namespace declaration, then it should apply that namespace to all
>> descendent nodes.
> 
> This looks like it will break content. E.g.:
> 
>   http://www.zapster.it/biografia/Suzy-Kendall/filmografia

>         <playlist version="1" xmlns="http://xspf.org/ns/0/">
>         <trackList>

> If the <playlist xmlns> causes the descendants to have the 
> http://xspf.org/ns/0/ namespace instead of the HTML namespace, then 
> they will no longer be rendered correctly as HTML links and images.

That <playlist> element on that page doesn't have an end tag. Perhaps 
the extension specification should require that it has - i.e. that it 
isn't interpreted as a namespaced section unless it is well formed XML. 
(Of course, such a rule only solves this particular case.) 
-- 
leif halvard silli
Received on Monday, 22 March 2010 19:54:51 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:59 UTC