InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

BPEL4People and WS-HumanTask Head To OASIS

Posted by Mark Little on Jan 11, 2008

Sections
Enterprise Architecture
Topics
Business Process Management ,
SOA ,
Web Services ,
WS Standards
Tags
Web services ,
BPEL ,
Standardization
When BPEL4WS first came on the scene there was a lot of hype around it, but many people said that it would only gain mass adoption once it went to a standards body. It did eventually and became WS-BPEL, which has gone through a few revisions as a standard. The WS-BPEL TC officially closed in May 2007 and the jury is still out as to whether or not WS-BPEL has achieved what the initial hype would have suggested. However, it cannot be doubted that WS-BPEL has become one of the major WS-* standards and a tick-box on all serious Web Service vendor's implementations.

However, one of the areas WS-BPEL didn't target was human task interaction/BPM. As the WS-BPEL FAQ points out:

  1. What is the relationship between BPMN and WS-BPEL2.0?
    1. WS-BPEL is an OASIS standard for a service orchestration language.  BPMN is an OMG standard for visual representation of a business process. While a BPEL process can be represented using BPMN, some BPMN models cannot be represented using BPEL.  At the time this FAQ was prepared there were no mappings from BPMN to WS-BPEL 2.0.

 

  1. How does WS-BPEL handle human tasks?
    1. BPEL was not designed for human workflow.
There have been other attempts to provide this mapping/integration, but none of them have really had a chance to become a standard. However, this was an important omission. Therefore it didn't come as a surprise when WS-HumanTask and BPEL4People were announced by the same WS-BPEL authors. As with WS-BPEL, it's taken the authors a while to get their act together with respect to a standards body, but as John Evdemon (co-chair of the WS-BPEL technical committee) has just announced:
The BPEL4People and WS-HumanTask specs are headed to OASIS, resulting in a new BPEL4People Technical Committee (TC) - expect to see an announcement and call for participation soon.  The TC will focus on defining human interactions (“human tasks”) as part of a WS-BPEL process, enabling these definitions to be exposed as web services.
Whether the output of these technical committees will have the impact of WS-BPEL remains to be seen, but BPM is important within SOA. A standard for this in Web Services can only be a good thing.
  • This article is part of a featured topic series on SOA

No comments

Watch Thread Reply

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.