<?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: Contractual Control over Information Goods after ML Genius v. Google (Guest Blog Post)	</title>
	<atom:link href="https://blog.ericgoldman.org/archives/2023/07/contractual-control-over-information-goods-after-ml-genius-v-google-guest-blog-post.htm/feed" rel="self" type="application/rss+xml" />
	<link>https://blog.ericgoldman.org/archives/2023/07/contractual-control-over-information-goods-after-ml-genius-v-google-guest-blog-post.htm</link>
	<description></description>
	<lastBuildDate>Wed, 19 Jul 2023 17:58:00 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: John_Levine		</title>
		<link>https://blog.ericgoldman.org/archives/2023/07/contractual-control-over-information-goods-after-ml-genius-v-google-guest-blog-post.htm#comment-3970</link>

		<dc:creator><![CDATA[John_Levine]]></dc:creator>
		<pubDate>Wed, 19 Jul 2023 17:58:00 +0000</pubDate>
		<guid isPermaLink="false">https://blog.ericgoldman.org/?p=25307#comment-3970</guid>

					<description><![CDATA[Seems to me that browsewrap is problematic if a site is being scraped by a machine, rather than read by a person, since machines have no idea what might look obvious to a person. Back in 2006 in &lt;i&gt;Field vs. Google&lt;/i&gt;, the court agreed with our theory that the web cache wasn&#039;t infringing, in large part because machines can and do use ROBOTS.TXT to opt out from the cache and index. Genius is arguing that yes, you can read our site to index it but not to do other stuff, and there is at least at this point, no mechanical way to say that.
Given all of the arguments about scraping for LLM training, it would be a good idea for the industry to extend the robots convention to declare some categories of permission, e.g., indexing vs. other stuff.]]></description>
			<content:encoded><![CDATA[<p>Seems to me that browsewrap is problematic if a site is being scraped by a machine, rather than read by a person, since machines have no idea what might look obvious to a person. Back in 2006 in <i>Field vs. Google</i>, the court agreed with our theory that the web cache wasn&#8217;t infringing, in large part because machines can and do use ROBOTS.TXT to opt out from the cache and index. Genius is arguing that yes, you can read our site to index it but not to do other stuff, and there is at least at this point, no mechanical way to say that.<br />
Given all of the arguments about scraping for LLM training, it would be a good idea for the industry to extend the robots convention to declare some categories of permission, e.g., indexing vs. other stuff.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
