BPEL 2.0 Delay

Standard mechanisms to orchestrate business processes in Web services applications known as BPEL 2.0 standard will have to wait until next year for final OASIS approval.Amendments to enable human interactions as part of this technology will wait even longer.This being delayed until the first half of 2006 while technologists at OASIS continue sorting through approximately three dozen issues, whittled down from a list that had totaled around 230. Considered critical for applications such as transactional and B2B systems, the XML-based BPEL technology has wide industry support.BPEL has functions such as language constructs to enable if-then-else statements for the 2.0 version. Dynamic, parallel invocation of services also is an important addition,for adapting the number of steps in a process based on the number of partners participating in a transaction, according to IBM. Version 2.0 is aimed at improving the way that Web services are used to call out to partner links to enable more flexibility. One of the noted weakness in BPEL2.0 is that it is orchestrated automation and perhaps provides limited flexibility for accommodating human workflow mechanisms. IBM’s BPEL4People is defined in a way that it is layered on top of the BPEL language so that its features can be composed with the BPEL core features whenever needed as this paper explains in detail.
BPEL identified as one of the hot technologies for 2005 is an important component in the development of In order to work effectively a BPMS often requires that the underlying software is constructed according to the principles of a service-oriented architecture. Business Process Execution Language for Web Services provides a means to formally specify business processes and interaction protocols. BPEL4WS provides a language for the formal specification of business processes and business interaction protocols. By doing so, it extends the Web Services interaction model and enables it to support business transactions. BPEL4WS 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. It is often the case that to make a suite of existing legacy systems to fit with a BPMS is often difficult.
business process management solutions, a hot rage these days critically depend on this standard to be finalized fast. As this clarification shows BPEL is an interchange language allowing systems that otherwise don't talk to one another to understand some basic system-to-system issues. It's analogous to SQL in that way. It's not a standard language where a business analyst would to start to define a process.I agree with the view its not a lingua franca bit its evolution shows fair amount of legitimate cooperation among otherwise competitive vendors, & the fact that it has now been adopted and is being managed by OASIS - all that says this is a good thing and something to keep on top of.