Copyright © OASIS® 1993–2007.
All Rights Reserved.
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.
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
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
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
Replace:
|
wsam
|
http://www.w3.org/2007/02/addressing/metadata
|
With:
|
wsam
|
http://www.w3.org/2007/05/addressing/metadata
|
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
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
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
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
Replace:
xmlns:wsam="http://www.w3.org/2007/02/addressing/metadata"
With:
xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata"
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
In the RM Source Sequence State Transition
Table, on the " Message Number Rollover Fault [msg]" event,
replace:
[Rollover]
With:
[Same]
In the RM Source Sequence State Transition
Table, on the " Expires exceeded [int]" event, replace:
{3.7}
With:
{3.4}
[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:
