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:
  1. Agenda for the 2009-08-18 conference call (from eric@tibco.com on 2009-08-17)
  2. RE: Agenda for 2009-08-11 conference call (from peaston@progress.com on 2009-08-11)
  3. Agenda for 2009-08-11 conference call (from eric@tibco.com on 2009-08-10)
  4. Re: ISSUE-3: update available (from eric@tibco.com on 2009-08-10)
  5. ISSUE-3: update available (from phil_adams@us.ibm.com on 2009-08-10)
  6. Re: Agenda for 2009-08-04 conference call (from M8PHILLI@uk.ibm.com on 2009-08-04)
  7. Re: Agenda for 2009-08-04 conference call (from ylafon@w3.org on 2009-08-04)
  8. Agenda for 2009-08-04 conference call (from eric@tibco.com on 2009-08-03)
  9. Action item 95 complete (from eric@tibco.com on 2009-07-29)
  10. RE: Agenda for 2009-07-28 conference call (from peaston@progress.com on 2009-07-28)
  11. Agenda for 2009-07-28 conference call (from eric@tibco.com on 2009-07-27)
  12. 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:47

Issue apparently opened on:
http://www.w3.org/2009/08/04-soap-jms-minutes.html

Eric Johnson, 27 Sep 2010, 23:44:28

Issue apparently resolved as per:
http://www.w3.org/2009/08/04-soap-jms-minutes.html

Eric Johnson, 27 Sep 2010, 23:45:35

Display change log ATOM feed


Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 3.html,v 1.1 2013-09-16 14:06:35 carine Exp $