 |
 |
I have never run across a SRW service, or if I have, it was so long ago I can't remember. Of course, I haven't run across all that many SRU services, either… but I cannot think of a good reason *not* to omit SOAP from SRU 2.0. Basically, providing a SOAP interface is like saying "please don't use this service". -Ross. On Thursday, September 20, 2012 at 4:54 PM, LeVan,Ralph wrote: > I've developed both SRW and SRU client applications. I embed SRW/U > access to databases in a number of my applications. Originally, I > mostly used SOAP/SRW, but over time have found that mangling URLs and > either string searching through the XML response or using stock JAVA XML > parsers has just been more convenient. > > > I won't miss SRW. > > > Ralph > > > From: LeVan,Ralph > Sent: Thursday, September 20, 2012 4:50 PM > To: [log in to unmask] (mailto:[log in to unmask]) > Subject: Anyone using SOAP? > > > SRU version 2.0 is nearing the end of its standardization process. It > makes no reference to the SOAP version of SRU 1.2 (also known as SRW). > > > Does anyone actually use SOAP anymore? Is this a safe omission? > > > If there's still reasonable demand, I'll probably provide the WSDL and > request schemas as an addon for the SRU 2.0 response schemas controlled > by OASIS/LC. > > > Thanks! > > > Ralph