<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>XML Standardization Organizations and Processes</title><link>http://blogs.msdn.com/xmlteam/archive/2006/08/16/703459.aspx</link><description>There's been a lot of unhappiness about the W3C floating around recently, well-summarized by Dare Obasanjo . Most of us involved with XML at Microsoft share a good bit of the general frustration, if not the specific complaints, expressed in these posts.</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: XML Standardization Organizations and Processes</title><link>http://blogs.msdn.com/xmlteam/archive/2006/08/16/703459.aspx#704986</link><pubDate>Fri, 18 Aug 2006 03:10:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:704986</guid><dc:creator>Len Bullard</dc:creator><description>We've covered this ground. &amp;nbsp;Specifications are for technologies to be fielded and they follow an eccentric orbit until they approach commodity status, a lagrange point among the various forces that determine the evolution of the technology. &amp;nbsp; At that point, switching costs plunge and the small differences among product design, implementation, marketing and support determine the lifecycle of a given instance. &amp;nbsp;At that point, anyone still in the market is protecting the resources for the resources: think talent, production advantages, inter-customer relationships for deals of significant size, inter-vendor deals to share market opportunities and so on.&lt;br&gt;&lt;br&gt;It is true that the experience of the team producing the specification determines the probable success of a specification. &amp;nbsp; A standard can be and should be created as a result of a transparent and predictable process. &amp;nbsp; While the W3C could avail itself of the work of the previous generation, the success rate for its specifications was high. &amp;nbsp;Now, they have to work for it and they face the same issues as the product vendor and the standards organizations that preceded them: &amp;nbsp;dearth of talent, the problem of focusing resources, and the need to work within the legacy of previous work.&lt;br&gt;&lt;br&gt;Not news. &amp;nbsp;It will be interesting to see if the emerging second generation web systems producers will learn as much or more or less from the first generation as that generation did or did not from their 40-somethings. &amp;nbsp;&lt;br&gt;&lt;br&gt;All companies and organizations have to cope with the transition from the founders through their gophers to the leadership of a true next generation. &amp;nbsp; In such transitions, fortunes and careers are made and lost. &amp;nbsp; And so it goes.</description></item><item><title>Labnotes  &amp;raquo; The Web is broken &amp;#8230; follow up</title><link>http://blogs.msdn.com/xmlteam/archive/2006/08/16/703459.aspx#706134</link><pubDate>Fri, 18 Aug 2006 19:00:16 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:706134</guid><dc:creator>Labnotes  » The Web is broken … follow up</dc:creator><description>PingBack from &lt;a rel="nofollow" target="_new" href="http://blog.labnotes.org/2006/08/16/the-web-is-broken-follow-up/"&gt;http://blog.labnotes.org/2006/08/16/the-web-is-broken-follow-up/&lt;/a&gt;</description></item><item><title>Microsoft XML Team's WebLog : XML Standardization Organizations and Processes</title><link>http://blogs.msdn.com/xmlteam/archive/2006/08/16/703459.aspx#8576946</link><pubDate>Fri, 06 Jun 2008 07:53:49 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8576946</guid><dc:creator>Weddings</dc:creator><description>&lt;p&gt;There's been a lot of unhappiness about the W3C floating around recently, well-summarized by Dare Obasanjo . Most of us involved with XML at Microsoft share a good bit of the general frustration, if not the specific complaints, expressed in these posts&lt;/p&gt;
</description></item><item><title> Microsoft XML Team s WebLog XML Standardization Organizations and | Cellulite Creams</title><link>http://blogs.msdn.com/xmlteam/archive/2006/08/16/703459.aspx#9711887</link><pubDate>Tue, 09 Jun 2009 05:47:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9711887</guid><dc:creator> Microsoft XML Team s WebLog XML Standardization Organizations and | Cellulite Creams</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://cellulitecreamsite.info/story.php?id=10006"&gt;http://cellulitecreamsite.info/story.php?id=10006&lt;/a&gt;&lt;/p&gt;
</description></item><item><title> Microsoft XML Team s WebLog XML Standardization Organizations and | debt solutions</title><link>http://blogs.msdn.com/xmlteam/archive/2006/08/16/703459.aspx#9756486</link><pubDate>Tue, 16 Jun 2009 03:02:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9756486</guid><dc:creator> Microsoft XML Team s WebLog XML Standardization Organizations and | debt solutions</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://debtsolutionsnow.info/story.php?id=13476"&gt;http://debtsolutionsnow.info/story.php?id=13476&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>