ISSUE-57: @location attribute assertion about being a JMS Destination, but not flagged.

Unflagged assertion about JMS destination

@location attribute assertion about being a JMS Destination, but not flagged.

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 3.3.5 currently has the sentence:
"The value of the location attribute MUST be a URI corresponding to a JMS Destination, and SHOULD be a "jms" scheme URI."

Problem: This is not flagged as a normative statement.

Proposal:
Flag this as WSDLUsage-3004

Note, I believe this assertion is untestable.

Related Actions Items:

No related actions

Related emails:

1. Agenda for the 2010-08-24 conference call (from eric@tibco.com on 2010-08-23)
2. RE: Agenda for the 2010-08-17 conference call (from Derek.Rokicki@softwareag.com on 2010-08-17)
3. Agenda for the 2010-08-17 conference call (from eric@tibco.com on 2010-08-16)
4. Agenda for the 2010-08-03 conference call (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-57 (Unflagged assertion about JMS destination): @location attribute assertion about being a JMS Destination, but not flagged. [SOAP-JMS Binding specification] (from sysbot+tracker@w3.org on 2010-07-16)

Related notes:

Display change log