When
· Naughties
· · 2005
· · · November
· · · · 06 (1 entry)

WS-Interop · We did a Web Ser­vices an­nounce­ment Fri­day, and while I’m not on that team, I think it’s sig­nif­i­can­t. Ba­si­cal­ly, it says that we’re im­ple­ment­ing enough of WS-* to in­ter­op­er­ate with Mi­crosoft Indi­go Win­dows Com­mu­ni­ca­tions Foun­da­tion, and that the im­ple­men­ta­tions will be Open Source. Let’s be blunt (and re­mem­ber, I speak on­ly for my­self here): WS-* isn’t about stan­dard­s. It’s about what Mi­crosoft (there are part­ner­s, but it’s most­ly Mi­crosoft) choos­es to im­ple­ment while wav­ing the WS-banner and retroac­tive­ly shak­ing Stan­dards Fairy Dust over the pro­cess. Which is OK, as far as it goes; I get the im­pres­sion that Indi­go WCF is ac­tu­al­ly some pret­ty neat soft­ware that will be use­ful to a lot of Mi­crosoft cus­tomer­s, and Sun has a stake in the ground say­ing we’re go­ing to in­ter­op­er­ate with the Mi­crosoft WS-stack. Do I think this stuff is go­ing to Change The World? No. Do I think that this is the re­al fu­ture of Web Ser­vices? No. (I think the fu­ture looks like Ama­zon Web Ser­vices or the Atom Pub­lish­ing Pro­to­col or even re­cent ar­rivals like the Back­pack API, even though Back­pack could be done with the Atom Pro­to­col). But I do think that WS-Microsoft-Interop is the right thing to do at the mo­men­t. Oh, and by the way; if you’re one of the many many peo­ple grind­ing away at one of the WS-inventions that hasn’t shown up al­ready in this in­terop sto­ry, well, there may be grounds for wor­ry.
 
author · Dad · software · colophon · rights
Random image, linked to its containing fragment

By .

I am an employee
of Amazon.com, but
the opinions expressed here
are my own, and no other party
necessarily agrees with them.

A full disclosure of my
professional interests is
on the author page.