Mar 03 2007
Jonathan announces on his blog that WSDL 2.0 is moving forward to Proposed Recommendation (once the W3C Director approves it). Congratulations to Jonathan, who has been doing a great job maintaining the group on track to get there, and everybody who participated in this.
Looking back at the entire adventure, I think that a pivotal moment was about one year ago, in Mandelieu, when things were looking pretty grim and we managed to stir implementation interest around good French food.
WSDL 1.1 has been an endless source of interoperability issues. The WS-I Basic Profile has helped things a lot, however, it’s only constraints on top of a very loose language that are not enforced at the syntax level. Developers can still do whatever they want, and fall into a number of hidden traps. Along with the many changes and improvements over WSDL 1.1, WSDL 2.0 does one very important thing: it enacts, right in its language, constraints similar to the ones defined by the WS-I Basic Profile. That means that WSDL 2.0 can be used to describe current interoperable service descriptions, and pretty much only those, as will show the WSDL 1.1 to 2.0 converter.
The nearing completion of WSDL 2.0 is therefore good news for SOAP Web services: it should improve interoperability. Of course, in order for this to happen, WSDL 2.0 will need to be broadly adopted, and that will take a while. However, WSDL 2.0 is a move in the right direction.
And now on to the next interoperability issue, which is not limited to SOAP services, but also affects HTTP ones: XML Databinding.