<?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: Four Pillars: Thinking about standards in an enterprise architecture context</title>
	<atom:link href="http://confusedofcalcutta.com/2006/06/19/four-pillars-thinking-about-standards-in-an-enterprise-architecture-context/feed/" rel="self" type="application/rss+xml" />
	<link>http://confusedofcalcutta.com/2006/06/19/four-pillars-thinking-about-standards-in-an-enterprise-architecture-context/</link>
	<description>a blog about information</description>
	<lastBuildDate>Mon, 06 Feb 2012 01:37:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: JP</title>
		<link>http://confusedofcalcutta.com/2006/06/19/four-pillars-thinking-about-standards-in-an-enterprise-architecture-context/comment-page-1/#comment-1340</link>
		<dc:creator>JP</dc:creator>
		<pubDate>Wed, 21 Jun 2006 13:45:18 +0000</pubDate>
		<guid isPermaLink="false">http://confusedofcalcutta.com/2006/06/19/four-pillars-thinking-about-standards-in-an-enterprise-architecture-context/#comment-1340</guid>
		<description>We&#039;re on the same page. The perfect world is where we plug things in without incremental effort; since we are not there as yet, I am suggesting that emergence plays will allow the market to set the standard, and that resource is applied to the things that matter. You know my views on diverting resources to make things work with IE already. For sure I am not saying that the resources we save on Firefox should be used for IE. What I am saying is that Firefox adoption should not attract incremental resource until it needs to, and that we could use those resources to build business value elsewhere. Not in IE.</description>
		<content:encoded><![CDATA[<p>We&#8217;re on the same page. The perfect world is where we plug things in without incremental effort; since we are not there as yet, I am suggesting that emergence plays will allow the market to set the standard, and that resource is applied to the things that matter. You know my views on diverting resources to make things work with IE already. For sure I am not saying that the resources we save on Firefox should be used for IE. What I am saying is that Firefox adoption should not attract incremental resource until it needs to, and that we could use those resources to build business value elsewhere. Not in IE.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dominic Sayers</title>
		<link>http://confusedofcalcutta.com/2006/06/19/four-pillars-thinking-about-standards-in-an-enterprise-architecture-context/comment-page-1/#comment-1326</link>
		<dc:creator>Dominic Sayers</dc:creator>
		<pubDate>Wed, 21 Jun 2006 09:38:55 +0000</pubDate>
		<guid isPermaLink="false">http://confusedofcalcutta.com/2006/06/19/four-pillars-thinking-about-standards-in-an-enterprise-architecture-context/#comment-1326</guid>
		<description>So you&#039;re saying that the fact that our organisation decided *not* to support Firefox was part of the reason for the growth in its usage. The story being that (1) we allowed it to be used, (2) it had value because it encapsulated useful functionality and it required no support (i.e. if it had required support and none was available it would not have had value), (3) its usage grew because it had value.

So far I think I follow and if so then I agree. I am a little suspicious of the corollary that we should not divert resources into making things work with Firefox. Although there is a chicken-and-egg problem here I believe that Firefox represents a standard that should be the core target. Diverting resources into making things work with Internet Explorer is a necessary evil that we must tolerate for a little while longer.</description>
		<content:encoded><![CDATA[<p>So you&#8217;re saying that the fact that our organisation decided *not* to support Firefox was part of the reason for the growth in its usage. The story being that (1) we allowed it to be used, (2) it had value because it encapsulated useful functionality and it required no support (i.e. if it had required support and none was available it would not have had value), (3) its usage grew because it had value.</p>
<p>So far I think I follow and if so then I agree. I am a little suspicious of the corollary that we should not divert resources into making things work with Firefox. Although there is a chicken-and-egg problem here I believe that Firefox represents a standard that should be the core target. Diverting resources into making things work with Internet Explorer is a necessary evil that we must tolerate for a little while longer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Yeomans</title>
		<link>http://confusedofcalcutta.com/2006/06/19/four-pillars-thinking-about-standards-in-an-enterprise-architecture-context/comment-page-1/#comment-1255</link>
		<dc:creator>Andrew Yeomans</dc:creator>
		<pubDate>Tue, 20 Jun 2006 10:02:35 +0000</pubDate>
		<guid isPermaLink="false">http://confusedofcalcutta.com/2006/06/19/four-pillars-thinking-about-standards-in-an-enterprise-architecture-context/#comment-1255</guid>
		<description>Simple distinction is that de-facto standards are likely to be Officially Sanctioned Lock-ins but reduce costs of diversity at the risk of increased costs due to monopoly. 

De-jure standards have a chance of promoting competition leading to lower procurement costs but potentially higher support costs; but also have a risk of being agreed by a monopolistic cartel.

It&#039;s not inherently open vs proprietary standards. Open Source has its own de-facto standards (e.g. the Netscape bookmark format). But the key differentiator is the standardisation process itself, and the licence that the information is released under. 

IETF and W3C have been good at promoting open standards that are free (liberated and cost) for all.  Other standards bodies have gone down the proprietary documentation route (BSI, ISO) which restricts adoption. Remember OSI?</description>
		<content:encoded><![CDATA[<p>Simple distinction is that de-facto standards are likely to be Officially Sanctioned Lock-ins but reduce costs of diversity at the risk of increased costs due to monopoly. </p>
<p>De-jure standards have a chance of promoting competition leading to lower procurement costs but potentially higher support costs; but also have a risk of being agreed by a monopolistic cartel.</p>
<p>It&#8217;s not inherently open vs proprietary standards. Open Source has its own de-facto standards (e.g. the Netscape bookmark format). But the key differentiator is the standardisation process itself, and the licence that the information is released under. </p>
<p>IETF and W3C have been good at promoting open standards that are free (liberated and cost) for all.  Other standards bodies have gone down the proprietary documentation route (BSI, ISO) which restricts adoption. Remember OSI?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Dellow</title>
		<link>http://confusedofcalcutta.com/2006/06/19/four-pillars-thinking-about-standards-in-an-enterprise-architecture-context/comment-page-1/#comment-1220</link>
		<dc:creator>James Dellow</dc:creator>
		<pubDate>Tue, 20 Jun 2006 03:14:40 +0000</pubDate>
		<guid isPermaLink="false">http://confusedofcalcutta.com/2006/06/19/four-pillars-thinking-about-standards-in-an-enterprise-architecture-context/#comment-1220</guid>
		<description>JP - I had been thinking about this and other &quot;intranet 2.0&quot; related issues this week while revisting a blog piece I wrote last year, called the Intranet Imperative, here http://chieftech.blogspot.com/2005/06/intranet-imperative-part-1.html . The idea of &quot;software written above the level of the single device&quot; that Tim O&#039;Reilly refers to in his Web 2.0 explaination comes to mind in respect to your post - see http://www.synthesist.net/writing/onleavingms.html for the original. 

Unfortunately enterprises have been caught out in their intranet 1.0 approach by picking one browser application and building on top of it. But as we will increasingly want to extend the intranet beyond the desktop PC browser and borrow from the Web 2.0 this will need to change. I also believe I&#039;ve heard predictions from Gartner and the like that some enterprises will tell employees to supply their own computing equipment (of their choice), so even more so will the idea of enterprise standards need to move to a different layer of the system.

What do you think?</description>
		<content:encoded><![CDATA[<p>JP &#8211; I had been thinking about this and other &#8220;intranet 2.0&#8243; related issues this week while revisting a blog piece I wrote last year, called the Intranet Imperative, here <a href="http://chieftech.blogspot.com/2005/06/intranet-imperative-part-1.html" rel="nofollow">http://chieftech.blogspot.com/2005/06/intranet-imperative-part-1.html</a> . The idea of &#8220;software written above the level of the single device&#8221; that Tim O&#8217;Reilly refers to in his Web 2.0 explaination comes to mind in respect to your post &#8211; see <a href="http://www.synthesist.net/writing/onleavingms.html" rel="nofollow">http://www.synthesist.net/writing/onleavingms.html</a> for the original. </p>
<p>Unfortunately enterprises have been caught out in their intranet 1.0 approach by picking one browser application and building on top of it. But as we will increasingly want to extend the intranet beyond the desktop PC browser and borrow from the Web 2.0 this will need to change. I also believe I&#8217;ve heard predictions from Gartner and the like that some enterprises will tell employees to supply their own computing equipment (of their choice), so even more so will the idea of enterprise standards need to move to a different layer of the system.</p>
<p>What do you think?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JP</title>
		<link>http://confusedofcalcutta.com/2006/06/19/four-pillars-thinking-about-standards-in-an-enterprise-architecture-context/comment-page-1/#comment-1204</link>
		<dc:creator>JP</dc:creator>
		<pubDate>Tue, 20 Jun 2006 00:11:31 +0000</pubDate>
		<guid isPermaLink="false">http://confusedofcalcutta.com/2006/06/19/four-pillars-thinking-about-standards-in-an-enterprise-architecture-context/#comment-1204</guid>
		<description>I guess what I was trying to say, but in a bolshie way, was that enterprise battles are now between opensource and community standards and vendor standards. Not-adhering-to-a-vendor-standard-yet-working is the same as working-with-open-and-community-standards. At least to me.

I&#039;m working on another post on this subject which may help clarify this. Thanks anyway Kris.</description>
		<content:encoded><![CDATA[<p>I guess what I was trying to say, but in a bolshie way, was that enterprise battles are now between opensource and community standards and vendor standards. Not-adhering-to-a-vendor-standard-yet-working is the same as working-with-open-and-community-standards. At least to me.</p>
<p>I&#8217;m working on another post on this subject which may help clarify this. Thanks anyway Kris.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kris Tuttle</title>
		<link>http://confusedofcalcutta.com/2006/06/19/four-pillars-thinking-about-standards-in-an-enterprise-architecture-context/comment-page-1/#comment-1198</link>
		<dc:creator>Kris Tuttle</dc:creator>
		<pubDate>Mon, 19 Jun 2006 20:31:00 +0000</pubDate>
		<guid isPermaLink="false">http://confusedofcalcutta.com/2006/06/19/four-pillars-thinking-about-standards-in-an-enterprise-architecture-context/#comment-1198</guid>
		<description>I think they are.  All the examples of &quot;standards&quot; I know of are put in place to reduce costs.  That said I don&#039;t know that I&#039;ve ever seen a study that really concluded that buying 3000 computers from one vendor is cheaper than buying 300 from 10 vendors.  Or that &quot;locking down&quot; users doesn&#039;t diminish their productivity while it may lower helpdesk staffing costs.

Often people say &quot;well we can&#039;t support chaos.&quot;  But maybe that&#039;s just wrong thinking now that Internet standards, SOA, Firefox and other open source commodity products are broadly available.  

I think the infrastructure is really changing but still wonder what will happen inside the Enterprise.  They still seem stuck in the 1980&#039;s to me versus what companies like Google and Firefox are doing.</description>
		<content:encoded><![CDATA[<p>I think they are.  All the examples of &#8220;standards&#8221; I know of are put in place to reduce costs.  That said I don&#8217;t know that I&#8217;ve ever seen a study that really concluded that buying 3000 computers from one vendor is cheaper than buying 300 from 10 vendors.  Or that &#8220;locking down&#8221; users doesn&#8217;t diminish their productivity while it may lower helpdesk staffing costs.</p>
<p>Often people say &#8220;well we can&#8217;t support chaos.&#8221;  But maybe that&#8217;s just wrong thinking now that Internet standards, SOA, Firefox and other open source commodity products are broadly available.  </p>
<p>I think the infrastructure is really changing but still wonder what will happen inside the Enterprise.  They still seem stuck in the 1980&#8242;s to me versus what companies like Google and Firefox are doing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

