HTML5 and XML (was: Re: meta content-language)

[This is somewhat off-topic for www-international, so please
feel free to remove that list in further replies (but maybe
some xml-related list should be added).]

At 23:10 08/08/22, Anne van Kesteren wrote:
>On Fri, 22 Aug 2008 15:04:26 +0100, Mark Davis  
><> wrote:
>> 2. Language Inheritance. If there are conflicting languages, what should
>> win? (or in other words, what's the inheritance?)
>> (HTTP) Content-Language: lang1
>> <meta http-equiv="Content-Language" content="lang2"/>
>> <html lang="lang4" xml:lang="lang3">
>> <p lang="lang5">
>> My take is that HTML5 has it right, that the winner/inheritance should  
>> be in
>> the above order: lang5 wins over lang4 over lang3 over lang2 over lang1.
>FWIW, this is largely right (interpretation of HTML5), but lang3 would be  
>ignored if it was "xml:lang" not in a namespace and would take precedence  
>over lang4 if it was "lang" in the XML namespace. (This is indeed slightly  

What do you mean by (a) "xml:lang" not in a namespace
                    (b) "lang" in the XML namespace

For (a), I assume this was intended to refer to cases where
the document doesn't contain an in-scope declaration of the form

Please note that the XML Namespace recommendation says:

Namespace constraint: Reserved Prefixes and Namespace Names

The prefix xml is by definition bound to the namespace name It MAY, but need not, be declared, and MUST NOT be bound to any other namespace name. Other prefixes MUST NOT be bound to this namespace name, and it MUST NOT be declared as the default namespace.

"need not[,] be declared" means that it is IMPOSSIBLE for
xml:lang not to be in a namespace.

As for (b), my guess is that this is supposed to denote cases with e.g.
and later

However, this would be a clear VIOLATION of the XML Namespace Rec.

Can you explain?

Regards,     Martin.

#-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University

Received on Monday, 25 August 2008 08:53:16 UTC