Posted on 05-14-2012
I attended a great webinar put on by the folks at Apigee last week, where they discussed APIs & Copyright. A very timely discussion with the recent API copyright decision in the EU, and from the ongoing Oracle vs. Google case.
As I process all discussions around API copyright, I’m going to publish relevant pieces here at API Voice, for everyone else to process along with me. One interesting piece of the Apigee discussion is that APIs have been copyrightable for the last 22 years--specifically referencing the JOHNSON CONTROLS, INC. v. PHOENIX CONTROL SYSTEMS, INC. from October 3rd, 1989. On page three, it states:
"A computer program is made up of several different components, including the source and object code, the structure, sequence and/or organization of the program, the user interface, and the function, or purpose, of the program. Whether a particular component of a program is protected by a copyright depends on whether it qualifies as an "expression" of an idea, rather than the idea itself."
Beyond Johnson Controls, Inc v. Phoenix Control Systems, it appears there is further precedent to apply copyright to APIs. The filing also references:
See Harper & Row Publishers, Inc. v. Nation Enters.,471 U.S. 539, 547, 105 S.Ct. 2218, 2223, 85 L.Ed.2d 588 (1985); Data East USA, Inc. v. Epyx, Inc.,862 F.2d 204, 207-08 (9th Cir.1988); 17 U.S.C. § 102(b).
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Turning Forms Into APIs: Crap In, Crap Out
- The Private Internal Tier Of My API Service Composition
- API Virtual Stack Composition Like The Absolut Drinks Data API
- An Operational Harness For My Screen Capture API
- Two Things I Learned On Traffic And Weather Today
- Keep Your API Developer Area Blog Up To Date
- Interesting Example of Social Page Over At Cisco
- External API Deployments Using Sync One Possible Future Of Government API Deployments
- What Are Some Good Examples of Hypermedia APIs?
- API Driven Backend For Apps Using Orchestrate.io