I agree that BPEL is <<currently>> not workflow. And that's why I
called it the worst standard.

But some people behind BPEL at Microsoft, IBM, BEA and oracle believe
that their invention will become the future standard  for workflow.

Currently most of people refer to BPEL as web service orchestration
standard or web service composition language.
IBM extension to BPEL implemented in Webshpere App Server supports
human interactions, some (including IBM it self) are trying to address
this via more standard ways like BPEL-J or JSR 207.

Any way currently BPEL has much stronger support  than WFMC standards,
specially from the time SAP (First implementer of WFMC standards) has
shifted from XPDL to BPEL in its netweaver platform.

BPEL is considered as way to define business  process and it will
become a workflow  standard in future.
BPEL currently has 3 major problems:
1- human interaction
2- sub process
3- the underlying theory (Pi calculus)

Some people believe Pi calculus is a much found  theory to define
business process. So they don't bother them self with it much but for
the other two there are some work underway:

BPEL4People
Human user interactions – as known from existing workflow engines
www128.ibm.com/.../ws-bpel4p\
eople/

BPEL Subprocesses
Based on a coordination protocol
www-128.ibm.com/.../ws-bpels\
ubproc/

And at last
If any one has read this message to the last we are developing a
workflow engine  in our company and searching for talented software
developers if you are interested in working with us on this subject(of
course with all benefits of a good job) send me your resumes.