- From: Asir Vedamuthu <asirv@webmethods.com>
- Date: Fri, 16 Jul 2004 13:02:20 -0700
- To: 'Hugo Haas' <hugo@w3.org>, Asir Vedamuthu <asirv@webmethods.com>
- Cc: "'paul.downey@bt.com'" <paul.downey@bt.com>, www-ws-desc@w3.org
> ... the concept of SOAP module does not exist in SOAP 1.1 May be, again may be, it does. I have an example, read on. Web Services Security: SOAP Message Security 1.0 - "This specification proposes a standard set of SOAP [SOAP11, SOAP12] extensions that can be used when building secure Web services to implement message content integrity and confidentiality. This specification refers to this set of extensions and modules as the Web Services Security: SOAP Message Security or WSS: SOAP Message Security." [1] So, the WSS module can be used for both SOAP 11 and 12: <wsoap:module uri="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-sece xt-1.0.xsd" requried="true"/> Module is a concept. The term SOAP module does not exist in SOAP 1.1 technical draft. It is possible to back port it. I am not suggesting that someone should :-) Web Services Security and SOAP 11 combination is a good example for migrating from WSDL 1.1 to WSDL 2.0 markup. Flip side, we can always rule out wsoap:module for SOAP 1.1, by establishing another co-occurrence constraint, // SOAP 1.1 Binding If binding/@wsoap:version == http://schemas.xmlsoap.org/soap/envelope/ // Constraint B wsoap:module elements must be absent BTW, similar reasoning should also apply for @http:version=1.0 in conjunction with @http:transfer-coding. [1] http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-securit y-1.0.pdf Regards, Asir S Vedamuthu asirv at webmethods dot com http://www.webmethods.com/ -----Original Message----- From: Hugo Haas [mailto:hugo@w3.org] Sent: Friday, July 16, 2004 9:48 AM To: Asir Vedamuthu Cc: 'paul.downey@bt.com'; www-ws-desc@w3.org Subject: Re: Decouple SOAP Version from SOAP Binding ? Hi Asir. I need to think about this a little more, but as a first comment... * Asir Vedamuthu <asirv@webmethods.com> [2004-07-16 07:30-0400] > > One difference that does spring to mind: is > > SOAP 1.2 backwards compatible with SOAP 1.1 in > > the way HTTP 1.1 is with HTTP 1.0 ? > > Negative. > > > And if not, is that an issue? > > I can't think of any reason why that would be germane to binding > description. AFAIK, WSDL says nothing about protocol version compatibility. ... the concept of SOAP module does not exist in SOAP 1.1. Regards, Hugo -- Hugo Haas - W3C mailto:hugo@w3.org - http://www.w3.org/People/Hugo/
Received on Friday, 16 July 2004 16:05:55 UTC