> > <SRW:searchRetrieveResponse
> > xmlns:SRW="http://www.loc.gov/zing/srw/"
> > xmlns:DIAG="http://www.loc.gov/zing/srw/diagnostics/">
> > Why are SRW and DIAG defined -here- not on the SOAP:Envelope element?
> > Surely Envelope is the top level for this XML?
> Because in this case I'm signing the SOAP:Body so I move all namespaces
> defined under SOAP:body to the searchRetrieveElement.
> If I signed the Envelope then I would have to move the namespaces up to
> the SOAP:Envelope element (although that would be difficult because of
> the recursion caused by trying to sign the signature).
Ahh, okay. *Enlightenment*
> A) all the other recommendations can be implemented by an SRW server
> with an off-the-shelve WS-I compliant SOAP toolit. An WS-I compliant
> B) it is indeterminate - i.e. let us say we had a client which required
> It might work one day, but break the next because the routing topology
> has changed!
Hmmm. All true.
Okay, I concede the argument to Matthew :)
,'/:. Dr Robert Sanderson ([log in to unmask])
,'--/::(@)::. Special Collections and Archives, extension 3142
,'---/::::::::::. University of Liverpool
I L L U M I N A T I L5R Shop: http://www.cardsnotwords.com/