[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Web Services Business Process Execution Language Version 2.0 Submitted for OASIS Standard
OASIS Members: The OASIS OASIS Web Services Business Process Execution Language (WSBPEL) Technical Committee has submitted the following specification set, which is an approved Committee Specification, to be considered as an OASIS Standard: Web Services Business Process Execution Language Version 2.0 The text of the TC submission is appended. You now have until 15 March to familiarize yourself with the submission and provide input to your organization's voting representative. On 16 March, a Call For Vote will be issued to all Voting Representatives of OASIS member organizations. They will have until the last day of March, 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.php#3.4 Any statements related to the IPR of this specification are posted at: http://www.oasis-open.org/committees/wsbpel/ipr.php Your participation in the review and balloting process is greatly appreciated. Mary Mary P McRae Manager of TC Administration, OASIS email: firstname.lastname@example.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 Business Process Execution Language Version 2.0 http://docs.oasis-open.org/wsbpel/2.0/CS01/wsbpel-v2.0-CS01.doc http://docs.oasis-open.org/wsbpel/2.0/CS01/wsbpel-v2.0-CS01.html http://docs.oasis-open.org/wsbpel/2.0/CS01/wsbpel-v2.0-CS01.pdf Schemas: http://docs.oasis-open.org/wsbpel/2.0/CS01/plnktype/ws-bpel_plnktype.xsd http://docs.oasis-open.org/wsbpel/2.0/CS01/process/abstract/ws-bpel_abstract_common_base.xsd http://docs.oasis-open.org/wsbpel/2.0/CS01/process/executable/ws-bpel_executable.xsd http://docs.oasis-open.org/wsbpel/2.0/CS01/serviceref/ws-bpel_serviceref.xsd http://docs.oasis-open.org/wsbpel/2.0/CS01/varprop/ws-bpel_varprop.xsd (b) The editable version of all files that are part of the Committee Specification; http://docs.oasis-open.org/wsbpel/2.0/CS01/wsbpel-v2.0-CS01.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; The schema were validated and checked for well-formedness with Altova XMLSpy 2007Sp2 on 2007feb02. (http://lists.oasis-open.org/archives/wsbpel/200702/msg00004.html) (d) A clear English-language summary of the specification; WS-BPEL is an XML based language enabling users to describe business process activities as Web services and define how they can be connected to accomplish specific tasks. WS-BPEL is designed to specify business processes that are both composed of, and exposed as, Web Services. (e) A statement regarding the relationship of this specification to similar work of other OASIS TCs or other standards developing organizations; No such relationships exist. (f) Certification by at least three OASIS member organizations that they are successfully using the specification; The following email document usage by TC member companies: Sun Microsystems: http://www.oasis-open.org/archives/wsbpel/200701/msg00079.html SEEBURGER AG: http://www.oasis-open.org/archives/wsbpel/200701/msg00075.html Intalio http://www.oasis-open.org/archives/wsbpel/200701/msg00067.html IBM http://www.oasis-open.org/archives/wsbpel/200701/msg00065.html Active Endpoints, Inc. http://www.oasis-open.org/archives/wsbpel/200701/msg00062.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; The first public review period started on Sept. 10, 2006 and ended on Nov. 9, 2006. The announcement is at: http://lists.oasis-open.org/archives/tc-announce/200609/msg00004.html The second and last public review period started on Jan.7, 2007 and ended Jan. 22, 2007. The announcement is at: http://lists.oasis-open.org/archives/tc-announce/200701/msg00006.html All comments/issues raised during public review are documented here, along with their resolutions: http://www.oasis-open.org/committees/download.php/21303/WS_BPEL_review_issues_list.html (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; Vote to approve the specification as a Committee Specification was held during the TC meeting on Jan. 31, 2007. Details of the vote are included in the minutes: http://www.oasis-open.org/committees/download.php/22057/Minutes%20for%20Jan%2031.htm (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; There have been no previous attempts to standardize WS-BPEL. (j) A pointer to the publicly visible comments archive for the originating TC; The comments archive is at: http://lists.oasis-open.org/archives/wsbpel-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. No minority reports exist.