On Nov 11, 2004, at 12:00 AM, Automatic digest processor wrote:
> If there was a URL version of the Update operation, would that be
> desirable, or just an XML over HTTP version (as opposed to SOAP)
>
> How do you get a record in the URL?
>
> You don't. Instead you put a pointer to it and the server retrieves
> it to
> process.
>
> For example:
>
> http://srw.cheshire3.org/services/l5r?
> operation=update
> &recordIdentifier=1
> &recordVersion=versionNumber:1.1
> &recordSchema=ccg
> &recordPacking=URL
> &recordData=http://srw.cheshire3.org/services/l5r/1.xml
>
> If no one speaks up in favor of this, we're going to bin it, so if this
> would be useful to you Speak Now.
I sincerely apologize, and I must have missed something, but update?
I thought SRW/U was about search? If update becomes a part of the
"standard", then will my SRW/U services be required to support it?
Again, I think the addition of this operation diminishes the elegance
of the protocol. What is the problem SRW/U are trying to solve, and in
what way is update a part of that solution?
--
Eric Lease Morgan
University Libraries of Notre Dame
|