<?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: How Many Books Dance on the Head of an e-Pin?</title>
	<atom:link href="http://scholarlykitchen.sspnet.org/2009/11/20/how-many-books-dance-on-the-head-of-an-e-pin/feed/" rel="self" type="application/rss+xml" />
	<link>http://scholarlykitchen.sspnet.org/2009/11/20/how-many-books-dance-on-the-head-of-an-e-pin/</link>
	<description>What&#039;s Hot &#38; What&#039;s Cooking in Scholarly Publishing - from the Society for Scholarly Publishing</description>
	<lastBuildDate>Tue, 16 Mar 2010 10:55:31 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Lukas Koster</title>
		<link>http://scholarlykitchen.sspnet.org/2009/11/20/how-many-books-dance-on-the-head-of-an-e-pin/#comment-5702</link>
		<dc:creator>Lukas Koster</dc:creator>
		<pubDate>Mon, 23 Nov 2009 09:25:28 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=7054#comment-5702</guid>
		<description>I did not know of the existence of the ISTC, but in my original post http://commonplace.net/2009/11/is-an-e-book-a-book/ I argue we need an identifier for what I call &quot;stories&quot;, which are units of content, or the FRBR &quot;work&quot; entity. I suggested to use DOI for that.

About e-books being FRBR Manifestations: I argue that they can either be Expressions or Manifestations, depending on the nature of the e-book. If it&#039;s a new &quot;born digital&quot; publication containing for insatnce a number of earlier published articles/works, it would be an Expression of a new aggregate Work in its own right.</description>
		<content:encoded><![CDATA[<p>I did not know of the existence of the ISTC, but in my original post <a href="http://commonplace.net/2009/11/is-an-e-book-a-book/" rel="nofollow">http://commonplace.net/2009/11/is-an-e-book-a-book/</a> I argue we need an identifier for what I call &#8220;stories&#8221;, which are units of content, or the FRBR &#8220;work&#8221; entity. I suggested to use DOI for that.</p>
<p>About e-books being FRBR Manifestations: I argue that they can either be Expressions or Manifestations, depending on the nature of the e-book. If it&#8217;s a new &#8220;born digital&#8221; publication containing for insatnce a number of earlier published articles/works, it would be an Expression of a new aggregate Work in its own right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Kasdorf</title>
		<link>http://scholarlykitchen.sspnet.org/2009/11/20/how-many-books-dance-on-the-head-of-an-e-pin/#comment-5678</link>
		<dc:creator>Bill Kasdorf</dc:creator>
		<pubDate>Fri, 20 Nov 2009 17:42:22 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=7054#comment-5678</guid>
		<description>Quick correction: the end of the long paragraph should say &quot;because their systems CAN&#039;T handle the complexity.&quot;

And another observation: librarians tend to think in terms of WORKS whereas publishers tend to think in terms of MANIFESTATIONS. In the past, the librarian could just say &quot;sure, we have that book&quot; whereas the publisher is selling you a product. But that was then, this is now. We&#039;re now seeing that their needs intersect: the publisher needs customers, and the librarian needs patrons, who are looking for a WORK to be able to unambiguously specify which MANIFESTATION of that work they want.</description>
		<content:encoded><![CDATA[<p>Quick correction: the end of the long paragraph should say &#8220;because their systems CAN&#8217;T handle the complexity.&#8221;</p>
<p>And another observation: librarians tend to think in terms of WORKS whereas publishers tend to think in terms of MANIFESTATIONS. In the past, the librarian could just say &#8220;sure, we have that book&#8221; whereas the publisher is selling you a product. But that was then, this is now. We&#8217;re now seeing that their needs intersect: the publisher needs customers, and the librarian needs patrons, who are looking for a WORK to be able to unambiguously specify which MANIFESTATION of that work they want.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Kasdorf</title>
		<link>http://scholarlykitchen.sspnet.org/2009/11/20/how-many-books-dance-on-the-head-of-an-e-pin/#comment-5676</link>
		<dc:creator>Bill Kasdorf</dc:creator>
		<pubDate>Fri, 20 Nov 2009 17:17:25 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=7054#comment-5676</guid>
		<description>There&#039;s another very practical aspect to all this, and that&#039;s the issue of identifiers.

Here&#039;s how it&#039;s SUPPOSED to work:

--The ISTC, the International Standard Text Code, is the identifier of the WORK. (ISTC is a new standard and it has not been used much yet, but it should be.) A given work should have one and only one ISTC. (There is obviously the question of when one work becomes a different work: a corrected version in a reprint is not, a new edition generally IS considered a distinct work.)

--The ISBN, the International Standard Book Number, is the identifier of a SEPARATELY TRADEABLE PRODUCT, and thus is generally considered to correspond to the MANIFESTATION. Publishers have routinely assigned unique ISBNs to the hardcover and paperback versions of a book, because they are separate tradeable products: if somebody orders the book, you need to know which of those they want. The murkiness comes in the digital era. Technically (and officially) all separately tradeable versions of a book should have a separate ISBN: thus the Kindle version is not the same as the Sony version, and the NetLibrary version is not the same as the eBrary version. . . . You see the slippery slope here. Publishers are gravitating (incorrectly) to assigning an &quot;eISBN&quot; and using it to refer generically to any e-version of the book. That undermines the whole purpose of the ISBN because it eliminates the distinction between distinct tradeable products: the Kindle version is not the same as the Sony version. One way around this is for the publisher to assign an ISBN to the ePub version (and a separate one to a web-ready PDF version, I might add) . . . but this just pushes the issue downstream. My view (and I am currently in the minority here but I think this view will ultimately prevail) is that when another entity (say, Amazon or NetLibrary) takes that ePub or that PDF and creates _their_ version, THEY should assign a new ISBN to that SEPARATELY TRADEABLE PRODUCT. I think this is completely logical and consistent. However, publishers (currently) see this as &quot;losing control&quot; of the ISBN. On the other hand, many publishers balk at assigning bunches of ISBNs because their systems can handle the complexity.

Sorry to go on a bit but this is actually a huge issue that is preoccupying me a lot these days.

One other point: the &quot;item&quot; in the FRBR scheme is a COPY of the hardcover book, or a FILE on your Kindle; the hardcover and the Kindle version are each MANIFESTATIONS of the written EXPRESSION of the WORK.

Don&#039;t get me going on performances. . . .

--Bill Kasdorf</description>
		<content:encoded><![CDATA[<p>There&#8217;s another very practical aspect to all this, and that&#8217;s the issue of identifiers.</p>
<p>Here&#8217;s how it&#8217;s SUPPOSED to work:</p>
<p>&#8211;The ISTC, the International Standard Text Code, is the identifier of the WORK. (ISTC is a new standard and it has not been used much yet, but it should be.) A given work should have one and only one ISTC. (There is obviously the question of when one work becomes a different work: a corrected version in a reprint is not, a new edition generally IS considered a distinct work.)</p>
<p>&#8211;The ISBN, the International Standard Book Number, is the identifier of a SEPARATELY TRADEABLE PRODUCT, and thus is generally considered to correspond to the MANIFESTATION. Publishers have routinely assigned unique ISBNs to the hardcover and paperback versions of a book, because they are separate tradeable products: if somebody orders the book, you need to know which of those they want. The murkiness comes in the digital era. Technically (and officially) all separately tradeable versions of a book should have a separate ISBN: thus the Kindle version is not the same as the Sony version, and the NetLibrary version is not the same as the eBrary version. . . . You see the slippery slope here. Publishers are gravitating (incorrectly) to assigning an &#8220;eISBN&#8221; and using it to refer generically to any e-version of the book. That undermines the whole purpose of the ISBN because it eliminates the distinction between distinct tradeable products: the Kindle version is not the same as the Sony version. One way around this is for the publisher to assign an ISBN to the ePub version (and a separate one to a web-ready PDF version, I might add) . . . but this just pushes the issue downstream. My view (and I am currently in the minority here but I think this view will ultimately prevail) is that when another entity (say, Amazon or NetLibrary) takes that ePub or that PDF and creates _their_ version, THEY should assign a new ISBN to that SEPARATELY TRADEABLE PRODUCT. I think this is completely logical and consistent. However, publishers (currently) see this as &#8220;losing control&#8221; of the ISBN. On the other hand, many publishers balk at assigning bunches of ISBNs because their systems can handle the complexity.</p>
<p>Sorry to go on a bit but this is actually a huge issue that is preoccupying me a lot these days.</p>
<p>One other point: the &#8220;item&#8221; in the FRBR scheme is a COPY of the hardcover book, or a FILE on your Kindle; the hardcover and the Kindle version are each MANIFESTATIONS of the written EXPRESSION of the WORK.</p>
<p>Don&#8217;t get me going on performances. . . .</p>
<p>&#8211;Bill Kasdorf</p>
]]></content:encoded>
	</item>
</channel>
</rss>
