ISSUE-2
Protocol-2020 is spurious
Assertion Protocol-2020 missing RFC 2119 language
- State:
- CLOSED
- Product:
- SOAP-JMS Binding specification
- Raised by:
- Eric Johnson
- Opened on:
- 2009-07-27
- Description:
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.]†"
- Related Actions Items:
- No related actions
- Related emails:
- Agenda for the 2009-08-18 conference call (from eric@tibco.com on 2009-08-17)
- Minutes 2009/08/11 (from M8PHILLI@uk.ibm.com on 2009-08-11)
- RE: Agenda for 2009-08-11 conference call (from peaston@progress.com on 2009-08-11)
- Agenda for 2009-08-11 conference call (from eric@tibco.com on 2009-08-10)
- Re: ISSUE-2: update available (from eric@tibco.com on 2009-08-10)
- ISSUE-2: update available (from phil_adams@us.ibm.com on 2009-08-10)
- Re: Agenda for 2009-08-04 conference call (from M8PHILLI@uk.ibm.com on 2009-08-04)
- Re: Agenda for 2009-08-04 conference call (from ylafon@w3.org on 2009-08-04)
- Agenda for 2009-08-04 conference call (from eric@tibco.com on 2009-08-03)
- Action item 95 complete (from eric@tibco.com on 2009-07-29)
- RE: Agenda for 2009-07-28 conference call (from peaston@progress.com on 2009-07-28)
- Agenda for 2009-07-28 conference call (from eric@tibco.com on 2009-07-27)
- ISSUE-2 (Protocol-2020 is spurious): Assertion Protocol-2020 missing RFC 2119 language [SOAP-JMS Binding specification] (from sysbot+tracker@w3.org on 2009-07-27)
Related notes:
2009-08-04 16:37:16: Proposed and accepted change to proposal, from conference call of 2009-08-04:
"if using SOAP 1.2, and the contentType property has an action parameter, that parameter value is compared 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.]†" [Eric Johnson]
2009-08-24 19:18:05: Accepted resolution text as per http://www.w3.org/2009/08/18-soap-jms-minutes.html
[Eric Johnson]
Display change log
