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 4404 - editorial section 2
Summary: editorial section 2
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:
Blocks:
 
Reported: 2007-03-21 18:23 UTC by Christopher Ferris
Modified: 2007-04-25 19:36 UTC (History)
1 user (show)

See Also:


Attachments

Description Christopher Ferris 2007-03-21 18:23:19 UTC
Section 2

4. "is not required to detect [...] but should fault": the sentence is 
somewhat confusing.
Comment 1 Christopher Ferris 2007-03-21 18:42:06 UTC
See minutes: http://www.w3.org/2007/03/07-xmlprotocol-minutes.html

RESOLUTION: wsdl 4 closed with the following change: s/The sender is not required to detect whether transmission succeeds or fails, but the sender SHOULD fault in a binding specific manner if it discovers that transmission is unsuccessful./04 01If the sender provides a means of detecting successful or unsuccessful transmission, it SHOULD fault in a binding specific manner in the event that transmission failure is detected./
Comment 2 Christopher Ferris 2007-04-25 19:36:49 UTC
[15:33] cferris: The sending node MUST attempt to send, in a binding specific manner, the SOAP Message provided in http://www.w3.org/2003/05/soap/mep/OutboundMessage to the node(s) identified by http://www.w3.org/2003/05/soap/mep/ImmediateDestination. If the sender has a means of detecting successful or 
 unsuccessful transmission, it SHOULD fault in a binding specific manner in the 
 event that transmission failure is detected.
[15:34] * Yves +1
[15:34] cferris: RESOLUTION: issue 4404 re-resolved using the text above
[15:34] cferris: rrsagent, where am i?
[15:34] RRSAgent: See http://www.w3.org/2007/04/25-xmlprotocol-irc#T19-36-23