<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (jschneider)</title>
    <link>https://pinboard.in/u:jschneider/public/</link>
    <description>recent bookmarks from jschneider</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://chronicle.com/article/Google-s-Court-Victory-Is/233940?cid=at&amp;elq=ab85be13e8664678ba02ce75646209a1&amp;elqCampaignId=1706&amp;elqaid=6698&amp;elqat=1&amp;elqTrackId=4f32ed6302f34c76b44c16f3cd51492f"/>
	<rdf:li rdf:resource="http://xdl.drexelmed.edu/viewer.php?object_id=1127&amp;selected_segment=107&amp;t=womanmd"/>
	<rdf:li rdf:resource="http://www.slate.com/blogs/future_tense/2013/11/14/google_books_lawsuit_ruling_a_win_for_fair_use_or_rich_tech_firms_with_good.html"/>
	<rdf:li rdf:resource="http://www.reuters.com/article/2013/11/14/us-google-books-idUSBRE9AD0TT20131114"/>
	<rdf:li rdf:resource="http://chronicle.com/blogs/conversation/2013/07/22/how-google-rediscovered-the-19th-century/"/>
	<rdf:li rdf:resource="http://www.davidmckenzie.info/musings/2012/11/23/clio-3-short-tutorial/"/>
	<rdf:li rdf:resource="http://theartofgooglebooks.tumblr.com/post/27651378574/paul-gooding-of-university-college-london-talks"/>
	<rdf:li rdf:resource="http://winedarksea.org/?p=1501"/>
	<rdf:li rdf:resource="http://books.google.com/googlebooks/error.html"/>
	<rdf:li rdf:resource="http://kcoyle.blogspot.com/2012/01/google-book-search-redux.html"/>
	<rdf:li rdf:resource="http://dl.acm.org/citation.cfm?doid=2018396.2018408"/>
	<rdf:li rdf:resource="http://books.google.com/support/bin/answer.py?hl=en&amp;answer=1062968"/>
	<rdf:li rdf:resource="http://peterbrantley.com/gbs-settle-or-litigate-340"/>
	<rdf:li rdf:resource="http://www.nybooks.com/articles/archives/2009/feb/12/google-the-future-of-books/?pagination=false"/>
	<rdf:li rdf:resource="http://www.nybooks.com/articles/archives/2009/feb/12/google-the-future-of-books/"/>
	<rdf:li rdf:resource="http://kcoyle.blogspot.com/2011/03/judge-chin-rejects-aapgoogle-settlement.html"/>
	<rdf:li rdf:resource="http://beingnumero.us/blog/2011/07/digital-humanities-2011-and-the-elephant-in-the-tent/"/>
	<rdf:li rdf:resource="http://ryantrauman.com/blog/2010/10/05/trembling-before-the-google-books-project-a-response-to-joe-harris/"/>
	<rdf:li rdf:resource="http://peterbrantley.com/speculating-on-the-next-gbs-settlement-323"/>
	<rdf:li rdf:resource="http://bibwild.wordpress.com/2011/05/12/new-google-books-api/"/>
	<rdf:li rdf:resource="http://www.andrewnormanwilson.com/portfolios/70411-workers-leaving-the-googleplex"/>
	<rdf:li rdf:resource="http://everybodyslibraries.com/2011/04/09/opt-in-for-open-access/"/>
	<rdf:li rdf:resource="http://htlit.com/archives/March2011/GoogleUnsettlement.html"/>
	<rdf:li rdf:resource="http://go-to-hellman.blogspot.com/2011/02/judge-denny-chin-says-hes-working-on-it.html"/>
	<rdf:li rdf:resource="http://freerangelibrarian.com/2011/02/12/trends/?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+freerangelibrarian+%28Free+Range+Librarian%29"/>
	<rdf:li rdf:resource="http://paulcourant.net/2011/02/16/benefits-costs-and-googleization-a-comment-on-siva-vaidhaynathan/"/>
	<rdf:li rdf:resource="http://chronicle.com/article/Counting-on-Google-Books/125735/"/>
	<rdf:li rdf:resource="http://householdopera.typepad.com/household_opera/2011/01/fun-with-google-books-ngram-viewer.html"/>
	<rdf:li rdf:resource="http://books.google.com/support/bin/answer.py?hl=en&amp;answer=179839"/>
	<rdf:li rdf:resource="http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1387782"/>
	<rdf:li rdf:resource="http://ngrams.googlelabs.com/"/>
	<rdf:li rdf:resource="http://www.nytimes.com/2010/12/17/books/17words.html?_r=1"/>
	<rdf:li rdf:resource="http://bibwild.wordpress.com/2010/12/16/google-research-database-from-gbs/"/>
	<rdf:li rdf:resource="http://booktwo.org/notebook/the-beauty-of-engineers/"/>
	<rdf:li rdf:resource="http://scholarlykitchen.sspnet.org/2010/12/07/privacy-google-and-the-reading-public/?utm_source=feedburner&amp;utm_medium=twitter&amp;utm_campaign=Feed:+ScholarlyKitchen+(The+Scholarly+Kitchen)&amp;utm_content=Twitter"/>
	<rdf:li rdf:resource="http://peterbrantley.com/eye-to-eye-228"/>
	<rdf:li rdf:resource="http://irepeat.wordpress.com/2010/07/14/language-change-and-ir/"/>
	<rdf:li rdf:resource="http://bibwild.wordpress.com/2010/07/12/deals/"/>
	<rdf:li rdf:resource="http://kcoyle.blogspot.com/2010/07/catching-up-oclc-gbs-lod.html"/>
	<rdf:li rdf:resource="http://everybodyslibraries.com/2010/06/20/how-we-talk-about-the-president-a-quick-exploration-in-google-books/"/>
	<rdf:li rdf:resource="http://code.google.com/apis/books/docs/preview-wizard.html"/>
	<rdf:li rdf:resource="http://chronicle.com/article/Crunching-Words-in-Great/65777/"/>
	<rdf:li rdf:resource="http://www.cdlib.org/cdlinfo/2010/02/16/hurtling-toward-the-finish-line-should-the-google-books-settlement-be-approved/"/>
	<rdf:li rdf:resource="http://kcoyle.blogspot.com/2010/02/doj-bridge-too-far.html"/>
	<rdf:li rdf:resource="http://kcoyle.blogspot.com/2010/02/trust-and-settlement.html"/>
	<rdf:li rdf:resource="http://go-to-hellman.blogspot.com/2010/03/business-idea-number-3-gluejar-book.html"/>
	<rdf:li rdf:resource="http://www.dlib.org/dlib/september05/lavoie/09lavoie.html#7"/>
	<rdf:li rdf:resource="http://scitedaily.com/googles-book-scanning-technology-revealed/"/>
	<rdf:li rdf:resource="http://go-to-hellman.blogspot.com/2010/02/copyright-safe-full-text-indexing-of.html"/>
	<rdf:li rdf:resource="http://go-to-hellman.blogspot.com/2010/01/google-exposes-book-metadata-privates.html"/>
	<rdf:li rdf:resource="http://userscripts.org/scripts/show/37933"/>
	<rdf:li rdf:resource="http://kcoyle.blogspot.com/2009/09/gbs-and-bad-metadata.html"/>
	<rdf:li rdf:resource="http://kcoyle.blogspot.com/2009/08/academic-publishing-as-percentage-of.html"/>
	<rdf:li rdf:resource="http://www.nybooks.com/articles/23565"/>
	<rdf:li rdf:resource="http://www.cdt.org/policy/cdt-files-brief-urging-privacy-safeguards-google-books"/>
	<rdf:li rdf:resource="http://www.cdt.org/blogs/david-sohn/google-books-congress-and-orphan-works"/>
	<rdf:li rdf:resource="http://bibwild.wordpress.com/2009/12/02/improved-google-books-search-within-book-interface/"/>
	<rdf:li rdf:resource="http://www.arl.org/bm~doc/guide_for_the_perplexed_part3_final.pdf"/>
	<rdf:li rdf:resource="http://blogs.talis.com/panlibus/archives/2009/11/survival-with-the-fittest-the-story-of-a-google-library-partner.php"/>
	<rdf:li rdf:resource="http://kcoyle.blogspot.com/2009/11/1923.html"/>
	<rdf:li rdf:resource="http://dltj.org/article/revised-gbs-settlement/"/>
	<rdf:li rdf:resource="http://kcoyle.blogspot.com/2009/10/objecting-to-gbsaapag-settlement.html"/>
	<rdf:li rdf:resource="http://kcoyle.blogspot.com/2009/11/amended-googleaap-settlement.html"/>
	<rdf:li rdf:resource="http://exacteditions.blogspot.com/2009/10/google-is-going-for-it.html"/>
	<rdf:li rdf:resource="http://kcoyle.blogspot.com/2009/11/googled.html"/>
	<rdf:li rdf:resource="http://go-to-hellman.blogspot.com/2009/10/copyless-crowdscanning-how-to-legally.html"/>
	<rdf:li rdf:resource="http://go-to-hellman.blogspot.com/2009/10/judge-chin-confronts-scanning-problem.html"/>
	<rdf:li rdf:resource="http://www.npr.org/blogs/library/2009/04/the_granting_of_patent_7508978.html"/>
	<rdf:li rdf:resource="http://www.bitsbook.com/2009/10/do-it-yourself-book-scanning/"/>
	<rdf:li rdf:resource="http://www.themillions.com/2009/10/bringing-book-scanning-home.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://chronicle.com/article/Google-s-Court-Victory-Is/233940?cid=at&amp;elq=ab85be13e8664678ba02ce75646209a1&amp;elqCampaignId=1706&amp;elqaid=6698&amp;elqat=1&amp;elqTrackId=4f32ed6302f34c76b44c16f3cd51492f">
    <title>Google’s Court Victory Is Good for Scholarly Authors. Here’s Why. - The Chronicle of Higher Education</title>
    <dc:date>2015-10-29T17:42:38+00:00</dc:date>
    <link>http://chronicle.com/article/Google-s-Court-Victory-Is/233940?cid=at&amp;elq=ab85be13e8664678ba02ce75646209a1&amp;elqCampaignId=1706&amp;elqaid=6698&amp;elqat=1&amp;elqTrackId=4f32ed6302f34c76b44c16f3cd51492f</link>
    <dc:creator>jschneider</dc:creator><dc:subject>Chronicle GoogleBooks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:9ee79efe2c36/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Chronicle"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:GoogleBooks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://xdl.drexelmed.edu/viewer.php?object_id=1127&amp;selected_segment=107&amp;t=womanmd">
    <title>Women Physicians: 1850s - 1970s: Jungle days: Being the experiences of an American woman doctor in India, Page 86</title>
    <dc:date>2014-03-31T13:56:46+00:00</dc:date>
    <link>http://xdl.drexelmed.edu/viewer.php?object_id=1127&amp;selected_segment=107&amp;t=womanmd</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[OCR examples: fort Dora Chatterjee X]]></description>
