Why is Microsoft unique?

I was just reading a ZapThink report on Microsoft's new XAML-extensions for WWF (Windows WorkFlow) and got stuck again on one of Ronald Schmelzer's comments. Ron is quoted in several publications as saying:

"Microsofts use of XAML as a way to specify business processes is unique, Schmelzer said."

Now I don't know what you've been doing lately, Ron, but I just finished writing an entire book on XAML and let me tell you something, there's very little "unique" about XAML. Oh, don't get me wrong - it's cool, it's sexy, it's neato-nifty-keen and there's some new features available that will knock your socks off, but it isn't unique and neither is extending it to incorporate business process specific calls to WWF.

Ever heard of BPEL, Ron? You know, an XML-based specification that describes...

wait for it...

wait for it...

You got it - business processes. Specifically, the activities and steps that make up a business process. Sound familiar?

WWF XAML: BPEL :

Oooohhh.. now that's unique, isn't it?

Yes, there's some differences, but the core terminology - notice the term "sequence", Ron? - and concept is the same. They are both XML-based formats for referencing activities and interacting with a business process. Both are interpreted by a runtime engine. (BPEL -> BPEL Engine. WWF XAML -> WPF + WWF)

The only reason you might (and that's a big might) consider Microsoft unique in this area is because it is embedding activities and steps right in the user interface. That's right, XAML was primarily built for declaring user interfaces, and is being extended to support other Windows specific technologies as we speak. It certainly isn't unique because activity artifacts can be changed on the fly and reinterpreted because BPEL is treated the same way.

Why is using XAML unique? XAML is extensible, all XML is. That's not unique. I point you at WS-Policy as an example, which is being extended to support domain specific policy declarations such as security (WS-SecurityPolicy).

Using XAML - or any other XML - to specify business processes is hardly unique. Unless you're going to fall on your sword and claim that it's unique because it's a) embedded inside a user-interface (which breaks Microsoft's own best practices statement of separating user interface from application logic) or b) because it's a lot neater and cleaner than BPEL, I call horsepuckey. Well, which is it? I'd really like to know because this quote on the subject is really quite...vague...and quite frankly, I don't see how you can seriously say it's unique.