W3C home > Mailing lists > Public > xml-dist-app@w3.org > January 2006

Optional SOAP response; the transfer binding view

From: Mark Baker <distobj@acm.org>
Date: Tue, 10 Jan 2006 17:18:11 -0800
Message-ID: <c70bc85d0601101718m39915d70jcd7af1b8e84015ee@mail.gmail.com>
To: xml-dist-app@w3.org

I see there's at least a couple of attempts being made at changing the
HTTP binding to support the reception of response messages which don't
include a SOAP envelope.  I agree that it's a good idea to support
these responses, but I think it's already supported.

As I like to point out 8-), the definition of a SOAP message is
different than the definition of a SOAP envelope[1].  This is because
if the definitions were the same, then it would be impossible to
define transfer bindings.

Formulaiclly, we have this;

   SOAP message = SOAP envelope + transfer protocol envelope/message

In the case where we have no SOAP envelope then, we have;

   SOAP message = transfer protocol envelope/message

AFAICT - and I paid pretty close attention to this while in the WG -
this interpretation is entirely consistent with all aspects of the
SOAP 1.2 specification set.

So am I misunderstanding the intent of this change?  Or does the WG
not agree with my interpretation of the spec?  Is there some other
reason that motivates it?


 [1] http://www.w3.org/TR/2003/REC-soap12-part1-20030624/#encapsulation

Mark Baker.  Ottawa, Ontario, CANADA.       http://www.markbaker.ca
Coactus; Web-inspired integration strategies  http://www.coactus.com
Received on Wednesday, 11 January 2006 01:18:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:28 UTC