> > I have a few questions.
> > The basic request (i.e. srw parameters)  roughly consists of:
> > <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

That's bad behaviour, I think, on the part of the toolkit you're using.
There were similar complaints about Google's SOAP implementation on the
newsgroup about their web api.

Rob

--
      ,'/:.          Rob Sanderson ([log in to unmask])
    ,'-/::::.        http://www.o-r-g.org/~azaroth/
  ,'--/::(@)::.      Special Collections and Archives, extension 3142
,'---/::::::::::.    Twin Cathedrals:  telnet: liverpool.o-r-g.org 7777
____/:::::::::::::.              WWW:  http://liverpool.o-r-g.org:8000/
I L L U M I N A T I