Web Services Strategies
Beyond the technology, IT strategies for implementation of Web services by Doug Kaye.
|
W3C Versus OASIS? In this short Computerworld interview, Tim Berners-Lee succinctly and accurately describes the differences between the two standards bodies. OASIS is young, and the standards it's created haven't survived the test of time. While not perfect (and certainly not fast) W3C has produced standards that are relatively stable. (I think IETF has been even more successful, but they're not too involved with this web-services stuff.) Without OASIS pushing things through quickly, it would take at least a few extra years to achieve interoperability in the WS-xxx areas such as security and orchestration. Wouldn't it be great if OASIS took technologies to the point of interoperability and then submitted them (without patent restrictions) to W3C? Hey...it could work!
Posted Thursday, May 22, 2003 11:41:34 PM 
|
|
|
Who Needs SOAP and BPEL? Phil Wainewright noted that "last week that analysts at Gartner have backtracked on their previous definition of a web service, and now concede that it can be software automation that uses at least one of the three so-called foundation standards -- SOAP, WSDL or UDDI -- rather than having to use all three....Whether you use any of the higher-level web services standards, including SOAP and WSDL, is irrelevant. All you need is HTTP and XML, along with HTML and JavaScript for the user interface."
Phil is right, of course. From Amazon.com to Salesforce.com, we're seeing early but important examples of "real" web services that require not much more than XML over HTTP. I don't agree with Phil, however, when he writes, "they're starting to realize the power of connecting best-of-breed resources in a loosely coupled architecture." I don't see these early implementations as being loosely coupled. But his overall point is well taken, and one that the REST folks have been trying to make for some time now.
Posted Thursday, May 22, 2003 7:54:15 AM
|
|
|
|
|
|
