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


Help: OASIS Mailing Lists Help | MarkMail Help

ws-rx-editors message

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

Subject: Submission Package for WSRM 1.2


Please find attached the submission package for WSRM 1.2 OS vote. Expect 
two others shortly!


WSRM 1.2
(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
PDF - TBD by OASIS Staff
Schema - 
Namespace - 
(b) The editable version of all files that are part of the Committee

TBD by OASIS Staff

(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 TC;


(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.
Paul Fremantle
CTO and Co-Founder, WSO2
VP, Apache Synapse

Office: +44 844 484 8143
Cell: +44 798 447 4618

blog: http://pzf.fremantle.org

"Oxygenating the Web Service Platform", www.wso2.com

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