[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Web Services ReliableMessaging Policy 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 Policy 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 email@example.com. 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-2008-06-19.php#OASISstandard 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 Director, Technical Committee Administration OASIS: Advancing open standards for the information society email: firstname.lastname@example.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 Policy 1.2 PDF: http://docs.oasis-open.org/ws-rx/wsrmp/200702/wsrmp-1.2-spec-cs-02.pdf HTML: http://docs.oasis-open.org/ws-rx/wsrmp/200702/wsrmp-1.2-spec-cs-02.html Editable Source (Word): http://docs.oasis-open.org/ws-rx/wsrmp/200702/wsrmp-1.2-spec-cs-02.doc Schema: http://docs.oasis-open.org/ws-rx/wsrmp/200702/wsrmp-1.2-schema-200702.xsd Namespace: http://docs.oasis-open.org/ws-rx/wsrmp/200702/wsrmp-1.2-rddl-200702.html (b) The editable version of all files that are part of the Committee Specification; 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 WS-ReliableMessaging Policy 1.2 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. (e) A statement regarding the relationship of this specification to similar work of other OASIS TCs or other standards developing organizations; Not applicable (f) Certification by at least three OASIS member organizations that they are successfully using the specification; Certification via email: WSO2: http://lists.oasis-open.org/archives/ws-rx/200811/msg00023.html IBM: http://lists.oasis-open.org/archives/ws-rx/200811/msg00014.html Microsoft: http://lists.oasis-open.org/archives/ws-rx/200811/msg00013.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: 4 March 2008 to 3rd May 2008 Announcement of the first Public Review: http://lists.oasis-open.org/archives/tc-announce/200803/msg00002.html Public Review Issue and Resolution Log: http://docs.oasis-open.org/ws-rx/issues/pr-2008-05-16/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=1597 (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.