<dc:subject>OCR examples GoogleBooks GoogleScholar</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:8acfec768824/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:OCR"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:examples"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:GoogleBooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:GoogleScholar"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.slate.com/blogs/future_tense/2013/11/14/google_books_lawsuit_ruling_a_win_for_fair_use_or_rich_tech_firms_with_good.html">
    <title>Google Books lawsuit: Ruling a win for fair use, or rich tech firms with good lawyers?</title>
    <dc:date>2013-11-15T13:07:34+00:00</dc:date>
    <link>http://www.slate.com/blogs/future_tense/2013/11/14/google_books_lawsuit_ruling_a_win_for_fair_use_or_rich_tech_firms_with_good.html</link>
    <dc:creator>jschneider</dc:creator><dc:subject>GoogleBooks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:d684594a6b72/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:GoogleBooks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.reuters.com/article/2013/11/14/us-google-books-idUSBRE9AD0TT20131114">
    <title>Google defeats authors in U.S. book-scanning lawsuit | Reuters</title>
    <dc:date>2013-11-14T18:46:19+00:00</dc:date>
    <link>http://www.reuters.com/article/2013/11/14/us-google-books-idUSBRE9AD0TT20131114</link>
    <dc:creator>jschneider</dc:creator><dc:subject>GoogleBooks copyright</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:cdff389654c7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:GoogleBooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:copyright"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://chronicle.com/blogs/conversation/2013/07/22/how-google-rediscovered-the-19th-century/">
    <title>How Google Rediscovered the 19th Century</title>
    <dc:date>2013-07-30T17:16:32+00:00</dc:date>
    <link>http://chronicle.com/blogs/conversation/2013/07/22/how-google-rediscovered-the-19th-century/</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[via https://twitter.com/JMarkOckerbloom/status/359705908688863232?refsrc=email "At the end of that year, I left my sabbatical office carrying a computer filled with the virtual books that are rapidly becoming the bread and butter of teaching and scholarship.""This rediscovery of the 19th century as an open-source reading experience is accompanied by a subtle appreciation of the era’s intellectual merits. Consider the quantity of material—obscure novels, local histories, antique catalogs, minor journals, a sea of biographies, and those vast and terrifyingly erudite bibliographies that were a specialty of that age of scholarship.

Work that fails to enter a canon—literary, historical, or otherwise—tends to languish on the dustier shelves of college libraries. Digitization allows a new generation of scholars to look at them with fresh regard. This represents a significant change in the way we think about scholarship. Google Books is a kind of Victorian portal that takes me into a mare magnum of out-of-print authors, many of whom helped launch disciplines. Or who wrote essays, novels, and histories that did not transcend their time. Or who anonymously produced the paperwork of emerging bureaucracies, organizations, and businesses that, because printed, has been scanned and, because scanned, is now available.

I am not a scholar of the 19th century but have found its digitization to be one of the most fascinating new resource for understanding the centuries that precede it.

It is not by chance that the 19th century gave birth to projects such as the Oxford English Dictionary. The OED is the tip of an iceberg of genteel scholars, male and female, who had the time and resources to dig through vast mounds of material and make something of it. Those researchers lived in closer chronological proximity to their subjects than we do; they often worked amid the dimly lit bookshelves and attics of private homes. As a result, their experience of a historical subject captures a sense of intimacy that might otherwise be lost.""We now have access to one of the most valuable tools of archival and bibliographic research: the 19th-century catalog. It often contains precious annotations of the process by which living artifacts become a historical record—the quirky details that tend to be lost in modern information systems, which strip away the idiosyncrasies of personalized description in favor standardized data. In a way, the experience of using Google to access the 19th century has enriched our ability to work in the physical archives and libraries that many of us still consider to be the epicenter of scholarship. I am constantly moving between my Victorian online experience and the far richer evidence available at some brick-and-mortar libraries."]]></description>
<dc:subject>Google GoogleBooks digitalarchives archives Chronicle metadata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:199beaf18fed/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:GoogleBooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:digitalarchives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:archives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Chronicle"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:metadata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.davidmckenzie.info/musings/2012/11/23/clio-3-short-tutorial/">
    <title>Short tutorial: Cleaning up a Google Book for text mining</title>
    <dc:date>2012-11-29T13:31:53+00:00</dc:date>
    <link>http://www.davidmckenzie.info/musings/2012/11/23/clio-3-short-tutorial/</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[via https://twitter.com/dpmckenzie/status/273261295535550464]]></description>
<dc:subject>digitalhumanities GoogleBooks textmining</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:a27da676a235/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:GoogleBooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:textmining"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://theartofgooglebooks.tumblr.com/post/27651378574/paul-gooding-of-university-college-london-talks">
    <title>The Art of Google Books</title>
    <dc:date>2012-11-14T00:29:33+00:00</dc:date>
    <link>http://theartofgooglebooks.tumblr.com/post/27651378574/paul-gooding-of-university-college-london-talks</link>
    <dc:creator>jschneider</dc:creator><dc:subject>googlebooks awesome</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:2881e7ac6626/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:awesome"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://winedarksea.org/?p=1501">
    <title>Google Books: Ratio of Inked Space to Blank Space</title>
    <dc:date>2012-05-06T04:51:04+00:00</dc:date>
    <link>http://winedarksea.org/?p=1501</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["What if Google Books were to publish the ratio of inked to non-inked space for all of the items it has scanned? We could then see how writing of different types, for example, plays or prose fiction, move into larger print formats such as the Folio."]]></description>
