Well done to Mark and the rest of the group for a job well done! It took much much longer than expected but such is life in standards committees. The two W3C candidate recommendations:
We have until November 1 this year to submit comments. So, start reading everyone!
Update: Corrected the title. The WS-Addressing specs have become candidate recommendations.
Update: Link to core spec fixed. Thanks Tom!
2 responses to “WS-Addressing becomes a W3C Candidate Recommendation”
Sava man, the first link doesn’t work.
By the way, can you please give us an insight into the WS protocol that offers support for message queuing among disparate platforms and whether WSE 3.0 or WCF will offer any support for it?
I’ve read somewhere that the message queuing support provided by WSE 3.0 & WCF is built on top of MSMQ which would be a real shame if it’s true since it would mean that the premier Windows SOA infrastructure still suffers from a temporal dependency when it comes to integrating with different technologies.
Service Orientation is a falacy if the execution timeframe of the sender is coupled to that of the receiver and although that’s not the case if you’re using MSMQ compatible systems, it is done to the expense of interoperability which is the whole idea behind Web Services.
It looks like it will be a while before both the temporal and technology dependencies are dealt with when integrating applications between different vendors.
I’m interested in hearing your comments on this.
Kales Epitixies sto ktirio 42.
Hey Tom,
MSMQ is used as a transport. This has nothing to do with interoperability. At the moment SOAP over HTTP is the only safe, interoperable mechanism for message transfers. In the future we’ll have SOAP over TCP/UDP/SMTP standard bindings even though we are seeing interoperable solutions already (e.g. WSE 2.0-Axis for SOAP/TCP).
I hope this helps. Please, don’t hesitate to contact me directly if you want.