[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsrm] Draft Submission letter for TC review
Comments / updates:
List Item #2: ("A clear English-language summary of the specification")
The summary is using wording ("SOAP Module") that we removed in recent versions.
Suggests to reuse text from new Intro (instead of 1st paragraph under 2):
"WS-Reliability is a SOAP-based ([SOAP 1.1] and [SOAP 1.2 Part 1]) specification that fulfills reliable messaging requirements critical to some applications of Web Services. SOAP over HTTP [RFC2616] is not sufficient when an application-level messaging protocol must also guarantee some level of reliability and security. This specification defines reliability in the context of current Web Services standards. This specification has been designed for use in combination with other complementary protocols and builds on previous experiences (e.g., ebXML Message Service [ebMS].)"
List Item #4:
Fujitsu has successfully used for implementation the WS-Reliability committee
draft 1.086 approved for final submission to OASIS, consistently with the OASIS
From: Tom Rutt [mailto:email@example.com]
Sent: Wednesday, August 25, 2004 6:22 AM
Subject: [wsrm] Draft Submission letter for TC review
here is the draft submission letter for TC review.
Please provide any comments before Thursday Morning.
WSRM TC Chair
Draft Submission Letter for WS-Reliability 1.1
1. A formal specification that is a valid member of its type, together
with appropriate documentation for the specification, both of which
must be written using approved OASIS templates.
Zip file at:
containing the following five files:
WS-Reliability-CD1086.pdf WS-Reliability version 1.1, CD 1.086
ws-reliability-1.1.xsd Ws-Reliability schema
reference-1.1.xsd Reference type schema
fnp-1.1.xsd Features and Properties schema
wsrmfp-1.1.xsd wsrm features and properties schema
2. A clear English-language summary of the specification.
WS-Reliability version 1.1 specifies a SOAP Module (as defined by [SOAP
1.2]), which fulfills reliable messaging requirements that are critical
in some applications of Web Services. The WS-Reliabilty Specification,
version 1.1, specifies a transport-agnostic protocol based on SOAP for
providing quality of service in the reliable delivery of messages.
This specification defines the following reliability features:
- Guaranteed message delivery, or At-Least-Once delivery semantics.
- Guaranteed message duplicate elimination, or At-Most-Once delivery
- Guaranteed message delivery and duplicate elimination, or Exactly-Once
- Guaranteed message ordering for delivery, within a group of messages.
3. A statement regarding the relationship of this specification to
similar work of other OASIS TCs or other standards developing
This specification has been designed to be used in combination with
other complementary protocols, and has built upon previous experiences
from the ebXML Message Service [ebMS].) Both WS-Reliability and ebMS
have same messaging reliability contracts as objectives: guaranteed
delivery, no duplicate delivery, ordered delivery, and combinations of
However, WS-Reliability has improved on scalability and performance by
generalizing the use of sequence numbers, and can accommodate different
security and access conditions on each party, as this is more
frequently the case with a Web service and its clients, compared to
more symmetrical access conditions in messaging. The reliability
contract is more "application-oriented" in WS-R, where acknowledgment
is on final delivery, in contrast to "on receipt" by the message
handler in ebMS.
4. Certification by at least three OASIS member organizations that they
are successfully using the specification consistently with the OASIS IPR
The chair has received statements from the following TC member
organizations. We include pointers to the e-mail archive record of the
<note the following letters do not explicity mention WS-Reliability CD
1.086, and should be updated by the member companies to add the explicit
reference to the CD>
5. An account of each of the comments/issues raised during the public
review period, along with its resolution.
6. An account of and results of the voting to approve the
specification as a Committee Draft.
TC roll call vote at teleconf on August 24, 2004
Name Company Vote for CD 1.086
--------------- ------------------- ------------------
Joseph Chiusano Booz Allen Hamilton y
Jeff Turpin Cyclone Commerce y
Jacques Durand Fujitsu y
Kazunori Iwasa Fujitsu Not present
Tom Rutt Fujitsu y
Jishnu Mukerji Hewlett-Packard Not present
Robert Freund Hitachi y
Eisaku Nishiyama Hitachi y
Nobuyuki Yamamoto Hitachi Not present
Junichi Tatemura NEC Corporation y
Alan Weissberger NEC Corporation y
Abbie Barbir Nortel Networks y
Mark Peel Novell y
Sunil Kunisetty Oracle y
Jeff Mischkinsky Oracle Not present
Pete Wenzel SeeBeyond y
Doug Bunting Sun Microsystems y
Tony Graham Sun Microsystems y
Chi-Yuen Ng Univ of Hong Kong y
15 yes, 0 no, 0 abstain, 4 not present
78% of eligible voting members voted yes
0% of eligible voting members voted no
0% of eligible voting members abstained
7. 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 specification has not been previously submitted to OASIS.
8. A pointer to the publicly visible comments archive for the originating TC
WSRM TC public comment list:
WSRM TC list:
9. A statement from the chair of the TC certifying that all members of
the TC have been provided with a copy of the OASIS IPR Policy.
The TC chair certifies that all members have been reminded to read the
IPR statement on numerous occasions and also in an e-mail
“Call for IPR disclosure regarding ws-Reliability spec” at:
10. Optionally, a pointer to any minority reports submitted by one or
more TC members who did not vote in favor of approving the Committee
Draft, or certification by the chair that no minority reports exist.
No minority reports have been submitted to the chair as of this
Submitted by the TC chair, Tom Rutt, firstname.lastname@example.org
Tom Rutt email: email@example.com; firstname.lastname@example.org
Tel: +1 732 801 5744 Fax: +1 732 774 5133
To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsrm/members/leave_workgroup.php.