Skip to main content

BPEL and BPM Explained

"If you talk to many BPM practitioners, you will find that most assume that BPEL is, or will soon function as, the language of choice for BPM work. BPEL4WS was originally announced in August of 2003 by BEA, IBM, and Microsoft. Their announcement came just as the BPMI.org was about to release the first version of their own alternative BPM language specification, BPML, and the announcement effectively sidelined BPML. Soon after the initial announcement, the originators were joined by many others, including many of the folks that had been working on BPML, and the draft specification of BPEL4WS (now almost universally
know as BPEL) was submitted to OASIS for completion."

Popular posts from this blog

Connected Vehicles to Reach 1.05B by 2035

Every executive who has approved a connected product roadmap has made a quiet assumption: the network underneath it will still be there. That assumption is about to be tested at a scale the automotive industry has never faced. The global connected vehicle installed base is heading toward a billion units, and the cellular technology most of those vehicles depend on is scheduled to begin its retirement before the end of the decade. For automakers, fleet operators, insurers, and the telecom carriers that serve them, the question is whether the recurring revenue those services promise can survive a connectivity layer with a shorter life than the vehicle carrying it. How Scale Meets an Expiry Date Omdia research forecasts that the global connected vehicle installed base will surpass 1.05 billion units by 2035, up from 473.7 million in 2025. Few installed bases of any kind more than double in a decade, and this one signals that connectivity is moving from premium differentiator to baseline e...
Read more