- From: SOAP-JMS Binding Working Group Issue Tracker <sysbot+tracker@w3.org>
- Date: Mon, 27 Jul 2009 20:49:42 +0000 (GMT)
- To: public-soap-jms@w3.org
ISSUE-2 (Protocol-2020 is spurious): Assertion Protocol-2020 missing RFC 2119 language [SOAP-JMS Binding specification] http://www.w3.org/2002/ws/soapjms/tracker/issues/2 Raised by: Eric Johnson On product: SOAP-JMS Binding specification Description: ------------ We have this bullet point under the "soapAction" property: "if using SOAP 1.2, and the contentType property has an action parameter, that parameter value MUST match this SOAPJMS_soapAction value.† [Definition: Use fault subcode mismatchedSoapAction if the SOAP 1.2 action does not match.†] " Protocol-2019 captures the first sentence, and Protocol-2020 covers the [Definition:]. Notice that the definition doesn't have any RFC 2119 language. Justification: -------------- It is impossible to test Protocol-2020 without also testing 2019. Further, Protocol-2020 does not contain any RFC 2119 language. Yet it is clearly subsidiary to Protocol-2019, and the absence of this language leaves it unclear as to what MUST be done. Combining the two statements will clarify the possible confusion. Proposal: --------- Change the paragraph that reads: "if using SOAP 1.2, and the contentType property has an action parameter, that parameter value MUST match this SOAPJMS_soapAction value.† [Definition: Use fault subcode mismatchedSoapAction if the SOAP 1.2 action does not match.†] " to this: "if using SOAP 1.2, and the contentType property has an action parameter, that parameter value is checked for a match with the SOAPJMS_soapAction value. A fault MUST be generated with [Definition: subcode mismatchedSoapAction if the SOAP 1.2 action does not match the SOAPJMS_soapAction value.]†"
Received on Monday, 27 July 2009 20:49:52 UTC