Here's a little frustration of mine: the term webservices. The term implies a protocol. Services and protocols aren't the same. Actually services are protocol agnostic.
I seem to be explaining this a lot. Recently I discussed a change on an application to let it integrate with another application. Originally the application only provided file imports. The latter wanted to use MQ. The discussion went on and on when I said that only one service would be provided for both applications. People that worked on the original application told me that it was impossible to remove the file import.
Okay... MQ, Http and the file system are all protocols. They don't say anything about the service interface of an application. The service interface describes the fields, data types, required fields and format. The protocol is how the data is transmitted between applications. An application can publish it's service interface through various protocols (for example Http, MQ and the file system).
So, protocols and services aren't the same. I think it's important to keep the definitions clear, that will aid any discussion on the subject.