Two recent circuit court decisions highlight the need for companies to clearly identify their intellectual property (IP) assets and retain records of updates and other IP modifications on an ongoing basis.
In InDyne, Inc. v. Abacus Tech. Corp., the Eleventh Circuit affirmed an award of attorneys' fees to the copyright defendants after the plaintiff failed to identify the versions of its software allegedly infringed. Similarly, in Fair Wind Sailing, Inc. v. Dempster, the plaintiff Fair Wind's inability to identify its allegedly infringed trade dress with reasonable specificity resulted in both:
Although these decisions addressed diverse IP rights and considered fee awards under different standards, the decisive factor in each case was the plaintiff's failure to properly identify and produce the IP asset at the heart of its claims. This gives courts new precedent for censuring plaintiffs who inadequately identify their allegedly infringed IP.
Companies should therefore:
For more on proving copyright infringement, see Practice Notes, Copyright Infringement Claims, Remedies and Defenses and Copyright Litigation: Analyzing Substantial Similarity.
For more information on trade dress protection and enforcement, see Practice Note, Trade Dress Protection.
In Nguyen v. Barnes & Noble Inc., the plaintiff sued Barnes & Noble alleging deceptive business practices and false advertising when Barnes & Noble canceled orders for a handheld tablet after experiencing unexpected demand. Barnes & Noble unsuccessfully moved to compel arbitration, arguing that the plaintiff had constructive notice of, and was therefore bound by, its website TOU's arbitration provision. The plaintiff argued he was not bound because he had neither clicked on the TOU hyperlink nor read the TOU.
On appeal, the Ninth Circuit found that while a browsewrap agreement presenting terms through a hyperlink can create a binding contract, Barnes & Noble's TOU did not provide the actual or constructive notice needed to establish mutual assent. While Barnes & Noble posted the TOU hyperlink prominently on each web page, it did not:
Companies using these agreements should:
Patent owners should be aware of a recent US Supreme Court decision that significantly narrows the scope of induced patent infringement, particularly for software and business method patents.
In Limelight Networks, Inc. v. Akamai Technologies, Inc., the Supreme Court held that liability for induced patent infringement under 35 U.S.C. § 271(b) only exists if there is direct infringement by a single entity under 35 U.S.C. § 271(a). The Supreme Court rejected the Federal Circuit's holding that inducement liability does not require direct infringement attributable to a single entity.
The Supreme Court left intact the direct infringement standard in Muniauction, Inc. v. Thomson Corp., where the Federal Circuit held that direct infringement of a patented method exists if a party either performs:
In Limelight, the Supreme Court found no induced infringement because Limelight failed to perform one method step and did not control its customers' performance of that step.
As a result of the Limelight decision:
For more information on patent litigation and patent infringement claims and defenses, see Practice Note, Patent Infringement Claims and Defenses .
This look at the major issues on the horizon for corporate counsel comes from Practical Law – an online legal know-how service. View all the looming issues now – compliments of Practical Law The Journal, which covers the latest transactional and compliance topics that impact your practice. To gain access to more related know-how resources, please visit http://us.practicallaw.com.