R060: Description of message exchanges and protocol binding

Hi.

Philippe brought to my attention that there was some discussion about
section 1.4 of the charter[1], which lead to R060 (taken from [2]):

   R060
          [?Reject?, Draft, Must, Charter] The information exchanged to
          and from a Web Service can be carried in a large number of
          different ways. The action of carrying some XML-based
          communication in an underlying protocol is called, in the XML
          Protocol [SOAP 1.2] jargon, a binding. The description language
          defined should therefore describe how to reach the Web Service
          in a form which is orthogonal to its Message exchange patterns
          and its Messages. (Redundant with R028.)

The idea behind R060 is that the exchange between a service and a
consumer of this service, once agreed upon, can be carried in
different ways.

To relate to SOAP and R028, let's imagine a simple service which
returns an XML document as the result of processing a SOAP message.

SOAP can be carried by several underlying protocols, and the XML
document likewise. We can imagine that the exact same service could
operate with both HTTP and SMTP.

What R060 calls for is that it should be trivial to say that this data
exchange can take place using 2 different protocols ("bindings"), i.e.
that the language shouldn't require a complete description of the data
exchange for each of those.

I don't think this is a duplicate of R028, R028 calling for precise
description of SOAP messages.

Regards,

Hugo

  1. http://www.w3.org/2002/01/ws-desc-charter#bind
  2. http://lists.w3.org/Archives/Public/www-ws-desc/2002Mar/att-0087/01-WSRQ0326.HTM
-- 
Hugo Haas - W3C
mailto:hugo@w3.org - http://www.w3.org/People/Hugo/ - tel:+1-617-452-2092

Received on Wednesday, 3 April 2002 16:38:56 UTC