Web Services Atomic Transaction 1.1 Errata

2Web Services Coordination (WS- 3Coordination) Version 1.1 Errata

4Approved Errata

512 July 2007

6Specification URIs: 7This Version: 8 http://docs.oasis-open.org/ws-tx/wstx-wscoor-1.1-errata-os/wstx-wscoor-1.1-errata-os.html 9 http://docs.oasis-open.org/ws-tx/wstx-wscoor-1.1-errata-os.doc 10 http://docs.oasis-open.org/ws-tx/wstx-wscoor-1.1-errata-os.pdf 11Previous Version: 12 http://docs.oasis-open.org/ws-tx/wstx-wscoor-1.1-errata-pr/wstx-wscoor-1.1-errata-pr.html 13 http://docs.oasis-open.org/ws-tx/wstx-wscoor-1.1-errata-pr.doc 14 http://docs.oasis-open.org/ws-tx/wstx-wscoor-1.1-errata-pr.pdf 15Latest Approved Version: 16 http://docs.oasis-open.org/ws-tx/wstx-wscoor-1.1-errata/wstx-wscoor-1.1-errata.html 17 http://docs.oasis-open.org/ws-tx/wstx-wscoor-1.1-errata.doc 18 http://docs.oasis-open.org/ws-tx/wstx-wscoor-1.1-errata.pdf 19Technical Committee: 20 OASIS Web Services Transaction (WS-TX) TC 21Chair(s): 22 Eric Newcomer, Iona 23 Ian Robinson, IBM 24Editor(s): 25 Max Feingold, Microsoft 26 Ram Jeyaraman, Microsoft 27Related work: 28 This specification errata is related to WS-Coordination v1.1. 29Abstract: 30 This document lists errata for the OASIS Web Services Coordination Version 1.1 OASIS 31 Standard [WSCOOR] produced by the WS-TX Technical Committee. The standard was 32 approved by the OASIS membership on 16 April 2007. 33Status: 34 This document was last revised or approved by the WS-TX TC on the above date. The level of 35 approval is also listed above. Check the “Latest Approved Version” location noted above for 36 possible later revisions of this document. 37 Technical Committee members should send comments on this specification to the Technical 38 Committee’s email list. Others should send comments to the Technical Committee by using the 39 “Send A Comment” button on the Technical Committee’s web page at www.oasis- 40 open.org/committees/ws-tx .

41 For information on whether any patents have been disclosed that may be essential to 42 implementing this specification, and any offers of patent licensing terms, please refer to the 43 Intellectual Property Rights section of the Technical Committee web page (www.oasis- 44 open.org/committees/ws-tx/ipr.php). 45 The non-normative errata page for this specification is located at www.oasis- 46 open.org/committees/ws-tx.

47Notices

48Copyright © OASIS Open 2007. All Rights Reserved. 49All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual 50Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website. 51This document and translations of it may be copied and furnished to others, and derivative works that 52comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, 53and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice 54and this section are included on all such copies and derivative works. However, this document itself may 55not be modified in any way, including by removing the copyright notice or references to OASIS, except as 56needed for the purpose of developing any document or deliverable produced by an OASIS Technical 57Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must 58be followed) or as required to translate it into languages other than English. 59The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors 60or assigns. 61This document and the information contained herein is provided on an "AS IS" basis and OASIS 62DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY 63WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY 64OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 65PARTICULAR PURPOSE. 66OASIS requests that any OASIS Party or any other party that believes it has patent claims that would 67necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, 68to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to 69such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that 70produced this specification. 71OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of 72any patent claims that would necessarily be infringed by implementations of this specification by a patent 73holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR 74Mode of the OASIS Technical Committee that produced this specification. OASIS may include such 75claims on its website, but disclaims any obligation to do so. 76OASIS takes no position regarding the validity or scope of any intellectual property or other rights that 77might be claimed to pertain to the implementation or use of the technology described in this document or 78the extent to which any license under such rights might or might not be available; neither does it 79represent that it has made any effort to identify any such rights. Information on OASIS' procedures with 80respect to rights in any document or deliverable produced by an OASIS Technical Committee can be 81found on the OASIS website. Copies of claims of rights made available for publication and any 82assurances of licenses to be made available, or the result of an attempt made to obtain a general license 83or permission for the use of such proprietary rights by implementers or users of this OASIS Committee 84Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no 85representation that any information or list of intellectual property rights will at any time be complete, or 86that any claims in such list are, in fact, Essential Claims.

