On Feb 1, 2005, at 10:17 AM, Graham wrote:
There's an awful lot more to an aggregator than the 3 lines that pull stuff out of XML. My problem is that users want to see the content in their preferred language, which means I have to provide some mechanism to choose, which may end up being the most complex part of a simple app.
I agree that varying representations in the feed by language isn't productive, when you can vary the whole feed by language. I haven't been arguing that we should allow variance by language.
To be clear, I'm less interested in allowing people to put multiple representations in the feed (although I think it should be possible; e.g., for archiving -- which we're chartered to enable) than I am in making sure people understand that it's possible to have more than one representation for a resource.
So, I'm not going to lie in the road to defend multiple content, but would ask for an adjustment in the language to clarify things;
From:
[[[ 4.15 The "atom:content" Element
The "atom:content" element either contains or links to the content of the entry. ]]]
to:
[[[ 4.15 The "atom:content" Element
The "atom:content" element conveys a representation of the entry's content, either
by containing it directly, or by linking to it. Other representations of the entry
may exist; see the atom:link element.
]]]
And as I said, no one is going to use the functionality anyway.
Wow, that's a nifty trick. If you can tell me the outcome of the Superbowl next week, I'll cut you into the proceeds.
-- Mark Nottingham http://www.mnot.net/
