Mark Nottingham wrote:
Sorry, Bob I disagree. I tried to introduce a rigid concept of what a
feed is much earlier, and people pushed back; as a result, Atom
doesn't have a firm definition of the nature of a feed. As a result,
we can't go and say what it can't be at a later date.
Besides which, I think the use cases for Atom-as-list are powerful,
and just beginning to be seen. E.g., Netflix allows you to subscribe
to your Queue:
http://www.netflix.com/RSSFeeds
Are you saying that when/if Netflix switches over to Atom, they
shouldn't use it for the Queue?
It sounds like you've got use cases for Atom that other use cases
(e.g., lists) make difficult to work with. Banning those other use
cases makes things easier for you, but I don't think it's good for
Atom overall.
+1 on every point.
- James
