Joe Gregorio wrote on 1/19/2006, 5:29 PM:
>
> On 1/19/06, Eric Scheid <[EMAIL PROTECTED]> wrote:
> >
> > On 20/1/06 8:08 AM, "Joe Gregorio" <[EMAIL PROTECTED]> wrote:
> >
> > > """
> > > The purpose of Atom autodiscovery is for clients who know the URI
> of a
> > > web page to find the location of that page's associated Atom feed.
> > > """
> > >
> > > Not an entry but a feed. The autodiscovery is unambiguous on what
> such
> > > a link points to.
> >
> > Unambiguous? The autodiscovery spec does not outlaw using
> > [EMAIL PROTECTED]/atom+xml,@rel=alternate] for linking to atom
> entry
> > documents. It only says that such links may be used to find Atom Feed
> > Documents. This is a subtle nuance.
>
> That is not a subtle nuance but an incorrect interpretation. By that
> same logic it does not outlaw using
> [EMAIL PROTECTED]/atom+xml,@rel=alternate] to point to
> an RSS feed, or a PNG.
>
> The autodiscovery spec would be the only RFC that defines
> the behaviour of [EMAIL PROTECTED]/atom+xml,@rel=alternate],
> and the verbage in the autodiscovery spec is unambiguous
> about that fact that it is talking about feeds and not entries.
>
What autodiscovery links should I do on a web page that displays a
single blog entry, like this one?
http://journals.aol.com/panzerjohn/abstractioneer/entries/1238
It's not unreasonable to link to the overall feed for the entire blog
from this page, but it's a bit unreasonable to say that the feed is an
'alternate' for the current page -- it's a superset of the current page,
at best. It's also not unreasonable to want to have a way to find an
individual Atom entry associated with this page. This would intuitively
seem to be a reasonable 'alternate' since it contains the same
information in a different format.
--
John Panzer
Sr. Technical Manager
http://journals.aol.com/panzerjohn/abstractioneer