<dc:subject>googlebooks page-image ink print-formats</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:6831204fd3d6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:page-image"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:ink"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:print-formats"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://books.google.com/googlebooks/error.html">
    <title>Google Books</title>
    <dc:date>2012-03-12T13:57:42+00:00</dc:date>
    <link>http://books.google.com/googlebooks/error.html</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[via http://twitter.com/ryancordell/status/179204050410147840]]></description>
<dc:subject>failwhale googlebooks memes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:781fc0f3e346/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:failwhale"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:memes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kcoyle.blogspot.com/2012/01/google-book-search-redux.html">
    <title>Google Book Search Redux</title>
    <dc:date>2012-01-25T22:55:29+00:00</dc:date>
    <link>http://kcoyle.blogspot.com/2012/01/google-book-search-redux.html</link>
    <dc:creator>jschneider</dc:creator><dc:subject>googlebooks fairuse copyright digitization intellectual-property</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:f454713b53c4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:fairuse"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:copyright"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:digitization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:intellectual-property"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dl.acm.org/citation.cfm?doid=2018396.2018408">
    <title>Why the Google book settlement failed</title>
    <dc:date>2011-12-12T13:16:23+00:00</dc:date>
    <link>http://dl.acm.org/citation.cfm?doid=2018396.2018408</link>
    <dc:creator>jschneider</dc:creator><dc:subject>googlebooks ACM fairuse orphanworks privacy</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:31e87aed9f16/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:ACM"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:fairuse"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:orphanworks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:privacy"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://books.google.com/support/bin/answer.py?hl=en&amp;answer=1062968">
    <title>User Policies - Books Help</title>
    <dc:date>2011-07-25T13:11:17+00:00</dc:date>
    <link>http://books.google.com/support/bin/answer.py?hl=en&amp;answer=1062968</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["You may not lend or co-own any of your Google eBooks purchases with another person."]]></description>
<dc:subject>ebooks googlebooks sharing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:f6abd8521d1f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:ebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:sharing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://peterbrantley.com/gbs-settle-or-litigate-340">
    <title>Shimenawa » Blog Archive » GBS: Settle or Litigate?</title>
    <dc:date>2011-07-24T17:46:23+00:00</dc:date>
    <link>http://peterbrantley.com/gbs-settle-or-litigate-340</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["As James Grimmelmann noted at The Laboratorium, Chin also suggested that if settlement talks do not reach fruition and there was a return to litigation, the path would be clearly lit:
Judge Chin suggested that he saw the case, if it were to be litigated, in terms of fairly straightforward cross motions for summary judgment on whether snippet display is a fair use.
""It seems to me that the only benefit Google obtains from a new settlement is clean hands over the past claims of infringement for digitization, but if the only operation they conduct is snippet-view, there is not necessarily a requirement for all-party approval. One could well argue from Google’s perspective that they actually don’t want to establish a precedent for asking permission for a broad class of activities that have been held as Fair Use when they have been litigated. Regardless, the barrier of final class certification still resides in the settlement house."]]></description>
<dc:subject>googlebooks copyright fairuse</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:004d9bf6cf16/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:copyright"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:fairuse"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.nybooks.com/articles/archives/2009/feb/12/google-the-future-of-books/?pagination=false">
    <title>Google &amp; the Future of Books by Robert Darnton | The New York Review of Books</title>
    <dc:date>2011-07-20T15:17:51+00:00</dc:date>
    <link>http://www.nybooks.com/articles/archives/2009/feb/12/google-the-future-of-books/?pagination=false</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["I especially enjoy the exchange of letters between Jefferson and Madison. They discussed everything, notably the American Constitution, which Madison was helping to write in Philadelphia while Jefferson was representing the new republic in Paris. They often wrote about books, for Jefferson loved to haunt the bookshops in the capital of the Republic of Letters, and he frequently bought books for his friend. The purchases included Diderot’s Encyclopédie, which Jefferson thought that he had got at a bargain price, although he had mistaken a reprint for a first edition.""If we turned the sociology of knowledge onto the present—as Bourdieu himself did—we would see that we live in a world designed by Mickey Mouse, red in tooth and claw.""But we, too, cannot sit on the sidelines, as if the market forces can be trusted to operate for the public good."]]></description>
<dc:subject>google Robert Darnton googlebooks sociology-of-knowledge copyright publicdomain</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:06fe0f4eba7a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Robert"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Darnton"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:sociology-of-knowledge"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:copyright"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:publicdomain"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.nybooks.com/articles/archives/2009/feb/12/google-the-future-of-books/">
    <title>Google &amp; the Future of Books by Robert Darnton | The New York Review of Books</title>
    <dc:date>2011-07-20T15:17:22+00:00</dc:date>
    <link>http://www.nybooks.com/articles/archives/2009/feb/12/google-the-future-of-books/</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[""]]></description>
<dc:subject>google Robert Darnton ny-review-of-books googlebooks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:6b12faab851a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Robert"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Darnton"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:ny-review-of-books"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kcoyle.blogspot.com/2011/03/judge-chin-rejects-aapgoogle-settlement.html">
    <title>Coyle's InFormation: Judge Chin rejects AAP/Google settlement</title>
    <dc:date>2011-07-18T16:58:25+00:00</dc:date>
    <link>http://kcoyle.blogspot.com/2011/03/judge-chin-rejects-aapgoogle-settlement.html</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[""]]></description>
<dc:subject>googlebooks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:14b5242de474/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://beingnumero.us/blog/2011/07/digital-humanities-2011-and-the-elephant-in-the-tent/">
    <title>» Digital Humanities 2011 and the elephant in the tent Being Numerous</title>
    <dc:date>2011-07-16T12:01:40+00:00</dc:date>
    <link>http://beingnumero.us/blog/2011/07/digital-humanities-2011-and-the-elephant-in-the-tent/</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[see also http://jodischneider.com/blog/2011/07/16/qotd-move-the-computation-to-the-data-the-future-of-nonconsumptive-research-with-google-books/]]></description>
<dc:subject>digitalhumanities googlebooks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:859988d76ec7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ryantrauman.com/blog/2010/10/05/trembling-before-the-google-books-project-a-response-to-joe-harris/">
    <title>Trembling Before the Google Books Project, a Response to Joe Harris</title>
    <dc:date>2011-07-15T00:55:06+00:00</dc:date>
    <link>http://ryantrauman.com/blog/2010/10/05/trembling-before-the-google-books-project-a-response-to-joe-harris/</link>
    <dc:creator>jschneider</dc:creator><dc:subject>googlebooks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:d6dab1739c7f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://peterbrantley.com/speculating-on-the-next-gbs-settlement-323">
    <title>Shimenawa » Blog Archive » Speculating on the next GBS Settlement</title>
    <dc:date>2011-07-12T14:06:32+00:00</dc:date>
    <link>http://peterbrantley.com/speculating-on-the-next-gbs-settlement-323</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[""]]></description>
<dc:subject>googlebooks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:a81f1929e3a7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://bibwild.wordpress.com/2011/05/12/new-google-books-api/">
    <title>New Google Books API | Bibliographic Wilderness</title>
    <dc:date>2011-05-16T10:30:24+00:00</dc:date>
    <link>http://bibwild.wordpress.com/2011/05/12/new-google-books-api/</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[""]]></description>
<dc:subject>apis googlebooks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:0db135a44ad2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.andrewnormanwilson.com/portfolios/70411-workers-leaving-the-googleplex">
    <title>ANDREW NORMAN WILSON</title>
    <dc:date>2011-05-03T12:50:31+00:00</dc:date>
    <link>http://www.andrewnormanwilson.com/portfolios/70411-workers-leaving-the-googleplex</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["I then found out the chubby white man knew what I was doing because the first girl I had spoken to had followed the instructions on the back of her yellow badge – which is to call a certain manager if anyone asks about the work of the yellow badge class. "]]></description>
<dc:subject>class google labor politics googlebooks ScanOps</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:ef63d7336f06/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:class"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:labor"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:politics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:ScanOps"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://everybodyslibraries.com/2011/04/09/opt-in-for-open-access/">
    <title>Opt in for open access « Everybody's Libraries</title>
    <dc:date>2011-04-12T13:13:13+00:00</dc:date>
    <link>http://everybodyslibraries.com/2011/04/09/opt-in-for-open-access/</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[""]]></description>
