OASIS Forms Committee to Promote BPEL

 
 
By Darryl K. Taft  |  Posted 2003-04-29 Email Print this article Print
 
 
 
 
 
 
 

The group, led by IBM, Microsoft, BEA, Siebel and SAP, will work to advance the Business Process Execution Language for Web Services specification.

The Organization for the Advancement of Structured Information Systems (OASIS) is poised to announce the formation of a technical committee to promote a standard for interoperable business processes and business process execution for Web services orchestration. The new technical committee, to be announced as early as Tuesday, is known as the OASIS Web Services Business Process Execution Language (WSBPEL) technical committee. The group, led by IBM, Microsoft Corp., BEA Systems Inc., Siebel Systems Inc. and SAP AG, will work to advance the Business Process Execution Language for Web Services (BPEL4WS) specification. BPEL4WS is an XML-based specification that deals with Web services choreography. IBM, Microsoft, BEA, Siebel and SAP will officially submit BPEL4WS version 1.1 to OASIS under royalty-free terms on May 16 when the technical committee meets to consider submissions of related technology or standards efforts.
Meanwhile, other companies involved with BPEL4WS and who are members of the WSBPEL technical committee include CommerceOne, E2Open, EDS, Intalio, NEC, Novell, SeeBeyond Technology, Sybase, Tibco Software, Vignette and Waveset, among others.
Intalio Inc., San Mateo, Calif., a provider of business process management systems, said it provides full support for BPEL 1.0 and the Business Process Modeling Language specification. Company officials said native support for BPEL 1.1 will be included in the next release of Intalios core product. BPEL4WS actually competes with another prominent standards effort. And some see the submission of BPEL4WS to OASIS as a controversial move, in that it goes counter to the existing efforts to standardize this space. Sun Microsystems Inc. and Oracle Corp. are supporters of the Web Service Choreography Interface (WSCI) specification, as is BEA, which also supports BPEL4WS. And the World Wide Web Consortium (W3C) has a working group at work on a Web services choreography/orchestration specification, which does much the same as BPEL4WS. Microsoft attended the first face-to-face meeting of the W3C choreography working group, which was held at Oracle headquarters, but the company did not pursue it any further.


 
 
 
 
Darryl K. Taft covers the development tools and developer-related issues beat from his office in Baltimore. He has more than 10 years of experience in the business and is always looking for the next scoop. Taft is a member of the Association for Computing Machinery (ACM) and was named 'one of the most active middleware reporters in the world' by The Middleware Co. He also has his own card in the 'Who's Who in Enterprise Java' deck.
 
 
 
 
 
 
 

Submit a Comment

Loading Comments...
 
Manage your Newsletters: Login   Register My Newsletters























 
 
 
 
 
 
 
 
 
 
 
Thanks for your registration, follow us on our social networks to keep up-to-date
Rocket Fuel