Document identifier:
wsbpel-specification-draft-01
Location:
http://www.oasis-open.org/apps/org/workgroup/wsbpel/
Editors:
Alexandre
Alves,
BEA <aalves@bea.com>
Assaf Arkin <arkin@intalio.com>
Sid Askary <saskary@nuperus.com>
Ben Bloch <ben_b54@hotmail.com>
Francisco Curbera,
IBM <curbera@us.ibm.com>
Yaron Goland, BEA <ygoland@bea.com>
Neelakantan Kartha,
Sterling Commerce <N_Kartha@stercomm.com>
Canyang Kevin Liu,
SAP <kevin.liu@sap.com>
Vinkesh Mehta,
Deloitte <vmehta@deloitte.com>
Satish Thatte, Microsoft <satisht@microsoft.com>
Prasad Yendluri,
webMethods <pyendluri@webmethods.com>
Alex Yiu, Oracle <alex.yiu@oracle.com>
Alexandre
Alves,
BEA <aalves@bea.com>
Contributors:
{FirstName} {Last Name}, {Organization}
Editor’s
Notes – KevinL – this section should be consolidated with Appendix
H
This
document defines a notation for specifying business process behavior based on
Web Services. This notation is called Web Services Business Process Execution
Language (abbreviated to WS-BPEL in the rest of this document). Processes in
WS-BPEL export and import functionality by using Web Service interfaces
exclusively.
Business
processes can be described in two ways. Executable business processes model
actual behavior of a participant in a business interaction. Abstract business processes are
partially specified processes that are not
intended to be executed. An
abstract process may abstract away some of the required concrete operational
details. Abstract processes serve a
descriptive role, with more than one possible use case, including observable behavior and process
templating. Business protocols, in contrast, use process
descriptions that specify the mutually visible message exchange behavior of
each of the parties involved in the protocol, without revealing their internal
behavior. The process descriptions for business protocols are called abstract
processes. WS-BPEL is meant to be used to model the behavior of
both executable and abstract processes.
WS-BPEL
provides a language for the formal specification of Executable and Abstract business
processes and business interaction protocols.
By doing so, it extends the Web Services interaction model and enables it to
support business transactions. WS-BPEL defines an interoperable integration
model that should facilitate the expansion of automated process integration in
both the intra-corporate and the business-to-business spaces.
This is
a draft version of the WS-BPEL TC specification, updated from the origninal
BPEL4WS V1.1 specification dated May 5, 2003 that was submitted to the WS BPEL
TC. See: http://www.oasis-open.org/apps/org/workgroup/wsbpel/download.php/2046/BPEL%20V1-1%20May%205%202003%20Final.pdf
If you
are on the <wsbpel@lists.oasis-open.org> list for committee members, send comments
there. If you are not on that list, subscribe to the <wsbpel-comment@lists.oasis-open.org> list and send comments there. To
subscribe, send an email message to <mailto:wsbpel-comment-request@lists.oasis-open.org> with the word "subscribe"as the body of the message.
For
information on whether any patents have been disclosed that may be essential to
implementing this specification, and any offers of patent licensing terms,
please refer to the Intellectual Property Rights section of the WS-BPEL TC web
page http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsbpel
Copyright © 2004
OASIS Open, Inc. All Rights Reserved.
1. Introduction
3. Relationship with Other Specifications
4.
This Section Has Been
Deleted
45.
Core Concepts and Usage Patterns
56.
Defining a Business Process
56.1. Initial Example
56.2. The Structure of a Business Process
56.3. Language Extensibility
5.4 Document Linking
56.54.
The Lifecycle of a Business
Process
67.
Partner Link Types, Partner Links, and Endpoint
References
67.1. Partner Link Types
67.2. Partner Links
7.3. This Section Has Been Deleted
7.4. Endpoint References
78.
Message
PropertiesVariable Properties
78.1. Motivation
78.2. Defining Properties
89.
Data Handling
89.1.
Variables
89.2.
Usage of Query and
Expression Languages Variables
89.3. Expressions