Copyright law has always had a complicated relationship with software. Supreme Court Justice Stephen Breyer presaged the difficulties in applying copyright law to software in a seminal law review article in 1970, and despite a few legislative revisions of copyright law since then, many of those same inherent difficulties persist. In the past year, these problems received public attention in a few high profile news stories, including John Deere’s claim that tractor purchasers don’t actually “own” the tractors they buy. Instead, purchasers merely receive an implied license to operate the vehicle and the software it contains. To just about any rational person, this seems like a Kafka-esque absurdity that only the most creative lawyer could dream up. But as more and more of our everyday products become computerized and connected, it’s likely that we’ll see many more examples of how copyright laws meant to encourage creative production can produce bizarre outcomes when applied to products containing embedded software.
Spurred in large part by the John Deere story, the Copyright Office opened a public inquiry seeking commentary on the legal and policy challenges related to copyright’s application to software embedded in everyday products. Last week, Engine filed comments with the Copyright Office identifying the many challenges to startup innovation that arise from this application. Written by a crack team of legal students at Stanford Law School’s Juelsgaard Intellectual Property and Innovation Clinic under the guidance of Phil Malone and Jef Pearlman, the comments examine difficult questions surrounding the appropriate scope of software copyrights, focusing on how granting copyright protection to essentially functional code can hurt startup competition by undermining interoperability between platforms and services, and how limiting a user’s right to modify software in devices they own poses a range of threats to innovation and security.
The innovation-stifling threat of overbroad copyright protection for software is perhaps best encapsulated in the ongoing litigation between Google and Oracle over the copyrightability of Application Programming Interfaces (APIs) that facilitate communication between computer programs. As the comments explain, “APIs have been and are indispensable to interoperability in standalone software platforms and products and will be equally indispensable to software-enabled consumer devices,” such that allowing companies to assert copyrights over APIs to will create “incentives for incumbents in almost any industry to misuse copyright law to try to exclude new entrants and emerging competition.” Particularly in the emerging Internet of Things, where startups will be well-positioned to build apps and services that interact with the innumerable connected devices that will soon be a part of everyday life, protecting interoperability is paramount to encouraging innovation and competition. This competition will foster both enormous economic growth and consumer value, so it’s critical that we rein in rules that give incumbents the power to use ill-fitting copyright laws to exclude competitors.
The comments make a compelling case for sensible copyright rules in the age of embedded software, and we at Engine are incredibly grateful for the fantastic work of the Stanford team. Read the full submission here.
