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.

that <strong>the</strong> page should not be cached or archived. When <strong>the</strong> Googlebot visited a page, it wouldsearch for meta-tags in <strong>the</strong> HTML of <strong>the</strong> page and obey <strong>the</strong>m. 1101The sec<strong>on</strong>d mechanism by which Web site owners could communicate with searchengines’ robots was by placing a “robots.txt” file <strong>on</strong> <strong>the</strong> Web site c<strong>on</strong>taining textual instructi<strong>on</strong>sc<strong>on</strong>cerning whe<strong>the</strong>r crawling of <strong>the</strong> site was allowed. If <strong>the</strong> Googlebot encountered a robots.txtfile with a command disallowing crawling, it would not crawl <strong>the</strong> Web site, and <strong>the</strong>re would<strong>the</strong>refore be no entries for that Web site in Google’s search results and no “Cached” links. Thecourt noted that <strong>the</strong> <strong>Internet</strong> industry had widely recognized <strong>the</strong> robots.txt file as a standard forc<strong>on</strong>trolling automated access to Web pages since 1994. 1102In <strong>the</strong> court’s words, Field decided to “manufacture a claim for copyright infringementagainst Google in <strong>the</strong> hopes of making m<strong>on</strong>ey from Google’s standard practice” 1103 of cachingby placing his copyrighted works <strong>on</strong> a Web site available to <strong>the</strong> public for free and creating arobots.txt file <strong>on</strong> <strong>the</strong> site with <strong>the</strong> permissi<strong>on</strong>s set within <strong>the</strong> file to allow all robots to visit andindex all of <strong>the</strong> pages <strong>on</strong> <strong>the</strong> site, knowing that this would cause <strong>the</strong> Googlebot to cache hiscopyrighted works. Field testified in his depositi<strong>on</strong> that he had c<strong>on</strong>sciously chosen not to use <strong>the</strong>NOARCHIVE meta-tag <strong>on</strong> his Web site. When Google learned that Field had filed (but notserved) a complaint for copyright infringement, Google promptly removed <strong>the</strong> “Cached” links toall of <strong>the</strong> pages <strong>on</strong> his site. 1104Field alleged <strong>on</strong>ly claims of direct copyright infringement against Google (and made noclaims for c<strong>on</strong>tributory or vicarious liability), asserting that Google directly infringed hiscopyrights when a Google user clicked <strong>on</strong> a “Cached” link to <strong>the</strong> Web pages c<strong>on</strong>taining hiscopyrighted materials and downloaded a cached copy of those pages from Google’s systemcache. 1105 As discussed in Secti<strong>on</strong> II.A.4(l) above, <strong>the</strong> court ruled that Google was not a directinfringer because it lacked <strong>the</strong> necessary voliti<strong>on</strong>al act in resp<strong>on</strong>ding with a purely automateddownload process to users who clicked <strong>on</strong> <strong>the</strong> “Cached” links.In additi<strong>on</strong>, <strong>the</strong> court granted summary judgment to Google <strong>on</strong> its three defenses ofimplied license, estoppel, and fair use. With respect to <strong>the</strong> implied license defense, <strong>the</strong> courtfound that Field was aware of <strong>the</strong> industry standard mechanisms by which he could haveindicated a desire not to have his Web site crawled or cached, and that, with knowledge of howGoogle would use <strong>the</strong> copyrighted works he placed <strong>on</strong> his site, by choosing not to include metatags<strong>on</strong> <strong>the</strong> site that he knew would have caused <strong>the</strong> Googlebot not to archive his site, hisc<strong>on</strong>duct should reas<strong>on</strong>ably be interpreted as a license to Google for crawling and archiving <strong>the</strong>site. 11061101 Id. at 1112-13.1102 Id. at *1113.1103 Id.1104 Id. at *1113-14.1105 Id. at *1115.1106 Id. at *1115-16.- 256 -

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

Saved successfully!

Ooh no, something went wrong!