<?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: E-books: A Textbook Case</title>
	<atom:link href="http://scholarlykitchen.sspnet.org/2008/08/20/e-books-a-textbook-case/feed/" rel="self" type="application/rss+xml" />
	<link>http://scholarlykitchen.sspnet.org/2008/08/20/e-books-a-textbook-case/</link>
	<description>What&#039;s Hot &#38; What&#039;s Cooking in Scholarly Publishing - from the Society for Scholarly Publishing</description>
	<lastBuildDate>Thu, 16 Feb 2012 03:31:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Compellent CEO needs an Amazon Kindle &#124; The SAN Technologist</title>
		<link>http://scholarlykitchen.sspnet.org/2008/08/20/e-books-a-textbook-case/#comment-949</link>
		<dc:creator><![CDATA[Compellent CEO needs an Amazon Kindle &#124; The SAN Technologist]]></dc:creator>
		<pubDate>Fri, 03 Oct 2008 16:52:05 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.wordpress.com/?p=693#comment-949</guid>
		<description><![CDATA[[...] E-books: A Textbook Case [...]]]></description>
		<content:encoded><![CDATA[<p>[...] E-books: A Textbook Case [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thorn</title>
		<link>http://scholarlykitchen.sspnet.org/2008/08/20/e-books-a-textbook-case/#comment-748</link>
		<dc:creator><![CDATA[thorn]]></dc:creator>
		<pubDate>Wed, 20 Aug 2008 15:50:07 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.wordpress.com/?p=693#comment-748</guid>
		<description><![CDATA[re. citation difficulties: of course we will link rather than quoting, instead of using footnotes. but for the sake of flow, in our writing we will want to speak the words of others using our own voices and contexts, and links are still a visual distraction. how could that little bright blue thing in the middle of a bunch of black text *not* be? plus, we still haven&#039;t totally overcome the problem of *dead* links.

so at least for the transitional period, why not number paragraphs? page-breaks have *always* been strange and arbitrary, even in the world of pure print. that&#039;s why students were always instructed to all purchase the same edition of a textbook: so page numbers would always have the same meaning. line-numbering is conventional in the publication of literature; unfortunately, it is just as arbitrary and mess-up-able as page numbering. but units inherent to the text were numbered, we&#039;d be in decent shape, because paragraph breaks do not typically change with text layout. yeah, the idea seems like &#039;phase 0.5&#039; or lower;  but if one considers line-numbering of verse, and the fine-tuned numbering of passages in scripture, and then compares it with systems of tagging and indexing used today, the idea expresses a data-management principle which, while useful from the first moment of its inception, was also many centuries *ahead* of its time.]]></description>
		<content:encoded><![CDATA[<p>re. citation difficulties: of course we will link rather than quoting, instead of using footnotes. but for the sake of flow, in our writing we will want to speak the words of others using our own voices and contexts, and links are still a visual distraction. how could that little bright blue thing in the middle of a bunch of black text *not* be? plus, we still haven&#8217;t totally overcome the problem of *dead* links.</p>
<p>so at least for the transitional period, why not number paragraphs? page-breaks have *always* been strange and arbitrary, even in the world of pure print. that&#8217;s why students were always instructed to all purchase the same edition of a textbook: so page numbers would always have the same meaning. line-numbering is conventional in the publication of literature; unfortunately, it is just as arbitrary and mess-up-able as page numbering. but units inherent to the text were numbered, we&#8217;d be in decent shape, because paragraph breaks do not typically change with text layout. yeah, the idea seems like &#8216;phase 0.5&#8242; or lower;  but if one considers line-numbering of verse, and the fine-tuned numbering of passages in scripture, and then compares it with systems of tagging and indexing used today, the idea expresses a data-management principle which, while useful from the first moment of its inception, was also many centuries *ahead* of its time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jill ONeill</title>
		<link>http://scholarlykitchen.sspnet.org/2008/08/20/e-books-a-textbook-case/#comment-747</link>
		<dc:creator><![CDATA[Jill ONeill]]></dc:creator>
		<pubDate>Wed, 20 Aug 2008 13:58:53 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.wordpress.com/?p=693#comment-747</guid>
		<description><![CDATA[Echoing David&#039;s point above, what I wish I could see is greater linking between texts in the sense of a system recognizing the ties between a book containing the text of a novel and a book containing essays examining various aspects of that novel. The hyperlinks should help the user navigate across the two. At present such links occur in larger information environments, services such as those provided by an Elsevier or a Wolters Kluwer, but not in e-books aimed at the individual reader/researcher.]]></description>
		<content:encoded><![CDATA[<p>Echoing David&#8217;s point above, what I wish I could see is greater linking between texts in the sense of a system recognizing the ties between a book containing the text of a novel and a book containing essays examining various aspects of that novel. The hyperlinks should help the user navigate across the two. At present such links occur in larger information environments, services such as those provided by an Elsevier or a Wolters Kluwer, but not in e-books aimed at the individual reader/researcher.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Weinberger</title>
		<link>http://scholarlykitchen.sspnet.org/2008/08/20/e-books-a-textbook-case/#comment-744</link>
		<dc:creator><![CDATA[David Weinberger]]></dc:creator>
		<pubDate>Wed, 20 Aug 2008 11:10:34 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.wordpress.com/?p=693#comment-744</guid>
		<description><![CDATA[The biggest &quot;feature&quot; the Kindle is lacking -- the thing that keeps it as a 1.0, or 1.5 technology -- is that it&#039;s not networked. More exactly, it uses the Net only as a way to deliver content, and not as a way to connect readers and link ideas. A truly networked ebook would be disruptive technology and not just a digitized version of paper-based publishing.]]></description>
		<content:encoded><![CDATA[<p>The biggest &#8220;feature&#8221; the Kindle is lacking &#8212; the thing that keeps it as a 1.0, or 1.5 technology &#8212; is that it&#8217;s not networked. More exactly, it uses the Net only as a way to deliver content, and not as a way to connect readers and link ideas. A truly networked ebook would be disruptive technology and not just a digitized version of paper-based publishing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

