Antone Roundy wrote:
With @type="text" there is no container, neither with @type="html", so why should there be a container with @type="xhtml"?
Because it's XML in XML, which raises issues that don't exist for "text" and "html".
Yes, but it's still "content".
Some people prefer to switch default namespace when doing XML in XML.
If the XHTML content they're putting into atom:content isn't already
surrounded by a single element where that switch can be made, adding
a container to hold the namespace declaration is a common way of doing it.
...so they can use meaningless divs or spans containers, depending whether they have block or inline content.
And some people prefer having a clean, needless-container-free feed, using prefixes and declaring namespaces in the enclosing element (or any of its ancestors).
Just for carrying the xmlns declaration? Well, you'd better define it once in the feed element...
You can argue that that's a better method, but we have already discussed and rejected the idea of mandating that the namespace be declared in a particular place or a particular way.
I'm not trying to mandate anything!
And you're right: I'm just arguing that that's a better method.
What's the matter with having the entry content inside an XHTML div, itself being considered part of the content? A div element in (X)HTML has only a structural meaning. If the entry content is to be rendered as part of an XHTML document (as in a Web aggregator, or in a blog for example when Atom is used as a publishing protocol/syntax) and included inside a div element, the duplicate divs won't change anything to the document structure, there'll just be a needless duplicate div...
See http://www.imc.org/atom-syntax/mail-archive/msg14238.html for my response.
And putting a title in a div, therefore allowing paragraphs in it, does not disturb you?
I don't think we're going to oust the required container div unless we replace it with something. Between the options of having a required container div and having an optional attribute to indicate whether you're using a container div, which would you prefer?
The third option: using a "div" container when I want block- and "span" when I want inline-content.
However, I personally actually prefer using an "atom" prefix for Atom elements and no prefix for XHTML...
-- Thomas Broyer
