On 24/5/06 5:12 AM, "Tim Bray" <[EMAIL PROTECTED]> wrote: >>> If the other resource cannot be uniquely and persistently identified, >>> then it cannot be responded to. I think that's a fair trade off. >> >> :-( > > Gimme a break Eric, James' proposal isn't trying to boil the ocean, > it's trying to introduce something useful in the *Atom* space, and in > the Atom space, entries are either uniquely identified or they don't > exist. Talk about a big fat 80/20 point. -Tim
Sorry, I got distracted by the target being termed a "resource" .. I missed the bit about the fact these are implicitly *Atom* resources, and further lost track of the context being that this is on the thr:in-reply-to element and *not* atom:[EMAIL PROTECTED]'replies']. Further, fully agree this hits the 80:20 mark. mea culpa [...] hang on ... atom:[EMAIL PROTECTED]'replies'] is for noting that the linked resource contains replies *to* this resource. How do I then express a connection between this atom:entry and some random html page (which doesn't have unique and persistent ID)? Do I simply use the fall back of atom:[EMAIL PROTECTED]'related']? e.
