Thomas Broyer wrote:
James M Snell wrote:
/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>
#2 is not how atom:author "inheritance" works (assuming there is some kind
of atom:author inheritance, which is not established). I'd prefer #2 to be
Yeah, you're right. bad analogy.
equivalent to this:
<feed>
<entry>
<link rel=".../in-reply-to" href="{url2}" />
</entry>
</feed>
That is, the set of entry level links overrides the set of feed level links.
Gotta think about this a bit more. This may be the better approach.
If I understand correctly, ".../root" tells you where to find the entry
identified with ".../in-reply-to". How are you dealing with multiple
in-reply-to?
<link rel=".../root" href="feeda.xml" />
<link rel=".../root" href="feeda.xml" />
<link rel=".../in-reply-to" href="tag:entry1" />
<link rel=".../in-reply-to" href="tag:entry2" />
If I misunderstood, what is ".../root" for?
.../root is simply a link back to feeds that may contain root level
entries (e.g. the entries being responded to). In the example, the two
in-reply-to links could reference entries in either of the two linked
root feeds. It's up to the implementation to figure out exactly how to
handle it.
Again, I'm still stewing over all this so if you have any specific
suggestions on how to handle it better, please let me know.
- James
