- From: <noah_mendelsohn@us.ibm.com>
- Date: Wed, 19 Jul 2006 22:12:33 -0400
- To: "David Orchard" <dorchard@bea.com>
- Cc: xml-dist-app@w3.org
- Message-ID: <OF4F15DFB8.168BAB52-ON852571B1.000BD0D9-852571B1.000C2391@lotus.com>
Note that this is a very belated reply to a message sent by Dave at the
end of May, a copy of which is attached. Unless he's replaced it, I
believe that the attached is the draft he's proposing as the working base
for our one-way MEP. Having re-read it tonight, my feeling is that
overall it's very close to being ready for acceptance as a Recommendation,
should we wish to publish a one-way MEP. Though I'd want to read it once
or twice in more detail the only concern I caught this time was relatively
minor. Section 2.2 now says:
"2.2 Description
"The SOAP One-way MEP defines properties for the exchange of a SOAP
message. In the absence of failure in the underlying protocol, this MEP
consists of one SOAP message.
"Abnormal operation during a one-way message exchange might be caused by a
failure to transfer the message or a failure at the receiving SOAP node to
process the message. Such failures might be silent at either or both of
the sending and recieving SOAP nodes involved, or might result in the
generation of a SOAP or binding-specific fault (see 2.4 Fault Handling).
Also, during abnormal operation each SOAP node involved in the message
exchange might differ in its determination of the successful completion of
the message exchange. "
It seems to me that, editorially, it's a bit jarring to jump immediately
to the abnormal case. I think I'd move the abnormal operation paragraph
down below some of the ones describing the usual operation. Otherwise, it
looked pretty good to me overall. Thanks!
Noah
--------------------------------------
Noah Mendelsohn
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------
"David Orchard" <dorchard@bea.com>
Sent by: xml-dist-app-request@w3.org
05/31/2006 08:13 PM
To: <xml-dist-app@w3.org>
cc: (bcc: Noah Mendelsohn/Cambridge/IBM)
Subject: Updated SOAP 1.2 Part 3 document
I've added some text based upon Noah's suggestions for describing sender
and receiver responsibilities and changed to be SOAP 1.2 Part 3.
Let's talk on the list and the next telcon, whenever that occurs.
Cheers,
Dave
Attachments
- application/octet-stream attachment: soap12-part3.xml
- text/html attachment: soap12-part3.html
Received on Thursday, 20 July 2006 02:12:49 UTC