OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

tc-announce message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Web Services ReliableMessaging 1.2 Submitted for OASIS Standard

OASIS Members:

The OASIS Web Services Reliable Exchange (WS-RX) Technical Committee has
submitted the following specification, which is an approved Committee
Specification, to be considered as an OASIS Standard:

Web Services ReliableMessaging 1.2

The text of the TC submission is appended.

You now have until 15 January to familiarize yourself with the submission
and provide input to your organization's voting representative.

On 16 January, a Call For Vote will be issued to all Voting Representatives
of OASIS member organizations. They will have until the last day of January,
inclusive, to cast their ballots on whether this Committee Specification
should be approved as an OASIS Standard or not.

Members who wish to discuss this ballot may do so through

In accordance with the OASIS Technical Committee Process, this Committee
Specification has already completed the necessary 60-day public review
period as noted in the submission below.

The normative TC Process for approval of Committee Specifications as OASIS
Standards is found at

Any statements related to the IPR of this specification are posted at:

Your participation in the review and balloting process is greatly


Mary P McRae
Director, Technical Committee Administration
OASIS: Advancing open standards for the information society
email: mary.mcrae@oasis-open.org  
web: www.oasis-open.org
phone: 1.603.232.9090

(a) Links to the approved Committee Specification in the TC's document
repository, and any appropriate supplemental documentation for the
specification, both of which must be written using the OASIS templates.
The specification may not have been changed between its approval as a
Committee Specification and its submission to OASIS for consideration as an
OASIS Standard, except for the changes on the title page and running footer
noting the approval status and date.

Web Services ReliableMessaging 1.2
Editable Source (Word):
Schema -
Namespace -

(b) The editable version of all files that are part of the Committee
See above.

(c) Certification by the TC that all schema and XML instances included in
the specification, whether by inclusion or reference, including fragments of
such, are well formed, and that all expressions are valid;

All schema and XML instances included in the specification are well formed
and all expressions are valid.

(d) A clear English-language summary of the specification;

The core WS-ReliableMessaging 1.2 document defines a protocol for reliable
message exchange between two Web services, even in the presence of network
or system failures. For example, the protocol can ensure the resending of
messages that have been lost, and can ensure that duplicate messages are not
delivered. The protocol allows Web service nodes to implement a variety of
delivery assurances, including At Most Once, At Least Once, Exactly Once and
In Order delivery of messages. The protocol fundamentally defines a one-way
reliable channel (known as a Sequence), but also includes mechanisms to
optimize the creation of two-way reliable exchanges. The protocol is
designed to compose with other relevant standards such as WS-Security and
WS-SecureConversation. The protocol allows developers to add reliable
delivery of messages to their applications on a variety of platforms,
including Java and .NET.

(e) A statement regarding the relationship of this specification to similar
work of other OASIS TCs or other standards developing organizations;

-- The OASIS WS-Reliable Messaging (WSRM) TC also defines a reliable
messaging specification for Web services. The WS-RX TC and
WS-ReliableMessaging specification focuses on creating a specification that
works in conjunction with and composes with other specifications, in
particular the WS-Addressing, WS-Security and WS-SecureConversation, and
WS-Policy Framework specifications.

(f) Certification by at least three OASIS member organizations that they are
successfully using the specification;

Certification via email:



(g) The beginning and ending dates of the public review(s), a pointer to the
announcement of the public review(s), and a pointer to an account of each of
the comments/issues raised during the public review period(s), along with
its resolution;

First Public Review: 4 March 2008 to 3rd May 2008

Announcement of the first Public Review:

Public Review Issue and Resolution Log:

(h) An account of and results of the voting to approve the specification as
a Committee Specification, including the date of the ballot and a pointer to
the ballot;


(i) An account of or pointer to votes and comments received in any earlier
attempts to standardize substantially the same specification, together with
the originating TC's response to each comment;

This is the first submission to the OASIS membership

(j) A pointer to the publicly visible comments archive for the originating


(k) A pointer to any minority reports submitted by one or more Members who
did not vote in favor of approving the Committee Specification, which report
may include statements regarding why the member voted against the
specification or that the member believes that Substantive Changes were made
which have not gone through public review; or certification by the Chair
that no minority reports exist.

There are no minority reports.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]