I can see one use case where I may want to view my inbox as a set of feeds, each mail representing a feed, and the conversations within the mail as entries. Here i may want to view all the entries at a time like the gmail conversation view, in which case all the entries have to be rendered at once!
On 1/30/06, James M Snell <[EMAIL PROTECTED]> wrote:
Assuming the same document references are limited to the content, and
the content is rendered to the user as discrete entries, the same
document references are not going to be an issue. This is actually an
issue with atom and rss in general, not just APP. The important thing
that we really need to worry about here are relative URI's and same doc
refs contained in things like the atom link element.
Yogesh Mujumdar wrote:
> But what if i am aggregating entries into a single feed. e.g news items
> from different websites?
>
> On 1/30/06, *James M Snell* < [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED] >> wrote:
>
>
> Agreed. folks that process feeds (including content) as complete
> documents would need to be aware of the potential problems, but overall,
> it should be fine.
>
> Tim Bray wrote:
> >
> > On Jan 29, 2006, at 2:00 PM, James M Snell wrote:
> >
> >>
> >> Because of the way that most feed readers process content, this is
> >> probably unlikely to be a problem; however, there still is the
> >> potential for issues. For instance, what if this entry is
> included in
> >> an atom feed that contains another entry whose xhtml content
> uses the
> >> same anchor id's?
> >
> > Well, entries are typically viewed one at a time, so in practice it's
> > not apt to be a problem. I think same-doc refs should be just
> fine in
> > general. -Tim
> >
>
>
>
>
> --
> -yogesh
>
>
>
>
--
-yogesh
