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
- API Talent Agencies
- Which Building Blocks Should I Use As Part Of My API Support Strategy
- Common Building Blocks of Cloud APIs
- Viewbook Uses Flickr API Design When Designing Their Own
- Expanding An API Designers Horizon Using Apiary
- What Version Of The API Economy Are You Investing In?
- I Am Up To 34 APIs Out Of The Netherlands
- Hello World Product API With Blueprint, RAML And Swagger
- The New Github Developer Program and Integrations Page
- I Have A Valuable API Resource, What Now?