I agree with you that the lack of support for human workflow in BPEL has been slowing adoption down, but I’m not sure that I agree with the fact that it should be baked into the BPEL specification. Instead, I believe that having a set of standardized workflow services built on top of BPEL would give people what they need, without having to make any change to the BPEL specification itself, much like access control for a relational database can be built with custom user tables and standard SQL statements, without having to make any changes to the SQL specification itself.

I agree with you that BPEL does what it is intended to do. But don’t you think that instead of having multiple workflows for different services, we should have all those features in BPEL? Then it becomes easier for orchetrating business processes. I think that’s what stops its faster adoption…