<?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: A proto bill of ebook management rights</title>
	<atom:link href="http://peterbrantley.com/a-proto-bill-of-ebook-management-rights-221/feed" rel="self" type="application/rss+xml" />
	<link>http://peterbrantley.com/a-proto-bill-of-ebook-management-rights-221</link>
	<description>Peter Brantley's thoughts and speculations</description>
	<lastBuildDate>Wed, 22 Sep 2010 00:21:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: bowerbird</title>
		<link>http://peterbrantley.com/a-proto-bill-of-ebook-management-rights-221/comment-page-1#comment-231</link>
		<dc:creator>bowerbird</dc:creator>
		<pubDate>Wed, 25 Aug 2010 17:24:46 +0000</pubDate>
		<guid isPermaLink="false">http://peterbrantley.com/?p=221#comment-231</guid>
		<description>every word of every book ever published should be accessible
at any time by every person on the entire surface of the earth.

or else there will be a revolution.  greedy capitalists beware...

-bowerbird</description>
		<content:encoded><![CDATA[<p>every word of every book ever published should be accessible<br />
at any time by every person on the entire surface of the earth.</p>
<p>or else there will be a revolution.  greedy capitalists beware&#8230;</p>
<p>-bowerbird</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Mark Ockerbloom</title>
		<link>http://peterbrantley.com/a-proto-bill-of-ebook-management-rights-221/comment-page-1#comment-123</link>
		<dc:creator>John Mark Ockerbloom</dc:creator>
		<pubDate>Wed, 17 Mar 2010 13:09:22 +0000</pubDate>
		<guid isPermaLink="false">http://peterbrantley.com/?p=221#comment-123</guid>
		<description>It&#039;s an appealing list, though I haven&#039;t really thought much about &quot;cloud&quot;-based services and their interaction with these principles.  Personally, I think I&#039;d prefer personal, local management of my own ebookshelves, with the &quot;cloud&quot; only being used as a backup, transport, and transaction mechanism.  There&#039;s a certain tradeoff of convenience for privacy in doing that, but I think I&#039;d prefer that.

There&#039;s one other tension I *have* thought about some, that&#039;s worth thinking out, and that&#039;s the tension between lack of DRM (in the sense of technical restrictions) and the secondary markets that arise under a robust right of first sale.  In a nutshell, the problem is that unscrupulous sellers can &quot;sell&quot; the same DRM-free ebook any number of times, instead of deleting it after sale like they&#039;re supposed to, and in the largely anonymized marketplace of the web, even a few such unscrupulous sellers can push out the honest ones by undercutting the prevailing &quot;honest&quot; price.

If your marketplace mostly consists of honest people, though, as I believe the book market does, there are ways to deal with this problem.  One is with softer &quot;social&quot; DRM, such as electronic bookplates that don&#039;t technically prevent you from doing what you want with the books, but that contain data helping certify that your copy is from a genuine sale, and that you have rights to it.  You can have trusted brokers to help you verify the certification, and update bookplate data appropriately when you sell the book to someone.  Honest customers will deal with trusted bookplate services when making ebook transactions.

Making such a system also protect reader privacy is more of a challenge, but one that&#039;s addressable as well.   Some of the CS
research on &quot;digital cash&quot; (which is also designed to support
transactional privacy, while at the same time keeping a hard limit on certified copies) may help with this problem.</description>
		<content:encoded><![CDATA[<p>It&#8217;s an appealing list, though I haven&#8217;t really thought much about &#8220;cloud&#8221;-based services and their interaction with these principles.  Personally, I think I&#8217;d prefer personal, local management of my own ebookshelves, with the &#8220;cloud&#8221; only being used as a backup, transport, and transaction mechanism.  There&#8217;s a certain tradeoff of convenience for privacy in doing that, but I think I&#8217;d prefer that.</p>
<p>There&#8217;s one other tension I *have* thought about some, that&#8217;s worth thinking out, and that&#8217;s the tension between lack of DRM (in the sense of technical restrictions) and the secondary markets that arise under a robust right of first sale.  In a nutshell, the problem is that unscrupulous sellers can &#8220;sell&#8221; the same DRM-free ebook any number of times, instead of deleting it after sale like they&#8217;re supposed to, and in the largely anonymized marketplace of the web, even a few such unscrupulous sellers can push out the honest ones by undercutting the prevailing &#8220;honest&#8221; price.</p>
<p>If your marketplace mostly consists of honest people, though, as I believe the book market does, there are ways to deal with this problem.  One is with softer &#8220;social&#8221; DRM, such as electronic bookplates that don&#8217;t technically prevent you from doing what you want with the books, but that contain data helping certify that your copy is from a genuine sale, and that you have rights to it.  You can have trusted brokers to help you verify the certification, and update bookplate data appropriately when you sell the book to someone.  Honest customers will deal with trusted bookplate services when making ebook transactions.</p>
<p>Making such a system also protect reader privacy is more of a challenge, but one that&#8217;s addressable as well.   Some of the CS<br />
research on &#8220;digital cash&#8221; (which is also designed to support<br />
transactional privacy, while at the same time keeping a hard limit on certified copies) may help with this problem.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

