ISSUE-6: Protocol 2039 redundant, missing RFC 2119 language

Protocol 2039 redundant

Protocol 2039 redundant, missing RFC 2119 language

State:

CLOSED

Product:

SOAP-JMS Binding specification

Raised by:

Eric Johnson

Opened on:

2009-07-28

Description:

Description:
------------
Protocol-2039 reads: "the following table specifies how the binding properties described earlier explicitly affect the message constructed." Note that it does not contain any RFC 2119 language. Also note that the table following also does not contain any such language, either.

Justification:
--------------
Since there are no normative statements here, this doesn't seem to be appropriately classified as an assertion.

Proposal:
---------
Change the text that reads:
"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, remove assertion indication)

Also, the table includes an entry for JMSPriority. This should be removed.

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. ISSUE-6: update available (from phil_adams@us.ibm.com on 2009-08-10)
3. Re: Agenda for 2009-08-04 conference call (from M8PHILLI@uk.ibm.com on 2009-08-04)
4. Re: Agenda for 2009-08-04 conference call (from ylafon@w3.org on 2009-08-04)
5. Agenda for 2009-08-04 conference call (from eric@tibco.com on 2009-08-03)
6. Action item 95 complete (from eric@tibco.com on 2009-07-29)
7. ISSUE-6 (Protocol 2039 redundant): Protocol 2039 redundant, missing RFC 2119 language [SOAP-JMS Binding specification] (from sysbot+tracker@w3.org on 2009-07-28)

Related notes:

Display change log