Well, it's all XML parsing so in one sense the processing is the same.
The key difference arises in how the various documents are used. In my
experience, Atom Entry Documents are nearly the exclusive territory of
APP Clients and push notification services (e.g. Atom over XMPP) while
Feeds generally provide for the redistribution and indexing of entries.
When I parse an entry document, there is no implied feed.
- James
Mark Baker wrote:
Interesting, thanks. But serving different purposes doesn't
necessitate a new media type. What's important is how the two types
of documents are interpreted.
How does your processing of an entry document differ from the
processing of a feed containing (only) that same entry? If processing
the entry is a subset of processing the feed, then you probably don't
need a new media type.
Mark.
On 11/30/06, James M Snell <jasnell@xxxxxxxxx> wrote:
Mark Baker wrote:
[snip]
Yes, but more than that. An entry document is, AFAICT, little more
than shorthand for a feed with one entry, minus the feed-specific
metadata. It's processing is a subset of feed processing. If the
processing or content model of entry is extended, it applies to both
feed documents and entry documents.
Hmm.. I understand what you're saying but I don't think I agree. In the
APP implementations I've put together, Feed and Entry documents
generally serve two entirely different purposes and are usually intended
for two entirely different audiences.
- James