<?xml version="1.0" encoding="iso-8859-1"?><!-- generator="b2evolution/2.4.2" -->
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:admin="http://webns.net/mvcb/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
		<title>shimenawa - Latest comments on The ISBN as SKU</title>
		<link>http://blogs.lib.berkeley.edu/shimenawa.php?disp=comments</link>
		<description></description>
		<language>en-US</language>
		<docs>http://backend.userland.com/rss</docs>
		<admin:generatorAgent rdf:resource="http://b2evolution.net/?v=2.4.2"/>
		<ttl>60</ttl>
				<item>
			<title>In response to: The ISBN as SKU</title>
			<pubDate>Sun, 15 Jun 2008 14:31:15 +0000</pubDate>
			<dc:creator>Adam Hodgkin [Visitor]</dc:creator>
			<guid isPermaLink="false">c54386@http://blogs.lib.berkeley.edu/</guid>
			<description>Genuinely puzzled about one point. I always thought that the main point of the ISBN system was to provide publishers/distirbutors/booksellers with a consistent way of assigning SKU's. So what do you mean that the ISBN is *becoming* an SKU, isnt this what it has always been?</description>
			<content:encoded><![CDATA[Genuinely puzzled about one point. I always thought that the main point of the ISBN system was to provide publishers/distirbutors/booksellers with a consistent way of assigning SKU's. So what do you mean that the ISBN is *becoming* an SKU, isnt this what it has always been?]]></content:encoded>
			<link>http://blogs.lib.berkeley.edu/shimenawa.php/2008/06/13/the_isbn_as_sku#c54386</link>
		</item>
				<item>
			<title>In response to: The ISBN as SKU</title>
			<pubDate>Fri, 13 Jun 2008 17:18:49 +0000</pubDate>
			<dc:creator>bowerbird [Visitor]</dc:creator>
			<guid isPermaLink="false">c54375@http://blogs.lib.berkeley.edu/</guid>
			<description>customers will not&lt;br /&gt;
buy this nonsense...&lt;br /&gt;
&lt;br /&gt;
or even tolerate it.&lt;br /&gt;
&lt;br /&gt;
publishers are just&lt;br /&gt;
asking for napster.&lt;br /&gt;
&lt;br /&gt;
-bowerbird&lt;br /&gt;
</description>
			<content:encoded><![CDATA[customers will not<br />
buy this nonsense...<br />
<br />
or even tolerate it.<br />
<br />
publishers are just<br />
asking for napster.<br />
<br />
-bowerbird<br />
]]></content:encoded>
			<link>http://blogs.lib.berkeley.edu/shimenawa.php/2008/06/13/the_isbn_as_sku#c54375</link>
		</item>
				<item>
			<title>In response to: The ISBN as SKU</title>
			<pubDate>Fri, 13 Jun 2008 15:09:59 +0000</pubDate>
			<dc:creator>Personanondata [Visitor]</dc:creator>
			<guid isPermaLink="false">c54373@http://blogs.lib.berkeley.edu/</guid>
			<description>(Firstly it was a little freaky hearing someone else's voice read your post - interesting app non the less).&lt;br /&gt;
&lt;br /&gt;
A number of years ago Michael Healy and I were involved in the revision of the ISBN standard.  No other point garnered more emotion than the requirement that each version of a title p or e have its own ISBN.  Both Michael and I (and all of the people on the administration side of ISBN) felt this was necessary to maintain the integrity of the system and accord the same treatment to varying versions of an ebook as we would to a large print or paper version of a print book.  Some publishers didn't see this view; rather they saw the 'administrative' burden of applying many multiple ISBNs to a title as more than they could cope with.&lt;br /&gt;
&lt;br /&gt;
For me (and I think Michael H) the issue was more obvious.  If different versions of an e-book title were not given ISBN's by a publisher then entities in the supply chain would apply them for them.  At Bowker we saw this happen in multiple instances.  Why a publisher would allow a retailer or wholesaler to mess with their bib data made/makes no sense to me.  The Publisher should manage and administer this information and allowing others to apply their own ISBNs (or SKUs) is not in the publisher's interest.  What happens is that each supply chain entity applies their own number and this just increases confusion and inefficiency.  If publishers maintain the veracity of the standard then I don't think it will be difficult to identify specific formats of books and the channel in which they were sold.&lt;br /&gt;
</description>
			<content:encoded><![CDATA[(Firstly it was a little freaky hearing someone else's voice read your post - interesting app non the less).<br />
<br />
A number of years ago Michael Healy and I were involved in the revision of the ISBN standard.  No other point garnered more emotion than the requirement that each version of a title p or e have its own ISBN.  Both Michael and I (and all of the people on the administration side of ISBN) felt this was necessary to maintain the integrity of the system and accord the same treatment to varying versions of an ebook as we would to a large print or paper version of a print book.  Some publishers didn't see this view; rather they saw the 'administrative' burden of applying many multiple ISBNs to a title as more than they could cope with.<br />
<br />
For me (and I think Michael H) the issue was more obvious.  If different versions of an e-book title were not given ISBN's by a publisher then entities in the supply chain would apply them for them.  At Bowker we saw this happen in multiple instances.  Why a publisher would allow a retailer or wholesaler to mess with their bib data made/makes no sense to me.  The Publisher should manage and administer this information and allowing others to apply their own ISBNs (or SKUs) is not in the publisher's interest.  What happens is that each supply chain entity applies their own number and this just increases confusion and inefficiency.  If publishers maintain the veracity of the standard then I don't think it will be difficult to identify specific formats of books and the channel in which they were sold.<br />
]]></content:encoded>
			<link>http://blogs.lib.berkeley.edu/shimenawa.php/2008/06/13/the_isbn_as_sku#c54373</link>
		</item>
			</channel>
</rss>
