A concern was raised about having a single reliable data point available in all cases. The actual text in draft -11 says:
If the resource being responded to does not have a persistent, universally unique identifier, an IRI used to retrieve a representation of the resource SHOULD be used so long as that IRI can also be used as a valid atom:id value and so long as the "href" attribute is also specified. - James James Holderness wrote: > > James M Snell wrote: >> If this entry is a response to the html page, use thr:in-reply-to, where >> @ref equals the URI of the page (assuming that URI can also be used as >> an atom:id)... (note, this is new to draft -11 with will publish soon) > > Why wouldn't you use @href for this? I thought that's what it was there > for. If you're replying to an atom entry in a feed you use @ref to > indicate the atom:id of the entry plus (optionally) @source to point to > the actual feed. If you're replying to anything else you use @href to > point to the resource plus (optionally) @type to identify the type of > the resource. A combination of both is possible if you're replying to an > atom entry that also has a corresponding web page. > > Regards > James > >
