Sam Ruby wrote: > Now consider what happens when data is resyndicated (Planet XML, for > example). If such tools add a div element, and the div element is > considered part of the summary/content, then they are technically wrong. > But this will likely go unnoticed for a while as visually the results > appear correct. > > Now consider what happens if tools that implement the protocol do > likewise. Get a feed, modify an entry, and POST it. Over time, you > will end up with telescoping divs. > > The solution that some will likely come up with will be to ignore > enclosing divs.
Hmm.. considering DIV as being part of the summary is a bit like saying the <feed /> element in the content following example is part of the enclosing content... it just doesn't make sense.
<feed>
<entry>
<content ...>
<feed>
<entry/>
</feed>
</content>
</entry>
</feed>If a DIV is required for XHTML content, tools working with Atom should deal with it accordingly and properly without us having to specify a special handling case for XHTML content that does not apply to any other type of XML content.
If tools want to add additional div's in addition to the one in the content/summary, so be it, it is entirely up to that up to that particular tool to do implement its own brand of silliness.
- James M Snell
