<?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"
	>
<channel>
	<title>Comments on: Attributor&#8217;s Recipe for Inflated Copyright Claims: Not All Copying Is Infringement</title>
	<atom:link href="http://wendy.seltzer.org/blog/archives/2007/10/16/attributors-recipe-for-inflated-copyright-claims-not-all-copying-is-infringement.html/feed" rel="self" type="application/rss+xml" />
	<link>http://wendy.seltzer.org/blog/archives/2007/10/16/attributors-recipe-for-inflated-copyright-claims-not-all-copying-is-infringement.html</link>
	<description>Musings of a techie lawyer</description>
	<pubDate>Mon, 01 Dec 2008 19:03:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7-bleeding</generator>
		<item>
		<title>By: Rich Pearson</title>
		<link>http://wendy.seltzer.org/blog/archives/2007/10/16/attributors-recipe-for-inflated-copyright-claims-not-all-copying-is-infringement.html#comment-1638</link>
		<dc:creator>Rich Pearson</dc:creator>
		<pubDate>Thu, 18 Oct 2007 17:29:28 +0000</pubDate>
		<guid isPermaLink="false">http://wendy.seltzer.org/blog/archives/2007/10/16/attributors-recipe-for-inflated-copyright-claims-not-all-copying-is-infringement.html#comment-1638</guid>
		<description>Mike - I agree, there is no legal liability but it calls into question their "Don't be evil" mantra :-)</description>
		<content:encoded><![CDATA[<p>Mike - I agree, there is no legal liability but it calls into question their &#8220;Don&#8217;t be evil&#8221; mantra :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://wendy.seltzer.org/blog/archives/2007/10/16/attributors-recipe-for-inflated-copyright-claims-not-all-copying-is-infringement.html#comment-1637</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Thu, 18 Oct 2007 14:56:09 +0000</pubDate>
		<guid isPermaLink="false">http://wendy.seltzer.org/blog/archives/2007/10/16/attributors-recipe-for-inflated-copyright-claims-not-all-copying-is-infringement.html#comment-1637</guid>
		<description>Rich--

You're saying the content could still surface in a Google search but they shouldn't allow the pages to use AdSense?

I'm not saying these pages (bellook at least, publisherswiki is down) aren't contemptible -- I'm just saying I don't think Google has a *legal* liability here.

Thanks,
Mike</description>
		<content:encoded><![CDATA[<p>Rich&#8211;</p>
<p>You&#8217;re saying the content could still surface in a Google search but they shouldn&#8217;t allow the pages to use AdSense?</p>
<p>I&#8217;m not saying these pages (bellook at least, publisherswiki is down) aren&#8217;t contemptible &#8212; I&#8217;m just saying I don&#8217;t think Google has a *legal* liability here.</p>
<p>Thanks,<br />
Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich Pearson</title>
		<link>http://wendy.seltzer.org/blog/archives/2007/10/16/attributors-recipe-for-inflated-copyright-claims-not-all-copying-is-infringement.html#comment-1631</link>
		<dc:creator>Rich Pearson</dc:creator>
		<pubDate>Thu, 18 Oct 2007 04:39:39 +0000</pubDate>
		<guid isPermaLink="false">http://wendy.seltzer.org/blog/archives/2007/10/16/attributors-recipe-for-inflated-copyright-claims-not-all-copying-is-infringement.html#comment-1631</guid>
		<description>Mike,

I think you are referring to our Oct 1st blog post - http://attributor.com/blog/?p=21 - and may have misread our intent.  Let me explain our view and see if it changes your interpretation.

We believe that when an infringement is found, Google needs to do more than just pull the content from YouTube - they need to also remove the host page from the Google index so that the infringing party can't continue to make money via Adwords.

To illustrate how automated and widespread content theft has become, I found a few pages that have taken the lead paragraph from Jennifer's Recipe story and surrounded it with Google AdSense links.  

http://www.bellook.com/food/study-finds-copyright-infringement-of-recipes-online-gigalawcom-7.html

http://publisherswiki.com/?p=5231

From the data we've seen so far, this is the tip of iceberg - these pages are automatically created and done so to rank highly in search engines.  When you consider that Google makes a money off of every click on these ads, two questions come to mind:
1) How much of Google's $5b+ AdSense revenue is on the backs of this theft and 
2) How much traffic/notoriety/revenue is being siphoned off the content creators? 
 
I hope that helps,

Rich</description>
		<content:encoded><![CDATA[<p>Mike,</p>
<p>I think you are referring to our Oct 1st blog post - <a href="http://attributor.com/blog/?p=21" rel="nofollow">http://attributor.com/blog/?p=21</a> - and may have misread our intent.  Let me explain our view and see if it changes your interpretation.</p>
<p>We believe that when an infringement is found, Google needs to do more than just pull the content from YouTube - they need to also remove the host page from the Google index so that the infringing party can&#8217;t continue to make money via Adwords.</p>
<p>To illustrate how automated and widespread content theft has become, I found a few pages that have taken the lead paragraph from Jennifer&#8217;s Recipe story and surrounded it with Google AdSense links.  </p>
<p><a href="http://www.bellook.com/food/study-finds-copyright-infringement-of-recipes-online-gigalawcom-7.html" rel="nofollow">http://www.bellook.com/food/study-finds-copyright-infringement-of-recipes-online-gigalawcom-7.html</a></p>
<p><a href="http://publisherswiki.com/?p=5231" rel="nofollow">http://publisherswiki.com/?p=5231</a></p>
<p>From the data we&#8217;ve seen so far, this is the tip of iceberg - these pages are automatically created and done so to rank highly in search engines.  When you consider that Google makes a money off of every click on these ads, two questions come to mind:<br />
1) How much of Google&#8217;s $5b+ AdSense revenue is on the backs of this theft and<br />
2) How much traffic/notoriety/revenue is being siphoned off the content creators? </p>
<p>I hope that helps,</p>
<p>Rich</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://wendy.seltzer.org/blog/archives/2007/10/16/attributors-recipe-for-inflated-copyright-claims-not-all-copying-is-infringement.html#comment-1590</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Wed, 17 Oct 2007 21:35:58 +0000</pubDate>
		<guid isPermaLink="false">http://wendy.seltzer.org/blog/archives/2007/10/16/attributors-recipe-for-inflated-copyright-claims-not-all-copying-is-infringement.html#comment-1590</guid>
		<description>If you read their blog, Attributor seems to take a stance that Google shouldn't even surface search results containing "stolen" copyrighted materials as Google sells advertising against its search results. It also seems to say that Google shouldn't allow Adwords on any page that might contain copyrighted data.

Rich, if you're still reading this board, could you comment on my interpretation? Attributor's stance seems legally shaky, but I may have misread your blogs intent.</description>
		<content:encoded><![CDATA[<p>If you read their blog, Attributor seems to take a stance that Google shouldn&#8217;t even surface search results containing &#8220;stolen&#8221; copyrighted materials as Google sells advertising against its search results. It also seems to say that Google shouldn&#8217;t allow Adwords on any page that might contain copyrighted data.</p>
<p>Rich, if you&#8217;re still reading this board, could you comment on my interpretation? Attributor&#8217;s stance seems legally shaky, but I may have misread your blogs intent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich Pearson</title>
		<link>http://wendy.seltzer.org/blog/archives/2007/10/16/attributors-recipe-for-inflated-copyright-claims-not-all-copying-is-infringement.html#comment-1582</link>
		<dc:creator>Rich Pearson</dc:creator>
		<pubDate>Wed, 17 Oct 2007 14:24:46 +0000</pubDate>
		<guid isPermaLink="false">http://wendy.seltzer.org/blog/archives/2007/10/16/attributors-recipe-for-inflated-copyright-claims-not-all-copying-is-infringement.html#comment-1582</guid>
		<description>Wendy - we seem to be in sync.  Attributor's platform provides the visibility and the content creator decides if or how to act.</description>
		<content:encoded><![CDATA[<p>Wendy - we seem to be in sync.  Attributor&#8217;s platform provides the visibility and the content creator decides if or how to act.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wseltzer</title>
		<link>http://wendy.seltzer.org/blog/archives/2007/10/16/attributors-recipe-for-inflated-copyright-claims-not-all-copying-is-infringement.html#comment-1580</link>
		<dc:creator>wseltzer</dc:creator>
		<pubDate>Wed, 17 Oct 2007 12:05:59 +0000</pubDate>
		<guid isPermaLink="false">http://wendy.seltzer.org/blog/archives/2007/10/16/attributors-recipe-for-inflated-copyright-claims-not-all-copying-is-infringement.html#comment-1580</guid>
		<description>Thanks Rich, 
I'm still not completely on-board.  Someone might intentionally copy, word-for-word, a procedural description of the steps to bake a cake, and yet commit no infringement.  The initial poster might prefer a link back, but there's no legal obligation to offer one.  

If your tools are simply noting these occurrences, fine, but if you're suggesting legal threats or implying that there would be legal consequences based on "copying," I think you're assuming too much.

--Wendy</description>
		<content:encoded><![CDATA[<p>Thanks Rich,<br />
I&#8217;m still not completely on-board.  Someone might intentionally copy, word-for-word, a procedural description of the steps to bake a cake, and yet commit no infringement.  The initial poster might prefer a link back, but there&#8217;s no legal obligation to offer one.  </p>
<p>If your tools are simply noting these occurrences, fine, but if you&#8217;re suggesting legal threats or implying that there would be legal consequences based on &#8220;copying,&#8221; I think you&#8217;re assuming too much.</p>
<p>&#8211;Wendy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich Pearson</title>
		<link>http://wendy.seltzer.org/blog/archives/2007/10/16/attributors-recipe-for-inflated-copyright-claims-not-all-copying-is-infringement.html#comment-1551</link>
		<dc:creator>Rich Pearson</dc:creator>
		<pubDate>Wed, 17 Oct 2007 01:25:34 +0000</pubDate>
		<guid isPermaLink="false">http://wendy.seltzer.org/blog/archives/2007/10/16/attributors-recipe-for-inflated-copyright-claims-not-all-copying-is-infringement.html#comment-1551</guid>
		<description>Hi Wendy,

I work for Attributor and helped put together the study.  You can get a little more context for our study on the Attributor blog - "A link is worth 1,000 words" - while I can't say that we found all derivative works, we tried to pull these out of the totals that we shared with Jenifer Guevin.

You are absolutely correct about recipes being a tough category to quantify the amount of copying.   Like you, we were skeptical of the initial results, but when we looked at the details, we were surprised to find so many word-for-word copies.  Digging deeper, we found that most of these sites failed to link back or give attribution to the source.  

I'm sure some of the copying was done unintentionally and without malice - our goal is to give rights holders visibility into how and where their content is being copied plus a set of flexible set of remedies such as sending a link request as we noted in our blog. 

I'd be happy to get your feedback and answer any questions you have about our service.

Rich</description>
		<content:encoded><![CDATA[<p>Hi Wendy,</p>
<p>I work for Attributor and helped put together the study.  You can get a little more context for our study on the Attributor blog - &#8220;A link is worth 1,000 words&#8221; - while I can&#8217;t say that we found all derivative works, we tried to pull these out of the totals that we shared with Jenifer Guevin.</p>
<p>You are absolutely correct about recipes being a tough category to quantify the amount of copying.   Like you, we were skeptical of the initial results, but when we looked at the details, we were surprised to find so many word-for-word copies.  Digging deeper, we found that most of these sites failed to link back or give attribution to the source.  </p>
<p>I&#8217;m sure some of the copying was done unintentionally and without malice - our goal is to give rights holders visibility into how and where their content is being copied plus a set of flexible set of remedies such as sending a link request as we noted in our blog. </p>
<p>I&#8217;d be happy to get your feedback and answer any questions you have about our service.</p>
<p>Rich</p>
]]></content:encoded>
	</item>
</channel>
</rss>
