Each atom:entry also must have an id.
On Dec 4, 2007 9:29 AM, LeVan,Ralph <[log in to unmask]> wrote:
> > -----Original Message-----
> > From: SRU (Search and Retrieve Via URL) Implementors
> > On Behalf Of Ross Singer
> > So, what this means is that every search result would
> > have a unique and permanent URI, to which I say
> > "hallelujah!" but you might not be as overjoyed.
> I think there's some confusion about the id element.
> First, it is not a pointer to a static object. Remember, it is an
> identifier for a blog feed, which is not static. If I fetch that same
> blog feed a week later, it will still have the same ID, but will have
> new content. You need to understand the purpose of the id field. It is
> to allow a blog reader to recognize a blog when it comes from a
> different source. The intent is to support movable blogs. There is no
> equivalent concept in SRU.
> The nearest equivalent in SRU is the ability to know what query created
> the result set, so that it can be recreated at a later date with any new
> records added. We have that in our SearchRetrieveResponse records in
> the EchoedSearchRetrieveRequest element. When we map our
> SearchRetrieveResponse records to Atom Feeds, we can put that echoed
> query in the Link element with the "rel" attribute set to "self". This
> tells the reader that this is the URL that generated the response.