On 20/1/06 7:52 AM, "A. Pagaltzis" <[EMAIL PROTECTED]> wrote:
>> Here is a link to a resource: >> >> <link type="application/atom+xml" href="..." /> >> >> Please explain how a tool can decide whether that is a link to a >> <atom:feed> document, or is a link to an <atom:entry> document? > > this is an excellent point. How does either Pace address it? PaceDifferentRelValue addresses this. It suggests using "feed" as an @rel value to indicate the referenced resource is a feed (ie. is not an entry doc) which can be subscribed to. It doesn't rule out continuing to use "alternate" for those cases where the feed is actually an alternate to the current document. > I am trying to think of a scenario where I¹d want to autodiscover an entry > document (as opposed to simply linking to it) and the inability to distinguish > between feed and entry documents is causing a problem, but I can¹t come up > with anything. Can you provide an example? I'm not talking about autodiscovery of entry documents. I'm talking about autodiscovery of feeds, which (and this is the point) is *different* from autodiscovery of resources with the mime type of "application/atom+xml". Apart from Atom Entry Documents, there are also "application/ref+xml" documents ... and not all of those are RSS 1.0 feeds. Using "feed" solves the problem for both cases (atom entry and rdf+xml), and potentially any similar problems (eg newsml+xml?). e.
