Sunday, 23 January 2005
WS-Who's on First?
Meanwhile, SOAP has bindings and WSDL has bindings, and WS-Addressing has not one but two bindings too. But, a SOAP binding binds an underlying transport, a WSDL binding binds an abstract interface, and an Addressing binding binds abstract properties.
That’s different from Infoset properties, by the way, and not the properties in SOAP, which aren’t exactly the same as the properties in WSDL. Likewise, there are SOAP features and WSDL features, both doing similar-but-not-identical things.
Is it bad abstraction, or just a lack of imagination? Whatever the cause, please: stop… stop… hurting Web services. And my head.