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


Help: OASIS Mailing Lists Help | MarkMail Help

wsrm message

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

Subject: [Fwd: Re: WS-Reliability press release]

The press reliease will be occuring the first week of November.

Tom Rutt

Tom Rutt	email: tom@coastin.com; trutt@us.fujitsu.com
Tel: +1 732 801 5744          Fax: +1 732 774 5133

--- Begin Message ---
Aren't we talking about dropping a press release the first week of November?
Karl's message seems to indicate that voting doesn't conclude until 31 Oct.

When voting begins (16 Oct), I'll prepare a formal notification and ask you
to forward it to your TC members. It will contain hard dates and deadlines.
If you want to share the information below with your team before then,
that's fine. Please stress that all TC members should be sure their
organizations have a rep on the OASIS PR Group


-----Original Message-----
From: Tom Rutt [mailto:tom@coastin.com] 
Sent: Thursday, September 30, 2004 12:19 PM
To: Carol Geyer
Subject: Re: WS-Reliability press release

I am available every day of october, except Oct 20 thru 24.

Should I relay this message to the WSRM TC so each company can begin to
prepare their statement?

Tom Rutt

Carol Geyer wrote:

>When Karl's Call for Vote goes out, I'll send an announcement to the 
>OASIS PR Group and the OASIS WSRM TC, notifying members that a press 
>release is being prepared in anticipation of WS-Reliability being 
>approved as an OASIS Standard. The release will list all the OASIS 
>Sponsor members who are current members of the OASIS WSRM TC, as well 
>as non-profit orgs that have endorsed the work. These companies and 
>orgs will have a chance to prepare and send me quotes, should they so 
>desire. Sponsor members of OASIS who are not members of the OASIS WSRM 
>TC may also send WS-Reliability endorsement quotes, but they will not 
>be named as TC members. Our goal is to be ready to drop the press 
>release as soon as the positive results of the vote are announced.
>We can set the exact date of the release when the CfV goes out, but we 
>need to be sure you (or your TC's designated spokespersons) are 
>available to field press calls that day.
>Any members of the OASIS WSRM TC that would like to issue their own 
>press releases and/or speak to the press in support of WS-Reliability 
>are certainly welcome to do so. We ask only that they do not do this in 
>advance of the OASIS release.
>Looking forward to working on this,
>-----Original Message-----
>From: Karl F. Best [mailto:karl.best@oasis-open.org]
>Sent: Thursday, September 30, 2004 8:59 AM
>To: members@lists.oasis-open.org; tc-announce@lists.oasis-open.org
>Subject: [members] WS-Reliability specification submitted for OASIS 
>OASIS members:
>The OASIS Web Services Reliable Messaging (WSRM) TC has submitted the 
>WS-Reliability v1.1 specification, which is an approved Committee 
>Draft, for review and consideration for approval by OASIS members to 
>become an OASIS Standard. The TC's submission is attached below.
>In accordance with the OASIS Technical Committee Process, the 
>specification has already gone through a 30 day public review period.
>OASIS members now have until the 15th of the month to familiarize 
>themselves with the submission. OASIS members should give their input 
>on this question to the voting representative of their organization.
>By the 16th of the month I will send out a Call For Vote to the voting 
>representatives of the OASIS member organizations, who will have until 
>the end of the month to cast their ballots on whether this Committee 
>Draft should be approved as an OASIS Standard.
>The normative TC Process for approval of Committee Drafts as OASIS 
>Standards is found at 
>Any statements related to the IPR of this specification are posted at 
>Karl F. Best
>Vice President, OASIS
>office  +1 978.667.5115 x206     mobile +1 978.761.1648
>karl.best@oasis-open.org      http://www.oasis-open.org
>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;
>The zip file at
>contains the following five files:
>     WS-Reliability-CD1.086.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;
>The WS-Reliabilty specification, version 1.1, specifies a 
>transport-independent, SOAP based protocol for the reliable delivery of 
>messages. Reliable message delivery may be critical to some 
>applications using 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.
>The WS Reliability specification provides the following reliability
>- 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"
>delivery semantics.
>- Guaranteed message ordering for delivery within a group of
>(sequential) messages.
>The WS-Reliabilty specification uses SOAP 1.1 or 1.2 Part 1. It may be 
>used with other transport protocols/bindings besides HTTP.
>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
>4. Certification by at least three OASIS member organizations that they 
>are successfully using the specification consistently with the OASIS 
>IPR Policy;
>The chair has received statements from the following TC member 
>NEC Corporation:
>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 approve the 
>specification as a Committee Draft;
>Account of a 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 writing.
>Submitted by the OASIS WSRM TC chair, Tom Rutt, trutt@us.fujitsu.com
>This email list is used solely by OASIS for official consortium 
>communications. Opt-out requests may be sent to 
>member_services@oasis-open.org, however, all members are strongly 
>encouraged to maintain a subscription to this list.

Tom Rutt	email: tom@coastin.com; trutt@us.fujitsu.com
Tel: +1 732 801 5744          Fax: +1 732 774 5133

--- End Message ---

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