A. Pagaltzis wrote:
Given this constraint, do you have a better idea how do address
the following concerns?
• Threading-unaware clients should get at least some information
that allows the user to notice that there’s more to the entry,
even if the user agent remains blissfully unaware of the thread
as such.
I think a "related" link that points to the permalink of the original
message is a good start.
• The available information precise enough that threading-aware
can correlate all the related bits without guessing.
What about something like this:
<th:in-reply-to>
<id>tag:www.example.org:2005:entry1</id>
<link rel="feed" type="application/atom+xml"
href="http://www.example.org/feed.atom"/>
<link rel="related" type="text/html"
href="http:www.example.org/entry1.html"/>
</th:in-reply-to>
No doubt there are issues with the syntax, but the important concept is the
idea of having two clearly defined links: one being the permalink for the
entry being replied to and the other being the atom feed in which that entry
can be found. It could be made more flexible by allowing further "alternate"
links, but I'm not sure that's necessary.
Honestly, I haven’t seen any yet that do anything interesting at
all with extra links (be they related, via, or something else)…
(Which rather irks me.)
Me neither. I can't say I'm exactly doing anything interesting with links,
but I am at least doing something with them.
Regards
James
