ISSUE-52: JMSReplyTo description includes inappropriate use of "must" in section 2.6.1.1

bogus RFC 2119 keyword in table describing JMSReplyTo

JMSReplyTo description includes inappropriate use of "must" in section 2.6.1.1

State:

CLOSED

Product:

SOAP-JMS Binding specification

Raised by:

Eric Johnson

Opened on:

2010-07-16

Description:

From email: http://lists.w3.org/Archives/Public/public-soap-jms/2010Jul/0013.html

Description:
Section 2.6.1.1:
Description of JMSReplyTo has a "must" that should be replaced.

Not capitalized, bolded, or flagged as normative, and would be redundant with other normative statements anyway.

Proposal:
Change "Otherwise the implementation must determine the reply queue,..."

to "Otherwise the implementation has to determine the reply queue,..."

Related Actions Items:

No related actions

Related emails:

1. RE: Agenda for the 2010-08-17 conference call (from Derek.Rokicki@softwareag.com on 2010-08-17)
2. Agenda for the 2010-08-17 conference call (from eric@tibco.com on 2010-08-16)
3. Agenda for the 2010-08-03 conference call (from eric@tibco.com on 2010-08-02)
4. Completed ACTION-196 - applied accepted resolutions from last week (from eric@tibco.com on 2010-08-02)
5. Agenda for the 2010-07-27 conference call (from eric@tibco.com on 2010-07-26)
6. Re: Agenda for the 2010-07-20 conference call (from eric@tibco.com on 2010-07-20)
7. RE: Agenda for the 2010-07-20 conference call (from Derek.Rokicki@softwareag.com on 2010-07-20)
8. Re: Agenda for the 2010-07-20 conference call (from phil_adams@us.ibm.com on 2010-07-20)
9. Agenda for the 2010-07-20 conference call (from eric@tibco.com on 2010-07-19)
10. Re: ACTION 186 - top to bottom review of current copy of spec (from eric@tibco.com on 2010-07-16)
11. ISSUE-52 (bogus RFC 2119 keyword in table describing JMSReplyTo): JMSReplyTo description includes inappropriate use of 'must' in section 2.6.1.1 [SOAP-JMS Binding specification] (from sysbot+tracker@w3.org on 2010-07-16)

Related notes:

Display change log