On 1/30/08, Daniel Aleksandersen <[EMAIL PROTECTED]> wrote: > > Then what is wrong with the below? > > <summary type="xhtml" xmlns:xht="http://www.w3.org/1999/xhtml";> > <xht:p>Is this such a <xht:strong>bold</xht:strong> thing to do?</xht:p> > </summary> >
This has been discussed on the list a few times. If you haven't already, consider going through the archives if you're interested in seeing the rationale behind this decision. The chief benefit in my eyes is allowing for the ability to change the default namespace to improve the readability of your content's markup. It also underscores the fact that you're working with an XHTML document fragment, not an entire document. You should only feel comfortable putting content within the div element that you'd be comfortable putting within a div element inside of a real XHTML document. But does any of this really matter at this point? Even if there were good reasons to change this aspect of the standard, you'd introduce interoperability problems, because Atom implementations expect a div element to be there. If you make it optional, how would you unambiguously use a div element as a container for your content without some implementations trying to strip it out? You'd have to create some new mechanism to make the decision to strip it out explicit (and probably the default behavior), which means you're trading one oddity (div) for another (@strip-first-element="false").. David