<dc:subject>GoogleBooks openaccess orphan-works digital-libraries</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:516e65a27a39/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:GoogleBooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:openaccess"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:orphan-works"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:digital-libraries"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://htlit.com/archives/March2011/GoogleUnsettlement.html">
    <title>Google Unsettlement</title>
    <dc:date>2011-04-04T11:26:50+00:00</dc:date>
    <link>http://htlit.com/archives/March2011/GoogleUnsettlement.html</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[""]]></description>
<dc:subject>GoogleBooks opt-out</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:131d47b2c1ab/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:GoogleBooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:opt-out"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://go-to-hellman.blogspot.com/2011/02/judge-denny-chin-says-hes-working-on-it.html">
    <title>Go To Hellman: Judge Denny Chin Says He's Working On It</title>
    <dc:date>2011-02-28T13:31:05+00:00</dc:date>
    <link>http://go-to-hellman.blogspot.com/2011/02/judge-denny-chin-says-hes-working-on-it.html</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["The judge presiding over the trial, Denny Chin, was elevated to the Circuit Court of Appeals, but because of the shortage of judges on the district court (Judge Chin's District is down 9 judges) caused by the political stalemate in the US Senate, Judge Chin has been forced to keep most of his cases, including the Google case.""The case in which he ruled that Listerine was not as effective against gingivitis as flossing made him a hero with his dentist, and earned him the tabloid nickname of the "Listerine Judge". ""He did his Senior Thesis at Princeton on the "Old Ones" of Chinatown, the elderly Chinese. A photo of his grandfather was at the front of his thesis. His grandfather lived in a building of "railroad" apartments, each of which was occupied by an old man who had been separated from his family by the exclusion laws that had severely curtailed immigration from China to the United States. His grandfather had been able to go back to China only twice, once in the '20's when he got married, and then in the '30's, when Chin's father was born. Chin's Grandfather worked as a waiter in a Chinatown restaurant for many years, and like all the other men who lived in the railroad apartments, he would go to the post office every month and buy a money order to send home to his family in China. Chin's grandfather took the oath of citizenship in 1947, in the same court where his grandson would preside as a judge. Because his grandfather had become a citizen, and because immigration laws had been relaxed, Chin and his parents were allowed to come to the US in 1956 (Chin was only 2 years old)."]]></description>
<dc:subject>googlebooks China immigration</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:86aeba93477d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:China"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:immigration"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://freerangelibrarian.com/2011/02/12/trends/?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+freerangelibrarian+%28Free+Range+Librarian%29">
    <title>Free Range Librarian › Random Acts of Trendness</title>
    <dc:date>2011-02-21T19:41:46+00:00</dc:date>
    <link>http://freerangelibrarian.com/2011/02/12/trends/?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+freerangelibrarian+%28Free+Range+Librarian%29</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["Listening to her, I had that same “ah hah” moment I’ve had a few other times in my library career, like the first time I brought up Mosaic on my home computer and got the TCP-IP stack to work, and when a huge NASA image of Jupiter appeared on my screen I was so excited I had to leave the house and drive for an hour just to calm down. I haven’t shouted “squee” over repositories (not the same sex appeal), but as noted above, I’m getting ready for them.""Elsewhere people have commented on the surge in tablet use; Jason Griffey noted in a post-midwinter webinar that the Consumer Electronics Show featured over 40 tablets. The New York Times recently reported on the surge of e-readers by young adults. In addition to using actual data (“At HarperCollins, for example, e-books made up 25 percent of all young-adult sales in January, up from about 6 percent a year before”), this article was notable for not even attempting to debunk the trend in ebook readers, which assuredly would have happened ten or even three years ago.

My hunch, down the line (and I doubt this is a unique observation), is that we will all end up being our own personal networks; cellular speeds or other technologies will allow us self-contained connectivity. The person with an iPad with 3G is essentially a network unto herself."]]></description>
<dc:subject>streaming googlebooks kindle repositories reformatting weeding wifi tablets</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:f1f39450d092/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:streaming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:kindle"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:repositories"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:reformatting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:weeding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:wifi"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:tablets"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://paulcourant.net/2011/02/16/benefits-costs-and-googleization-a-comment-on-siva-vaidhaynathan/">
    <title>Benefits, Costs, and Googleization: A Comment on Siva Vaidhyanathan | Au Courant</title>
    <dc:date>2011-02-17T13:12:02+00:00</dc:date>
    <link>http://paulcourant.net/2011/02/16/benefits-costs-and-googleization-a-comment-on-siva-vaidhaynathan/</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[""]]></description>
<dc:subject>googlebooks digitization</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:e9bca0fb44c0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:digitization"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://chronicle.com/article/Counting-on-Google-Books/125735/">
    <title>Counting on Google Books - The Chronicle Review - The Chronicle of Higher Education</title>
    <dc:date>2011-01-12T01:23:26+00:00</dc:date>
    <link>http://chronicle.com/article/Counting-on-Google-Books/125735/</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[via http://householdopera.typepad.com/household_opera/2011/01/fun-with-google-books-ngram-viewer.html  "The English corpus alone contains some 360 billion words, a size that permits analyses on a scale that aren't possible with collections like the Corpus of Historical American English, at Brigham Young University, which tops out at a mere 410 million words.""That leaves out a lot, compared with what you can do with other corpora. As of now, for example, you can't ask for a list of the words that follow the adjective "traditional" for each decade from 1900 to 2000 in order of descending frequency, or restrict a search for "bronzino" to paragraphs that contain "fish" and don't contain "painting." Some of those capabilities will probably be available soon, though users won't be able to replicate many of the computationally heavy-duty exercises that the researchers report in the paper, and linguists won't really be happy until they can download the whole corpus and have their way with it.""And while the Harvard researchers have purged the research corpus of a large proportion of the metadata errors that have plagued Google Books, there are still a fair number of misdated works, and there's no way to restrict a query by genre or topic. You can ask the system to plot the trajectory "dear reader" in books published in Britain during the 19th century, but you can't limit the search to novels.""The more interesting exercises are also, in a way, the most problematic. In one exercise, the authors investigate the evolution of fame, as measured by the relative frequency of mentions of people's names. They began with the 740,000 people with entries in Wikipedia and sorted them by birth date, picking the 50 most frequently mentioned names from each birth year (so that the 1882 cohort contained Felix Frankfurter and Virginia Woolf, and so on). Next they plotted the median frequency of mention for each cohort over time and looked for historical tendencies. It turns out that people become famous more quickly and reach a greater maximum fame now than they did 100 years ago, but that their fame dies out more rapidly. You can take that result as a quantitative demonstration of the rise of what Leo Braudy called "disposable fame" in his book The Frenzy of Renown, which the authors cite. And the technique could be a powerful source of data for the burgeoning field of celebrity studies, as it's designated in the title of a new journal from Routledge.

But the method isn't up to distinguishing among the varieties of fame and eminence that Braudy and others have carved out. And there are obvious limits to equating fame with mere frequency of mention. At one point, for example, the authors observe that "'Galileo', 'Darwin', and 'Einstein' may be well-known scientists, but 'Freud' is more deeply ingrained in our collective subconscious." But it defies belief that Freud is vastly better known than Darwin among the authors of books in a corpus that was drawn from the collections of research libraries. We simply mention Freud more often. Maybe that's because we refer to Darwin only when we're talking about evolution, while we're apt to bring up Freud when we're talking about ourselves. Or maybe there's some other explanation. But the data don't wear their cultural significance on their sleeves; they need cultural historians to speak for them.""I have a friend, a gifted amateur musician and computer scientist, who was involved in electronic music in its early days. Inevitably, within a few years, the field was taken over by composers. That happened partly because new interfaces made the technology more accessible, but also because a command of the subject matter always trumps mere technical expertise. As my friend put it, "It's a lot easier to turn an artist into a geek than to turn a geek into an artist."

