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.

The court cast <strong>the</strong> issue of direct liability as “whe<strong>the</strong>r possessors of computers are liablefor incidental copies automatically made <strong>on</strong> <strong>the</strong>ir computers using <strong>the</strong>ir software as part of aprocess initiated by a third party.” 65 The court distinguished MAI, noting that “unlike MAI, <strong>the</strong>mere fact that Netcom’s system incidentally makes temporary copies of plaintiffs’ works doesnot mean that Netcom has caused <strong>the</strong> copying. The court believes that Netcom’s act ofdesigning or implementing a system that automatically and uniformly creates temporary copiesof all data sent through it is not unlike that of <strong>the</strong> owner of a copying machine who lets <strong>the</strong>public make copies with it.” 66 The court held that, absent any voliti<strong>on</strong>al act <strong>on</strong> <strong>the</strong> part of <strong>the</strong>OSP or <strong>the</strong> BBS operator o<strong>the</strong>r than <strong>the</strong> initial setting up of <strong>the</strong> system, <strong>the</strong> plaintiffs’ <strong>the</strong>ory ofliability, carried to its natural extreme, would lead to unreas<strong>on</strong>able liability:Although copyright is a strict liability statute, <strong>the</strong>re should still be some elementof voliti<strong>on</strong> or causati<strong>on</strong> which is lacking where a defendant’s system is merelyused to create a copy by a third party. 67Accordingly, <strong>the</strong> court refused to hold <strong>the</strong> OSP liable for direct infringement. The courtalso refused to hold <strong>the</strong> BBS operator liable for direct infringement. “[T]his court holds that <strong>the</strong>storage <strong>on</strong> a defendant’s system of infringing copies and retransmissi<strong>on</strong> to o<strong>the</strong>r servers is not adirect infringement by <strong>the</strong> BBS operator of <strong>the</strong> exclusive right to reproduce <strong>the</strong> work where suchcopies are uploaded by an infringing user.” 68 The court fur<strong>the</strong>r held that <strong>the</strong> warning of <strong>the</strong>presence of infringing material <strong>the</strong> plaintiffs had given did not alter <strong>the</strong> outcome with respect todirect infringement liability:Whe<strong>the</strong>r a defendant makes a direct copy that c<strong>on</strong>stitutes infringement cannotdepend <strong>on</strong> whe<strong>the</strong>r it received a warning to delete <strong>the</strong> message. This distincti<strong>on</strong>may be relevant to c<strong>on</strong>tributory infringement, however, where knowledge is anelement. 69The result of <strong>the</strong> Netcom case with respect to liability for direct infringement for <strong>the</strong>transmissi<strong>on</strong> and intermediate storage of copyrighted materials by an OSP was codified in <strong>the</strong>first safe harbor for OSPs set forth in Secti<strong>on</strong> 512(a)(1) of <strong>the</strong> Digital Millennium <str<strong>on</strong>g>Copyright</str<strong>on</strong>g>Act, 70 discussed in detail in Secti<strong>on</strong> III.C below.(b) The MAPHIA CaseAno<strong>the</strong>r well known case, Sega Enterprises Ltd. v. MAPHIA, 71 adopted <strong>the</strong> logic of <strong>the</strong>Netcom case and refused to hold a BBS and its system operator directly liable for <strong>the</strong> uploading65666768697071Id.Id. at 1369.Id. at 1370.Id. at 1370-71 (emphasis in original).Id. at 1370.H.R. Rep. No. 105-551 Part 1, at 11, 24 (1998).948 F. Supp. 923 (N.D. Cal. 1996).- 30 -

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

Saved successfully!

Ooh no, something went wrong!