<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Are Google and Microsoft Squaring Off Over Public Domain Works?</title>
	<atom:link href="http://scholarlykitchen.sspnet.org/2010/02/09/google-book-search-mysteries-and-the-public-view-of-public-domain-works/feed/" rel="self" type="application/rss+xml" />
	<link>http://scholarlykitchen.sspnet.org/2010/02/09/google-book-search-mysteries-and-the-public-view-of-public-domain-works/</link>
	<description>What&#039;s Hot &#38; What&#039;s Cooking in Scholarly Publishing - from the Society for Scholarly Publishing</description>
	<lastBuildDate>Wed, 15 Feb 2012 17:25:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Reblogging:Are Google and Microsoft Squaring Off Over Public Domain Works? &#171; Architrave Consulting</title>
		<link>http://scholarlykitchen.sspnet.org/2010/02/09/google-book-search-mysteries-and-the-public-view-of-public-domain-works/#comment-8423</link>
		<dc:creator><![CDATA[Reblogging:Are Google and Microsoft Squaring Off Over Public Domain Works? &#171; Architrave Consulting]]></dc:creator>
		<pubDate>Sun, 07 Mar 2010 04:10:28 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=8304#comment-8423</guid>
		<description><![CDATA[[...] 6, 2010   View the complete post. &#8230; Microsoft has plans of its own involving public domain materials.An article  in [...]]]></description>
		<content:encoded><![CDATA[<p>[...] 6, 2010   View the complete post. &#8230; Microsoft has plans of its own involving public domain materials.An article  in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William Rubel</title>
		<link>http://scholarlykitchen.sspnet.org/2010/02/09/google-book-search-mysteries-and-the-public-view-of-public-domain-works/#comment-8220</link>
		<dc:creator><![CDATA[William Rubel]]></dc:creator>
		<pubDate>Fri, 26 Feb 2010 09:06:51 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=8304#comment-8220</guid>
		<description><![CDATA[I am an independent scholar. I use Google Books and other databases, including JSTOR, EEBO and various databases maintained by Gale Research. 

My reply does not speak to the direct issue of government documents, but rather to the broader issue of the use of contract law by private companies to use contract law to circumvent the copyright law which allows for the existence of texts outside of copyright -- &quot;public domain&quot; texts. 

To one extent or another, the claim is made that through ones use of the database that one agrees to restrictions on the use of the material even when there is no dispute that the underlying material is in the public domain.

I fully agree with your reading of Google&#039;s &quot;usage guidelines.&quot; I also think it is a clear statement by its lawyers that they cannot, in fact, assert any control over the files. However, as I mention, below, it seems that they are finding ways to effectively limit ones use of their files by using contract law to control what certain printers are able to print.

1. Regarding Google, as your post points out, Google &quot;asks&quot; us to refrain from making commercial use of its PDF. As the post points out, asking does not seem to be the same as actually making the claim that commercial use of the PDF, i.e. offering the title for sale via an on demand printer is prohibited.

2. Google is, however, making efforts to make just such a use impossible. For example, I was told today by the owner of an Esspresso Book Machine that while Google has licensed its public domain books (or at least nearly two million of them) to on  demand book printers who own the Espresso Book Machine (a new product effectively making its commercial debut this year, in 2010) this license carries restrictions. For a nominal fee, the license provides for printing public domain books from Google&#039;s archive (with covers provided by Google) as long as the book has 500 or fewer pages. 

However, I was told that the license also states that one cannot add material to the book, cannot, for example, add an introduction. As part of the license the owner of the on demand book printer is also prohibited from printing PDFs of Google Books that have been provided by anyone else. This means one cannot print a PDF on the Espresso Book Machine one has downloaded from Google. It also means one cannot alter a work by, for example, adding an introduction. It also means one cannot print any book over 500 pages (the limit imposed by the Espresso Book technology) by breaking a 900 page book into two volumes. [Note: I have not checked this with Google. As I said, this information is based on a conversation with the manager of an Espresso Book Machine.]

3. With regards Google, and all of the databases offering PDFs with restrictions, I think one must differentiate between the PDF and the text. Is Google making any claim to control of the words within the PDF? I think not. 

4. Print publishers of public domain texts are always careful to make clear that the only thing that is copyright is the introduction to the text, or other material added by the publisher, but not the text itself. 

5. Google specifically refers to &quot;non-commercial use of the file.&quot; The PDF is the file. On each book&#039;s web page Google offers an (often poor) OCR version of the same text. While they do not offer this as a single file, a single file could be pieced together from what Google does offer. Google does not seem to make a claim regarding its OCR version of the text. 

6. One implication of a text being in the public domain is that one is free to copy the text and use it for commercial purposes. One is free to check a public domain book out of a library, scan it, and then publish it. One is thus presumably free to print out a Google PDF, scan it, and then use it as one would wish, including publish it. 

7. One is free to type out the text of a pubic domain book and re-set the type and publish the work. One can re-type a Google text and then it is free of any restrictions. Or, if the Google scan is good enough, one could print out their PDF and OCR that to obtain the text. 

8.Google&#039;s scan has a &quot;water mark&quot; that they placed there and that they say must not be removed as it is, in effect, the mark of their claim to ownership of the PDF. While a copyrighted text will, eventually, go out of copyright, and as government documents are never copyrighted, Google&#039;s claim (and those of the owners of other databases as well) seems to be a claim with no termination clause. Even awful crimes have statutes of limitations. Can these corporate claims of control really apply for forever?

Google does not place a copyright notice on the PDF.  No copy of the scanned text has been registered with the US copyright office, nor has the PDF been deposited at the US Library of Congress. That Google has put money into the project of scanning books is their business, both in the sense, literally, of their business and also in the figurative sense. In a sense, this is the essence of Google&#039;s asking for control of the PDF&#039;s they make available, and it is the basis for all of the claims made by the databases that make claims (all do not). In essence, the claim is, we spent money scanning texts (or in the case of Gale Research for many of their texts they spent money scanning microfilm), and we spend money making these texts available to you online and therefore we have a right to control their use. 

9. Public domain images in museums are controlled by museums through their control of copyrighted reproductions of the images. The Mona Lisa is in the public domain. If you walk into the Louvre and take its picture you then control that image in ones camera. The image in ones camera is a piece of intellectual property that is protected by copyright law. Thus, museums go to great lengths to prohibit photography altogether, or photography that would be of a quality that would enable one to publish the image, hence the universal prohibition of taking photographs in museums with a tripod. Google does not seem, though, to make the claim that their PDF of the original public domain work constitutes a new copyrightable product. This cannot be said of all the other database owners.

10. JSTOR seems to take one of the more extreme views of its ownership rights. Here is what JSTOR says on its &quot;wrapper&quot; page to the PDF of an article published in 1868. [The US law that protects the rights of software producers mentions the use of a &quot;wrapper&quot;, something that is in front of whatever it is one is trying to protect and must, ideally, be clicked through to get to the product. Hence, all the &quot;I accept&quot; buttons that one must get through to get to software. Google&#039;s front page to the PDF is its &quot;wrapper&quot; in a legal sense, as is JSTORs statement attached to each of its downloaded PDF files that, &quot;Your use of the JSTOR archive indicates your acceptance of JSTOR&#039;s Terms and Conditions of Use available at http://www.jstor.org/page/info/about/policies/terms.jsp. JSTOR&#039;s Terms and Conditions of Use provides, in part, that unless you have obtained prior permission, you may not download an entire issue of a journal or multiple copies of articles, and you may use content in the JSTOR archive only for your personal, non-commercial use.&quot;

Not only is a professor prohibited from printing out 12, much less 150 copies of an article, even if the underlying article is in the public domain and thus if the professor had a copy of the original journal the copies would be perfectly legal, but JSTOR seems to make claims over the actual words. 

In the case of the wrapper I am quoting here, JSTOR seems to claim control over the &quot;content&quot; of a PDF of a text that was first published in the 19th century and is thus without doubt in the public domain. 

11. In conclusion, it is my sense that few, if any, of the claims controlling the material in these databases have been tested in the courts. I hope that they are tested, and that the public domain wins. It is not just a mattter of attempting to privatize government documents, it is really an attempt to privatize as much of the the public domain as they can manage to privatize, either legally, or through intimidating langauge in legal-sounding &quot;wrappers.&quot;]]></description>
		<content:encoded><![CDATA[<p>I am an independent scholar. I use Google Books and other databases, including JSTOR, EEBO and various databases maintained by Gale Research. </p>
<p>My reply does not speak to the direct issue of government documents, but rather to the broader issue of the use of contract law by private companies to use contract law to circumvent the copyright law which allows for the existence of texts outside of copyright &#8212; &#8220;public domain&#8221; texts. </p>
<p>To one extent or another, the claim is made that through ones use of the database that one agrees to restrictions on the use of the material even when there is no dispute that the underlying material is in the public domain.</p>
<p>I fully agree with your reading of Google&#8217;s &#8220;usage guidelines.&#8221; I also think it is a clear statement by its lawyers that they cannot, in fact, assert any control over the files. However, as I mention, below, it seems that they are finding ways to effectively limit ones use of their files by using contract law to control what certain printers are able to print.</p>
<p>1. Regarding Google, as your post points out, Google &#8220;asks&#8221; us to refrain from making commercial use of its PDF. As the post points out, asking does not seem to be the same as actually making the claim that commercial use of the PDF, i.e. offering the title for sale via an on demand printer is prohibited.</p>
<p>2. Google is, however, making efforts to make just such a use impossible. For example, I was told today by the owner of an Esspresso Book Machine that while Google has licensed its public domain books (or at least nearly two million of them) to on  demand book printers who own the Espresso Book Machine (a new product effectively making its commercial debut this year, in 2010) this license carries restrictions. For a nominal fee, the license provides for printing public domain books from Google&#8217;s archive (with covers provided by Google) as long as the book has 500 or fewer pages. </p>
<p>However, I was told that the license also states that one cannot add material to the book, cannot, for example, add an introduction. As part of the license the owner of the on demand book printer is also prohibited from printing PDFs of Google Books that have been provided by anyone else. This means one cannot print a PDF on the Espresso Book Machine one has downloaded from Google. It also means one cannot alter a work by, for example, adding an introduction. It also means one cannot print any book over 500 pages (the limit imposed by the Espresso Book technology) by breaking a 900 page book into two volumes. [Note: I have not checked this with Google. As I said, this information is based on a conversation with the manager of an Espresso Book Machine.]</p>
<p>3. With regards Google, and all of the databases offering PDFs with restrictions, I think one must differentiate between the PDF and the text. Is Google making any claim to control of the words within the PDF? I think not. </p>
<p>4. Print publishers of public domain texts are always careful to make clear that the only thing that is copyright is the introduction to the text, or other material added by the publisher, but not the text itself. </p>
<p>5. Google specifically refers to &#8220;non-commercial use of the file.&#8221; The PDF is the file. On each book&#8217;s web page Google offers an (often poor) OCR version of the same text. While they do not offer this as a single file, a single file could be pieced together from what Google does offer. Google does not seem to make a claim regarding its OCR version of the text. </p>
<p>6. One implication of a text being in the public domain is that one is free to copy the text and use it for commercial purposes. One is free to check a public domain book out of a library, scan it, and then publish it. One is thus presumably free to print out a Google PDF, scan it, and then use it as one would wish, including publish it. </p>
<p>7. One is free to type out the text of a pubic domain book and re-set the type and publish the work. One can re-type a Google text and then it is free of any restrictions. Or, if the Google scan is good enough, one could print out their PDF and OCR that to obtain the text. </p>
<p>8.Google&#8217;s scan has a &#8220;water mark&#8221; that they placed there and that they say must not be removed as it is, in effect, the mark of their claim to ownership of the PDF. While a copyrighted text will, eventually, go out of copyright, and as government documents are never copyrighted, Google&#8217;s claim (and those of the owners of other databases as well) seems to be a claim with no termination clause. Even awful crimes have statutes of limitations. Can these corporate claims of control really apply for forever?</p>
<p>Google does not place a copyright notice on the PDF.  No copy of the scanned text has been registered with the US copyright office, nor has the PDF been deposited at the US Library of Congress. That Google has put money into the project of scanning books is their business, both in the sense, literally, of their business and also in the figurative sense. In a sense, this is the essence of Google&#8217;s asking for control of the PDF&#8217;s they make available, and it is the basis for all of the claims made by the databases that make claims (all do not). In essence, the claim is, we spent money scanning texts (or in the case of Gale Research for many of their texts they spent money scanning microfilm), and we spend money making these texts available to you online and therefore we have a right to control their use. </p>
<p>9. Public domain images in museums are controlled by museums through their control of copyrighted reproductions of the images. The Mona Lisa is in the public domain. If you walk into the Louvre and take its picture you then control that image in ones camera. The image in ones camera is a piece of intellectual property that is protected by copyright law. Thus, museums go to great lengths to prohibit photography altogether, or photography that would be of a quality that would enable one to publish the image, hence the universal prohibition of taking photographs in museums with a tripod. Google does not seem, though, to make the claim that their PDF of the original public domain work constitutes a new copyrightable product. This cannot be said of all the other database owners.</p>
<p>10. JSTOR seems to take one of the more extreme views of its ownership rights. Here is what JSTOR says on its &#8220;wrapper&#8221; page to the PDF of an article published in 1868. [The US law that protects the rights of software producers mentions the use of a &#8220;wrapper&#8221;, something that is in front of whatever it is one is trying to protect and must, ideally, be clicked through to get to the product. Hence, all the &#8220;I accept&#8221; buttons that one must get through to get to software. Google&#8217;s front page to the PDF is its &#8220;wrapper&#8221; in a legal sense, as is JSTORs statement attached to each of its downloaded PDF files that, &#8220;Your use of the JSTOR archive indicates your acceptance of JSTOR&#8217;s Terms and Conditions of Use available at <a href="http://www.jstor.org/page/info/about/policies/terms.jsp" rel="nofollow">http://www.jstor.org/page/info/about/policies/terms.jsp</a>. JSTOR&#8217;s Terms and Conditions of Use provides, in part, that unless you have obtained prior permission, you may not download an entire issue of a journal or multiple copies of articles, and you may use content in the JSTOR archive only for your personal, non-commercial use.&#8221;</p>
<p>Not only is a professor prohibited from printing out 12, much less 150 copies of an article, even if the underlying article is in the public domain and thus if the professor had a copy of the original journal the copies would be perfectly legal, but JSTOR seems to make claims over the actual words. </p>
<p>In the case of the wrapper I am quoting here, JSTOR seems to claim control over the &#8220;content&#8221; of a PDF of a text that was first published in the 19th century and is thus without doubt in the public domain. </p>
<p>11. In conclusion, it is my sense that few, if any, of the claims controlling the material in these databases have been tested in the courts. I hope that they are tested, and that the public domain wins. It is not just a mattter of attempting to privatize government documents, it is really an attempt to privatize as much of the the public domain as they can manage to privatize, either legally, or through intimidating langauge in legal-sounding &#8220;wrappers.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Droits d&#8217;auteur &#38; co (14/02/10) &#171; pintiniblog</title>
		<link>http://scholarlykitchen.sspnet.org/2010/02/09/google-book-search-mysteries-and-the-public-view-of-public-domain-works/#comment-7811</link>
		<dc:creator><![CDATA[Droits d&#8217;auteur &#38; co (14/02/10) &#171; pintiniblog]]></dc:creator>
		<pubDate>Sun, 14 Feb 2010 19:00:18 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=8304#comment-7811</guid>
		<description><![CDATA[[...] Are Google and Microsoft Squaring Off Over Public Domain Works? (source: The Scholarly Kitchen, 09/02/2010) Why Google apparently gives government documents more [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Are Google and Microsoft Squaring Off Over Public Domain Works? (source: The Scholarly Kitchen, 09/02/2010) Why Google apparently gives government documents more [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Sleeman (Baltimore, Md.)</title>
		<link>http://scholarlykitchen.sspnet.org/2010/02/09/google-book-search-mysteries-and-the-public-view-of-public-domain-works/#comment-7644</link>
		<dc:creator><![CDATA[Bill Sleeman (Baltimore, Md.)]]></dc:creator>
		<pubDate>Fri, 12 Feb 2010 16:21:03 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=8304#comment-7644</guid>
		<description><![CDATA[Access to government information has been a concern in the library community almost from the very first announcement that many of our leading libraries would be working with Google to digitize their collection. For the most part librarians, particularly those who specialize in government information, have had their concerns and trepidations dismissed. However, there is good reason, based on experience, to be concerned about a single company –  even one that promise to do no evil – serving as the primary and possibly the only source for much of this publicly created, tax-payer produced information. It is not unlike what happened with access to legal information which is owned and distributed primarily by two companies (both foreign owned – but that is another matter). 

Readers may be interested in the discussion around this aspect of Google’s scanning efforts on the website of the American Library Association - http://www.law.umaryland.edu/marshall/ . 

Thanks Alix for turning your attention to this.]]></description>
		<content:encoded><![CDATA[<p>Access to government information has been a concern in the library community almost from the very first announcement that many of our leading libraries would be working with Google to digitize their collection. For the most part librarians, particularly those who specialize in government information, have had their concerns and trepidations dismissed. However, there is good reason, based on experience, to be concerned about a single company –  even one that promise to do no evil – serving as the primary and possibly the only source for much of this publicly created, tax-payer produced information. It is not unlike what happened with access to legal information which is owned and distributed primarily by two companies (both foreign owned – but that is another matter). </p>
<p>Readers may be interested in the discussion around this aspect of Google’s scanning efforts on the website of the American Library Association &#8211; <a href="http://www.law.umaryland.edu/marshall/" rel="nofollow">http://www.law.umaryland.edu/marshall/</a> . </p>
<p>Thanks Alix for turning your attention to this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Google Book Settlement News 2/11/2010 &#171;</title>
		<link>http://scholarlykitchen.sspnet.org/2010/02/09/google-book-search-mysteries-and-the-public-view-of-public-domain-works/#comment-7607</link>
		<dc:creator><![CDATA[Google Book Settlement News 2/11/2010 &#171;]]></dc:creator>
		<pubDate>Thu, 11 Feb 2010 17:08:39 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=8304#comment-7607</guid>
		<description><![CDATA[[...] Alix Vance writes on Google Books Terms of Service and how they may be designed to blunt Microsoft efforts. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Alix Vance writes on Google Books Terms of Service and how they may be designed to blunt Microsoft efforts. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Rusbridge</title>
		<link>http://scholarlykitchen.sspnet.org/2010/02/09/google-book-search-mysteries-and-the-public-view-of-public-domain-works/#comment-7549</link>
		<dc:creator><![CDATA[Chris Rusbridge]]></dc:creator>
		<pubDate>Wed, 10 Feb 2010 10:55:23 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=8304#comment-7549</guid>
		<description><![CDATA[Yes, I have found it particularly annoying that GBS doesn&#039;t give access to non-copyright US government texts. The arguments seem bonkers; it&#039;s hard to imagine they don&#039;t understand that part of the US copyright system!]]></description>
		<content:encoded><![CDATA[<p>Yes, I have found it particularly annoying that GBS doesn&#8217;t give access to non-copyright US government texts. The arguments seem bonkers; it&#8217;s hard to imagine they don&#8217;t understand that part of the US copyright system!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph J. Esposito</title>
		<link>http://scholarlykitchen.sspnet.org/2010/02/09/google-book-search-mysteries-and-the-public-view-of-public-domain-works/#comment-7513</link>
		<dc:creator><![CDATA[Joseph J. Esposito]]></dc:creator>
		<pubDate>Tue, 09 Feb 2010 19:02:08 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=8304#comment-7513</guid>
		<description><![CDATA[Welcome, Alix Vance, to the Scholarly Kitchen.]]></description>
		<content:encoded><![CDATA[<p>Welcome, Alix Vance, to the Scholarly Kitchen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Link to &#8220;Are Google and Microsoft Squaring Off Over Public Domain Works?&#8221; &#171; Informationatorium</title>
		<link>http://scholarlykitchen.sspnet.org/2010/02/09/google-book-search-mysteries-and-the-public-view-of-public-domain-works/#comment-7505</link>
		<dc:creator><![CDATA[Link to &#8220;Are Google and Microsoft Squaring Off Over Public Domain Works?&#8221; &#171; Informationatorium]]></dc:creator>
		<pubDate>Tue, 09 Feb 2010 16:19:47 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=8304#comment-7505</guid>
		<description><![CDATA[[...] 9, 2010 by Alix Vance    This new post (from me) on The Scholarly Kitchen blog is of interest to Paratext-ians.  It stems from observations about my use of Google links within [...]]]></description>
		<content:encoded><![CDATA[<p>[...] 9, 2010 by Alix Vance    This new post (from me) on The Scholarly Kitchen blog is of interest to Paratext-ians.  It stems from observations about my use of Google links within [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

