Mark Nottingham wrote:
Using XPath as a yardstick, what's so complex about this?
/atom:feed/atom:entry[1]/atom:[EMAIL PROTECTED]'HTML'|@type='TEXT'][0]
I'm not even sure how I'd approach choosing between HTML and text in the current approach, where one is in atom:content and the other is referred to by atom:link; I'd need to use XSLT, I suspect.
If your software only wants to live in a world where entries have only one type of content, it's maybe a few lines of extra code to choose one, and no change to the database. Atom doesn't require you to persist all of the entry.
We dropped multiple content elements months ago, with good reason. Two of the more serious concerns were accessbility and the fact that nobody uses them in Atom 0.3. As I understand it, the only reason they were there originally was for uploading photos, an approach which is no longer necessary.
Robert Sayre
