* Eric Scheid <[EMAIL PROTECTED]> [2005-08-05 08:10]: > how about this instead > > <link rel="in-reply-to" > href="http://www.example.com/atom"; > type="application/atom+xml" > thread:idref="urn:foo:1" /> > > this way processors that have a basic understanding of what a > <link> is can still do something useful.
No, that requires entries to be located in a feed available at a dereferencable URI because @href is not optional. So it would preclude replying to feeds delivered via SMTP, XMPP or other protocols that don’t work like that. You can try messy workarounds, but please, let’s not go there yet again. Please read my “refactoring” post for a long trail of thoughts which addresses pretty well everything which has been brought up since. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/>
