W3C home > Mailing lists > Public > public-soap-jms@w3.org > July 2009

ISSUE-3 (Protocol-2023 is spurious): Assertion Protocol-2023 missing RFC 2119 language [SOAP-JMS Binding specification]

From: SOAP-JMS Binding Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Mon, 27 Jul 2009 23:19:26 +0000 (GMT)
To: public-soap-jms@w3.org
Message-Id: <20090727231926.D27886B64D@kent.w3.org>

ISSUE-3 (Protocol-2023 is spurious): Assertion Protocol-2023 missing RFC 2119 language [SOAP-JMS Binding specification]

http://www.w3.org/2002/ws/soapjms/tracker/issues/3

Raised by: Eric Johnson
On product: SOAP-JMS Binding specification

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.]† "
Received on Monday, 27 July 2009 23:19:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:16:20 GMT