> -----Original Message-----
> From: Ray Denenberg [mailto:[log in to unmask]]
> Sent: Monday, May 13, 2002 4:08 PM
>
> I have a few questions.
>
> The basic request (i.e. srw parameters)  roughly consists of:
>
> <v1>nuclear</v1>
> <v2>4</v2>
> <v3>1</v3>
> <v4></v4>
> <v5></v5>
>
> 1. Where are the "v"s defined?

As best I can tell, the names of the parameters are ignored by SOAP, so the
particular client that got used to make the request stuck its own parameter
names in.  This behavior is consistent with Java, where the class that
executes the request is based on the name of the method (searchRetrieve) and
the types, not names) of the parameters.


> 2. Can we stick in an example that better illustrates the cql
> funtionality,
> than just "nuclear"? Can someone supply one (or else I'll
> make one up!)

Make one up.


> 3. I suppose v4 is supposed to be the responseSchema, which
> is left blank to
> indicate the default, rs1, I assume.  Did we agree to retain
> this parameter?

I think we've agreed to drop it, but it is still in the wsdl that I'm using.

> Did we agree that there would be a response schema as opposed
> to a wsdl
> definition?  Could someone summarize what we decided?

The wsdl defines the response in SRW.  I still think it is needed in SRU,
but the implementors of SRU seem to claim not.


> 4.  I assume that v5 is supposed to be the record schema. Is
> it left blank
> because we don't know it's form, to let the server decide,
> or to indicate
> default (and if so what is the default?)

All the above.  Explain will tell the client what the default schema is.
I'm using DC as the default.

Ralph