ISSUE-3: Assertion Protocol-2023 missing RFC 2119 language
Protocol-2023 is spurious
Assertion Protocol-2023 missing RFC 2119 language
- State:
- CLOSED
- Product:
- SOAP-JMS Binding specification
- Raised by:
- Eric Johnson
- Opened on:
- 2009-07-27
- Description:
- Description:
------------
The description of the "requestURI" property has this bullet point: " MUST appear in the JMS message in the JMS property named SOAPJMS_requestURI.†[Definition: Use fault subcode missingRequestURI if the SOAPJMS_requestURI is missing from the message.†]"
Protocol-2022 captures the first phrase, and Protocol-2023 captures the "Definition:". Notice that the definition does not use RFC 2119 keywords.
Justification
-------------
It is impossible to test Protocol-2023 without also testing 2022.
Further, Protocol-2023 does not contain any RFC 2119 language. Yet it
is clearly subsidiary to Protocol-2022, 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 this text: " MUST appear in the JMS message in the JMS property named SOAPJMS_requestURI.†[Definition: Use fault subcode missingRequestURI if the SOAPJMS_requestURI is missing from the message.†] "
to this:
" appears in the JMS message in the JMS property named SOAPJMS_requestURI. A fault must be generated with [Definition: subcode missingRequestURI if the SOAPJMS_requestURI property is missing from the message.]†"
- Related Actions Items:
- No related actions
- Related emails:
- Agenda for the 2009-08-18 conference call (from eric@tibco.com on 2009-08-17)
- 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-3: update available (from eric@tibco.com on 2009-08-10)
- ISSUE-3: 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-3 (Protocol-2023 is spurious): Assertion Protocol-2023 missing RFC 2119 language [SOAP-JMS Binding specification] (from sysbot+tracker@w3.org on 2009-07-27)
Related notes:
Accepted resolution text as per http://www.w3.org/2009/08/18-soap-jms-minutes.html
Eric Johnson, 24 Aug 2009, 19:18:47Issue apparently opened on:
http://www.w3.org/2009/08/04-soap-jms-minutes.html
Issue apparently resolved as per:
http://www.w3.org/2009/08/04-soap-jms-minutes.html
Display change log