>> The XML on the wire for rpc/encoded is very different from the XML on
>> the wire for document/literal. You could with a bit of fiddling get a

All I can speak for is the ZSI tk for Python, but I can produce the
correct XML from RPC style definitions.  I expect that those definitions
could be encoded back into WSDL.

Secondly, if you hit Ralph's server for its WSDL it's very simple, but
produces real SRW.

So obviously -some- wsdl would produce the same result and be simpler.

> Then have we made a horrible, horrible mistake in the way we've
> defined SRW?  It it basically don't work with existing toolkits, do we
> need to throw it all up in the air and make 2.0 that uses rpc/encoded?

No, it does work with some existing tks, but not all.  And some that it
doesn't work with can still be used with some tweaking (eg ZSI)

Rob

       ,'/:.          Dr Robert Sanderson ([log in to unmask])
     ,'-/::::.        http://www.o-r-g.org/~azaroth/
   ,'--/::(@)::.      Special Collections and Archives, extension 3142
,'---/::::::::::.    University of Liverpool
____/:::::::::::::.
I L L U M I N A T I  L5R Shop: http://www.cardsnotwords.com/