Ron Schmelzer of ZapThink, a SOA consultancy, was glad the specification didn’t kowtow to Web services too much, according to the article.

He clarified in the e-mail to me that people should understand this as a way to talk about SOA, not a computer language for developing SOA:

“Rather than it being a language for system-to-system communication, it’s a language to help with modeling… that is, machine-facilitated human-to-human communication. They want to standardize the way people refer to various aspects of SOA, and as such it’s more of a language for people to use in communicating SOA concepts.”

Read more at: IT Business Edge