- From: Geoff Arnold <Geoff.Arnold@Sun.COM>
- Date: Mon, 07 Apr 2003 15:20:44 -0400
- To: www-ws-arch@w3.org
Oops - I sent this as a reply, so I got the wrong WS list. Repeated here for convenience.... ------ Everyone who is interested in this topic should probably be tracking the thread "amazon: rest and soap" over on www-tag@w3.org (Chris Lilley's comment at http://lists.w3.org/Archives/Public/www-tag/2003Apr/0027.html and Noah's reply at http://lists.w3.org/Archives/Public/www-tag/2003Apr/0031.html ). One important question is the following: if I define a web service as a SOAP service, and if one of the transports that I can use to convey SOAP is HTTP, what is the significance of *how* I use HTTP to convey SOAP? Do I want the semantics of SOAP-over-HTTP to be the same as SOAP-over-MOM? If not, why not? If so, my application semantics must be defined purely at SOAP and above, and the precise HTTP mapping is relevant only for interoperability; it must be semantically neutral. This feels trivially obvious, so either I'm wasting your time or I'm missing something.....
Received on Monday, 7 April 2003 15:21:54 UTC