[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ws-rx] WS-ReliableMessaging 1.1 Submitted for OASIS Standard
Mary On behalf of the WS-RX TC I would like to thank you for your efforts on this specification. Best Regards, Paul Mary McRae wrote: > 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: > > WS-ReliableMessaging 1.1: > - Web Services ReliableMessaging 1.1 > - Web Services ReliableMessaging Policy 1.1 > - Web Services MakeConnection 1.0 > > The text of the TC submission is appended. > > You now have until 15 May to familiarize yourself with the submission and provide input to your organization's voting > representative. > > On 16 May, a Call For Vote will be issued to all Voting Representatives of OASIS member organizations. They will have > until the last day of May, 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 member-discuss@lists.oasis-open.org. > > 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 > http://www.oasis-open.org/committees/process.php#3.4 > > Any statements related to the IPR of this specification are posted at: > http://www.oasis-open.org/committees/ws-rx/ipr.php > > Your participation in the review and balloting process is greatly appreciated. > > Mary > > Mary P McRae > Manager of TC Administration, OASIS > email: mary.mcrae@oasis-open.org > phone: 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.1 > PDF - http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-spec-cs-01.pdf > HTML - http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-spec-cs-01.html > Schema - http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-schema-200702.xsd > WSDL - http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-wsdl-200702.wsdl > Namespace - http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-rddl-200702.html > > Web Services ReliableMessaging Policy 1.1 > PDF - http://docs.oasis-open.org/ws-rx/wsrmp/200702/wsrmp-1.1-spec-cs-01.pdf > HTML - http://docs.oasis-open.org/ws-rx/wsrmp/200702/wsrmp-1.1-spec-cs-01.html > Schema - http://docs.oasis-open.org/ws-rx/wsrmp/200702/wsrmp-1.1-schema-200702.xsd > Namespace - http://docs.oasis-open.org/ws-rx/wsrmp/200702/wsrmp-1.1-rddl-200702.html > > Web Services MakeConnection 1.0 > PDF - http://docs.oasis-open.org/ws-rx/wsmc/200702/wsmc-1.0-spec-cs-01.pdf > HTML - http://docs.oasis-open.org/ws-rx/wsmc/200702/wsmc-1.0-spec-cs-01.html > Schema - http://docs.oasis-open.org/ws-rx/wsmc/200702/wsmc-1.0-schema-200702.xsd > WSDL - http://docs.oasis-open.org/ws-rx/wsmc/200702/wsmc-1.0-wsdl-200702.wsdl > Namespace - http://docs.oasis-open.org/ws-rx/wsmc/200702/wsmc-1.0-rddl-200702.html > > (b) The editable version of all files that are part of the Committee > Specification; > > http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-spec-cs-01.doc > http://docs.oasis-open.org/ws-rx/wsrmp/200702/wsrmp-1.1-spec-cs-01.doc > http://docs.oasis-open.org/ws-rx/wsmc/200702/wsmc-1.0-spec-cs-01.doc > > (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 WS-ReliableMessaging 1.1 specification consists of multiple parts. > > The core WS-ReliableMessaging 1.1 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. > > The WS-ReliableMessaging Policy 1.1 document defines an XML policy > language that enables Web services to advertise their support for the > WS-ReliableMessaging specification. The specification is designed for > use with the WS-Policy Framework. The language aids the interoperability > of nodes that support WS-ReliableMessaging by publishing their support > and requirements for aspects of reliable messaging. For example, an > endpoint may use this specification to indicate that it requires that > the reliable message protocol to be secured using transport level > security. WS-ReliableMessaging Policy is designed to be used with other > policy languages, such as WS-Security Policy, in the scope of the > WS-Policy Framework. > > The WS-MakeConnection 1.0 document defines a protocol that can be > used to allow two-way communications when only a transport specific > back-channel (such as the HTTP response mechanism) is available. For > example, this allows a client to establish a two-way reliable > message exchange even in the presence of firewalls and network address > translation, that otherwise would prevent the server from initiating > connections to the client. > > (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: > WSO2: > http://www.oasis-open.org/archives/ws-rx/200702/msg00068.html > > IBM: > http://www.oasis-open.org/archives/ws-rx/200702/msg00069.html > > SAP AG: > http://www.oasis-open.org/archives/ws-rx/200703/msg00000.html > > (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: 24 August 2006 to 21 October 2006 > Second Public Review: 12 February 2007 to 27 February 2007 > > Announcement of the first Public Review: > http://lists.oasis-open.org/archives/tc-announce/200608/msg00005.html > > Announcement of the second Public Review: > http://lists.oasis-open.org/archives/tc-announce/200702/msg00004.html > > Public Review Issue and Resolution Log: > http://docs.oasis-open.org/ws-rx/issues/pr/Issues.xml > > (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; > > http://www.oasis-open.org/committees/ballot.php?id=1266 > > (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; > > http://lists.oasis-open.org/archives/ws-rx-comment/ > > (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 VP/Technical Sales, WSO2 OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle paul@wso2.com cell/mobile +44 798 447 4618 landline +1 (646) 290 8050 "Oxygenating the Web Service Platform", www.wso2.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]