Web Services Reliable Messaging (WS-ReliableMessaging) Version 1.1 Errata

Approved Errata

07 January 2008

Specification URIs:

This Version:

http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-errata-cs-01.pdf

http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-errata-cs-01.html

http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-errata-cs-01.doc

Previous Version:

http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-errata-cd-01.pdf

http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-errata-cd-01.html

http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-errata-cd-01.doc

Latest Version:

http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-errata-cs-01.pdf

http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-errata-cs-01.html

http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-errata-cs-01.doc

Technical Committee:

OASIS Web Services Reliable Exchange (WS-RX) TC

Chairs:

Paul Fremantle <paul@wso2.com>

Sanjay Patil <sanjay.patil@sap.com>

Editors:

Doug Davis, IBM <dug@us.ibm.com>

Anish Karmarkar, Oracle <Anish.Karmarkar@oracle.com>

Gilbert Pilz, BEA <gpilz@bea.com>

Steve Winkler, SAP <steve.winkler@sap.com>

Ümit Yalçinalp, SAP <umit.yalcinalp@sap.com>

Related Work:

This specification errata is related to WS-ReliableMessaging v1.1.

Abstract:

This document lists errata for the OASIS Web Services Reliable Messaging Version 1.1 OASIS Standard [WS-RM] produced by the WS-RX Technical Committee. The standard was approved by the OASIS membership on 14 June 2007.

Status:

This document was last revised or approved by the WS-RX Technical Committee on the above date. The level of approval is also listed above. Check the "Latest Version" or "Latest Approved Version" location noted above for possible later revisions of this document.

Technical Committee members should send comments on this specification to the Technical Committee's email list. Others should send comments to the Technical Committee by using the "Send A Comment" button on the Technical Committee's web page at http://www.oasis-open.org/committees/ws-rx/.