In the same way, we'll know that the program of quantitative corpus research is successful when the engineers have stepped back as the techniques are absorbed into the academy, sometimes as a method, sometimes just as a background of operating assumptions. That was the fate of 19th-century philology—the study of "La Vie des Mots" (The Life of Words) in the title of a book of the period by Arsène Darmesteter. Quantitative corpus studies are destined to play the same role, though they imply a different understanding of what the life of words is all about. We really don't even need a name like "culturomics," or any new name at all: this is just e-philology. (Or "the newer philology," since "the new philology" is taken.)""Whatever precedents yesterday's article in Science may establish for the humanities, the 12-author paper won't be one of them."]]></description>
<dc:subject>googlebooks linguistics digialhumanities metadata distant-reading</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:61ec2ccd8a78/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:linguistics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:digialhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:distant-reading"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://householdopera.typepad.com/household_opera/2011/01/fun-with-google-books-ngram-viewer.html">
    <title>Household Opera: Fun with Google Books Ngram Viewer</title>
    <dc:date>2011-01-12T01:20:08+00:00</dc:date>
    <link>http://householdopera.typepad.com/household_opera/2011/01/fun-with-google-books-ngram-viewer.html</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["Thanks to my background research on the commonplace book project, I already knew that "scrapbooking" (as we now call it) took off in the mid-19th century and eventually became a more popular pastime than the keeping of commonplace books; the graph suggests something of the rise of one format and the fall of the other. "]]></description>
<dc:subject>ngrams googlebooks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:a19b8ed2f2ca/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:ngrams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://books.google.com/support/bin/answer.py?hl=en&amp;answer=179839">
    <title>How Google eBooks works - Books Help</title>
    <dc:date>2011-01-05T07:35:30+00:00</dc:date>
    <link>http://books.google.com/support/bin/answer.py?hl=en&amp;answer=179839</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[""]]></description>
