Inevitable confusion

Today's confusion over Web services standards was inevitable, argues Tarak Modi. Two reasons: 1) rapid advancement within the industry that eclipsed existing standards and 2) political jostling among vendors to gain a competitive edge. But that's OK. Modi suggests that sensible people can still bring sense to the challenge of capitalizing on Web services:

"As a software architect, designer, or developer working (or planning to work) with Web services there are two steps to ensure success in your endeavors," he writes. "First, you should become intimately familiar with the core Web Services related specifications published by the W3C. These include XML Schemas, SOAP, WSDL, XML Digital Signature, and XML Encryption.Another crucial specification to peruse is the WS-I's Basic Profile, which is published by WS-I for ensuring Web Service interoperability. Second, remember that the success of your Web services project is not dependent on the number of different specifications that you can claim to have used in it. Always keep your Web services as simple as you can. Start off with the basics and select each specification as required after careful evaluation of your requirements."