Mark Nottingham wrote:
> [snip]
> ...new metadata can be added using extensions, rather than by versioning Atom.
It's also possible for new RFC's to update the current Atom namespace in
a backwards compatible way without deprecating/obsoleting RFC4287.
>> However, XHTML 2.0 will have a new namespace
>> "http://www.w3.org/2002/06/xhtml2/";, and the chance of having more
>> future versions of XHTML cannot be eliminated. Have Atom prepared for
>> this?
>
> This was intentional; if we allowed future, non-backwards compatible
> versions of HTML to appear in the same places that XHTML1 content is
> allowed, processors wouldn't know what to do with it unless they
> understood XHTML2. Tying the allowed content to a specific version of
> XHTML promotes interoperability.
>
That said, Atom can currently carry XHTML2 by specifying the media type
and properly declaring the namespace.
- James
