ISSUE-14: Apparently normative statements about WSDL are not written that way.
WSDL conformance statements missing
Apparently normative statements about WSDL are not written that way.
- State:
- CLOSED
- Product:
- SOAP-JMS Binding specification
- Raised by:
- Eric Johnson
- Opened on:
- 2009-09-29
- Description:
- From email:
http://lists.w3.org/Archives/Public/public-soap-jms/2009Sep/0019.html
Description: Section three of the specification includes statements that
sound like they're intended to be normative. But they're not written
that way, or captured that way.
Section 3.4.2:
This section currently reads:
"The wsdl11soap11:binding element has a transport attribute. The
developer indicates the use of the SOAP/JMS binding by putting
http://www.w3.org/2008/07/soap/bindings/JMS/ as the value of the transport."
The should probably read something like:
"For each of SOAP 1.1 and SOAP 1.2, the @transport attribute of the
wsdl11soap11:binding element, and the wsdl11soap12:binding element,
respectively, indicate the transport value. To indicate that this
SOAP/JMS binding is in use, the @transport attribute MUST be set to the
value http://www.w3.org/2008/07/soap/bindings/JMS/ ."
Section 3.4.5:
This section is missing any sort of declaration that ties the URL to the
use of JMS. Suggest adding to the second paragraph of this section:
"The value of the @location attribute MUST be a URI corresponding to a
JMS Destination, and SHOULD be a "jms" scheme URI."
Section 3.5:
Has an sentence that reads:
"Line 4 shows the protocol URI in the wsoap:protocol attribute of the
<binding>, which indicates that this SOAP over JMS binding is in use."
This should probably read something like this:
"Line 4 shows the protocol URI in the @wsoap:protocol attribute of the
<binding>. To indicate that this SOAP/JMS binding is in use, the
@wsoap:protocol attribute MUST be set to the value
http://www.w3.org/2008/07/soap/bindings/JMS/ ."
Section 3.5:
This section has another sentence that reads:
"Lines 18-19 are also additions to specify the location at which this
new implementation exists. Line 19 showing the JMS URI Scheme jms: in
the address attribute of the <endpoint> element. As with the WSDL 1.1
binding, you may also set connection properties in the URI."
This should get an additional sentence:
"The value of the @address attribute MUST be a URI corresponding to a
JMS Destination, and SHOULD be a "jms" scheme URI."
- Related Actions Items:
- No related actions
- Related emails:
- Re: Agenda for the 2009-11-03 conference call (from eric@tibco.com on 2009-12-14)
- Agenda for the 2009-12-01 conference call (from peaston@progress.com on 2009-11-30)
- Agenda for the 2009-11-17 conference call (from M8PHILLI@uk.ibm.com on 2009-11-16)
- Re: Agenda for the 2009-11-03 conference call (from eric@tibco.com on 2009-11-03)
- RE: Agenda for the 2009-11-03 conference call (from Derek.Rokicki@softwareag.com on 2009-11-03)
- Agenda for the 2009-11-03 conference call (from eric@tibco.com on 2009-11-02)
- RE: Agenda for 2009-10-27 conference call (from peaston@progress.com on 2009-10-27)
- Agenda for 2009-10-27 conference call (from eric@tibco.com on 2009-10-26)
- Agenda for 2009-10-20 conference call (from eric@tibco.com on 2009-10-19)
- ISSUE-14: Update available (from phil_adams@us.ibm.com on 2009-10-13)
- Agenda for 2009-10-13 conference call (from eric@tibco.com on 2009-10-12)
- ISSUE-14 (WSDL conformance statements missing): Apparently normative statements about WSDL are not written that way. [SOAP-JMS Binding specification] (from sysbot+tracker@w3.org on 2009-09-29)
Related notes:
Opened as per: http://www.w3.org/2009/09/29-soap-jms-minutes.html
Eric Johnson, 5 Oct 2009, 22:57:46Applied resolution accepted
Peter Easton, 1 Dec 2009, 18:07:13Display change log