Different Strokes for Different Folks
As stated previously, Web services often represent a different challenge to understand something new. They are different for the document markup community because the purpose of Web services is to connect programs to each other automatically, without human intervention. That is, Web services represent a browserless Web. Will markup language capabilities be able to support this?
On the other hand, distributed computing people have to learn to deal with HTTP, which is itself an application-level protocol, and not a transfer protocol of the type they're used to.
The Web services community therefore seems headed for divergence: Some prefer to stick to XML's origins as a markup language, whereas others are much more interested in the capability of XML to structure and type dataunless these differences are bridged or reconciled.