[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [search-ws] relating schemas to specifications
One is not a major SRW operation and the other a minor operation; they are peers. If one must be done in SOAP, then both must. If there are clients out there in the world written to communicate with an SRW server, they probably implemented both the searchRetrieve and scan operations as the WSDL was provided for both. You can’t just drop the Scan support. Ralph From: Ray Denenberg, Library of Congress [mailto:rden@loc.gov] What is the requirement? Do you have a requirement to do it? As I recall, when we wrote the charter, we included SOAP "for political reasons", not for any real requirement. We covered that by doing it for searchRetrieve. I don't think the charter compels us to do SOAP for Scan. From: LeVan,Ralph [mailto:levan@oclc.org] We have as much of a requirement to do Scan via SOAP and we do Search. Ralph From: Ray Denenberg, Library of Congress [mailto:rden@loc.gov] I've assumed there doesn't need to be a scanRequest schema - the sruRequest schema exists solely for SOAP, and I had assumed that we don't need to do Scan via SOAP. But I don't completely understand all of the SOAP intricacies (never having cared much about it). So we need Matthew to figure this out. From: LeVan,Ralph [mailto:levan@oclc.org] I don’t see the scanRequest. I expected to see it in the sruRequest schema and the “Used by” note to include Scan. Ralph From: Denenberg, Ray [mailto:rden@loc.gov] See table below; in the left column are our schemas. I need to relate them to the specifications. In the right column for each schema I have listed the specs that use that schema. Please look this over and see if I've overlooked anything.
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]