> I propose to extend ZeeRex:
>  - make serverInfo repeatable
>  - add an attribute @method to <serverInfo> 

I think the consensus seems to be to extend Explain to support multiple
endpoints for SRW and SRU etc. and the above seems to be the obvious way
of doing this.
 
> <serverInfo protocol="SRW/U" version="1.1" transport="http"
> method="post,get">
>   <host>gondolin.hist.liv.ac.uk</host>
>   <port>80</port>
>   <database>IR-Explain---1</database>
> </serverInfo>
> 
> This configures SRU and SRW on gondolin.hist.liv.ac.uk:80, 
> POST and GET.
> (Although GET probably bites with SOAP, so maybe this is a 
> bad example.)

I think we should probably deprecate protocol="SRW/U" and instead use
the following to express this.

<serverInfo protocol="SRU" version="1.1" transport="http"
  method="post,get">
  <host>gondolin.hist.liv.ac.uk</host>
  <port>80</port>
  <database>IR-Explain---1</database>
</serverInfo>
<serverInfo protocol="SRW" version="1.1" transport="http" 
  method="post">
  <host>gondolin.hist.liv.ac.uk</host>
  <port>80</port>
  <database>IR-Explain---1</database>
</serverInfo>
 
> Question: does protocol="SRW" need extra attributes like RPC or
> doc/literal ?? I don't know enough about SOAP for that..

No - SRW is *always* doc/literal. This is to comply with the Web Service
Interoperability profile (ws-i.org)

Matthew