13.07.2015 Views

Advanced Copyright Issues on the Internet - Fenwick & West LLP

Advanced Copyright Issues on the Internet - Fenwick & West LLP

Advanced Copyright Issues on the Internet - Fenwick & West LLP

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

such as up<strong>on</strong> payment of a fee or provisi<strong>on</strong>s of a password, permit access to <strong>the</strong> cachedinformati<strong>on</strong> “in significant part” 1771 <strong>on</strong>ly up<strong>on</strong> <strong>the</strong> same c<strong>on</strong>diti<strong>on</strong>s; and (v) resp<strong>on</strong>dexpeditiously to remove or disable access to any cached informati<strong>on</strong> up<strong>on</strong> receipt of notice thatsuch informati<strong>on</strong> has been removed or disabled from <strong>the</strong> originating site (or ordered by a court tobe removed) from which <strong>the</strong> informati<strong>on</strong> was cached.a. Field v. Google. The facts of <strong>the</strong> case of Field v.Google 1772 are set forth in Secti<strong>on</strong> III.B.4(a) above. In that case, <strong>the</strong> court ruled that Google wasentitled to <strong>the</strong> Secti<strong>on</strong> 512(b) safe harbor for its activities of caching web sites through its Webcrawler known as <strong>the</strong> “Googlebot” and making <strong>the</strong> cached copies of particular pages availablefor download directly from Google’s computers by end users clicking <strong>on</strong> <strong>the</strong> “Cached” link to aweb page c<strong>on</strong>tained in search results returned by Google’s search engine.The court rejected a number of arguments by <strong>the</strong> plaintiff, Field, c<strong>on</strong>cerning why Googleshould not be entitled to <strong>the</strong> Secti<strong>on</strong> 512(b) safe harbor. First, Field c<strong>on</strong>tended that, in operatingits cache, Google did not make “intermediate and temporary storage” of <strong>the</strong> cached material, asrequired by Secti<strong>on</strong> 412(b)(1). The court cited <strong>the</strong> Ellis<strong>on</strong> v. Roberts<strong>on</strong> case, 1773 involving <strong>the</strong>Secti<strong>on</strong> 512(a) safe harbor, which ruled that AOL’s storage of Usenet postings for about 14 dayswas both “intermediate” and “transient” as required by Secti<strong>on</strong> 512(a). Analogizing to that case,<strong>the</strong> court noted that <strong>the</strong> copy of Web pages Google stored in its cache were present forapproximately 14 to 20 days. The court found that this period was sufficiently short to bedeemed “temporary” under Secti<strong>on</strong> 512(b). 1774In a significant aspect of its ruling, <strong>the</strong> court also implicitly held that, to qualify for <strong>the</strong>Secti<strong>on</strong> 512(b) safe harbor, <strong>the</strong> caching need not be d<strong>on</strong>e <strong>on</strong>ly after a user has made an initialrequest for <strong>the</strong> materials being cached, but could be d<strong>on</strong>e in anticipati<strong>on</strong> of user requests for <strong>the</strong>materials: “Like AOL’s repository of Usenet postings in Ellis<strong>on</strong> which operated between <strong>the</strong>individuals posting informati<strong>on</strong> and <strong>the</strong> users requesting it, Google’s cache is a repository ofmaterial that operates between <strong>the</strong> individual posting <strong>the</strong> informati<strong>on</strong>, and <strong>the</strong> end-userrequesting it.” 1775Field also c<strong>on</strong>tended that Google’s cache did not satisfy <strong>the</strong> requirements of Secti<strong>on</strong>512(b)(1)(B) that <strong>the</strong> material in questi<strong>on</strong> be transmitted from <strong>the</strong> pers<strong>on</strong> who makes it available<strong>on</strong>line, here <strong>the</strong> plaintiff, to a pers<strong>on</strong> o<strong>the</strong>r than himself, at <strong>the</strong> directi<strong>on</strong> of <strong>the</strong> o<strong>the</strong>r pers<strong>on</strong>. 1776The court rejected this argument: “Field transmitted <strong>the</strong> material in questi<strong>on</strong>, <strong>the</strong> pages of hisWeb site, to Google’s Googlebot at Google’s request. Google is a pers<strong>on</strong> o<strong>the</strong>r than Field.1771 This language appears to have been inserted in recogniti<strong>on</strong> of <strong>the</strong> fact that hackers or o<strong>the</strong>rs may be able tocircumvent such restricti<strong>on</strong>s <strong>on</strong> access without knowledge of <strong>the</strong> Service Provider. Id. at 7.1772 412 F. Supp. 2d 1106 (D. Nev. 2006).1773 357 F.3d 1072, 1081 (9 th Cir. 2004).1774 Field v. Google, 412 F. Supp. 2d at 1124.1775 Id.1776 Id.- 386 -

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!