Implemention strategies for Web services are splitting into two camps:
building enterprise SOAs and exploiting Web technologies. One group advocates using Web services to build complex internal systems known as enterprise service-oriented architectures (SOAs). The other seeks to use emerging Web technologies in tandem with Web services to create flexible external applications. Their divergent approaches each require different organizational skill sets. Unlike the enterprise-SOA camp, Web-technologies evangelists say Web services are a mechanism for programmability. But this camp is also expanding its definition of a Web service. Initially, many people thought any service delivered over the Web was, logically enough, a Web service. At the time, however, that idea was considered an anathema to those of us who saw Web services as specific to the use of things like SOAP and Web Services Definition Language (WSDL). Web-technologies groups are now forcing the acknowledgment that Web services will indeed use mechanisms other than SOAP, WSDL, or even Universal Description, Discovery, and Integration (UDDI). Instead, standards such as Plain Old XML (POX) over HTTP and Representational State Transfer (REST) are asserting themselves as legitimate and very credible ways of delivering on the value proposition of Web services. As Web services assume more expansive definitions, we can represent them using a wide variety of formats and communications protocols.
Yup, totally agree with that. Interesting times ahead.