For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page (http://www.oasis-open.org/committees/ws-rx/ipr.php).

The non-normative errata page for this specification is located at http://www.oasis-open.org/committees/ws-rx/.


Notices

Copyright © OASIS® 1993–2007. All Rights Reserved. OASIS trademark, IPR and other policies apply.

All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.

OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.

OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.

The name "OASIS", WS-ReliableMessaging, WSRM and WS-RX are trademarks of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see http://www.oasis-open.org/who/trademark.php for above guidance.

Table of Contents

1      List of Changes. 5

1.1 Section 1.3 Non-Normative References, line 253-255: 5

1.2 Section 1.3 Non-Normative References, line 260-262: 5

1.3 Section 1.4 Namespace, line 291: 5

1.4 Use of the word "Sequence": 5

1.5 References to WS-RM and WS-Addressing XML items: 5

1.6 Use of the word "Offer": 6

1.7 Use of the word "Identifier": 6

1.8 Appendix B. WSDL, line 1804: 6

1.9 Appendix B. WSDL, Line 1797: 6

1.10 Appendix D. State Tables, line 2141: 7

1.11 Appendix B. WSDL, line 2141: 7

2      References. 8

Appendix A. Acknowledgments. 9

 

1        List of Changes

1.1 Section 1.3 Non-Normative References, line 253-255:

Replace:

W3C Candidate Recommendation, "Web Services Policy 1.5 - Framework," February 2007.
http://www.w3.org/TR/2007/CR-ws-policy-20070228

With:

W3C Recommendation, "Web Services Policy 1.5 - Framework," September 2007.
http://www.w3.org/TR/2007/REC-ws-policy-20070904

1.2 Section 1.3 Non-Normative References, line 260-262:

Replace:

W3C Candidate Recommendation, "Web Services Policy 1.5 - Attachment," February 2007.
http://www.w3.org/TR/2007/CR-ws-policy-attach-20070228

With:

W3C Recommendation, "Web Services Policy 1.5 - Attachment," September 2007.
http://www.w3.org/TR/2007/REC-ws-policy-attach-20070904

1.3 Section 1.4 Namespace, line 291:

Replace:

wsam

http://www.w3.org/2007/02/addressing/metadata

With:

wsam

http://www.w3.org/2007/05/addressing/metadata

1.4 Use of the word "Sequence":

There are several places in the specification where the word "sequence" was used when referring to a WS-RM Sequence. These are replaced with the capitalized "S" version of the word. For example:

Replace:

sequence

With:

Sequence

1.5 References to WS-RM and WS-Addressing XML items:

In the text of the WS-RM specification, there are several placed where the use of the WS-RM and WS-Addressing XML items are referenced. Some of these references incorrectly used the wrong font. They are changed to use Courier New 10pt.  For example:

Replace:

AcksTo

With:

AcksTo

1.6 Use of the word "Offer":

There are several places in the specification where the word "Offer" was used when referring to a WS-RM Sequence that was created using the WS-RM Offer feature. These are replaced with the non-capitalized "o" version of the word as they did not refer to the WS-RM Offer element. For example:

Replace:

Offered

With:

offered

1.7 Use of the word "Identifier":

There are several places in the specification where the word "identifier" was used when referring to the WS-RM Identifier element. These are replaced with the capitalized "I" version of the word. For example:

Replace:

identifier

With:

Identifier

1.8 Appendix B. WSDL, line 1804:

Replace:

xmlns:wsam="http://www.w3.org/2007/02/addressing/metadata"

With:

xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata"

1.9 Appendix B. WSDL, Line 1797:

Due to the change in the WSDL (see section 1.8, above), a new WSDL file was created.

Replace:

http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-wsdl-200702.wsdl

With:

http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-wsdl-200702e1.wsdl

1.10 Appendix D. State Tables, line 2141:

In the RM Source Sequence State Transition Table, on the " Message Number Rollover Fault [msg]" event, replace:

[Rollover]

With:

[Same]

1.11 Appendix B. WSDL, line 2141:

In the RM Source Sequence State Transition Table, on the " Expires exceeded [int]" event, replace:

{3.7}

With:

{3.4}

 

2        References

 [WS-RM]                OASIS WS-RX Technical OASIS Standard, "Web Services Reliable Messaging ( WS-RM)," June 2007
http://docs.oasis-open.org/ws-rx/wsrm/v1.1/wsrm.pdf

 

Appendix A.  Acknowledgments

This document is based on initial contribution to OASIS WS-RX Technical Committee by the following authors:


Ruslan Bilorusets, BEA

Don Box, Microsoft

Luis Felipe Cabrera, Microsoft

Doug Davis, IBM

Donald Ferguson, IBM

Christopher Ferris, IBM

Tom Freund. IBM

Mary Ann Hondo, IBM

John Ibbotson, IBM

Lei Jin, BEA

Chris Kaler, Microsoft

David Langworthy-Editor, Microsoft

Amelia Lewis, TIBCO Software

Rodney Limprecht, Microsoft

Steve Lucco, Microsoft

Don Mullen, TIBCO Software

Anthony Nadalin, IBM

Mark Nottingham, BEA

David Orchard, BEA

Jamie Roots, IBM

Shivajee Samdarshi, TIBCO Software

John Shewchuk, Microsoft

Tony Storey, IBM


The following individuals have provided invaluable input into the initial contribution:


Keith Ballinger, Microsoft

Stefan Batres, Microsoft

Rebecca Bergersen, Iona

Allen Brown, Microsoft

Michael Conner, IBM

George Copeland, Microsoft

Francisco Curbera, IBM

Paul Fremantle, IBM

Steve Graham, IBM

Pat Helland, Microsoft

Rick Hill, Microsoft

Scott Hinkelman, IBM

Tim Holloway, IBM

Efim Hudis, Microsoft

David Ingham, Microsoft

Gopal Kakivaya, Microsoft

Johannes Klein, Microsoft

Frank Leymann, IBM

Martin Nally, IBM

Peter Niblett, IBM

Jeffrey Schlimmer, Microsoft

James Snell, IBM

Keith Stobie, Microsoft

Satish Thatte, Microsoft

Stephen Todd, IBM

Sanjiva Weerawarana, IBM

Roger Wolter, Microsoft


The following individuals were members of the committee during the development of this specification:


Abbie Barbir, Nortel

Charlton Barreto, Adobe

Stefan Batres, Microsoft

Hamid Ben Malek, Fujitsu

Andreas Bjarlestam, Ericsson

Toufic Boubez, Layer 7

Doug Bunting, Sun

Lloyd Burch, Novell

Steve Carter, Novell

Martin Chapman, Oracle

Dave Chappell, Sonic

Paul Cotton, Microsoft

Glen Daniels, Sonic

Doug Davis, IBM

Blake Dournaee, Intel

Jacques Durand, Fujitsu

Colleen Evans, Microsoft

Christopher Ferris, IBM

Paul Fremantle, WSO2

Robert Freund, Hitachi

Peter Furniss, Erebor

Marc Goodner, Microsoft

Alastair Green, Choreology

Mike Grogan, Sun

Ondrej Hrebicek, Microsoft

Kazunori Iwasa, Fujitsu

Chamikara Jayalath, WSO2

Lei Jin, BEA

Ian Jones, BTplc

Anish Karmarkar, Oracle

Paul Knight, Nortel

Dan Leshchiner, Tibco

Mark Little, JBoss

Lily Liu, webMethods

Matt Lovett, IBM

Ashok Malhotra, Oracle

Jonathan Marsh, Microsoft

Daniel Millwood, IBM

Jeff Mischkinsky, Oracle

Nilo Mitra, Ericsson

Peter Niblett, IBM

Duane Nickull, Adobe

Eisaku Nishiyama, Hitachi

Dave Orchard, BEA

Chouthri Palanisamy, NEC

Sanjay Patil, SAP

Gilbert Pilz, BEA

Martin Raepple, SAP

Eric Rajkovic, Oracle

Stefan Rossmanith, SAP

Tom Rutt, Fujitsu

Rich Salz, IBM

Shivajee Samdarshi, Tibco

Vladimir Videlov, SAP

Claus von Riegen, SAP

Pete Wenzel, Sun

Steve Winkler, SAP

Ümit Yalçinalp, SAP

Nobuyuki Yamamoto, Hitachi