This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 4406 - ambiguous statement
Summary: ambiguous statement
Status: RESOLVED FIXED
Alias: None
Product: XMLP WG
Classification: Unclassified
Component: one way mep (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Christopher Ferris
QA Contact: Christopher Ferris
URL: http://lists.w3.org/Archives/Public/x...
Whiteboard:
Keywords:
Depends on: 4405
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-21 18:26 UTC by Christopher Ferris
Modified: 2007-03-21 20:17 UTC (History)
1 user (show)

See Also:


Attachments

Description Christopher Ferris 2007-03-21 18:26:34 UTC
6. "Determination of success by a receiver": do you mean 'successful 
processing as per SOAP's processing model', or that + "successfully 
received"? I suspect the former, but the current text is a little ambiguous.
Comment 1 Christopher Ferris 2007-03-21 18:43:56 UTC
See minutes: http://www.w3.org/2007/03/07-xmlprotocol-minutes.html

RESOLUTION: blend 5 and 6 together
Comment 2 Christopher Ferris 2007-03-21 20:17:51 UTC
 Closed with resolution from 4405:

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