What a timely message. I am - right now - implementing this kind of functionality in our app, SmartFish.
We support both RSS2.0 and Atom syndication formats and I was looking for prior art in this area. I came across the Atom Threading extension spec:
http://www.ietf.org/rfc/rfc4685.txt
Among other things it defines an "in-reply-to" element. Our posts (we call them 'pebbles') use a SHA-1 hash as a unique identifier so ours are in the form:
<thr:in-reply-to ref="urn:uuid:5504D8DDA86E21C5CE62575B03A048F0B84F4E60"/>
The spec defines other behaviour that would support more complex threading functionality but this is all we need at the moment.
I'd be interested in your thoughts on this spec and interoperating in this area.
Kind regards,
Matt
Ah, belatedly I see you have come across the Atom threading extension and more besides. I've had a quick browse of the other links that you've posted to prior art. It's not clear to me that there's anything substantially better or more widely deployed than Atom threading. But if I'm wrong I'm certainly happy to look at other, more interoperable, approaches.
I'm not sure that I consider Atom threading extension widely deployed.
For that reason and because I did not really want to mix in anything
Atom and was attempting to come up with a new simpler way to achieve
RSS replies/comments.
Thanks for your interest. What is SmartFish?
Sull