W3C home > Mailing lists > Public > xml-dist-app@w3.org > February 2003

Re: What is a SOAP Message

From: <noah_mendelsohn@us.ibm.com>
Date: Tue, 4 Feb 2003 22:36:06 -0500
To: Mark Baker <distobj@acm.org>
Cc: David Orchard <dorchard@bea.com>, "'Jean-Jacques Moreau'" <jean-jacques.moreau@crf.canon.fr>, xml-dist-app@w3.org
Message-ID: <OFD716A910.EF294589-ON85256CC4.0013C611@lotus.com>

I agree with Mark.  There are many situations in which a SOAP envelope is 
modeled as being of media type application/soap+xml, but in which the 
model used is not REST, and the term "representation" is thus more 
confusing than helpful.

Noah Mendelsohn                              Voice: 1-617-693-4036
IBM Corporation                                Fax: 1-617-693-8676
One Rogers Street
Cambridge, MA 02142

Mark Baker <distobj@acm.org>
02/04/2003 09:32 PM

        To:     David Orchard <dorchard@bea.com>
        cc:     noah_mendelsohn@us.ibm.com, "'Jean-Jacques Moreau'" 
<jean-jacques.moreau@crf.canon.fr>, xml-dist-app@w3.org
        Subject:        Re: What is a SOAP Message

On Tue, Feb 04, 2003 at 02:48:58PM -0800, David Orchard wrote:
> While I can't see
> where REST speaks about binding to protocols being in the definition of
> representations, it also doesn't appear to preclude this.  REST talks 
> representations being the transfer of application state.

Right, representations are serializations of application state.  But
everything is not a representation.  For example, any SOAP envelope with
a method in it is not a representation.

For at least one use of SOAP - the so-called "chameleon" use - it
appears that what you call a "SOAP representation" is indeed a
representation.  But in the tunnel use of SOAP, or when SOAP is bound to
a *transport* protocol, a "SOAP representation" is not a representation.

Just my 2c.

Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca
Web architecture consulting, technical reports, evaluation & analysis
Received on Tuesday, 4 February 2003 22:39:22 UTC

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