For example, the BPEL process does not directly support abstractions for people, roles, work items or inboxes/queues, hence BPEL is not equivalent to workflow. Such capabilities can be added outside the scope of BPEL in a service-oriented fashion, e.g. by adding a specialized "task service" that manages people, roles, etc. BPEL is also not equivalent to BPM, since the language does not specify a data model for process reporting, analysis or monitoring/administration.
Finally, BPEL is not equivalent to integration, as the specification is protocol independent and does not include common integration facilities such as adapters, transformation, etc. As with workflow, such facilities can be easily provided in a service-oriented manner into a BPEL solution framework.
This was first published in December 2003