InfoQ

News

WS-Addressing Working Group Closes

Posted by Mark Little on Sep 06, 2007

Community
SOA
Topics
Web Services
Tags
WS-Addressing ,
Standardization
The W3C have just announced that the WS-Addressing Working Group has closed. As the announcement states:
This message is to inform you that the Web Services Addressing Working Group
is now closed. Many thanks to Robert Freund (Hitachi, Ltd., Chair), Mark
Nottingham (previously BEA Systems) and the Working Group participants for all
of their contributions in this area.

There is no plan to produce a new version for Web Services Addressing at this
time. The current plan is for a Web Services Core Working Group to maintain these specifications. We are also
working separately on evaluating additional work to specify a mechanism for
associating WS-Policy with an Endpoint Reference.
WS-Addressing first came to visibility in 2004, with many of the current plethora of WS-* specifications using it back then, such as WS-Transactions and WS-Security. There have been a few criticisms leveled at WS-Addressing over the years, such as the way in which it is possible to define sessions with it (related to that would be the overlap with WS-Context), or that it's not tied closely enough to the SOAP specification. Like most of the WS-* specifications, there was a competitor on the horizon, even if only briefly: WS-Message Delivery from Oracle et al. Whether or not the intention of that specification was simply to force the WS-Addressing author companies at the time to go to a standards body, several months later it duly arrived at W3C.

There have been a few changes since it went to W3C, such as the removal of ReferenceProperties and a reference to WS-Context. However, even the W3C Technical Architecture Group asked for clarification on the Web-ness of EndPoint References. But in general most people agreed that WS-Addressing was an important missing piece from the WS-* architecture if we were to achieve interoperability. Those that disagreed still probably classed it as Mostly Harmless.

No comments

Watch Thread Reply

Educational Content

Brian Marick on 4 Challenges and 5 Guiding Values of Agile Software Development

Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).

Are You a Software Architect?

The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?

Agile – A Way of Life and Pragmatic Use of Authority

The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.

Getting Started with Grails, Second Edition

"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?

Using ITIL V3 as a Foundation for SOA Governance

Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.

Adrian Colyer on AspectJ, tc Server and dm Server

SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.

Adam Wiggins on Heroku

Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.

SOA as an Architectural Pattern: Best Practices in Software Architecture

For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.