W3C home > Mailing lists > Public > public-soap-jms@w3.org > October 2009

ISSUE-16 (non-existent "soap" prefix): Section 3.4.5 refers to a non-existent "soap" prefix [SOAP-JMS Binding specification]

From: SOAP-JMS Binding Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Tue, 20 Oct 2009 00:41:44 +0000 (GMT)
To: public-soap-jms@w3.org
Message-Id: <20091020004144.CE6907F472@otto.w3.org>

ISSUE-16 (non-existent "soap" prefix): Section 3.4.5 refers to a non-existent "soap" prefix [SOAP-JMS Binding specification]

http://www.w3.org/2002/ws/soapjms/tracker/issues/16

Raised by: Eric Johnson
On product: SOAP-JMS Binding specification

Description:

Section 3.4.5 of the specification ("Specifying Properties Via the JMS URI") starts with:

"This URI, in turn, is represented as the location attribute on the <wsdl11soap11:address>  element. Note that with SOAP 1.2, the same pattern applies, although the "soap" prefix corresponds to the SOAP 1.2 binding namespace http://schemas.xmlsoap.org/wsdl/soap12/ as established by [WSDL 1.1 for SOAP 1.2]."

The problem is that the specification doesn't define any "soap" prefix.

Proposal:
Replace the above two sentences with the following:

"This URI is found as value of the location attribute on the <wsdl11soap11:address> or <wsdl11soap12:address> element when using SOAP 1.1 and SOAP 1.2, respectively."

Changes here include:
 * Replaced the "in turn, is represented as" phrasing
 * Combined the two sentences into one
 * Used explicit references to the QNames for the elements in question
Received on Tuesday, 20 October 2009 00:41:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:16:21 GMT