A. Pagaltzis wrote:
* James M Snell <[EMAIL PROTECTED]> [2005-07-21 23:15]:
Feedback requested.
I like it so far; comments follow (no pun intended).
;-)
/root provides the URL (dereferencable) to the Atom feed that
contains the original entries and may appear within atom:feed
and/or atom:entry
Why is this restricted to being an Atom feed? Shouldn’t @type
govern the precise meaning? Should linking to other kinds of
resources, such as a weblog with the appropriate autodiscovery
tags in its HTML or to a FOAF file, be outlawed? If not, are
there any SHOULD/MUST requirements for linked resources?
The restriction is to make the link predictable and keep the spec
simple. For instance, if I linked to anything but an Atom feed, what
would in-reply-to link to?
/in-reply-to provides the atom:id (not dereferencable) of an
original atom:entry and may appear within atom:feed or
atom:entry. in-reply-to on the feed level indicates that all
of the entries within the feed are considered replies to the
identified atom:entry.
Is it legal if it appears at both levels? And what does it mean
then?
Yes. If the entry level link has the same URI as the feed level link,
there is no effect... it's basically just redundant data. If the entry
level link specifies a different URI, then it's basically an assertion
that the entry is a response to two different entries. If all of the
entries within a feed are replies to the same entry, putting the
in-reply-to at the feed level simply gives you a shortcut the same way
that putting atom:author elements at the feed level rather than entry
level does.
e.g.
1.
<!-- legal but redundant -->
<feed>
<link rel=".../in-reply-to" href="{url1}" />
<entry>
<link rel=".../in-reply-to" href="{url1}" />
</entry>
</feed>
2.
<!-- equivalent to #3 below -->
<feed>
<link rel=".../in-reply-to" href="{url1}" />
<entry>
<link rel=".../in-reply-to" href="{url2}" />
</entry>
</feed>
3.
<!-- equivalent to #3 below -->
<feed>
<entry>
<link rel=".../in-reply-to" href="{url1}" />
<link rel=".../in-reply-to" href="{url2}" />
</entry>
</feed>
- James