<dc:subject>googlebooks ebooks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:bd64c21174b9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:ebooks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1387782">
    <title>SSRN-Legally Speaking: The Dead Souls of the Google Booksearch Settlement by Pamela Samuelson</title>
    <dc:date>2011-01-02T03:23:53+00:00</dc:date>
    <link>http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1387782</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["Pamela Samuelson in her forthcoming ACM article on the settlement notes that "the settlement would, in effect, give Google the exclusive right to commercially exploit millions of orphan books."" via http://blog.librarylaw.com/librarylaw/2009/04/google-book-settlement-orphan-works-and-foreign-works.html]]></description>
<dc:subject>googlebooks copyright orphanworks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:9b258ed79c3b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:copyright"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:orphanworks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ngrams.googlelabs.com/">
    <title>Google Labs - Books Ngram Viewer</title>
    <dc:date>2010-12-16T22:08:05+00:00</dc:date>
    <link>http://ngrams.googlelabs.com/</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[""]]></description>
<dc:subject>ngrams googlebooks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:e60102f6534c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:ngrams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.nytimes.com/2010/12/17/books/17words.html?_r=1">
    <title>From Google and Harvard, a New Way to Analyze the Written Word - NYTimes.com</title>
    <dc:date>2010-12-16T22:07:24+00:00</dc:date>
    <link>http://www.nytimes.com/2010/12/17/books/17words.html?_r=1</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["So far, Google has scanned more than 11 percent of the entire corpus of published books, about 2 trillion words. The data analyzed in the Science article contains about 4 percent of the corpus."]]></description>
<dc:subject>nytimes googlebooks digitalhumanities language-evolution</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:f6160285d5e8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:nytimes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:language-evolution"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://bibwild.wordpress.com/2010/12/16/google-research-database-from-gbs/">
    <title>google research database from GBS « Bibliographic Wilderness</title>
    <dc:date>2010-12-16T22:04:29+00:00</dc:date>
    <link>http://bibwild.wordpress.com/2010/12/16/google-research-database-from-gbs/</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[""]]></description>
<dc:subject>googlebooks research copyright</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:299451750b86/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:copyright"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://booktwo.org/notebook/the-beauty-of-engineers/">
    <title>The beauty of engineers: Google Books.app | booktwo.org</title>
    <dc:date>2010-12-12T13:48:27+00:00</dc:date>
    <link>http://booktwo.org/notebook/the-beauty-of-engineers/</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[turn off 3D pageturns! :)]]></description>
<dc:subject>ebooks GoogleBooks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:ac632be32f1a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:ebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:GoogleBooks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://scholarlykitchen.sspnet.org/2010/12/07/privacy-google-and-the-reading-public/?utm_source=feedburner&amp;utm_medium=twitter&amp;utm_campaign=Feed:+ScholarlyKitchen+(The+Scholarly+Kitchen)&amp;utm_content=Twitter">
    <title>Privacy, Google, and the Reading Public « The Scholarly Kitchen</title>
    <dc:date>2010-12-08T20:25:22+00:00</dc:date>
    <link>http://scholarlykitchen.sspnet.org/2010/12/07/privacy-google-and-the-reading-public/?utm_source=feedburner&amp;utm_medium=twitter&amp;utm_campaign=Feed:+ScholarlyKitchen+(The+Scholarly+Kitchen)&amp;utm_content=Twitter</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["it’s one thing to use Gmail in the full knowledge that Google is going to examine the contents of your email and your calendar.  It’s another thing, for example, to access e-books and be unsure whether your online reading behavior is going to be examined in the same way.""Accessing the Internet, for any purpose, almost always requires much more personal disclosure — to your home access provider, your employer, your library, or whatever other entity is granting or selling you access.  To argue that the Google settlement should only be approved if it includes provisions that make use of the service as private as the use of printed books is, in practice, to argue that the settlement should not be passed."]]></description>
<dc:subject>advertising privacy Google GoogleBooks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:8772e1e130c8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:advertising"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:privacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:GoogleBooks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://peterbrantley.com/eye-to-eye-228">
    <title>Shimenawa » Blog Archive » Eye to eye: The Authors Guild, Random House, and GBS</title>
    <dc:date>2010-08-25T14:43:24+00:00</dc:date>
    <link>http://peterbrantley.com/eye-to-eye-228</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["One of the keystones of the settlement proposal is lodged in Attachment A (Author-Publisher Procedures), which attempts to clarify the digital rights issues that have brought authors and publishers so often to litigation or its brink. The proposal provides for a default bright line assignment of revenue from the exploitation of works included in the terms of the settlement. ""It is not too much to suggest that the conflict over ebook rights and royalties is one of the most outstanding irritants in the transition to digital publishing. It is an irritant that has drawn the Authors Guild and authors, and the AAP and publishers, into conflict time and time again."]]></description>
<dc:subject>publishing ebooks rights backlist litigation GoogleBooks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:e067ecb78ff6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:ebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:rights"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:backlist"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:litigation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:GoogleBooks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://irepeat.wordpress.com/2010/07/14/language-change-and-ir/">
    <title>Language change and IR « IRepeat — IR</title>
    <dc:date>2010-07-19T21:33:06+00:00</dc:date>
    <link>http://irepeat.wordpress.com/2010/07/14/language-change-and-ir/</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[via http://palblog.fxpal.com/?p=4246]]></description>
<dc:subject>googlebooks machinelearning textmining IR machine-translation temporal-IR</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:9dd864ca6ea1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:machinelearning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:textmining"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:IR"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:machine-translation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:temporal-IR"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://bibwild.wordpress.com/2010/07/12/deals/">
    <title>deals « Bibliographic Wilderness</title>
    <dc:date>2010-07-15T22:16:49+00:00</dc:date>
    <link>http://bibwild.wordpress.com/2010/07/12/deals/</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[""]]></description>
<dc:subject>HathiTrust googlebooks copyright Jonathan Rochkind</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:6b0121711947/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:HathiTrust"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:copyright"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Jonathan"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Rochkind"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kcoyle.blogspot.com/2010/07/catching-up-oclc-gbs-lod.html">
    <title>Coyle's InFormation: Catching up: OCLC, GBS, LOD</title>
    <dc:date>2010-07-04T17:35:22+00:00</dc:date>
    <link>http://kcoyle.blogspot.com/2010/07/catching-up-oclc-gbs-lod.html</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[""]]></description>
<dc:subject>Karen Coyle Worldcat copyright compilations googlebooks orphanworks linkeddata semanticlibraries</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:1b33fc55c2e7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Karen"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Coyle"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Worldcat"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:copyright"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:compilations"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:orphanworks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:semanticlibraries"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://everybodyslibraries.com/2010/06/20/how-we-talk-about-the-president-a-quick-exploration-in-google-books/">
    <title>How we talk about the president: A quick exploration in Google Books « Everybody's Libraries</title>
    <dc:date>2010-06-24T15:40:23+00:00</dc:date>
    <link>http://everybodyslibraries.com/2010/06/20/how-we-talk-about-the-president-a-quick-exploration-in-google-books/</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["I wondered, as I went through the Emory collection, whether the terms we use for the president reflect shifts in the role he has played over American history.  Is he called “commander in chief” more in times of war or military buildup, for instance?  How often was he instead called “chief magistrate” or “chief executive” over the course of American history?  And how long did “chief magistrate” stay in common use, and what replaced it?

Not too long ago, those questions would have simply remained idle curiosity.  Perhaps, if I’d had the time and patience, I could have painstakingly compiled a small selection of representative writings from various points in US history, read through them, and tried to draw conclusions from them.  But now I– and anyone else on the web– also have a big searchable, dated corpus of text to query: the Google Books collection.  Could that give me any insight into my questions?

It looks like it can, and without too much expenditure of time.  I’m by no means an expert on corpus analysis, but in a couple of hours of work, I was able to assemble promising-looking data that turned up some unexpected (but plausible) results.  Below, I’ll describe what I did and what I found out.""It’s true that the Google corpus is imperfect, as I and others have noted before.  The metadata isn’t always accurate; the number of reported hits is approximate when more than 100 or so, and the mix of volumes in Google’s corpus varies in different time periods.  (For instance, recent years of the corpus may include more magazine content than earlier years; and reprints can make texts reappear decades after they were actually written.  The rise of print-on-demand scans of old public-domain books in the 2000s may be partly responsible for the uptick in “chief magistrate” that decade, for instance.)"]]></description>
<dc:subject>googlebooks Lincoln corpus-analysis textual-analysis google-books</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:c2178ac99a0a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Lincoln"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:corpus-analysis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:textual-analysis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:google-books"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://code.google.com/apis/books/docs/preview-wizard.html">
    <title>Preview Wizard - Google Book Search APIs - Google Code</title>
    <dc:date>2010-06-10T15:16:33+00:00</dc:date>
    <link>http://code.google.com/apis/books/docs/preview-wizard.html</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[""]]></description>
<dc:subject>googlebooks apis</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:d00e71072ecb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:apis"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://chronicle.com/article/Crunching-Words-in-Great/65777/">
    <title>Crunching Words in Great Number - Technology - The Chronicle of Higher Education</title>
    <dc:date>2010-06-05T22:18:14+00:00</dc:date>
    <link>http://chronicle.com/article/Crunching-Words-in-Great/65777/</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["if Google Books has "changed the landscape" of our scholarly perception, and it has, perhaps its greatest legacy will be the spur it gave to the educational community to "do it right"—to create a virtual depository of the kind Robert Darnton and others like him have been pleading for: a virtual collection of our cultural heritage that actually meets the needs of scholarship and public education. At least we can hope that will be its great legacy.""The history of science is in no small part the history of instruments—better and better (and, usually more and more expensive) gadgets and techniques employed in the service of increasingly precise measurement. Telescopes and particle accelerators allow us to see almost to the beginning of the universe, microscopes resolve the unimaginably small, and supercomputers find order in vast quantities of data. The humanities also use technology—classicists were early adopters of photography, and every new technology of imaging has opened up texts that were theretofore invisible. Indeed, literary theory itself can be thought of as a technology, similar to mathematical technique, in that both provide powerful ways of analyzing and thinking about their respective domains.""By mining the Google database, it should be possible to trace literary relations in a whole new way: to show who was the first person to use an influential term or to highlight a theme, and to find verbal patterns that will help reveal the real literary relations whereby the few novelists we still read emerged from the background noise of the genre fiction of their day. "]]></description>
<dc:subject>googlebooks digitalhumanities Chronicle distant-reading close-reading</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:2b800f20c45c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Chronicle"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:distant-reading"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:close-reading"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.cdlib.org/cdlinfo/2010/02/16/hurtling-toward-the-finish-line-should-the-google-books-settlement-be-approved/">
    <title>Hurtling Toward the Finish Line: Should the Google Books Settlement Be Approved?: California Digital Library</title>
    <dc:date>2010-03-18T14:41:45+00:00</dc:date>
    <link>http://www.cdlib.org/cdlinfo/2010/02/16/hurtling-toward-the-finish-line-should-the-google-books-settlement-be-approved/</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[""]]></description>
<dc:subject>googlebooks CDL digitization</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:eb4a9edd86be/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:CDL"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:digitization"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kcoyle.blogspot.com/2010/02/doj-bridge-too-far.html">
    <title>Coyle's InFormation: DOJ: &quot;A Bridge Too Far&quot;</title>
    <dc:date>2010-03-18T14:39:08+00:00</dc:date>
    <link>http://kcoyle.blogspot.com/2010/02/doj-bridge-too-far.html</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[""]]></description>
<dc:subject>copyright GoogleBooks fairuse class-action DOJ Karen Coyle</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:b9fdfb89a6b3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:copyright"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:GoogleBooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:fairuse"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:class-action"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:DOJ"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Karen"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Coyle"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kcoyle.blogspot.com/2010/02/trust-and-settlement.html">
    <title>Coyle's InFormation: Trust and the Settlement</title>
    <dc:date>2010-03-18T14:37:48+00:00</dc:date>
    <link>http://kcoyle.blogspot.com/2010/02/trust-and-settlement.html</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["
The interesting upshot of this entire settlement process is that by digitizing the contents of libraries and managing those digital copies through contracts, the publishers could finally get the kind of control over library uses that they would have liked to have over the paper books held in libraries. They would like to have controls over inter-library loan, classroom use, and reserves, but they cannot exercise such controls in the analog world. Publishers have argued since the very early days of digital documents that all lending of digital documents is the making of a copy, and therefore is not allowed by copyright law.

As a matter of fact, right on page one of the Plaintiff's statement for the judge, among the bullet points describing the main achievements of the settlement, is this one:

    Limits library uses of digital copies of Rightsholders’ works.

Perhaps it has been naive of me to see this settlement as being about Google's commercialization of the world of books. It is possible that the more pertinent end result could be a renewed control of books and their uses by the publisher community. Attempts to modify copyright law to cover digital resources have failed, and the rights of the public in relation to those resources are as yet unclear. This has left a gap that the AAP/AG settlement exploits fully."]]></description>
<dc:subject>Karen Coyle GoogleBooks copyright</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:544bbec67236/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Karen"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Coyle"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:GoogleBooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:copyright"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://go-to-hellman.blogspot.com/2010/03/business-idea-number-3-gluejar-book.html">
    <title>Go To Hellman: Business Idea Number 3: Gluejar Book Search</title>
    <dc:date>2010-03-18T11:53:55+00:00</dc:date>
    <link>http://go-to-hellman.blogspot.com/2010/03/business-idea-number-3-gluejar-book.html</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["There were 3 different presentations, from Stanford, NC State (3.65 MB ppt), and University of Wisconsin, Oshkosh, on "virtual bookshelves".""While the virtual bookshelf is a sensible and practical incremental improvement on the library catalog interface, it's also backward looking. People looking for information today want to search inside the books, not just "browse the stacks". But libraries don't have the ability (today) to search inside the books that they think they own.""as the Open Book Alliance's Peter Brantley has argued, it's very hard to tell what sort of innovations might arise from the availability of large numbers of digitized texts as data; the same goes for indices of these works.""Gluejar Book Search would be a business focused on collecting, aggregating and redistributing full-text indices of copyrighted material."]]></description>
<dc:subject>Eric Hellman googlebooks digiization search-inside virtual-browse full-text-indexing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:314e1a04edca/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Eric"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Hellman"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:digiization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:search-inside"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:virtual-browse"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:full-text-indexing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.dlib.org/dlib/september05/lavoie/09lavoie.html#7">
    <title>Anatomy of Aggregate Collections: The Example of Google Print for Libraries</title>
    <dc:date>2010-03-17T10:58:47+00:00</dc:date>
    <link>http://www.dlib.org/dlib/september05/lavoie/09lavoie.html#7</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[""]]></description>
<dc:subject>googlebooks DLIB collection-development collection-analysis brian Lavoie</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:41687d8fe309/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:DLIB"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:collection-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:collection-analysis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:brian"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Lavoie"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://scitedaily.com/googles-book-scanning-technology-revealed/">
    <title>Google’s Book Scanning Technology Revealed « SciTeDaily</title>
    <dc:date>2010-02-06T20:05:38+00:00</dc:date>
    <link>http://scitedaily.com/googles-book-scanning-technology-revealed/</link>
    <dc:creator>jschneider</dc:creator><dc:subject>googlebooks digitization</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:5736196ba630/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:digitization"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://go-to-hellman.blogspot.com/2010/02/copyright-safe-full-text-indexing-of.html">
    <title>Go To Hellman: Copyright-Safe Full-Text Indexing of Books</title>
    <dc:date>2010-02-06T12:56:26+00:00</dc:date>
    <link>http://go-to-hellman.blogspot.com/2010/02/copyright-safe-full-text-indexing-of.html</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["ull-text indexing is allowed as fair use under US copyright law. Indices are allowed as "transformative uses". Judge Robert Patterson's decision (pdf, 195K) in the "Harry Potter Lexicon" case gives an excellent background of this jurisprudence and concludes:

    The purpose of the Lexicon’s use of the Harry Potter series is transformative.""It doesn't take a computer science degree to see that it's easy to reconstruct the sentence from this index. For that reason this form of index is equivalent to a copy. If you remove the position pointers, however, the index loses enough information that the sentence cannot be reconstructed. So if we take the words on a page of text and sort the words in each sentence, then sort the word-sorted sentences, we get an index of a page that can't be used to reconstruct text, but can be used to build a useful full-text index of a book."]]></description>
<dc:subject>indexing copyright googlebooks Eric Hellman</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:d1dee5e8b6eb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:indexing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:copyright"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Eric"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Hellman"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://go-to-hellman.blogspot.com/2010/01/google-exposes-book-metadata-privates.html">
    <title>Go To Hellman: Google Exposes Book Metadata Privates at ALA Forum</title>
    <dc:date>2010-02-06T12:46:39+00:00</dc:date>
    <link>http://go-to-hellman.blogspot.com/2010/01/google-exposes-book-metadata-privates.html</link>
    <dc:creator>jschneider</dc:creator><dc:subject>metadata Eric Hellman googlebooks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:a18392f16cab/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Eric"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Hellman"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://userscripts.org/scripts/show/37933">
    <title>Google Book Downloader for Greasemonkey</title>
    <dc:date>2010-01-10T14:44:31+00:00</dc:date>
    <link>http://userscripts.org/scripts/show/37933</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[see also http://book.huhiho.com/]]></description>
<dc:subject>greasemonkey googlebooks code4lib</dc:subject>
<dc:identifier>https://pinboard.in/u:jschneider/b:c3d656c86757/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:greasemonkey"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:code4lib"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kcoyle.blogspot.com/2009/09/gbs-and-bad-metadata.html">
    <title>Coyle's InFormation: GBS and Bad Metadata</title>
    <dc:date>2010-01-02T23:29:19+00:00</dc:date>
    <link>http://kcoyle.blogspot.com/2009/09/gbs-and-bad-metadata.html</link>
    <dc:creator>jschneider</dc:creator><dc:subject>Karen Coyle metadata googlebooks</dc:subject>
<dc:identifier>https://pinboard.in/u:jschneider/b:011e26c2e7e5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Karen"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Coyle"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kcoyle.blogspot.com/2009/08/academic-publishing-as-percentage-of.html">
    <title>Coyle's InFormation: Academic publishing as a percentage of Google Books</title>
    <dc:date>2010-01-02T23:01:15+00:00</dc:date>
    <link>http://kcoyle.blogspot.com/2009/08/academic-publishing-as-percentage-of.html</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["it was interesting to me that a university press (Oxford UP) turned up in the #1 spot as the publisher with the greatest number of books in the OL. As a matter of fact, out of the top 20 publishers, five are university presses (UPs), and they make up over 1/4 of the books in that group.""This study of OL publisher data was just experimental, so these figures should be taken with a grain of salt. However, this shows that there is an interesting study to be done, if it can be done, quantifying the relative roles of academic and commercial publishing."]]></description>
<dc:subject>publishing googlebooks Karen Coyle</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jschneider/b:7cdfed8ab4ce/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Karen"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Coyle"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.nybooks.com/articles/23565">
    <title>Google &amp; the Future of Books: An Exchange - The New York Review of Books</title>
    <dc:date>2009-12-28T22:44:41+00:00</dc:date>
    <link>http://www.nybooks.com/articles/23565</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA[It's a bit jarring to see "January 14, 2010" 2+ weeks ahead! "I like Theodore Koditschek's suggestion that Google be treated as a public utility subject to regulation in the public interest. If that seems unrealistic, one should consider a compromise solution, which would draw a line between the books digitized by Google that are strictly commercial and the books that are no longer in print, although some of them are still covered by copyright. Google would continue with its project to commercialize digital copies of books currently in print, sharing the proceeds with the rights holders. At the same time, it would continue to scan out-of-print books and to include them in a database that would constitute a separate, open-access repository. The rights holders of the in-copyright but out-of-print books in that database would be given the opportunity to choose to keep their books out of the open-access plan and, if they preferred, to include their books in Google's commercial operation."
]]></description>
<dc:subject>nyreviewofbooks googlebooks hathitrust Robert Darnton copyright orphan-works</dc:subject>
<dc:identifier>https://pinboard.in/u:jschneider/b:5115652f4e77/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:nyreviewofbooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:hathitrust"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Robert"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Darnton"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:copyright"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:orphan-works"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.cdt.org/policy/cdt-files-brief-urging-privacy-safeguards-google-books">
    <title>CDT files brief urging privacy safeguards for Google Books | Center for Democracy &amp; Technology</title>
    <dc:date>2009-12-28T22:40:25+00:00</dc:date>
    <link>http://www.cdt.org/policy/cdt-files-brief-urging-privacy-safeguards-google-books</link>
    <dc:creator>jschneider</dc:creator><dc:subject>googlebooks copyright cdt privacy</dc:subject>
