Antone Roundy wrote:
Could we drop the xhtml:div requirement in [EMAIL PROTECTED]"xhtml"],
+1
and instead clarify the status of the div that is commonly being put there (is it part of the content or not?)
+1
by adding an attribute to atom:content
-1
Let me explain my point of view:
With @type="text" there is no container, neither with @type="html", so why should there be a container with @type="xhtml"?
Just for carrying the xmlns declaration? Well, you'd better define it once in the feed element...
Just to allow for prefix-free Atom documents? See below about "legacy Atom" documents.
So what about those existing Atom documents (0.3 or draft-ietf-atompub-format-07) using a div container? Well, keep them as they are!
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...
So someone willing to use a div container in its Atom documents (e.g. to produce prefix-free documents, by declaring the XHTML namespace on the div) can do it as it won't change anything!
-- Thomas Broyer
