This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
5. "A receiving node MUST determine whether a given message is successfully received": this is likely outside the scope of SOAP. The SOAP 'middleware' may not even be able to detect the message was not successfully received. Suggestion: "When a message is successfully received by a SOAP node, the node MUST populate etc.".
See minutes: http://www.w3.org/2007/03/07-xmlprotocol-minutes.html ACTION: Chris to provide replacement text for 3rd paragraph in section 2.2 [recorded in http://www.w3.org/2007/03/07-xmlprotocol-minutes.html#action05]
RESOLUTION: WSDL #5 closed with the following replacement text for 3rd para sect 2.2: When a message is successfully received by a SOAP node, that node MUST populate http://www.w3.org/2003/05/soap/mep/InboundMessage with the received message and MUST process the message in http://www.w3.org/2003/05/soap/mep/InboundMessage according to the SOAP Processing Model (see SOAP 1.2 Part 1 [SOAP Part 1] Processing SOAP messages). A receiver might, in exceptional circumstances, treat as erroneous, or lost, a message that has been received intact. Typical reasons for making such decisions might include shortage of buffer space, network interface overruns, etc.. A receiver MAY fault in a binding-specific manner if some particular message is determined to have been unsuccessfully received (note, however, that in many cases where receipt is unsuccessful, information identifying the message or its sender may be unreliable, in which case there may be little if any value in reflecting a message-specific fault.) See http://www.w3.org/2007/03/21-xmlprotocol-irc#T19-34-29