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

ISSUE-1: update available

From: Phil Adams <phil_adams@us.ibm.com>
Date: Mon, 10 Aug 2009 14:40:34 -0500
To: public-soap-jms@w3.org
Message-ID: <OF1818E351.CB34BAA5-ON8625760E.006B3115-8625760E.006C15F0@us.ibm.com>
Hi everyone,
I've committed changes to resolve ISSUE-1 to the binding spec.   Version 
1.53 of soapjms.html has these changes.

You can view the document here: 

Please take a look before tomorrow's call if you have time. 

Note that I took the liberty to make a slight editorial change from the 
proposed text that we settled on in last week's meeting. 
For example, the proposed change was this:
"If the charset parameter is specified it is checked to ensure that it 
matches the encoding value from the supplied XML. A fault MUST be 
generated with [Definition: subcode *contentTypeMismatch* if the encoding 
values do not match.]†"

But I moved the "[Definition:" part back to the beginning of the 
containing sentence, like this:
[Definition: A fault MUST be generated with subcode contentTypeMismatch if 
the encoding values do not match.†] 

I made this small change so that the full sentence would appear in the 
assertion table in Appendix E.
This seems to be aligned with other similar situations throughout the 
document (e.g. sentences that start with "Use fault subcode XYZ" are 
usually completely within the "Definition:" marker).

I'll be making similar changes for issues 2-7.  Hopefully I can get them 
all finished before tomorrow's call...


Phil Adams (phil_adams@us.ibm.com)

WebSphere Application Server
Office: (512) 286-5041 (t/l 363)
Web Services Development
Cell: (512) 750-6599
IBM - Austin, TX

Received on Monday, 10 August 2009 19:41:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:17:21 UTC