W3C home > Mailing lists > Public > xmlp-comments@w3.org > March 2002

Re: Issue 103 closed: Precisely describe message path semantics

From: <noah_mendelsohn@us.ibm.com>
Date: Tue, 5 Mar 2002 13:56:03 -0500
To: John_Ibbotson/UK/IBM%IBMGB%IBMUS@lotus.com
Cc: xmlp-comments@w3.org
Message-ID: <OF43BE05E8.98F4E5AC-ON85256B73.0068FE90@lotus.com>
As originator of Issue 103, I hereby signal my satisfaction with this 
resolution.  Thank you.

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







John Ibbotson@IBMGB
03/04/2002 05:01 AM

 
        To:     xmlp-comments@w3.org
        cc:     Noah Mendelsohn/Cambridge/IBM
        Subject:        Issue 103 closed: Precisely describe message path semantics

The SOAP WG has decided to close issue 103 [1] with the following 
resolution:

The introductory paragraphs of section 2 in [2] will be rewritten as:

SOAP provides a distributed processing model that assumes that a SOAP
message originates at an initial SOAP sender and is sent to an ultimate
SOAP receiver via zero or more SOAP intermediaries.

The SOAP distributed processing model can support many message exchange
patterns including but not limited to one-way messages, request/response
interactions, and peer-to-peer conversations.

This section defines the SOAP distributed processing model. Section 5
defines a framework for describing how message exchange patterns as well
as additional features such as routing, reliability and security
interact with the distributed processing model.

In addition, there are some minor changes in the terminology section:

1) In the definition of "SOAP message path" replace "the ultimate SOAP
receiver" with "an ultimate SOAP receiver" resulting in:

"The set of SOAP senders and SOAP receivers through which a single SOAP
message passes. This includes the initial SOAP sender, zero or more SOAP
intermediaries, and an ultimate SOAP receiver."

2) In the definition of "SOAP intermediary" replace "towards the
ultimate" with "towards an ultimate" resulting in:

A SOAP intermediary is both a SOAP receiver and a SOAP sender and is
target-able from within a SOAP message. It processes a defined set of
SOAP header blocks in a SOAP message along a SOAP message path. It acts
in order to forward the SOAP message towards an ultimate SOAP receiver.

3) In the definition of "Ultimate SOAP receiver", remove the first
sentence and modify resulting in the following text:

The ultimate SOAP receiver is responsible for processing the contents of
the SOAP body. Normally the ultimate receiver is the last SOAP node
along the SOAP message path. As described in section 2, a SOAP ultimate
receiver cannot also be a SOAP intermediary. In certain circumstances, a
SOAP message may not reach the ultimate recipient because of a SOAP
fault generated by a SOAP node along the SOAP message path.

[1] http://www.w3.org/2000/xp/Group/xmlp-issues.html#x103
[2] http://www.w3.org/2000/xp/Group/1/10/11/soap12-part1.html

John

Emerging ebusiness Industry Architecture , 
XML Technology and Messaging, 
IBM UK Ltd, Hursley Park,
Winchester, SO21 2JN

Tel: (work) +44 (0)1962 815188        (home) +44 (0)1722 781271
Fax: +44 (0)1962 816898
Notes Id: John Ibbotson/UK/IBM
email: john_ibbotson@uk.ibm.com
Received on Tuesday, 5 March 2002 14:10:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:42:27 GMT