<dc:identifier>https://pinboard.in/u:jschneider/b:c75e90fbc548/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:copyright"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:cdt"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:privacy"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.cdt.org/blogs/david-sohn/google-books-congress-and-orphan-works">
    <title>Google Books, Congress, and Orphan Works | Center for Democracy &amp; Technology</title>
    <dc:date>2009-12-28T22:39:56+00:00</dc:date>
    <link>http://www.cdt.org/blogs/david-sohn/google-books-congress-and-orphan-works</link>
    <dc:creator>jschneider</dc:creator><dc:subject>googlebooks copyright cdt</dc:subject>
<dc:identifier>https://pinboard.in/u:jschneider/b:a03156fe5c82/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:copyright"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:cdt"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://bibwild.wordpress.com/2009/12/02/improved-google-books-search-within-book-interface/">
    <title>improved google books search-within-book interface? « Bibliographic Wilderness</title>
    <dc:date>2009-12-04T18:18:49+00:00</dc:date>
    <link>http://bibwild.wordpress.com/2009/12/02/improved-google-books-search-within-book-interface/</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["What I now see, at least in one example, is actual scanned pages, with band markers on the vertical scrollbar indicating at what points the matches were found; clicking on them shows highlighted matches on actual scanned images. Very nice! Although I wonder if it will confuse some users."
]]></description>
<dc:subject>googlebooks</dc:subject>
<dc:identifier>https://pinboard.in/u:jschneider/b:1734533efeac/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.arl.org/bm~doc/guide_for_the_perplexed_part3_final.pdf">
    <title>guide_for_the_perplexed_part3_final.pdf (application/pdf Object)</title>
    <dc:date>2009-11-26T07:53:16+00:00</dc:date>
    <link>http://www.arl.org/bm~doc/guide_for_the_perplexed_part3_final.pdf</link>
    <dc:creator>jschneider</dc:creator><dc:subject>googlebooks libraries</dc:subject>
<dc:identifier>https://pinboard.in/u:jschneider/b:91c6281539b4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:libraries"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blogs.talis.com/panlibus/archives/2009/11/survival-with-the-fittest-the-story-of-a-google-library-partner.php">
    <title>Panlibus » Blog Archive » Survival with the fittest: the story of a Google library partner</title>
    <dc:date>2009-11-25T11:45:51+00:00</dc:date>
    <link>http://blogs.talis.com/panlibus/archives/2009/11/survival-with-the-fittest-the-story-of-a-google-library-partner.php</link>
    <dc:creator>jschneider</dc:creator><dc:subject>googlebooks</dc:subject>
