<?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: Putting Your Golden Eggs in One Basket</title>
	<atom:link href="http://blog.ecorrado.us/2008/11/26/putting-your-golden-eggs-in-one-basket/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ecorrado.us/2008/11/26/putting-your-golden-eggs-in-one-basket/</link>
	<description>Ramblings about library technology, open source software, and other adventures!</description>
	<lastBuildDate>Fri, 28 Oct 2011 05:59:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Jonathan Rochkind</title>
		<link>http://blog.ecorrado.us/2008/11/26/putting-your-golden-eggs-in-one-basket/comment-page-1/#comment-8609</link>
		<dc:creator>Jonathan Rochkind</dc:creator>
		<pubDate>Wed, 26 Nov 2008 20:38:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ecorrado.us/?p=578#comment-8609</guid>
		<description>Thanks Ed. The biggest problem I see with &#039;one basket&#039; actually isn&#039;t captured by my &#039;egg&#039; metaphor. 

When you count on only one organization to provide you your innovation, you are limited to the timelines, resources, and priorities of that organization. We are certainly used to that with our ILS and other software vendors. There&#039;s a feature you really want, and you just have to wait for the vendor to implement it, maybe, someday.  

And the vendor, like all of us, has limited resources. And the vendor, like all of us, has to chose priorities based on a variety of factors, including their business model. I&#039;m not talking about an incompetent vendor here, _any_ vendor has limited resources, and has to make priorities, and when you&#039;ve got only &#039;one basket&#039;, you are limited to hoping they do what you need, eventually. 

In an open world, open data, open source, you don&#039;t have to wait for your one vendor. Other people can work collaboratively with that vendor, to add their resources to the mix, based on their priorities. Other people, even other vendors, can go ahead and work on it themselves even without collaborating with the first vendor, again based on their own priorities and their own resources. If you need something and _you&#039;ve_ got the resources, you can make it happen. If you don&#039;t have the resources, there&#039;s a chance there&#039;s someone else who needs the same thing who DOES. 

You don&#039;t have to wait on the timeline and constrained resources of the one closed vendor. When you&#039;ve got open-ness, there is a synergistic effect where everyone&#039;s efforts build on each other, and you can collectively accomplish more than you ever could with a collection of &#039;closed&#039; data or products, that only one organization can work on. 

(Incidentally, its recognition of that that leads to such things as the Ex Libris &#039;open platform strategy&#039;. They&#039;re trying to get the benefits of that synergy in open-ness, _without_ actually giving up the closed monopoly on their central assets. It&#039;s an interesting combination, there may be some way to get it right, especially when it comes to software, but it&#039;ll take some experimenting.  When it comes to data, I&#039;m less optimistic that anything short of actual openness can give you the benefits.)</description>
		<content:encoded><![CDATA[<p>Thanks Ed. The biggest problem I see with &#8216;one basket&#8217; actually isn&#8217;t captured by my &#8216;egg&#8217; metaphor. </p>
<p>When you count on only one organization to provide you your innovation, you are limited to the timelines, resources, and priorities of that organization. We are certainly used to that with our ILS and other software vendors. There&#8217;s a feature you really want, and you just have to wait for the vendor to implement it, maybe, someday.  </p>
<p>And the vendor, like all of us, has limited resources. And the vendor, like all of us, has to chose priorities based on a variety of factors, including their business model. I&#8217;m not talking about an incompetent vendor here, _any_ vendor has limited resources, and has to make priorities, and when you&#8217;ve got only &#8216;one basket&#8217;, you are limited to hoping they do what you need, eventually. </p>
<p>In an open world, open data, open source, you don&#8217;t have to wait for your one vendor. Other people can work collaboratively with that vendor, to add their resources to the mix, based on their priorities. Other people, even other vendors, can go ahead and work on it themselves even without collaborating with the first vendor, again based on their own priorities and their own resources. If you need something and _you&#8217;ve_ got the resources, you can make it happen. If you don&#8217;t have the resources, there&#8217;s a chance there&#8217;s someone else who needs the same thing who DOES. </p>
<p>You don&#8217;t have to wait on the timeline and constrained resources of the one closed vendor. When you&#8217;ve got open-ness, there is a synergistic effect where everyone&#8217;s efforts build on each other, and you can collectively accomplish more than you ever could with a collection of &#8216;closed&#8217; data or products, that only one organization can work on. </p>
<p>(Incidentally, its recognition of that that leads to such things as the Ex Libris &#8216;open platform strategy&#8217;. They&#8217;re trying to get the benefits of that synergy in open-ness, _without_ actually giving up the closed monopoly on their central assets. It&#8217;s an interesting combination, there may be some way to get it right, especially when it comes to software, but it&#8217;ll take some experimenting.  When it comes to data, I&#8217;m less optimistic that anything short of actual openness can give you the benefits.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

