RE: What is a SOAP Message

woah, that seems a bit extreme.

Does that mean if I have a method in an HTML form - like GetStockQuote :-) -
that the HTML result isn't a representation as well?  I assume that the
non-representation that is an HTML page is still "on the web".

So dereferencing URIs can result in representations and non-representations?
In which case, the Web Architecture has to talk about non-representations as
well as representations.  That's most excellent.

Cheers,
Dave

> -----Original Message-----
> From: xml-dist-app-request@w3.org
> [mailto:xml-dist-app-request@w3.org]On
> Behalf Of Mark Baker
> Sent: Tuesday, February 04, 2003 6:32 PM
> To: David Orchard
> Cc: noah_mendelsohn@us.ibm.com; 'Jean-Jacques Moreau';
> 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 about
> > 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.
>
> MB
> --
> Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca
> Web architecture consulting, technical reports, evaluation & analysis
>

Received on Tuesday, 4 February 2003 22:10:29 UTC