<?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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Google Book Search Privacy, Orphan Works, and Monopoly</title>
	<atom:link href="http://dltj.org/article/gbs-chronicle-highered/feed/" rel="self" type="application/rss+xml" />
	<link>http://dltj.org/article/gbs-chronicle-highered/</link>
	<description>We&#039;re Disrupted, We&#039;re Librarians, and We&#039;re Not Going to Take It Anymore</description>
	<lastBuildDate>Wed, 17 Mar 2010 20:21:17 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Google Book Settlement Link Dump Awesomeness at pureinformation.org</title>
		<link>http://dltj.org/article/gbs-chronicle-highered/comment-page-1/#comment-36903</link>
		<dc:creator>Google Book Settlement Link Dump Awesomeness at pureinformation.org</dc:creator>
		<pubDate>Tue, 30 Jun 2009 17:18:30 +0000</pubDate>
		<guid isPermaLink="false">http://dltj.org/?p=1100#comment-36903</guid>
		<description>[...] Disruptive Library Technology Jester: Google Book Search Privacy, Orphan Works, Monopoly [...]</description>
		<content:encoded><![CDATA[<p>[...] Disruptive Library Technology Jester: Google Book Search Privacy, Orphan Works, Monopoly [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the Jester</title>
		<link>http://dltj.org/article/gbs-chronicle-highered/comment-page-1/#comment-36856</link>
		<dc:creator>the Jester</dc:creator>
		<pubDate>Mon, 29 Jun 2009 13:44:38 +0000</pubDate>
		<guid isPermaLink="false">http://dltj.org/?p=1100#comment-36856</guid>
		<description>Agreed -- it should be a user&#039;s informed choice.  I think the point that could be argued is what the default is (collecting versus not collecting).  It probably also represents some tricky choices in designing the user interface in a way that makes sense, but Google already has a track record in this with the &lt;a href=&quot;http://www.google.com/support/accounts/bin/topic.py?topic=14148&amp;hl=en&quot; rel=&quot;nofollow&quot;&gt;web search history&lt;/a&gt; service.</description>
		<content:encoded><![CDATA[<p>Agreed &#8212; it should be a user&#8217;s informed choice.  I think the point that could be argued is what the default is (collecting versus not collecting).  It probably also represents some tricky choices in designing the user interface in a way that makes sense, but Google already has a track record in this with the <a href="http://www.google.com/support/accounts/bin/topic.py?topic=14148&amp;hl=en" rel="nofollow">web search history</a> service.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Murphy</title>
		<link>http://dltj.org/article/gbs-chronicle-highered/comment-page-1/#comment-36855</link>
		<dc:creator>Joe Murphy</dc:creator>
		<pubDate>Mon, 29 Jun 2009 13:17:19 +0000</pubDate>
		<guid isPermaLink="false">http://dltj.org/?p=1100#comment-36855</guid>
		<description>It occurs to me that very popular sites like LibraryThing, GoodReads, and (arguably) Amazon couldn&#039;t exist if users didn&#039;t see the value in allowing access to their reading history. It seems to me that the right answer isn&#039;t for Google to make the privacy decision one way or another, but to decide to put it in the hands of the user.

Of course, there are a lot of preconditions for that to work right, like anonymizing/discarding data about browsing which isn&#039;t linked to a Google account, clear policies, interface issues...</description>
		<content:encoded><![CDATA[<p>It occurs to me that very popular sites like LibraryThing, GoodReads, and (arguably) Amazon couldn&#8217;t exist if users didn&#8217;t see the value in allowing access to their reading history. It seems to me that the right answer isn&#8217;t for Google to make the privacy decision one way or another, but to decide to put it in the hands of the user.</p>
<p>Of course, there are a lot of preconditions for that to work right, like anonymizing/discarding data about browsing which isn&#8217;t linked to a Google account, clear policies, interface issues&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
