- From: Mark Phillips <M8PHILLI@uk.ibm.com>
- Date: Fri, 29 Jan 2010 19:10:46 +0000
- To: public-soap-jms@w3.org
I've applied the changes for ACTION-135 [1] / ISSUE-22 [2] as agreed in the call dated 2010/01/26 [3]. This completes action 135. The previous 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]. and the updated binding spec is here: http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?rev=1.74&content-type=text/html&f=h]. Specifically: ============= In appendix C2, second table, SOAPJMS_contentType row, changed "value" entry from: multipart/related type="application/xop+xml"; boundary="--MIME_boundary" to: multipart/related type="application/xop+xml"; boundary="MIME_boundary" and in the "comments" column, replaced: inferred from the SOAP Envelope and presence attachments. In this case it is SOAP 1.2 with: inferred from the SOAP Envelope and use of MTOM. In this case it is SOAP 1.2 ================================================================= This is a link to view the differences: http://dev.w3.org/cvsweb/2008/ws/soapjms/soapjms.html.diff?r1=1.73&r2=1.74&f=h ...and 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.74&r2=1.75&f=h [1] http://www.w3.org/2002/ws/soapjms/tracker/actions/135 [2] http://www.w3.org/2002/ws/soapjms/tracker/issues/22 [3] http://www.w3.org/2010/01/26-soap-jms-minutes.html Regards Mark
Received on Friday, 29 January 2010 19:20:34 UTC