Somebody actually read my proposal in detail and pointed out that it was wrong. Retake: ================================================================ Here's the canonical RPC example from http://www.w3.org/TR/xmlp-scenarios <r:GetLastTradePrice env:encodingStyle="http://www.w3.org/2001/12/soap-encoding" xmlns:r="http://example.org/2001/06/quotes"> <r:Symbol>DEF</r:Symbol></r:GetLastTradingPrice> This becomes something like http://example.org/SoapGet?ns=http://example.org/2001/06/quotes&serv=GetLastTradingPrice&Symbol=DEF I don't provide the encodingStyle - let's assert that if you do it this way you get soap-encoding by default (or in fact that that's all you can have). To simplify, let's say that the service namespace is by default a relative URI reference with the base established by the that of the URI itself, thus http://example.org/SoapGet?ns=/2001/06/quotes&Serv=GetLastTradingPrice&Symbol=DEFReceived on Wednesday, 24 April 2002 11:05:50 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 20 September 2007 13:52:35 GMT