- From: Henrik Frystyk Nielsen <henrikn@microsoft.com>
- Date: Wed, 25 Sep 2002 16:23:04 -0700
- To: <duerst@w3.org>, <xmlp-comments@w3.org>
- Cc: "Martin Gudgin" <mgudgin@microsoft.com>
Martin, The XML Protocol WG has decided to close editorial issue 265 [1] raised by you without changes to the specification. The justification follows below. If you cannot accept this resolution then please send your concerns to the <xml-dist-app@w3.org> mailing list [2] indicating the issue number of the issue in the subject. We believe the issue of interacting features, regardless of whether they are expressed as SOAP modules or part of the binding) is covered in part 1, section 3.2 where it is stated that a SOAP module specification: "MUST clearly specify any known interactions with or changes to the interpretation of the SOAP body. Furthermore, it MUST clearly specify any known interactions with or changes to the interpretation of other SOAP features (whether or not those features are themselves modules). For example, we can imagine a module which encrypts the SOAP body and inserts a SOAP header block containing a checksum and an indication of the encryption mechanism used. The specification for such a module would indicate that the decryption algorithm on the receiving side is to be run prior to any other modules which rely on the contents of the SOAP body." Thanks, Henrik Frystyk Nielsen mailto:henrikn@microsoft.com [1] http://www.w3.org/2000/xp/Group/xmlp-lc-issues.html#x265 [2] http://lists.w3.org/Archives/Public/xml-dist-app/ [3] http://www.w3.org/2000/xp/Group/2/06/LC/soap12-part1.xml#soapmodules
Received on Wednesday, 25 September 2002 19:24:01 UTC