87Table of contents

881 List of Changes...... 5 89 1.1 Section 1.8 Normative References, lines 118-120:...... 5 902 References...... 6 91A. Acknowledgements...... 7 92

931 List of Changes

951.1 Section 1.8 Normative References, lines 118-120: 96 97Replace: 98 99[WSPOLICY] Web Services Policy Framework (WS-Policy), 100http://schemas.xmlsoap.org/ws/2004/09/policy, VeriSign, Microsoft, Sonic Software, IBM, BEA Systems, 101SAP, September 2004. 102 103With: 104 105[WSPOLICY] Web Services Policy 1.2 – Framework (WS-Policy), 106http://www.w3.org/Submission/2006/SUBM-WS-Policy-20060425/, W3C Member Submission, 25 April 1072006.

1082 References 109 [WSCOOR] Web Services Coordination (WS-Coordination) version 1.1, "http:/docs.oasis- 110 open.org/ws-tx/wscoor/2006/06".

111A. Acknowledgements

112This document is based on initial contributions to the OASIS WS-TX Technical Committee by the 113following authors: Luis Felipe Cabrera (Microsoft), George Copeland (Microsoft), Max Feingold 114(Microsoft), Robert W Freund (Hitachi), Tom Freund (IBM), Jim Johnson (Microsoft), Sean Joyce (IONA), 115Chris Kaler (Microsoft), Johannes Klein (Microsoft), David Langworthy (Microsoft), Mark Little (Arjuna 116Technologies), Frank Leymann (IBM), Eric Newcomer (IONA), David Orchard (BEA Systems), Ian 117Robinson (IBM), Tony Storey (IBM), Satish Thatte (Microsoft). 118 119The following individuals have provided invaluable input into the initial contribution: Francisco Curbera 120(IBM), Doug Davis (IBM), Gert Drapers (Microsoft), Don Ferguson (IBM), Kirill Gavrylyuk (Microsoft), Dan 121House (IBM), Oisin Hurley (IONA), Thomas Mikalsen (IBM), Jagan Peri (Microsoft), John Shewchuk 122(Microsoft), Stefan Tai (IBM). 123 124The following individuals were members of the committee during the development of this specification: 125Participants: 126 Charlton Barreto, Adobe Systems, Inc. 127 Martin Chapman, Oracle 128 Kevin Conner, JBoss Inc. 129 Paul Cotton, Microsoft Corporation 130 Doug Davis, IBM 131 Colleen Evans, Microsoft Corporation 132 Max Feingold, Microsoft Corporation 133 Thomas Freund, IBM 134 Robert Freund, Hitachi, Ltd. 135 Peter Furniss, Choreology Ltd. 136 Marc Goodner, Microsoft Corporation 137 Alastair Green, Choreology Ltd. 138 Daniel House, IBM 139 Ram Jeyaraman, Microsoft Corporation 140 Paul Knight, Nortel Networks Limited 141 Mark Little, JBoss Inc. 142 Jonathan Marsh, Microsoft Corporation 143 Monica Martin, Sun Microsystems 144 Joseph Fialli, Sun Microsystems 145 Eric Newcomer, IONA Technologies 146 Eisaku Nishiyama, Hitachi, Ltd. 147 Alain Regnier, Ricoh Company, Ltd. 148 Ian Robinson, IBM 149 Tom Rutt, Fujitsu Limited 150 Andrew Wilkinson, IBM