<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Copyright, the public domain, &amp; digital history</title>
	<atom:link href="http://behind.aotw.org/2006/03/29/copyright-the-public-domain-digital-history/feed/" rel="self" type="application/rss+xml" />
	<link>http://behind.aotw.org/2006/03/29/copyright-the-public-domain-digital-history/</link>
	<description>the backwash of a digital history project</description>
	<lastBuildDate>Sat, 13 Mar 2010 04:09:41 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: behind AotW &#187; Blog Archive &#187; Craighill: staff officers, a lighthouse, and copyfraud</title>
		<link>http://behind.aotw.org/2006/03/29/copyright-the-public-domain-digital-history/comment-page-1/#comment-5218</link>
		<dc:creator>behind AotW &#187; Blog Archive &#187; Craighill: staff officers, a lighthouse, and copyfraud</dc:creator>
		<pubDate>Tue, 09 Jan 2007 04:52:29 +0000</pubDate>
		<guid isPermaLink="false">http://aotw.org/blog/2006/03/29/copyright-the-public-domain-digital-history/#comment-5218</guid>
		<description>[...] For pointers to more about the Public Domain and US copyright Law, see an older post on this blog. [...]</description>
		<content:encoded><![CDATA[<p>[...] For pointers to more about the Public Domain and US copyright Law, see an older post on this blog. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Digital History Hacks &#187; Blog Archive &#187; Behind the Scenes of a Digital History Site</title>
		<link>http://behind.aotw.org/2006/03/29/copyright-the-public-domain-digital-history/comment-page-1/#comment-2616</link>
		<dc:creator>Digital History Hacks &#187; Blog Archive &#187; Behind the Scenes of a Digital History Site</dc:creator>
		<pubDate>Sun, 15 Oct 2006 23:21:48 +0000</pubDate>
		<guid isPermaLink="false">http://aotw.org/blog/2006/03/29/copyright-the-public-domain-digital-history/#comment-2616</guid>
		<description>[...] At 10 years of age, AOTW is an obvious labor of love and a source of ideas and inspiration. Since March of this year, however, Brian has also been blogging at behind AOTW, &#8220;the backwash of a digital history project&#8221;. The combination of the AOTW site and Brian&#8217;s blog provide the student of digital history with an unparalleled view behind the scenes of a successful project. In March, for example, Brian posted about footnotes in online history, allowing the reader to compare his code with the implementation on the AOTW site. In another post that month, he discussed copyright and the public domain, something that he has a more-than-academic interest in. In April he laid out a top-down strategy for practicing digital history, continued in June. In July, he discussed the question of whether a site should host advertisements in &#8220;Pimping the History Web?&#8221; and reviewed some 19th-century online works from the Perseus Project. In August, he implemented a timeline widget and gazeteer for AOTW. This month he has a series of great posts to help someone get started without &#8220;an IT shop or a CHNM&#8221;: tools for putting history online, PHP+database+webserver and jumping in with both feet. [...]</description>
		<content:encoded><![CDATA[<p>[...] At 10 years of age, AOTW is an obvious labor of love and a source of ideas and inspiration. Since March of this year, however, Brian has also been blogging at behind AOTW, &#8220;the backwash of a digital history project&#8221;. The combination of the AOTW site and Brian&#8217;s blog provide the student of digital history with an unparalleled view behind the scenes of a successful project. In March, for example, Brian posted about footnotes in online history, allowing the reader to compare his code with the implementation on the AOTW site. In another post that month, he discussed copyright and the public domain, something that he has a more-than-academic interest in. In April he laid out a top-down strategy for practicing digital history, continued in June. In July, he discussed the question of whether a site should host advertisements in &#8220;Pimping the History Web?&#8221; and reviewed some 19th-century online works from the Perseus Project. In August, he implemented a timeline widget and gazeteer for AOTW. This month he has a series of great posts to help someone get started without &#8220;an IT shop or a CHNM&#8221;: tools for putting history online, PHP+database+webserver and jumping in with both feet. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Downey</title>
		<link>http://behind.aotw.org/2006/03/29/copyright-the-public-domain-digital-history/comment-page-1/#comment-17</link>
		<dc:creator>Brian Downey</dc:creator>
		<pubDate>Fri, 31 Mar 2006 02:07:58 +0000</pubDate>
		<guid isPermaLink="false">http://aotw.org/blog/2006/03/29/copyright-the-public-domain-digital-history/#comment-17</guid>
		<description>Hi David,

Thanks for the comment.  There are certainly a host of other issues about using historical materials online, too.  

I wouldn&#039;t expect your example of cleaning up or enhancing an image, by the way, to qualify it as a new image for copyright purposes.  Courts have generally found these to be &quot;slavish copies&quot;, essentially duplicates of the original - not different enough to be derivative works entitled to copyright protection.  You have to &quot;warhol&quot; an image before it&#039;s distant enough to be new (and art), I guess.

&lt;a href=&quot;http://digitalgallery.nypl.org/nypldigital/dgkeysearchdetail.cfm?strucID=111929#&quot; rel=&quot;nofollow&quot;&gt;&lt;img title=&quot;Bonfils, c. 1870, via NYPL&quot; src=&quot;http://www.aotw.org/blog/images/sphinx.jpg&quot; style=&quot;border:0&quot; /&gt;&lt;/a&gt;

I don&#039;t understand the nuances of &quot;ownership&quot; as your Davis portrait example raises, either.  Instinctively, I feel there&#039;s something wrong with the NY Public Library requiring a fee to publish a copy of a picture (as above) from their collection which is in the public domain.  I resent the constriction of historical information, but I recognize they have costs to recoup.

Which is heading for fair use.  A topic I feel strongly about, but will save for another time ...

Brian</description>
		<content:encoded><![CDATA[<p>Hi David,</p>
<p>Thanks for the comment.  There are certainly a host of other issues about using historical materials online, too.  </p>
<p>I wouldn&#8217;t expect your example of cleaning up or enhancing an image, by the way, to qualify it as a new image for copyright purposes.  Courts have generally found these to be &#8220;slavish copies&#8221;, essentially duplicates of the original &#8211; not different enough to be derivative works entitled to copyright protection.  You have to &#8220;warhol&#8221; an image before it&#8217;s distant enough to be new (and art), I guess.</p>
<p><a href="http://digitalgallery.nypl.org/nypldigital/dgkeysearchdetail.cfm?strucID=111929#" rel="nofollow"><img title="Bonfils, c. 1870, via NYPL" src="http://www.aotw.org/blog/images/sphinx.jpg" style="border:0" /></a></p>
<p>I don&#8217;t understand the nuances of &#8220;ownership&#8221; as your Davis portrait example raises, either.  Instinctively, I feel there&#8217;s something wrong with the NY Public Library requiring a fee to publish a copy of a picture (as above) from their collection which is in the public domain.  I resent the constriction of historical information, but I recognize they have costs to recoup.</p>
<p>Which is heading for fair use.  A topic I feel strongly about, but will save for another time &#8230;</p>
<p>Brian</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Woodbury</title>
		<link>http://behind.aotw.org/2006/03/29/copyright-the-public-domain-digital-history/comment-page-1/#comment-16</link>
		<dc:creator>David Woodbury</dc:creator>
		<pubDate>Thu, 30 Mar 2006 18:19:19 +0000</pubDate>
		<guid isPermaLink="false">http://aotw.org/blog/2006/03/29/copyright-the-public-domain-digital-history/#comment-16</guid>
		<description>Brian,

I think your summary of copyright laws is right on the money, and the propriety of lifting images from other sites is often a question unrelated to copyright. 

But there is a question of &quot;ownership&quot; and permissions. If a museum, for example, owns an original, pre-copyright portrait of Jefferson Davis, I could not simply reproduce it in a publication without permission.  And in that case, &quot;publishing&quot; something online may be indistinguishable from conventional publishing. All that said, it&#039;s easy to restrict oneself to images known to be in the public domain, including everything at U.S. government web sites.

There is such a thing as a new materials copyright, for example, when Bob Younger took an old tome, reset the type, added an intro and index, and possibly fixed typos, etc. One would have to quote the original text to avoid infringement. That might apply to otherwise public domain images on the internet, if the poster has scanned the image and enhanced it with software to make it more crisp, or to lend better contrast. In that case, it&#039;s effectively a new work, but I don&#039;t know how the law applies. 

Where things really get gray is determining how much text constitutes &quot;fair use.&quot;

Good post.</description>
		<content:encoded><![CDATA[<p>Brian,</p>
<p>I think your summary of copyright laws is right on the money, and the propriety of lifting images from other sites is often a question unrelated to copyright. </p>
<p>But there is a question of &#8220;ownership&#8221; and permissions. If a museum, for example, owns an original, pre-copyright portrait of Jefferson Davis, I could not simply reproduce it in a publication without permission.  And in that case, &#8220;publishing&#8221; something online may be indistinguishable from conventional publishing. All that said, it&#8217;s easy to restrict oneself to images known to be in the public domain, including everything at U.S. government web sites.</p>
<p>There is such a thing as a new materials copyright, for example, when Bob Younger took an old tome, reset the type, added an intro and index, and possibly fixed typos, etc. One would have to quote the original text to avoid infringement. That might apply to otherwise public domain images on the internet, if the poster has scanned the image and enhanced it with software to make it more crisp, or to lend better contrast. In that case, it&#8217;s effectively a new work, but I don&#8217;t know how the law applies. </p>
<p>Where things really get gray is determining how much text constitutes &#8220;fair use.&#8221;</p>
<p>Good post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Downey</title>
		<link>http://behind.aotw.org/2006/03/29/copyright-the-public-domain-digital-history/comment-page-1/#comment-15</link>
		<dc:creator>Brian Downey</dc:creator>
		<pubDate>Wed, 29 Mar 2006 23:34:43 +0000</pubDate>
		<guid isPermaLink="false">http://aotw.org/blog/2006/03/29/copyright-the-public-domain-digital-history/#comment-15</guid>
		<description>Thanks Eric - good to hear from a pro.</description>
		<content:encoded><![CDATA[<p>Thanks Eric &#8211; good to hear from a pro.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Wittenberg</title>
		<link>http://behind.aotw.org/2006/03/29/copyright-the-public-domain-digital-history/comment-page-1/#comment-14</link>
		<dc:creator>Eric Wittenberg</dc:creator>
		<pubDate>Wed, 29 Mar 2006 19:24:26 +0000</pubDate>
		<guid isPermaLink="false">http://aotw.org/blog/2006/03/29/copyright-the-public-domain-digital-history/#comment-14</guid>
		<description>Excellent post Brian, and you see the copyright laws just as I, an attorney of 20 years&#039; experience, see them.

Eric</description>
		<content:encoded><![CDATA[<p>Excellent post Brian, and you see the copyright laws just as I, an attorney of 20 years&#8217; experience, see them.</p>
<p>Eric</p>
]]></content:encoded>
	</item>
</channel>
</rss>
