I take issue with lumping UML and BPM together. Yes I know IBM/OMG has worked hard to make BPML an application of UML to leverage/repurpose their investment, ju

I take issue with lumping UML and BPM together. Yes I know IBM/OMG has worked hard to make BPML an application of UML to leverage/repurpose their investment, just like UML itself was portrayed as "unifying" earlier OO and ER modelling techniques. But I don't believe it was for the better of BPM adoption. I know for sure that around 2000-2005 there was BPEL. It sure had its own problems (one being that it was criticized as not being "real" BPM, another being that devs didn't like XML and misunderstood BPEL as a programming language competing with eg Java, a further one being that it went down when the WS-* SOA death star became out of fashion). But it still was remotely successful in describing interactions between "web services" as it was called then, and would still be very useful to describe and execute interactions/integrations in today's SaaS landscape. And yes, WSDL (2001 or earlier) could describe today's idiotic "REST" interfaces squeezing every invocation parameter into URL query params for some reason (and JSON for responses) even if the consumer is neither a browser, nor does HATEOS; we've just stagnated since.