W3C home > Mailing lists > Public > public-soap-jms@w3.org > January 2010

Applied resolution for ISSUE-17 (ACTION-123)

From: Mark Phillips <M8PHILLI@uk.ibm.com>
Date: Tue, 26 Jan 2010 12:20:57 +0000
To: public-soap-jms@w3.org
Message-ID: <OFAE6A4DAB.8638C358-ON802576B7.003FFB20-802576B7.0043D633@uk.ibm.com>

I've applied the changes for ACTION-123 [1] / ISSUE-4 [2] as per the
proposal discussed in the minutes of 2009/11/10 [3].

Specifically
============
In section 1.1, changed third bullet to:

How SOAP over JMS uses the Uniform Resource Identifier (URI) [IETF RFC3986]
specification for JMS endpoints [URI Scheme for JMS].

Section 2.2.4:
Removed reference to IETF RFC 3987

Section A:
Replaced reference to "Internationalized Resource Identifiers (IRIs) (3987)
with reference to Uniform Resource Identifier (URI) (3986)

(Note: The reference to IETF RFC 3987 had been removed from Section 3.4.5
in an earlier change so did not require any changes.)

=================================================================

The updated binding spec is available here:
http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?rev=1.73&content-type=text/html&f=h



This is a link to view the differences from the previous XML Spec version:
http://dev.w3.org/cvsweb/2008/ws/soapjms/soapjms.xml.diff?r1=1.72&r2=1.73&f=h



...and this is a link to view the differences from the previous HTML
version:
http://dev.w3.org/cvsweb/2008/ws/soapjms/soapjms.html.diff?r1=1.61&r2=1.72&f=h



[1] http://www.w3.org/2002/ws/soapjms/tracker/actions/123.
[2] http://www.w3.org/2002/ws/soapjms/tracker/issues/17
[3] http://www.w3.org/2009/11/10-soap-jms-minutes.html




Mark Phillips. IBM WebSphere MQ/ESB Technical Strategy - Clients & APIs.
(bluepages entry).
Received on Tuesday, 26 January 2010 12:27:55 GMT

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