BPEL4People

 

Notes (Note)

 

Public Description - BPEL4People

BPEL 4 People

This is an initiative to build a human oriented process language on top of BPEL.

To understand the chance for success, perhaps it is best to understand the difference between human-oriented processes and system-oriented processes.

Potential Issues

  • People Resolution - clearly missing from BPEL, would not be hard to address
  • Change and Migration - very difficult for BPEL
  • Reassign - also difficult
  • Forward Compatibility - It defines a new type of basic activity which uses human tasks as an implementation. What about existing systems which have made a sub-class of the regular activity for this purpose?
  • sub-process - missing from BPEL, does this add it?
  • collaborative - BPEL was designed to move data from point A to point B, but a group of people working on the same process need to share data, and means a lot more than being sent data and later returning it. Can two people who work in parallel see the partial results of the other person? This is more important when there are parallel thread of multiple activities.

History

  • Originally supplied as a white paper August 2005
  • Specification published June 2007
  • Additional WS-HumanTask published on June 2007

Resources