Why is Microsoft unique?: Page 3 of 3

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.