W3C home > Mailing lists > Public > xml-dist-app@w3.org > October 2001

Re: SOAP concerns

From: <Noah_Mendelsohn@lotus.com>
Date: Fri, 12 Oct 2001 10:10:58 -0400
To: Christopher Ferris <chris.ferris@sun.com>
Cc: "Roger L. Costello" <costello@mitre.org>, Marwan Sabbouh <ms@mitre.org>, "Denning,Paul B." <pauld@mitre.org>, "'xml-dist-app@w3.org'" <xml-dist-app@w3.org>
Message-ID: <OF4938259F.EABBB237-ON85256AE3.004E4632@lotus.com>
Chris Ferris writes:

>> SOAP doesn't mandate what can go in the SOAP Body at all.

Actually that's not quite true.  It requires that the child of a header 
body be namespace qualified [1].  That's crucial, because the SOAP 
processing model mandates that you only process header or body entries for 
which you "understand" the corresponding specification.  The spec makes 
clear that such "understanding" is indeed keyed to the namespace-qualified 
name of those child elements [2]:

"A SOAP header block is said to be understood by a SOAP node if the 
software at that SOAP node has been written to fully conform to and 
implement the semantics conveyed by the combination of local name and 
namespace name of the outer-most element information item of that block."

Those mechanisms apply uniformly whether the content is RPC [3] or not. 
So, not only does SOAP say something about what goes into headers and 
body, I think the answer is key to dealing with some of Roger's concerns.

[1] http://www.w3.org/TR/2001/WD-soap12-part1-20011002/#soaphead
[2] http://www.w3.org/TR/2001/WD-soap12-part1-20011002/#muprocessing
[3] http://www.w3.org/TR/2001/WD-soap12-part2-20011002/#soapforrpc

Noah Mendelsohn                                    Voice: 1-617-693-4036
Lotus Development Corp.                            Fax: 1-617-693-8676
One Rogers Street
Cambridge, MA 02142
Received on Friday, 12 October 2001 10:20:00 UTC

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