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

ISSUE-5 (Protocol-2035 is redundant): Protocol-2035 is redundant [SOAP-JMS Binding specification]

From: SOAP-JMS Binding Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Mon, 27 Jul 2009 23:44:01 +0000 (GMT)
To: public-soap-jms@w3.org
Message-Id: <20090727234401.E71117F46F@otto.w3.org>

ISSUE-5 (Protocol-2035 is redundant): Protocol-2035 is redundant [SOAP-JMS Binding specification]

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

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

Description:
------------
The text of the assertion is "the following table specifies how the binding properties described earlier explicitly affect the message constructed.†"

However, neither the protocol text itself, nor the table that follows, include any RFC 2119 language.  This makes the purpose of this assertion confusing.

Justification:
--------------
Altering the text to reflect the fact that this assertion does not add any normative text would simplify the understanding of the text.

Proposal:
---------
In section 2.6.1.1., change: "A number of the message header properties are implicitly created by the use of the JMS API,  the following table specifies how the binding properties described earlier explicitly affect the message constructed.†"

to this:

"A number of the message header properties are implicitly created by the use of the JMS API.  The following table shows how the binding properties described earlier explicitly affect the message constructed."

(specifies --> shows, drop normative statement indication)
Received on Monday, 27 July 2009 23:44:11 GMT

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