<dc:identifier>https://pinboard.in/u:jschneider/b:2493261dbe36/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kcoyle.blogspot.com/2009/11/1923.html">
    <title>Coyle's InFormation: 1923</title>
    <dc:date>2009-11-24T13:00:11+00:00</dc:date>
    <link>http://kcoyle.blogspot.com/2009/11/1923.html</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["how many public domain works have been republished after the 1923 cut-off date?

Google appears to currently lack the ability to make the proper connection between the original text that is in the public domain and the many “manifestations” (as they are called in library-speak) that were published later — and are also in the public domain, at least as far as the primary text is concerned. This is a non-trivial exercise when one is working only with the metadata that describes the work, but may become more feasible with the ability to do a full text analysis of the contents of the various packages in which publishers have placed the original work of Melville. I assume that Google is working on this, although I cannot predict how it will affect their assessment of the PD/(c) split.
"
]]></description>
<dc:subject>publicdomain manifestations Karen Coyle googlebooks 1923</dc:subject>
<dc:identifier>https://pinboard.in/u:jschneider/b:3d06abca3430/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:publicdomain"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:manifestations"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Karen"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Coyle"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:1923"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dltj.org/article/revised-gbs-settlement/">
    <title>Revised Google Book Search Settlement from a Library Perspective | Disruptive Library Technology Jester</title>
    <dc:date>2009-11-24T12:57:28+00:00</dc:date>
    <link>http://dltj.org/article/revised-gbs-settlement/</link>
    <dc:creator>jschneider</dc:creator><dc:subject>googlebooks</dc:subject>
<dc:identifier>https://pinboard.in/u:jschneider/b:258c31172703/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kcoyle.blogspot.com/2009/10/objecting-to-gbsaapag-settlement.html">
    <title>Coyle's InFormation: Objecting to GBS/AAP/AG Settlement</title>
    <dc:date>2009-11-15T22:49:07+00:00</dc:date>
    <link>http://kcoyle.blogspot.com/2009/10/objecting-to-gbsaapag-settlement.html</link>
    <dc:creator>jschneider</dc:creator><dc:subject>Karen Coyle googlebooks</dc:subject>
<dc:identifier>https://pinboard.in/u:jschneider/b:e2f8d59c8693/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Karen"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Coyle"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kcoyle.blogspot.com/2009/11/amended-googleaap-settlement.html">
    <title>Coyle's InFormation: Amended Google/AAP Settlement</title>
    <dc:date>2009-11-15T22:48:25+00:00</dc:date>
    <link>http://kcoyle.blogspot.com/2009/11/amended-googleaap-settlement.html</link>
    <dc:creator>jschneider</dc:creator><dc:subject>googlebooks Karen Coyle</dc:subject>
<dc:identifier>https://pinboard.in/u:jschneider/b:d6d8dfc35687/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Karen"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Coyle"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://exacteditions.blogspot.com/2009/10/google-is-going-for-it.html">
    <title>Exact Editions: Google is Going for It</title>
    <dc:date>2009-11-15T22:26:27+00:00</dc:date>
    <link>http://exacteditions.blogspot.com/2009/10/google-is-going-for-it.html</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["Google has this week announced its Google Editions project, which is intended to make its books database resource, title by title, available to all readers everywhere in every format of ebook reader. So Google at one step is embracing and enlisting all the ebook platforms which might otherwise be a form of competitive counterbalance to the Google Books Library."
]]></description>
<dc:subject>googlebooks</dc:subject>
<dc:identifier>https://pinboard.in/u:jschneider/b:3a0862100727/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kcoyle.blogspot.com/2009/11/googled.html">
    <title>Coyle's InFormation: Googled</title>
    <dc:date>2009-11-10T18:10:50+00:00</dc:date>
    <link>http://kcoyle.blogspot.com/2009/11/googled.html</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["   1. Engineering can fix anything
   2. Information is neutral and measurable
   3. Advertising is information"
]]></description>
<dc:subject>googlebooks Karen Coyle google advertising</dc:subject>
<dc:identifier>https://pinboard.in/u:jschneider/b:b6cffca05498/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Karen"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Coyle"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:advertising"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://go-to-hellman.blogspot.com/2009/10/copyless-crowdscanning-how-to-legally.html">
    <title>Go To Hellman: Copyless Crowdscanning: How to Legally Index the World's Books</title>
    <dc:date>2009-10-28T14:13:16+00:00</dc:date>
    <link>http://go-to-hellman.blogspot.com/2009/10/copyless-crowdscanning-how-to-legally.html</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["It made me realize that the idea of having hundreds of thousands of people scanning their books with cheap scanners was not out of the realm of possibility. The main barrier to assembling a database of all the world's books will no longer be the scanning, but rather the laws governing copyright. So my focus is on how to do crowdscanning so that copyrights are not infringed; the easiest way to do that is to not make any copies.""neither the index aggregator nor the sentence server would be able to reconstitute a book or even the pages from a book"
]]></description>
<dc:subject>engineering googlebooks crowdscanning</dc:subject>
<dc:identifier>https://pinboard.in/u:jschneider/b:b55fb9b7270d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:engineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:crowdscanning"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://go-to-hellman.blogspot.com/2009/10/judge-chin-confronts-scanning-problem.html">
    <title>Go To Hellman: Judge Chin Confronts the Scanning Problem</title>
    <dc:date>2009-10-28T14:06:41+00:00</dc:date>
    <link>http://go-to-hellman.blogspot.com/2009/10/judge-chin-confronts-scanning-problem.html</link>
    <dc:creator>jschneider</dc:creator><dc:subject>Eric Hellman googlebooks</dc:subject>
<dc:identifier>https://pinboard.in/u:jschneider/b:78bb950ab667/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Eric"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:Hellman"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.npr.org/blogs/library/2009/04/the_granting_of_patent_7508978.html">
    <title>The Secret Of Google's Book Scanning Machine Revealed - As A Matter Of Fact Blog : NPR</title>
    <dc:date>2009-10-28T13:56:30+00:00</dc:date>
    <link>http://www.npr.org/blogs/library/2009/04/the_granting_of_patent_7508978.html</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["Google created some seriously nifty infrared camera technology that detects the three-dimensional shape and angle of book pages when the book is placed in the scanner. This information is transmitted to the OCR software, which adjusts for the distortions and allows the OCR software to read text more accurately."
]]></description>
<dc:subject>NPR googlebooks digitization</dc:subject>
<dc:identifier>https://pinboard.in/u:jschneider/b:5ceddc02ba17/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:NPR"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:digitization"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.bitsbook.com/2009/10/do-it-yourself-book-scanning/">
    <title>Blown to Bits » Blog Archive » Do It Yourself Book Scanning</title>
    <dc:date>2009-10-28T13:55:54+00:00</dc:date>
    <link>http://www.bitsbook.com/2009/10/do-it-yourself-book-scanning/</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["Or make them publicly available. I said “can,” not “may” or “should.” But the existence of the device has the potential to raise lots of the same kinds of questions those other duplicating technologies raised. It empowers individuals, and enough empowered individuals could produce a Wikipedian digital library, collectively assembled, imperfect and incomplete, but growing and expanding."
]]></description>
<dc:subject>digitization DIY-scanner googlebooks</dc:subject>
<dc:identifier>https://pinboard.in/u:jschneider/b:8667e1fcf013/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:digitization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:DIY-scanner"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.themillions.com/2009/10/bringing-book-scanning-home.html">
    <title>The Millions: Bringing Book Scanning Home</title>
    <dc:date>2009-10-28T13:55:12+00:00</dc:date>
    <link>http://www.themillions.com/2009/10/bringing-book-scanning-home.html</link>
    <dc:creator>jschneider</dc:creator><description><![CDATA["dan reetz & his diy book scanner

It’s pure 21st-century ingenuity. Reetz designed his first book scanner because, as a grad student at North Dakota State, he was appalled by textbook prices. Then he built it, in two days, from old digital cameras, cardboard, and scrap parts; a friend wrote the page-processing software.""I think the Reetz-Clancy continuum augurs good things for the future of books. On one end, the recognition that books have to live online now, and that publishing has to operate at internet scale. On the other, the passion for (obsession with?) independence and the cottage-industry craftiness that’s been the best part of book publishing for so long already."
]]></description>
<dc:subject>digitization DIY-scanner googlebooks</dc:subject>
<dc:identifier>https://pinboard.in/u:jschneider/b:80e74b1303fd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:digitization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:DIY-scanner"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jschneider/t:googlebooks"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>