Phew.
This doesn't do much increase my liking of the webservices bandwagon....

• Interoperability appears to be poor to sorry, not to mention wrapped in thick layers of hard to understand issues of RPC vs. literal encoding.

• Calling a method requires all the parameters to be named (that's OK) and in a given order (way less than OK in my book)

• The field is already strewn with horribly complex message formats (e.g. ADO.Net datasets) that force you to either reinvent client side behavior OR to use a Microsoft client. (How is this supposed to be good? Document/literal advocates in the "webservices are about document based messaging, not RPC" field say it is, but this forced separation of data and behaviour looks a gigantic leap backwards to me)

Ok, I got it off my chest. Now let the flamethrowers be unsheathed.