<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Tagging Redux &#8211; Curse of the Bifurcated Standards Bodies</title>
	<atom:link href="http://www.douglasgourlay.com/blog/2009/07/tagging-redux-curse-of-the-bifurcated-standards-bodies/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.douglasgourlay.com/blog/2009/07/tagging-redux-curse-of-the-bifurcated-standards-bodies/</link>
	<description>Data Centers, Virtualization, and Cloud Computing</description>
	<lastBuildDate>Sun, 02 May 2010 01:04:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: LeitM</title>
		<link>http://www.douglasgourlay.com/blog/2009/07/tagging-redux-curse-of-the-bifurcated-standards-bodies/comment-page-1/#comment-122</link>
		<dc:creator>LeitM</dc:creator>
		<pubDate>Mon, 10 Aug 2009 20:40:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.douglasgourlay.com/blog/?p=99#comment-122</guid>
		<description>Your summary in the comment about the vicious-cycle/race condition  is very clear and accurate.  Especially your point about the bodies being onerous and bureaucratic - case in point is the 48 byte cell size of ATM, which, reportedly, was chosen as a compromise between 32 and 64 bytes :-) 

Innovative vendors should be rewarded by customer adoption - interestingly, customers are more discerning than we often assume and can also reject solutions they don&#039;t need, independent of how innovative these are.  

As one of your other posts indicated, it would be great if innovation could also result in a simple solution, but that&#039;s not easy... :-)</description>
		<content:encoded><![CDATA[<p>Your summary in the comment about the vicious-cycle/race condition  is very clear and accurate.  Especially your point about the bodies being onerous and bureaucratic &#8211; case in point is the 48 byte cell size of ATM, which, reportedly, was chosen as a compromise between 32 and 64 bytes <img src='http://www.douglasgourlay.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  </p>
<p>Innovative vendors should be rewarded by customer adoption &#8211; interestingly, customers are more discerning than we often assume and can also reject solutions they don&#8217;t need, independent of how innovative these are.  </p>
<p>As one of your other posts indicated, it would be great if innovation could also result in a simple solution, but that&#8217;s not easy&#8230; <img src='http://www.douglasgourlay.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Douglas Gourlay</title>
		<link>http://www.douglasgourlay.com/blog/2009/07/tagging-redux-curse-of-the-bifurcated-standards-bodies/comment-page-1/#comment-64</link>
		<dc:creator>Douglas Gourlay</dc:creator>
		<pubDate>Wed, 29 Jul 2009 02:48:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.douglasgourlay.com/blog/?p=99#comment-64</guid>
		<description>Had a good debate/dialog with @daveobarry via Twitter this eve.  Short version is I think we have a vicious-cycle/race condition here...

1) Innovative infrastructure vendors like to build new things in a way that creates competitive advantage, usually in the form of some lock-out

2) Followers always play the &#039;standards card&#039; to level the playing field, yet in the process always try to change the specification just enough to nullify the advantage gained by the innovator

3) The standards bodies are rather onerous and bureaucratic so most end-customers aside from large SPs don&#039;t take the time to invest in attending/shaping the standardization

Dave asserts that this is broken - I concur.  

However, I am not certain how this could be fixed.  The innovator is taking the risk, there needs to be some reward for this risk.  Innovation in infrastructure in a way that co-creates a standard inline with the shipment of the technology nullifies many of the reasons investors would want to bet on the innovator, thus reducing investment in innovation!</description>
		<content:encoded><![CDATA[<p>Had a good debate/dialog with @daveobarry via Twitter this eve.  Short version is I think we have a vicious-cycle/race condition here&#8230;</p>
<p>1) Innovative infrastructure vendors like to build new things in a way that creates competitive advantage, usually in the form of some lock-out</p>
<p>2) Followers always play the &#8216;standards card&#8217; to level the playing field, yet in the process always try to change the specification just enough to nullify the advantage gained by the innovator</p>
<p>3) The standards bodies are rather onerous and bureaucratic so most end-customers aside from large SPs don&#8217;t take the time to invest in attending/shaping the standardization</p>
<p>Dave asserts that this is broken &#8211; I concur.  </p>
<p>However, I am not certain how this could be fixed.  The innovator is taking the risk, there needs to be some reward for this risk.  Innovation in infrastructure in a way that co-creates a standard inline with the shipment of the technology nullifies many of the reasons investors would want to bet on the innovator, thus reducing investment in innovation!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
