<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Yet another reason for (cc) licenses in RSS feeds</title>
	<atom:link href="http://blogs.law.harvard.edu/palfrey/2003/07/11/yet-another-reason-for-cc-licenses-in-rss-feeds/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/palfrey/2003/07/11/yet-another-reason-for-cc-licenses-in-rss-feeds/</link>
	<description>From the Berkman Center at Harvard Law School</description>
	<lastBuildDate>Wed, 18 Nov 2009 13:34:17 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Etiquette Manners Miss</title>
		<link>http://blogs.law.harvard.edu/palfrey/2003/07/11/yet-another-reason-for-cc-licenses-in-rss-feeds/comment-page-1/#comment-167</link>
		<dc:creator>Etiquette Manners Miss</dc:creator>
		<pubDate>Mon, 03 Oct 2005 17:10:38 +0000</pubDate>
		<guid isPermaLink="false">http://clem.law.harvard.edu/jpalfrey/2003/07/11/yet-another-reason-for-cc-licenses-in#comment-167</guid>
		<description>&lt;a&gt;&lt;/a&gt;

Manners Southern</description>
		<content:encoded><![CDATA[<p><a></a></p>
<p>Manners Southern</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Monster In Law</title>
		<link>http://blogs.law.harvard.edu/palfrey/2003/07/11/yet-another-reason-for-cc-licenses-in-rss-feeds/comment-page-1/#comment-163</link>
		<dc:creator>Monster In Law</dc:creator>
		<pubDate>Mon, 19 Sep 2005 15:40:39 +0000</pubDate>
		<guid isPermaLink="false">http://clem.law.harvard.edu/jpalfrey/2003/07/11/yet-another-reason-for-cc-licenses-in#comment-163</guid>
		<description>&lt;a&gt;&lt;/a&gt;

Murphys Law</description>
		<content:encoded><![CDATA[<p><a></a></p>
<p>Murphys Law</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cell Phone Plan</title>
		<link>http://blogs.law.harvard.edu/palfrey/2003/07/11/yet-another-reason-for-cc-licenses-in-rss-feeds/comment-page-1/#comment-161</link>
		<dc:creator>Cell Phone Plan</dc:creator>
		<pubDate>Thu, 15 Sep 2005 17:49:59 +0000</pubDate>
		<guid isPermaLink="false">http://clem.law.harvard.edu/jpalfrey/2003/07/11/yet-another-reason-for-cc-licenses-in#comment-161</guid>
		<description>&lt;a&gt;&lt;/a&gt;

Used Cellular Phone</description>
		<content:encoded><![CDATA[<p><a></a></p>
<p>Used Cellular Phone</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Logo Subway</title>
		<link>http://blogs.law.harvard.edu/palfrey/2003/07/11/yet-another-reason-for-cc-licenses-in-rss-feeds/comment-page-1/#comment-131</link>
		<dc:creator>Logo Subway</dc:creator>
		<pubDate>Wed, 31 Aug 2005 16:56:36 +0000</pubDate>
		<guid isPermaLink="false">http://clem.law.harvard.edu/jpalfrey/2003/07/11/yet-another-reason-for-cc-licenses-in#comment-131</guid>
		<description>&lt;a&gt;&lt;/a&gt;

Logo Subway</description>
		<content:encoded><![CDATA[<p><a></a></p>
<p>Logo Subway</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: miglena</title>
		<link>http://blogs.law.harvard.edu/palfrey/2003/07/11/yet-another-reason-for-cc-licenses-in-rss-feeds/comment-page-1/#comment-123</link>
		<dc:creator>miglena</dc:creator>
		<pubDate>Fri, 19 Aug 2005 00:46:45 +0000</pubDate>
		<guid isPermaLink="false">http://clem.law.harvard.edu/jpalfrey/2003/07/11/yet-another-reason-for-cc-licenses-in#comment-123</guid>
		<description>&lt;a&gt;&lt;/a&gt;

News on every hour. http://www.bignews.com</description>
		<content:encoded><![CDATA[<p><a></a></p>
<p>News on every hour. <a href="http://www.bignews.com" rel="nofollow">http://www.bignews.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jam</title>
		<link>http://blogs.law.harvard.edu/palfrey/2003/07/11/yet-another-reason-for-cc-licenses-in-rss-feeds/comment-page-1/#comment-293</link>
		<dc:creator>jam</dc:creator>
		<pubDate>Sun, 13 Jul 2003 16:54:38 +0000</pubDate>
		<guid isPermaLink="false">http://clem.law.harvard.edu/jpalfrey/2003/07/11/yet-another-reason-for-cc-licenses-in#comment-293</guid>
		<description>&lt;a&gt;&lt;/a&gt;

I have had some further thoughts on this (after going back to the definitions in the statute) which I&#039;ve &lt;a href=&quot;http://www.freeroller.net/page/jam/20030713&quot;&gt;posted to Jam Today&lt;/a&gt;.  I&#039;ve not convinced myself either way on Blogger #1&#039;s copyright at the point when Blogger #2 allegedly infringes.  The reproduction on Blogger #2&#039;s page shouldn&#039;t be relied on to establish Blogger #1&#039;s copyright because it&#039;s unauthorized.</description>
		<content:encoded><![CDATA[<p><a></a></p>
<p>I have had some further thoughts on this (after going back to the definitions in the statute) which I&#8217;ve <a href="http://www.freeroller.net/page/jam/20030713">posted to Jam Today</a>.  I&#8217;ve not convinced myself either way on Blogger #1&#8217;s copyright at the point when Blogger #2 allegedly infringes.  The reproduction on Blogger #2&#8217;s page shouldn&#8217;t be relied on to establish Blogger #1&#8217;s copyright because it&#8217;s unauthorized.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Palfrey</title>
		<link>http://blogs.law.harvard.edu/palfrey/2003/07/11/yet-another-reason-for-cc-licenses-in-rss-feeds/comment-page-1/#comment-292</link>
		<dc:creator>John Palfrey</dc:creator>
		<pubDate>Sat, 12 Jul 2003 16:58:51 +0000</pubDate>
		<guid isPermaLink="false">http://clem.law.harvard.edu/jpalfrey/2003/07/11/yet-another-reason-for-cc-licenses-in#comment-292</guid>
		<description>&lt;a&gt;&lt;/a&gt;

To Bill Brown&#039;s question: How is the (c) assertion being made by someone who doesn&#039;t hold the (c)?  Isn&#039;t Blogger #1 clearly the (c) holder, at least in my hypo?

Jam&#039;s comment is a cool one, but I&#039;m not sure where that would end: is there no (c) on the Net just because it&#039;s so easy to change content quickly and frequently?  Just because it might be edited doesn&#039;t make it unfinished, does it?  And then once, at the end of the day or whenever it is forever done, reproduction persists, possibly every time someone accesses Blogger #2&#039;s page.  The &quot;fixed in a final form&quot; problem seems implausible as a means of undermining the original (c) interest here, as intriguing as the idea is.</description>
		<content:encoded><![CDATA[<p><a></a></p>
<p>To Bill Brown&#8217;s question: How is the (c) assertion being made by someone who doesn&#8217;t hold the (c)?  Isn&#8217;t Blogger #1 clearly the (c) holder, at least in my hypo?</p>
<p>Jam&#8217;s comment is a cool one, but I&#8217;m not sure where that would end: is there no (c) on the Net just because it&#8217;s so easy to change content quickly and frequently?  Just because it might be edited doesn&#8217;t make it unfinished, does it?  And then once, at the end of the day or whenever it is forever done, reproduction persists, possibly every time someone accesses Blogger #2&#8217;s page.  The &#8220;fixed in a final form&#8221; problem seems implausible as a means of undermining the original (c) interest here, as intriguing as the idea is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jam</title>
		<link>http://blogs.law.harvard.edu/palfrey/2003/07/11/yet-another-reason-for-cc-licenses-in-rss-feeds/comment-page-1/#comment-291</link>
		<dc:creator>jam</dc:creator>
		<pubDate>Sat, 12 Jul 2003 01:33:15 +0000</pubDate>
		<guid isPermaLink="false">http://clem.law.harvard.edu/jpalfrey/2003/07/11/yet-another-reason-for-cc-licenses-in#comment-291</guid>
		<description>&lt;a&gt;&lt;/a&gt;

Does &quot;fixed in final form&quot; apply here?  Is something that&#039;s in process of editing, even if the editing is done in public, as it were, fixed in final form?  If not, does copyright inhere?  Does the existence of copyright notices affect whether copyright inheres?

I don&#039;t know the answer to these questions (although I believe the answer to the last is &quot;No.&quot;) .</description>
		<content:encoded><![CDATA[<p><a></a></p>
<p>Does &#8220;fixed in final form&#8221; apply here?  Is something that&#8217;s in process of editing, even if the editing is done in public, as it were, fixed in final form?  If not, does copyright inhere?  Does the existence of copyright notices affect whether copyright inheres?</p>
<p>I don&#8217;t know the answer to these questions (although I believe the answer to the last is &#8220;No.&#8221;) .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Brown</title>
		<link>http://blogs.law.harvard.edu/palfrey/2003/07/11/yet-another-reason-for-cc-licenses-in-rss-feeds/comment-page-1/#comment-290</link>
		<dc:creator>Bill Brown</dc:creator>
		<pubDate>Fri, 11 Jul 2003 23:48:55 +0000</pubDate>
		<guid isPermaLink="false">http://clem.law.harvard.edu/jpalfrey/2003/07/11/yet-another-reason-for-cc-licenses-in#comment-290</guid>
		<description>&lt;a&gt;&lt;/a&gt;

Also, the quotations are cited as such by &lt;a href=&quot;http://www.diveintomark.org/ww/&quot;&gt;Blogger #2&lt;/a&gt;, the work is quite transformative, doesn&#039;t diminish the market value of &lt;a href=&quot;http://www.scripting.com/&quot;&gt;Blogger #1&lt;/a&gt;&#039;s work, and serves as criticism of the copyrighted work.

Finally, the copyright assertion is being made by someone other than the copyright holder.

It seems like a pretty clear-cut instance of fair use.</description>
		<content:encoded><![CDATA[<p><a></a></p>
<p>Also, the quotations are cited as such by <a href="http://www.diveintomark.org/ww/">Blogger #2</a>, the work is quite transformative, doesn&#8217;t diminish the market value of <a href="http://www.scripting.com/">Blogger #1</a>&#8217;s work, and serves as criticism of the copyrighted work.</p>
<p>Finally, the copyright assertion is being made by someone other than the copyright holder.</p>
<p>It seems like a pretty clear-cut instance of fair use.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Bernstein</title>
		<link>http://blogs.law.harvard.edu/palfrey/2003/07/11/yet-another-reason-for-cc-licenses-in-rss-feeds/comment-page-1/#comment-289</link>
		<dc:creator>Michael Bernstein</dc:creator>
		<pubDate>Fri, 11 Jul 2003 20:44:59 +0000</pubDate>
		<guid isPermaLink="false">http://clem.law.harvard.edu/jpalfrey/2003/07/11/yet-another-reason-for-cc-licenses-in#comment-289</guid>
		<description>&lt;a&gt;&lt;/a&gt;

IANAL.

In this case, Blogger #2 is excerpting and reproducing the edited postings only in full, with highlghting to show their differences, for purposes of non-commercial commentary.

The &#039;unit of work&#039; question is a tough call in this instance. It would be easier to decide that each posting was an individual work if they appeared on their own page, and were all longer than a single paragraph. As it is, it can be argued that the individual postings are only part of a larger work, both on the page and in the syndication feed (though they are part of different larger works. The feed will not map exactly to a single page at any time). To my mind, in this case, selecting some postings and not others qualifies as excerpting.</description>
		<content:encoded><![CDATA[<p><a></a></p>
<p>IANAL.</p>
<p>In this case, Blogger #2 is excerpting and reproducing the edited postings only in full, with highlghting to show their differences, for purposes of non-commercial commentary.</p>
<p>The &#8216;unit of work&#8217; question is a tough call in this instance. It would be easier to decide that each posting was an individual work if they appeared on their own page, and were all longer than a single paragraph. As it is, it can be argued that the individual postings are only part of a larger work, both on the page and in the syndication feed (though they are part of different larger works. The feed will not map exactly to a single page at any time). To my mind, in this case, selecting some postings and not others qualifies as excerpting.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
