ISSUE-56: @transport value assertion not flagged, should be

Unflagged assertion about @transport value

@transport value assertion not flagged, should be

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:
In section 3.3.2, we have:
"To indicate that this SOAP/JMS binding is in use, the transport attribute MUST be set to the value http://www.w3.org/2010/soapjms/ . "

Problem:
This is not flagged as a normative statement.

Suggestion flag it as such (WSDLUsage-3003).

Note - I don't believe that this assertion is testable. Some other value implies some other binding.

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. ACTION-201 (Part 1) - Issue-56 and 57 (from M8PHILLI@uk.ibm.com on 2010-08-23)
3. RE: Agenda for the 2010-08-17 conference call (from Derek.Rokicki@softwareag.com on 2010-08-17)
4. Agenda for the 2010-08-17 conference call (from eric@tibco.com on 2010-08-16)
5. Agenda for the 2010-08-03 conference call (from eric@tibco.com on 2010-08-02)
6. Agenda for the 2010-07-27 conference call (from eric@tibco.com on 2010-07-26)
7. Re: Agenda for the 2010-07-20 conference call (from eric@tibco.com on 2010-07-20)
8. RE: Agenda for the 2010-07-20 conference call (from Derek.Rokicki@softwareag.com on 2010-07-20)
9. Re: Agenda for the 2010-07-20 conference call (from phil_adams@us.ibm.com on 2010-07-20)
10. Agenda for the 2010-07-20 conference call (from eric@tibco.com on 2010-07-19)
11. Re: ACTION 186 - top to bottom review of current copy of spec (from eric@tibco.com on 2010-07-16)
12. ISSUE-56 (Unflagged assertion about @transport value): @transport value assertion not flagged, should be [SOAP-JMS Binding specification] (from sysbot+tracker@w3.org on 2010-07-16)

Related notes:

Display change log