http://blogs.msdn.com/mikechampion/archive/2008/04/01/web-services-standards-and-net-interoperability.aspxSuccessive versions of the .NET framework closely track the evolution of the WS-* specs as they progress from publication, to submissions to W3C or OASIS, and ultimately as W3C Recommendations or OASIS Standards. See for example the list of supporteden-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/mikechampion/archive/2008/04/01/web-services-standards-and-net-interoperability.aspx#8349560Wed, 02 Apr 2008 05:10:26 GMT91d46819-8472-40ad-a661-2c78acb4018c:8349560Web Services Standards and .NET Interoperability | Specs<p>PingBack from <a rel="nofollow" target="_new" href="http://www.sppec.com/web-services-standards-and-net-interoperability/">http://www.sppec.com/web-services-standards-and-net-interoperability/</a></p> http://blogs.msdn.com/mikechampion/archive/2008/04/01/web-services-standards-and-net-interoperability.aspx#8350128Wed, 02 Apr 2008 10:10:20 GMT91d46819-8472-40ad-a661-2c78acb4018c:8350128concerned<p>And again in Mike Champion-ese rather than Mike-rosoft-ese?</p>http://blogs.msdn.com/mikechampion/archive/2008/04/01/web-services-standards-and-net-interoperability.aspx#8411155Sun, 20 Apr 2008 09:41:25 GMT91d46819-8472-40ad-a661-2c78acb4018c:8411155mikechampion<p>Sorry, that comment was marked as spam by the blog software and I didn't notice it. &nbsp;It's a fair point, but I'd reply that there is a fine line between being a shill and being a pushover in the blog world. I didn't want to get into the blog war centered around the ISO OOXML debate, but there was some stuff being thrown around in there that splattered into my domain. I felt it was time for a statement of our story on WS-* standards compliance and interoperability.</p>