W3C home > Mailing lists > Public > public-html@w3.org > February 2009

Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"

From: Karl Dubost <karl+w3c@la-grange.net>
Date: Tue, 17 Feb 2009 09:14:04 +0900
Cc: Larry Masinter <masinter@adobe.com>, Lachlan Hunt <lachlan.hunt@lachy.id.au>, HTML WG <public-html@w3.org>
Message-Id: <8F74C174-D3EF-47DB-9AE4-A5F57E594A6A@la-grange.net>
To: Maciej Stachowiak <mjs@apple.com>

Le 17 févr. 2009 à 04:23, Maciej Stachowiak a écrit :
>> So I would propose instead:
>> a)  XHTML5 *MUST NOT* be used in arbitrary generic XML compound  
>> documents. Any
>>  use of the namespace in such contexts denotes XHTML2, not XHTML5.
>>  Since HTML5 and XHTML5 are not being designed for inclusion in  
>> arbitrary
>>  XML compound documents, this should not have any impact in practice.
>
> Since this proposal is based on a false premise I do not think it is  
> viable. Further, since user agents in practice support XHTML  
> namespace elements in arbitrary XML compound documents, this would  
> amount to requiring XHTML5 user agents to implement XHTML2, which is  
> not a reasonable requirement.


It has consequences already. The namespace is used in other formats  
such as

1. [Atom Syndication Format][1]
The reference given for the namespace/xhtml markup is [Modularization  
of XHTML][2]

    3.1.1.3. XHTML
    If the value of "type" is "xhtml", the content
    of the Text construct MUST be a single XHTML div
    element [XHTML] and SHOULD be suitable for
    handling as XHTML. The XHTML div element itself
    MUST NOT be considered part of the content. Atom
    Processors that display the content MAY use the
    markup to aid in displaying it. The escaped
    versions of characters such as "&" and ">"
    represent those characters, not markup.



2. [XMPP XHTML-IM][3]

    XMPP references also Modularization of XHTML.

    4. Concepts and Approach
    However, this <html/> element is used solely as
    a "wrapper" for the XHTML content itself, which
    content is encapsulated via one or more <body/>
    elements qualified by the
    'http://www.w3.org/1999/xhtml' namespace, along
    with appropriate child elements thereof.





[1]: http://tools.ietf.org/html/rfc4287#section-3.1.1.3
[2]: http://tools.ietf.org/html/rfc4287#ref-XHTML
[3]: http://xmpp.org/extensions/xep-0071.html

-- 
Karl Dubost
Montréal, QC, Canada
http://twitter.com/karlpro
Received on Tuesday, 17 February 2009 00:14:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:31 GMT