On 9/11/04 10:53 AM, "Tim Bray" <[EMAIL PROTECTED]> wrote:

> Atom as currently specified has the following advantages over RSS:
> 
> 1. There's zero ambiguity about single and double escaping, you can use
> whichever suits your publication process better and not worry about
> silent data loss.
> 2. You can include binary chunks right there in-feed, base64 encoded.
> 3. You get help for aggregate feeds using atom:origin
> 4. You have a date, atom:updated, with cleanly-specified semantics
> ("publisher says something changed") that's *guaranteed to be there*
> per-entry
> 5. It's in an XML namespace
> 6. It's got a good accessibility story: you have to have an
> atom:summary if there's no src= or it's binary.
> 7. You have clean semantics for linking to the entry this describes or
> the entry it's talking about.

8. multiple <link> children allowed, with attributes to distinguish them
from each other. Thus we can have 'via' links, 'about' links, and more (vs
the confusion which is <link> vs <guid>)

9. improved granularity by content/@src, reducing bandwidth costs.

e.

Reply via email to