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
- Swagger Visualization Layer Using D3.js
- Establishing Common Dictionaries That Industries Can Use In Their API Design
- Top 5 Most Popular Themes On API Evangelist In 2014
- Query Parameter Determining Which Fields Are Queried For API Call
- Now Our Development Environment Is Now Containerized And Scalable Like Our Production Environment
- Guest Post: Let Our Sponsors Blow A Little Smoke Up Your Ass
- API Discovery Continues Its Move Into The IDE With Eclipse Che
- Evolving Beyond Just Resources Towards A More Experience Based API Design
- Another View of The API vs. Data Download Model
- If You Have A Publicly Available Mobile App You Have a Public API