<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Libology Blog &#187; Copyright</title>
	<atom:link href="http://www.libology.com/blog/category/copyright/feed" rel="self" type="application/rss+xml" />
	<link>http://www.libology.com/blog</link>
	<description>Libraries::Technology::Ideas</description>
	<lastBuildDate>Wed, 17 Mar 2010 02:44:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Public Domain Manifesto</title>
		<link>http://www.libology.com/blog/2010/02/06/public-domain-manifesto.html</link>
		<comments>http://www.libology.com/blog/2010/02/06/public-domain-manifesto.html#comments</comments>
		<pubDate>Sat, 06 Feb 2010 22:11:33 +0000</pubDate>
		<dc:creator>Rick Mason</dc:creator>
				<category><![CDATA[Copyright]]></category>
		<category><![CDATA[Government]]></category>
		<category><![CDATA[History]]></category>
		<category><![CDATA[Libraries]]></category>
		<category><![CDATA[Licensing]]></category>
		<category><![CDATA[Manifesto]]></category>
		<category><![CDATA[public domain]]></category>
		<category><![CDATA[Public Domain Manifesto]]></category>

		<guid isPermaLink="false">http://www.libology.com/blog/?p=3281</guid>
		<description><![CDATA[The Public Domain Manifesto is an effort to describe the strengths of public domain, and to encourage support.
Some of the general principles:

The Public Domain is the rule, copyright protection is the exception.
Copyright protection should last only as long as necessary to achieve a reasonable compromise between protecting and rewarding the author for his intellectual labour [...]]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://www.publicdomainmanifesto.org/"><strong>Public Domain Manifesto</strong></a> is an effort to describe the strengths of public domain, and to encourage support.</p>
<p>Some of the general principles:</p>
<ul>
<li>The Public Domain is the rule, copyright protection is the exception.</li>
<li>Copyright protection should last only as long as necessary to achieve a reasonable compromise between protecting and rewarding the author for his intellectual labour and safeguarding the public interest in the dissemination of culture and knowledge.</li>
<li>What is in the Public Domain must remain in the Public Domain.</li>
<li>The lawful user of a digital copy of a Public Domain work should be free to (re-)use, copy and modify such work.</li>
<li>Contracts or technical protection measures that restrict access to and re-use of Public Domain works must not be enforced.</li>
</ul>
<p>I recommend that you review the manifesto, and if you agree with it, show your support by signing it.</p>
<p><em>found via <a href="http://www.opensource.org/node/506">Open Source Initiative </a></em></p>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.libology.com%2Fblog%2F2010%2F02%2F06%2Fpublic-domain-manifesto.html&amp;linkname=Public%20Domain%20Manifesto"><img src="http://www.libology.com/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.libology.com/blog/2010/02/06/public-domain-manifesto.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RECAPing PACER</title>
		<link>http://www.libology.com/blog/2009/08/16/recaping-pacer.html</link>
		<comments>http://www.libology.com/blog/2009/08/16/recaping-pacer.html#comments</comments>
		<pubDate>Sun, 16 Aug 2009 21:58:08 +0000</pubDate>
		<dc:creator>Rick Mason</dc:creator>
				<category><![CDATA[Archival]]></category>
		<category><![CDATA[Copyright]]></category>
		<category><![CDATA[Government]]></category>
		<category><![CDATA[Online Databases]]></category>
		<category><![CDATA[Online Services]]></category>
		<category><![CDATA[Open Access]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[appellate court]]></category>
		<category><![CDATA[Bankruptcy court]]></category>
		<category><![CDATA[federal government]]></category>
		<category><![CDATA[firefox]]></category>
		<category><![CDATA[Internet Archive]]></category>
		<category><![CDATA[Legal research]]></category>
		<category><![CDATA[PACER]]></category>
		<category><![CDATA[Public records]]></category>
		<category><![CDATA[RECAP]]></category>
		<category><![CDATA[United States copyright law]]></category>

		<guid isPermaLink="false">http://www.libology.com/blog/?p=3133</guid>
		<description><![CDATA[PACER is the online access portal for &#8220;U.S. Appellate,               District, and Bankruptcy court records and documents nationwide&#8221;.  Because the documents it provides are created by the federal judiciary, they are not  copyrightable; because PACER is the only place to obtain [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://pacer.psc.uscourts.gov/">PACER</a> is the online access portal for &#8220;U.S. Appellate,               District, and Bankruptcy court records and documents nationwide&#8221;.  Because the documents it provides are created by the federal judiciary, they are not  copyrightable; because PACER is the only place to obtain these records, it is a critical link to those who need case information.  PACER also charges a per-page fee ($0.08 per page up to 30 pages in a specific document) for access.</p>
<p><a href="https://www.recapthelaw.org/"><strong>RECAP</strong></a> (which is PACER spelled backwards) is a new, open source Firefox extension which appears to follow all the rules:  you access documents through PACER, paying all assessed fees, and you get your docuements.  RECAP, however adds two elements to the mix:</p>
<ol>
<li>RECAP automatically uploads any document that is accessed by users of the extension to a public repository hosted by the Internet Archive.</li>
<li>RECAP will alert the user when a document they wish to access is available through the public repository.</li>
</ol>
<p>On the surface, it may appear that people are conducting an end-run against the court&#8217;s system for providing documents.  However, a broader view strongly suggests that these documents are public, and that the PACER system is actually an exception in the realm of access to public records.</p>
<p>The Executive and Legislative branches of the federal government provide documents free to the user; this is an attempt to make the workings and decisions of the judiciary as public as the other branches.  RECAP is a fully legal means to provide information in a way that is the spirit of the law.</p>
<p>Further reading:</p>
<ul>
<li><a href="http://arstechnica.com/tech-policy/news/2009/04/case-against-pacer.ars">The Case Against PACER</a></li>
<li><a href="http://arstechnica.com/tech-policy/news/2009/08/recap-firefox-extension-builds-crowdsourced-pacer-mirror.ars">Firefox Extension Liberates US Court Docs from Paywall</a></li>
<li><a href="http://www.techcrunch.com/2009/08/14/use-recap-to-bypass-court-document-pacer-paywall/">Use RECAP to Bypass Court Document Paywall</a></li>
</ul>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.libology.com%2Fblog%2F2009%2F08%2F16%2Frecaping-pacer.html&amp;linkname=RECAPing%20PACER"><img src="http://www.libology.com/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.libology.com/blog/2009/08/16/recaping-pacer.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Books : A Plan To Scan</title>
		<link>http://www.libology.com/blog/2009/08/13/books-a-plan-to-scan.html</link>
		<comments>http://www.libology.com/blog/2009/08/13/books-a-plan-to-scan.html#comments</comments>
		<pubDate>Thu, 13 Aug 2009 21:45:12 +0000</pubDate>
		<dc:creator>Rick Mason</dc:creator>
				<category><![CDATA[Books]]></category>
		<category><![CDATA[Copyright]]></category>
		<category><![CDATA[Ethics]]></category>
		<category><![CDATA[Fair Use]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Libraries]]></category>
		<category><![CDATA[Library 2.0]]></category>
		<category><![CDATA[Licensing]]></category>
		<category><![CDATA[Book scanning]]></category>
		<category><![CDATA[Digital libraries]]></category>
		<category><![CDATA[Financial Times]]></category>
		<category><![CDATA[Library and information science]]></category>
		<category><![CDATA[Orphan works]]></category>
		<category><![CDATA[United States copyright law]]></category>

		<guid isPermaLink="false">http://www.libology.com/blog/?p=3126</guid>
		<description><![CDATA[A very straightforward and readable overview of the issues surrounding Google&#8217;s book scanning project appeared in yesterdays Financial Times :  Books : A plan to scan.
A prime focus of the analysis is the Orphan Works issue, books that fall under copyright guidelines but have no clear indication of who the actual copyright holder is.  A [...]]]></description>
			<content:encoded><![CDATA[<p>A very straightforward and readable overview of the issues surrounding Google&#8217;s book scanning project appeared in yesterdays Financial Times :  <a href="http://www.ft.com/cms/s/d9c722a6-877e-11de-9280-00144feabdc0,dwp_uuid=03d100e8-2fff-11da-ba9f-00000e2511c8,print=yes.html">Books : A plan to scan</a>.</p>
<p>A prime focus of the analysis is the Orphan Works issue, books that fall under copyright guidelines but have no clear indication of who the actual copyright holder is.  A chart detailing the number of orphan works in existence is an excellent example of  providing just the right amount of information in a very readable way (note the use of Google&#8217;s colors):</p>
<div id="attachment_3127" class="wp-caption aligncenter" style="width: 510px"><a href="http://media.ft.com/cms/89d54068-8763-11de-9280-00144feabdc0.gif"><img class="size-full wp-image-3127" title="FT-OrphanWorks" src="http://www.libology.com/blog/wp-content/uploads/2009/08/FT-OrphanWorks.gif" alt="Financial Times Graphic on Orphan Works" width="500" height="391" /></a><p class="wp-caption-text">Financial Times Graphic on Orphan Works</p></div>
<p>There is also an interesting <a href="http://www.ft.com/cms/s/54f4008a-877e-11de-9280-00144feabdc0,dwp_uuid=cbad994c-3017-11da-ba9f-00000e2511c8,print=yes.html">accompanying article on the European reaction to the issue</a>.</p>
<p><em>thanks to Jim Campbell for <a href="http://lists.webjunction.org/wjlists/web4lib/2009-August/049946.html">posting about this on Web4Lib</a>!</em></p>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.libology.com%2Fblog%2F2009%2F08%2F13%2Fbooks-a-plan-to-scan.html&amp;linkname=Books%20%3A%20A%20Plan%20To%20Scan"><img src="http://www.libology.com/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.libology.com/blog/2009/08/13/books-a-plan-to-scan.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TinEye Reverse Image Search</title>
		<link>http://www.libology.com/blog/2009/08/09/tineye-reverse-image-search.html</link>
		<comments>http://www.libology.com/blog/2009/08/09/tineye-reverse-image-search.html#comments</comments>
		<pubDate>Sun, 09 Aug 2009 23:40:37 +0000</pubDate>
		<dc:creator>Rick Mason</dc:creator>
				<category><![CDATA[Copyright]]></category>
		<category><![CDATA[Online Services]]></category>
		<category><![CDATA[Photography]]></category>
		<category><![CDATA[Search]]></category>
		<category><![CDATA[WebSearch]]></category>
		<category><![CDATA[image search engine]]></category>
		<category><![CDATA[MetaFilter]]></category>
		<category><![CDATA[search engine]]></category>
		<category><![CDATA[Technology/Internet]]></category>
		<category><![CDATA[TinEye]]></category>

		<guid isPermaLink="false">http://www.libology.com/blog/?p=3117</guid>
		<description><![CDATA[TinEye is an image search engine with a twist:  you provide it with an image, and it returns a list of websites utilizing that image.
I can quickly think of a few really good uses of this service:

You have an image that you downloaded sometime in the past, but you don&#8217;t remember where you got it.
You [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://tineye.com/"><strong>TinEye</strong></a> is an image search engine with a twist:  you provide it with an image, and it returns a list of websites utilizing that image.</p>
<p>I can quickly think of a few really good uses of this service:</p>
<ul>
<li>You have an image that you downloaded sometime in the past, but you don&#8217;t remember where you got it.</li>
<li>You have found an image that would be perfect for a project, but you aren&#8217;t sure who the owner is, or what the usage terms might be.</li>
<li>You are the owner of an image, and want to ensure that it isn&#8217;t being mis-appropriated by others.</li>
<li>You have an image, and want to locate a site with a higher quality or different version of the image.</li>
</ul>
<p><em>found via a <a href="http://www.metafilter.com/83997/Plagarism-and-the-art-school">comment thread in MetaFilter</a></em></p>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.libology.com%2Fblog%2F2009%2F08%2F09%2Ftineye-reverse-image-search.html&amp;linkname=TinEye%20Reverse%20Image%20Search"><img src="http://www.libology.com/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.libology.com/blog/2009/08/09/tineye-reverse-image-search.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Copyfraud &#8211; Poisoning the Public Domain</title>
		<link>http://www.libology.com/blog/2009/07/16/copyfraud-poisoning-the-public-domain.html</link>
		<comments>http://www.libology.com/blog/2009/07/16/copyfraud-poisoning-the-public-domain.html#comments</comments>
		<pubDate>Thu, 16 Jul 2009 17:26:27 +0000</pubDate>
		<dc:creator>Rick Mason</dc:creator>
				<category><![CDATA[Archival]]></category>
		<category><![CDATA[Books]]></category>
		<category><![CDATA[Copyright]]></category>
		<category><![CDATA[Ethics]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[History]]></category>
		<category><![CDATA[Licensing]]></category>
		<category><![CDATA[Online Services]]></category>
		<category><![CDATA[Publishing]]></category>
		<category><![CDATA[copyfraud]]></category>
		<category><![CDATA[copyright law]]></category>
		<category><![CDATA[creative commons]]></category>
		<category><![CDATA[Project Gutenberg]]></category>
		<category><![CDATA[public domain]]></category>
		<category><![CDATA[Technology/Internet]]></category>

		<guid isPermaLink="false">http://www.libology.com/blog/?p=3095</guid>
		<description><![CDATA[Copyfraud : Poisoning the Public Domain is an introduction to some of the ways that content providers (websites, publishers, etc.) abuse copyright protections when they use public domain materials.  A couple of minor points, however:

The act of assigning a copyright to something already in the public domain is the issue; taking a Project Gutenberg text, [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.theregister.co.uk/2009/06/26/copyfraud/print.html"><strong>Copyfraud : Poisoning the Public Domain</strong></a> is an introduction to some of the ways that content providers (websites, publishers, etc.) abuse copyright protections when they use public domain materials.  A couple of minor points, however:</p>
<ul>
<li>The act of assigning a copyright to something already in the public domain is the issue; taking a <a href="http://www.gutenberg.org/wiki/Main_Page">Project Gutenberg</a> text, formatting it, and publishing it is of great benefit to people, as long as one doesn&#8217;t claim protection that doesn&#8217;t actually exist for the material.</li>
<li>The <a href="http://creativecommons.org/publicdomain/">Creative Commons Public Domain Tools</a> is not a license, nor is it  an attempt &#8220;to become the arbiter of  public domain licensing&#8221;, but a way to allow people to have an easy and effective way to display that a work belongs to the Public Domain.</li>
</ul>
<p><em>found via <a href="http://lisnews.org/copyfraud_poisoning_public_domain">LISNews</a> </em></p>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.libology.com%2Fblog%2F2009%2F07%2F16%2Fcopyfraud-poisoning-the-public-domain.html&amp;linkname=Copyfraud%20%26%238211%3B%20Poisoning%20the%20Public%20Domain"><img src="http://www.libology.com/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.libology.com/blog/2009/07/16/copyfraud-poisoning-the-public-domain.html/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>OCLC Withdraws Records Policy</title>
		<link>http://www.libology.com/blog/2009/06/29/oclc-withdraws-records-polic.html</link>
		<comments>http://www.libology.com/blog/2009/06/29/oclc-withdraws-records-polic.html#comments</comments>
		<pubDate>Mon, 29 Jun 2009 04:09:25 +0000</pubDate>
		<dc:creator>Rick Mason</dc:creator>
				<category><![CDATA[Books]]></category>
		<category><![CDATA[Cataloging]]></category>
		<category><![CDATA[Copyright]]></category>
		<category><![CDATA[Ethics]]></category>
		<category><![CDATA[Fair Use]]></category>
		<category><![CDATA[Groups]]></category>
		<category><![CDATA[Libraries]]></category>
		<category><![CDATA[Library 2.0]]></category>
		<category><![CDATA[Licensing]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[OCLC]]></category>
		<category><![CDATA[Online Computer Library Center]]></category>

		<guid isPermaLink="false">http://www.libology.com/blog/?p=3052</guid>
		<description><![CDATA[The Review Board on Principles of Shared Data Creation and Stewardship has released their final report on OCLC&#8217;s proposed policy for use of records (pdf), and after reviewing the report, OCLC has formally withdrawn the policy.
This conclusion to the records policy proposal is the best that could be imagined.  OCLC has listened to criticism from [...]]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://www.oclc.org/worldcat/catalog/policy/board/default.htm">Review Board on Principles of Shared Data Creation and Stewardship</a> has released their <strong><a href="http://www.oclc.org/worldcat/catalog/FinalReport_ReviewBoard.pdf">final report on OCLC&#8217;s proposed policy for use of records (pdf)</a>,</strong> and after reviewing the report, <a href="http://www.oclc.org/worldcat/catalog/policy/board/default.htm">OCLC has formally withdrawn the policy</a>.</p>
<p>This conclusion to the records policy proposal is the best that could be imagined.  OCLC has listened to criticism from the greater library community, considered both the policy and it&#8217;s criticism through the efforts of the Review Board, and has responded in a way that allows everyone to move forward with a greater understanding of how best to go about updating the policy.</p>
<p>I suggested early on that <a href="http://www.libology.com/blog/2008/11/03/oclc-proposed-policy-text.html">OCLC was a tiger, instinctively defending its territory</a>.  This still feels like a proper metaphor:  the movement towards creating a policy without proper input from the library community, and the subsequent review and withdrawing of the policy, seems more like an organization that didn&#8217;t realize the true implications of what it was putting in place, as opposed to one that was attempting a power grab to create a monopoly.</p>
<p>This was, and remains, a critical issue for libraries.  The ability to use the metadata representing our collections (as well as connecting them to collections and resources beyond what we own) is critical to our future ability to offer services in ways that will serve our patrons best.</p>
<p>I certainly hope that OCLC sets up a policy creation board similar to the review board &#8211; one that seeks a wide a range of ideas, opinion and input.  This will ensure a policy that takes a broader and more complete view of the use of cataloging records, but will also strengthen OCLC, because a membership organization is stronger when the constituent members are consistently heard and respected.  This has happened with the Review Board, and if OCLC continues to encourage it, everyone will come out ahead.</p>
<p><strong>To OCLC</strong>:  You have responded well, and in the process have created an opportunity to solidify your position as a membership organization.  Keep up the good work and you will benefit, along with your members.</p>
<p><strong>To the Review Board</strong>:  The report is well-written, and does an excellent job of stating what was wrong with the policy (and the process of creating the policy), as well as providing a constructive means to create a new policy that will properly reflect the needs and desires of the membership as a whole.</p>
<p><strong>To detractors of the policy</strong>:  Those who offered strong, but constructive, criticism deserve recognition.  This was an emotional debate, and keeping focused on the issues at hand has ultimately won the day.  The best, and most complete, resource of commentary and information is the <a href="http://wiki.code4lib.org/index.php/OCLC_Policy_Change"><strong>Code4Lib OCLC Policy Change</strong></a> page.</p>
<p>This has been an education for all involved:  the power of sustained commentary, of constructive criticism, of listening as well as talking, and of reviewing and changing positions when necessary.  Everyone should keep it up.</p>
<p><em>resources:  <a href="http://www.resourceshelf.com/2009/06/26/oclc-review-board-on-principles-of-shared-data-creation-and-stewardship-releases-final-report/">ResourceShelf</a> &amp; <a href="http://dltj.org/article/record-use-policy-withdrawn/">Disruptive Library Technology Jester</a></em></p>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.libology.com%2Fblog%2F2009%2F06%2F29%2Foclc-withdraws-records-polic.html&amp;linkname=OCLC%20Withdraws%20Records%20Policy"><img src="http://www.libology.com/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.libology.com/blog/2009/06/29/oclc-withdraws-records-polic.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Use It or Lose It</title>
		<link>http://www.libology.com/blog/2009/05/19/use-it-or-lose-it.html</link>
		<comments>http://www.libology.com/blog/2009/05/19/use-it-or-lose-it.html#comments</comments>
		<pubDate>Wed, 20 May 2009 02:07:14 +0000</pubDate>
		<dc:creator>Rick Mason</dc:creator>
				<category><![CDATA[Copyright]]></category>
		<category><![CDATA[Definitions]]></category>
		<category><![CDATA[Video]]></category>
		<category><![CDATA[American University]]></category>
		<category><![CDATA[Center for Social Media]]></category>
		<category><![CDATA[Fair Use]]></category>
		<category><![CDATA[mashup]]></category>
		<category><![CDATA[remix]]></category>

		<guid isPermaLink="false">http://www.libology.com/blog/?p=2971</guid>
		<description><![CDATA[The Center for Social Media at American University&#8217;s School of Communication has a PDF guide available for download titled Code of Best Practices in Fair Use for Online Video.
To both illustrate and promote the practices, they have just released a video called Remix Culture : Fair Use is Your Friend.

found via Lessig 2.0
]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://www.centerforsocialmedia.org/">Center for Social Media at American University&#8217;s School of Communication</a> has a PDF guide available for download titled <a href="http://www.centerforsocialmedia.org/files/pdf/online_best_practices_in_fair_use.pdf"><strong>Code of Best Practices in Fair Use for Online Video</strong></a>.</p>
<p style="text-align: left;">To both illustrate and promote the practices, they have just released a video called <a href="http://www.centerforsocialmedia.org/resources/publications/fair_use_in_online_video/">Remix Culture : Fair Use is Your Friend</a>.</p>
<p style="text-align: left;"><p><a href="http://www.libology.com/blog/2009/05/19/use-it-or-lose-it.html"><em>Click here to view the embedded video.</em></a></p></p>
<p style="text-align: left;"><em>found via <a href="http://www.lessig.org/blog/2009/05/remix_culture_they_say_fair_us.html">Lessig 2.0</a></em></p>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.libology.com%2Fblog%2F2009%2F05%2F19%2Fuse-it-or-lose-it.html&amp;linkname=Use%20It%20or%20Lose%20It"><img src="http://www.libology.com/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.libology.com/blog/2009/05/19/use-it-or-lose-it.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Copyright Law, Love and Hate</title>
		<link>http://www.libology.com/blog/2009/05/16/copyright-law-love-and-hate.html</link>
		<comments>http://www.libology.com/blog/2009/05/16/copyright-law-love-and-hate.html#comments</comments>
		<pubDate>Sat, 16 May 2009 19:32:24 +0000</pubDate>
		<dc:creator>Rick Mason</dc:creator>
				<category><![CDATA[Copyright]]></category>
		<category><![CDATA[Fair Use]]></category>
		<category><![CDATA[Libraries]]></category>
		<category><![CDATA[Publishing]]></category>
		<category><![CDATA[copyright law]]></category>
		<category><![CDATA[Cory Doctorow]]></category>
		<category><![CDATA[fan fiction]]></category>
		<category><![CDATA[Firefly]]></category>

		<guid isPermaLink="false">http://www.libology.com/blog/?p=2956</guid>
		<description><![CDATA[Cory Doctorow has an interesting take on the differing attitude of copyright between those who wish to wish to honor a creative work and those who wish to diminish it.  An excerpt:
&#8220;The upshot of this is that you&#8217;re on much more solid ground if you want to quote or otherwise reference a work for the [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.guardian.co.uk/technology/2009/may/13/cory-doctorow-copyright"><strong>Cory Doctorow has an interesting take</strong></a> on the differing attitude of copyright between those who wish to wish to honor a creative work and those who wish to diminish it.  An excerpt:</p>
<blockquote><p>&#8220;The upshot of this is that you&#8217;re on much more solid ground if you want to quote or otherwise reference a work for the purposes of rubbishing it than if you are doing so to celebrate it. This is one of the most perverse elements of copyright law: the reality that loving something doesn&#8217;t confer any right to make it a part of your creative life.&#8221;</p></blockquote>
<p>An added bonus is a reference to a <a href="http://en.wikipedia.org/wiki/Firefly_(TV_series)">Firefly</a>-based <a href="http://en.wikipedia.org/wiki/Fan_fiction">fan fiction</a> that I hadn&#8217;t encountered before, titled <a href="http://dreamcafe.com/firefly.html">My Own Kind of Freedom</a>.</p>
<p>found via <a href="http://www.tk421.net/librarylink/">Library Link of the Day</a> (16 May 2009)</p>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.libology.com%2Fblog%2F2009%2F05%2F16%2Fcopyright-law-love-and-hate.html&amp;linkname=Copyright%20Law%2C%20Love%20and%20Hate"><img src="http://www.libology.com/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.libology.com/blog/2009/05/16/copyright-law-love-and-hate.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Book Search Settlement Links</title>
		<link>http://www.libology.com/blog/2009/05/06/google-book-search-settlement-links.html</link>
		<comments>http://www.libology.com/blog/2009/05/06/google-book-search-settlement-links.html#comments</comments>
		<pubDate>Thu, 07 May 2009 02:27:42 +0000</pubDate>
		<dc:creator>Rick Mason</dc:creator>
				<category><![CDATA[Books]]></category>
		<category><![CDATA[Copyright]]></category>
		<category><![CDATA[Fair Use]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Government]]></category>
		<category><![CDATA[Libraries]]></category>
		<category><![CDATA[Library 2.0]]></category>
		<category><![CDATA[Online Services]]></category>
		<category><![CDATA[Publishing]]></category>
		<category><![CDATA[Google Books]]></category>
		<category><![CDATA[Peter Murray]]></category>

		<guid isPermaLink="false">http://www.libology.com/blog/?p=2934</guid>
		<description><![CDATA[Peter Murray has an incredibly good selection of links about the Google Book Search Settlement on the Disruptive Library Technology Jester blog.  Really.  Spend some time perusing them.
]]></description>
			<content:encoded><![CDATA[<p>Peter Murray has an <a href="http://dltj.org/article/gbs-summary/"><strong>incredibly good selection of links about the Google Book Search Settlement on the Disruptive Library Technology Jester blog</strong></a>.  Really.  Spend some time perusing them.</p>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.libology.com%2Fblog%2F2009%2F05%2F06%2Fgoogle-book-search-settlement-links.html&amp;linkname=Google%20Book%20Search%20Settlement%20Links"><img src="http://www.libology.com/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.libology.com/blog/2009/05/06/google-book-search-settlement-links.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Stupid Disclaimer</title>
		<link>http://www.libology.com/blog/2009/04/24/stupid-disclaimer.html</link>
		<comments>http://www.libology.com/blog/2009/04/24/stupid-disclaimer.html#comments</comments>
		<pubDate>Fri, 24 Apr 2009 16:56:32 +0000</pubDate>
		<dc:creator>Rick Mason</dc:creator>
				<category><![CDATA[Copyright]]></category>
		<category><![CDATA[Language]]></category>
		<category><![CDATA[WebSearch]]></category>
		<category><![CDATA[copyfraud]]></category>
		<category><![CDATA[disclaimer]]></category>
		<category><![CDATA[general public communication]]></category>
		<category><![CDATA[internet search]]></category>
		<category><![CDATA[legal]]></category>

		<guid isPermaLink="false">http://www.libology.com/blog/?p=2921</guid>
		<description><![CDATA[A brief rant, if you will accomodate me for a moment:
I encountered a disclaimer in an e-mail that strikes me as extreme enough to mention:
This email, and any attachment, is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, copying, dissemination or [...]]]></description>
			<content:encoded><![CDATA[<p>A brief rant, if you will accomodate me for a moment:</p>
<p>I encountered a disclaimer in an e-mail that strikes me as extreme enough to mention:</p>
<blockquote><p>This email, and any attachment, is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, copying, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited.</p></blockquote>
<p>This came as part of a response from a company I had asked about the availability of an item.  Note that, by a strict interpretation of the statement, only the specific recipient of the message can use the information contained within.  If the e-mail had been from the company&#8217;s legal department, or if it hadn&#8217;t been about a product with a great deal of publicity and interest, there might have been some justification.</p>
<p>I know that legal boilerplate such as this seems to go along with incorporation, and that many of the employees of this company must stifle a groan every time they send information on their products, but these statements can be worded in such a way that they don&#8217;t throw a giant blanket of silence over simple sale information.  Or, perhaps, the statement can be reserved for those departments that handle legal, fiscal, and personnel matters, and a &#8220;lighter&#8221; disclaimer be used for general public communication.</p>
<p>This is something that falls into the same general category as <a href="http://www.libology.com/blog/2008/01/30/copyfraud.html">Copyfraud</a>, in that it attempts to place a much stronger restriction on something that doesn&#8217;t legally deserve it.</p>
<p>Or am I supposed to take the information about whether a particular item is available for sale to the grave?</p>
<p><em>My own disclaimer:  I changed the language of the disclaimer a tad, even though a quick internet search revealed several companies using the same wording as the e-mail.</em></p>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.libology.com%2Fblog%2F2009%2F04%2F24%2Fstupid-disclaimer.html&amp;linkname=Stupid%20Disclaimer"><img src="http://www.libology.com/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.libology.com/blog/2009/04/24/stupid-disclaimer.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
