One of the nice things about being a critic of the current approach to Web services, is that the infighting amoungst the players had a chilling effect on standardization efforts, which made my job – of keeping the W3C as free from this stuff as possible – easier. Unfortunately, today, everybody seems to have come together for the worst spec of them all; WS-Addressing is now a W3C submission.

SOAP, I liked very much, just not how people were/are using it.

WSDL, I didn’t like because of the bad practice it encouraged, but I felt that it might have a role to play.

But this monstrosity actively causes harm by not using URIs as EPRs. That part of the spec has no redeeming qualities, except that it represents an attempt on behalf of the authors to Do The Right Thing regarding addressing (i.e. standardize it). Unfortunately, those authors fail to recognize that we’ve already got a perfectly good identification spec.

Update; P.S. yes, I understand than an EPR has a mandatory wsa:Address, but that doesn’t change anything, as any identifying information in the SOAP envelope is necessarily in conflict with the HTTP Request-URI. One endpoint per message, please.

A vision of things to come; personal servers, event servers, REST, RDF, …
(link) [Mark Baker’s Bookmarks]

Sean highlights Reinout van Rees’s Zen moment

Awesome, another recruit!

I just want to add that I think it’s important to recognize that “getting it” requires a Zen moment. For everybody I know who came from a CORBA/DCOM-like distributed systems background, but now understands the Web, serious mental model rewiring occurred. If you haven’t had that rewiring, you don’t (yet) get the Web.