<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Let&#8217;s Hear It for Reckless Enthusiasm!</title>
	<atom:link href="http://scholarlykitchen.sspnet.org/2010/01/01/lets-hear-it-for-reckless-enthusiasm/feed/" rel="self" type="application/rss+xml" />
	<link>http://scholarlykitchen.sspnet.org/2010/01/01/lets-hear-it-for-reckless-enthusiasm/</link>
	<description>What&#039;s Hot &#38; What&#039;s Cooking in Scholarly Publishing - from the Society for Scholarly Publishing</description>
	<lastBuildDate>Wed, 15 Feb 2012 17:25:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Joe&#8217;s Picks for 2010: Reckless Enthusiasm and the Platform Wars &#171; The Scholarly Kitchen</title>
		<link>http://scholarlykitchen.sspnet.org/2010/01/01/lets-hear-it-for-reckless-enthusiasm/#comment-25847</link>
		<dc:creator><![CDATA[Joe&#8217;s Picks for 2010: Reckless Enthusiasm and the Platform Wars &#171; The Scholarly Kitchen]]></dc:creator>
		<pubDate>Tue, 28 Dec 2010 09:13:56 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=7543#comment-25847</guid>
		<description><![CDATA[[...] Posts: Let&#8217;s Hear It for Reckless Enthusiasm! and Platform Wars Come to the Book [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Posts: Let&#8217;s Hear It for Reckless Enthusiasm! and Platform Wars Come to the Book [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wanda Braga</title>
		<link>http://scholarlykitchen.sspnet.org/2010/01/01/lets-hear-it-for-reckless-enthusiasm/#comment-10610</link>
		<dc:creator><![CDATA[Wanda Braga]]></dc:creator>
		<pubDate>Mon, 19 Apr 2010 11:07:04 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=7543#comment-10610</guid>
		<description><![CDATA[Nice!Just bookmarked this site, i&#039;ll be back here once again.Love &lt;a href=&quot;http://scholarlykitchen.sspnet.org/2010/01/01/lets-hear-it-for-reckless-enthusiasm/&quot; rel=&quot;nofollow&quot;&gt;http://scholarlykitchen.sspnet.org/2010/01/01/lets-hear-it-for-reckless-enthusiasm/&lt;/a&gt;]]></description>
		<content:encoded><![CDATA[<p>Nice!Just bookmarked this site, i&#8217;ll be back here once again.Love <a href="http://scholarlykitchen.sspnet.org/2010/01/01/lets-hear-it-for-reckless-enthusiasm/" rel="nofollow">http://scholarlykitchen.sspnet.org/2010/01/01/lets-hear-it-for-reckless-enthusiasm/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Crotty</title>
		<link>http://scholarlykitchen.sspnet.org/2010/01/01/lets-hear-it-for-reckless-enthusiasm/#comment-6301</link>
		<dc:creator><![CDATA[David Crotty]]></dc:creator>
		<pubDate>Mon, 04 Jan 2010 16:43:51 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=7543#comment-6301</guid>
		<description><![CDATA[A minor technical point--while I don&#039;t use the system myself, there appears to be a variety of pdf readers out there for use on Android phones, including &lt;a href=&quot;http://andpdf.sourceforge.net/&quot; rel=&quot;nofollow&quot;&gt;Android PDF Viewer&lt;/a&gt;, &lt;a href=&quot;http://zdravkodimitrov.blogspot.com/2009/05/android-apps-review-icviewer.html&quot; rel=&quot;nofollow&quot;&gt;ICViewer&lt;/a&gt;, &lt;a href=&quot;http://www.cerience.com/products/reader/android&quot; rel=&quot;nofollow&quot;&gt;Repligo&lt;/a&gt;, &lt;a href=&quot;http://www.dataviz.com/products/documentstogo/android/&quot; rel=&quot;nofollow&quot;&gt;Documents To Go&lt;/a&gt; and others.]]></description>
		<content:encoded><![CDATA[<p>A minor technical point&#8211;while I don&#8217;t use the system myself, there appears to be a variety of pdf readers out there for use on Android phones, including <a href="http://andpdf.sourceforge.net/" rel="nofollow">Android PDF Viewer</a>, <a href="http://zdravkodimitrov.blogspot.com/2009/05/android-apps-review-icviewer.html" rel="nofollow">ICViewer</a>, <a href="http://www.cerience.com/products/reader/android" rel="nofollow">Repligo</a>, <a href="http://www.dataviz.com/products/documentstogo/android/" rel="nofollow">Documents To Go</a> and others.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Hellman</title>
		<link>http://scholarlykitchen.sspnet.org/2010/01/01/lets-hear-it-for-reckless-enthusiasm/#comment-6267</link>
		<dc:creator><![CDATA[Eric Hellman]]></dc:creator>
		<pubDate>Sat, 02 Jan 2010 17:05:16 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=7543#comment-6267</guid>
		<description><![CDATA[George Gilder talked a lot about the dark fiber problem. But the problem was never paying for the excess fiber, because the incremental cost of laying a hundred fibers instead of just one was negligible compared to the cost of digging the ditch or string the pole.

I guess the comparable excess the information industry has is an excess of content. Who is ever going to read it all? We don&#039;t know, but it gets produced nonetheless.]]></description>
		<content:encoded><![CDATA[<p>George Gilder talked a lot about the dark fiber problem. But the problem was never paying for the excess fiber, because the incremental cost of laying a hundred fibers instead of just one was negligible compared to the cost of digging the ditch or string the pole.</p>
<p>I guess the comparable excess the information industry has is an excess of content. Who is ever going to read it all? We don&#8217;t know, but it gets produced nonetheless.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martyn Daniels</title>
		<link>http://scholarlykitchen.sspnet.org/2010/01/01/lets-hear-it-for-reckless-enthusiasm/#comment-6265</link>
		<dc:creator><![CDATA[Martyn Daniels]]></dc:creator>
		<pubDate>Sat, 02 Jan 2010 08:51:25 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=7543#comment-6265</guid>
		<description><![CDATA[Joe many congratulations on a well thought out piece and insights into disruption over the last few decades.

I find the thing that often holds us back from leaping forward is assumptions. We see &#039;a&#039; anlongside &#039;b&#039; and automatically believe that the two are joined for life. 

In business we all too often see the package and miss the indivual parts that comprise it. People often can&#039;t get it at first when we seperate out the all the parts and often bulke and say &#039;you can&#039;t do that&#039;. They see it as one end to end process not many merely assembled one way.

When we reassemble and understand the parts better it often makes change easy.]]></description>
		<content:encoded><![CDATA[<p>Joe many congratulations on a well thought out piece and insights into disruption over the last few decades.</p>
<p>I find the thing that often holds us back from leaping forward is assumptions. We see &#8216;a&#8217; anlongside &#8216;b&#8217; and automatically believe that the two are joined for life. </p>
<p>In business we all too often see the package and miss the indivual parts that comprise it. People often can&#8217;t get it at first when we seperate out the all the parts and often bulke and say &#8216;you can&#8217;t do that&#8217;. They see it as one end to end process not many merely assembled one way.</p>
<p>When we reassemble and understand the parts better it often makes change easy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph J. Esposito</title>
		<link>http://scholarlykitchen.sspnet.org/2010/01/01/lets-hear-it-for-reckless-enthusiasm/#comment-6264</link>
		<dc:creator><![CDATA[Joseph J. Esposito]]></dc:creator>
		<pubDate>Sat, 02 Jan 2010 06:38:18 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=7543#comment-6264</guid>
		<description><![CDATA[I am familiar with the voice vs. data topic, but it was separate from the excess capacity matter.  As I recall, one telco consultant referred to the excess capacity as &quot;the dark fiber problem.&quot;]]></description>
		<content:encoded><![CDATA[<p>I am familiar with the voice vs. data topic, but it was separate from the excess capacity matter.  As I recall, one telco consultant referred to the excess capacity as &#8220;the dark fiber problem.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger</title>
		<link>http://scholarlykitchen.sspnet.org/2010/01/01/lets-hear-it-for-reckless-enthusiasm/#comment-6263</link>
		<dc:creator><![CDATA[Roger]]></dc:creator>
		<pubDate>Sat, 02 Jan 2010 03:17:32 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=7543#comment-6263</guid>
		<description><![CDATA[I appreciate your support for “reckless enthusiasm” particularly when applied to building out infrastructure and basic R&amp;D.  Your noting the huge need for a “new order of bibliographical records” is particularly apt.  I’m engaged in attempting to accomplish such by supporting the application of principles of the emerging Semantic Web to media metadata.]]></description>
		<content:encoded><![CDATA[<p>I appreciate your support for “reckless enthusiasm” particularly when applied to building out infrastructure and basic R&amp;D.  Your noting the huge need for a “new order of bibliographical records” is particularly apt.  I’m engaged in attempting to accomplish such by supporting the application of principles of the emerging Semantic Web to media metadata.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Hellman</title>
		<link>http://scholarlykitchen.sspnet.org/2010/01/01/lets-hear-it-for-reckless-enthusiasm/#comment-6260</link>
		<dc:creator><![CDATA[Eric Hellman]]></dc:creator>
		<pubDate>Fri, 01 Jan 2010 21:41:50 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=7543#comment-6260</guid>
		<description><![CDATA[Joe, 

In the Mid 90&#039;s, I worked at Bell Labs. Your recollection is slightly off. Our worry was not about filling the pipes, although we wondered how that would happen. Our worry was mainly about the huge gap between the cost of provisioning long distance phone calls and the revenue they were generating. When it cost a fraction of a penny to carry a voice call, and typical charges were 10 cents- $1 per minute, how long would that revenue stream survive? There was no way you could charge for data what you could charge for voice, but there was still a lot of money to be made. So the result was a lot of energy put into protecting the long distance revenue stream.

The analogy to today is clear. Publishers are spending most of their energy trying to protect to print revenue stream, when it&#039;s clear that a lot of money could be made on the digital channel with appropriate pricing.

In the end, it&#039;s impossible to sustain a big gap between cost and price. Efforts to sustain the incumbent revenue will eventually lead to a collapse.

In telecom, it turned out that the RBOCs, the unsexy low-growth stepchildren of the Bell System ended up on top. They had the connections to the customer and the expensive physical plant. You must have advised them well, because they did quite well while AT&amp;T, Sprint and MCI ran off a cliff.

In the Book ecosystem, the entities analogous to the RBOCs would be the distributors (Ingram, B&amp;T) and the bricks and mortar chains. Interestingly, they&#039;re the ones best placed to create the &quot;direct connection&quot; infrastructure that you suggest will require &quot;reckless enthusiasm&quot;. What is so reckless, exactly?]]></description>
		<content:encoded><![CDATA[<p>Joe, </p>
<p>In the Mid 90&#8242;s, I worked at Bell Labs. Your recollection is slightly off. Our worry was not about filling the pipes, although we wondered how that would happen. Our worry was mainly about the huge gap between the cost of provisioning long distance phone calls and the revenue they were generating. When it cost a fraction of a penny to carry a voice call, and typical charges were 10 cents- $1 per minute, how long would that revenue stream survive? There was no way you could charge for data what you could charge for voice, but there was still a lot of money to be made. So the result was a lot of energy put into protecting the long distance revenue stream.</p>
<p>The analogy to today is clear. Publishers are spending most of their energy trying to protect to print revenue stream, when it&#8217;s clear that a lot of money could be made on the digital channel with appropriate pricing.</p>
<p>In the end, it&#8217;s impossible to sustain a big gap between cost and price. Efforts to sustain the incumbent revenue will eventually lead to a collapse.</p>
<p>In telecom, it turned out that the RBOCs, the unsexy low-growth stepchildren of the Bell System ended up on top. They had the connections to the customer and the expensive physical plant. You must have advised them well, because they did quite well while AT&amp;T, Sprint and MCI ran off a cliff.</p>
<p>In the Book ecosystem, the entities analogous to the RBOCs would be the distributors (Ingram, B&amp;T) and the bricks and mortar chains. Interestingly, they&#8217;re the ones best placed to create the &#8220;direct connection&#8221; infrastructure that you suggest will require &#8220;reckless enthusiasm&#8221;. What is so reckless, exactly?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Kasdorf</title>
		<link>http://scholarlykitchen.sspnet.org/2010/01/01/lets-hear-it-for-reckless-enthusiasm/#comment-6258</link>
		<dc:creator><![CDATA[Bill Kasdorf]]></dc:creator>
		<pubDate>Fri, 01 Jan 2010 19:40:32 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=7543#comment-6258</guid>
		<description><![CDATA[As another old timer who tries not to think like one, I applaud this post, Joe--it puts so much of our shared experience of the past few decades into such good perspective.

A couple of thoughts it has prompted:

--How can we improve our chances of taking the right reckless leaps? Two strategies come to mind: attention and humility. They go hand in hand. You can&#039;t really see what&#039;s happening if you think you already have it all figured out. And if you really are paying attention, it will be obvious to you that you don&#039;t have it all figured out.

--An important part of this dynamic is how one reckless leap leads to another unanticipated reckless leap. We jumped from Gopher to Netscape because it had just become so darn hard to _see_ into the Internet. We have Google because it was so darn hard to _find_ what we were looking for, when the &quot;Information Superhighway&quot; (which implied on- and off-ramps, clear starting and ending points, from me to you and you to me) became a real Web. We owe all the exciting work now being done on semantics to the problem we have figuring out what all this stuff _is_. (Ditto for standards.) And do I need to mention that despite the initial wrongheaded expectation that advertising was going to pay for everything (the previous commenter, Tim O&#039;Reilly, gave the most cogent analysis of this, especially for professional publishers, I&#039;ve ever seen, at TOC a couple of years ago--his walk through the logic and the math was very illuminating), guess where Google has gotten all its billions?

Thanks again for a terrific post.

--Bill Kasdorf]]></description>
		<content:encoded><![CDATA[<p>As another old timer who tries not to think like one, I applaud this post, Joe&#8211;it puts so much of our shared experience of the past few decades into such good perspective.</p>
<p>A couple of thoughts it has prompted:</p>
<p>&#8211;How can we improve our chances of taking the right reckless leaps? Two strategies come to mind: attention and humility. They go hand in hand. You can&#8217;t really see what&#8217;s happening if you think you already have it all figured out. And if you really are paying attention, it will be obvious to you that you don&#8217;t have it all figured out.</p>
<p>&#8211;An important part of this dynamic is how one reckless leap leads to another unanticipated reckless leap. We jumped from Gopher to Netscape because it had just become so darn hard to _see_ into the Internet. We have Google because it was so darn hard to _find_ what we were looking for, when the &#8220;Information Superhighway&#8221; (which implied on- and off-ramps, clear starting and ending points, from me to you and you to me) became a real Web. We owe all the exciting work now being done on semantics to the problem we have figuring out what all this stuff _is_. (Ditto for standards.) And do I need to mention that despite the initial wrongheaded expectation that advertising was going to pay for everything (the previous commenter, Tim O&#8217;Reilly, gave the most cogent analysis of this, especially for professional publishers, I&#8217;ve ever seen, at TOC a couple of years ago&#8211;his walk through the logic and the math was very illuminating), guess where Google has gotten all its billions?</p>
<p>Thanks again for a terrific post.</p>
<p>&#8211;Bill Kasdorf</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcia Conner</title>
		<link>http://scholarlykitchen.sspnet.org/2010/01/01/lets-hear-it-for-reckless-enthusiasm/#comment-6257</link>
		<dc:creator><![CDATA[Marcia Conner]]></dc:creator>
		<pubDate>Fri, 01 Jan 2010 19:19:17 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=7543#comment-6257</guid>
		<description><![CDATA[Our work creating learning cultures shows they produce more energy than they consume -- fueling creativity that often yields unexpected returns and appreciating the serendipity that lets them see more opportunities than their competitors. You&#039;ve made a wonderful case for considering that energy &quot;enthusiasm&quot;: wild, exuberant, unabated fire. Thank you.]]></description>
		<content:encoded><![CDATA[<p>Our work creating learning cultures shows they produce more energy than they consume &#8212; fueling creativity that often yields unexpected returns and appreciating the serendipity that lets them see more opportunities than their competitors. You&#8217;ve made a wonderful case for considering that energy &#8220;enthusiasm&#8221;: wild, exuberant, unabated fire. Thank you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

