Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Copyright, Open Source and APIs (towards an Interface Commons)


Published on

Session talk at defrag 2012, Steven Willmott:

Published in: Technology
  • Hi there! Get Your Professional Job-Winning Resume Here - Check our website!
    Are you sure you want to  Yes  No
    Your message goes here

Copyright, Open Source and APIs (towards an Interface Commons)

  1. 1. Copyright, OpenSource and APIs
  2. 2. Steven Willmott, 3scale networks / @njyx
  3. 3. @3scale 21-22 Feb, 2013
  4. 4. IANAL(& This is Not Legal Advice)
  5. 5. Outline• Copyright and APIs don’t mix• Alsup to the rescue• But there’s still a problem• Share rather than copyright - towards an Interface Commons
  6. 6. Copyright & APIs From: API Copyright would imply, no reuse of whole or (possibly) fragments
  7. 7. Copyrighting APIs? v’s v’s
  8. 8. Bad News for Everybody• Copyrighting the Idea of something rather than its Expression• Copyrighting every possible implementation of that thing• Makes • Building almost any new language or API hard • Integrating systems impossible
  9. 9. Copyright Gridlock API 2 Bad news even if you API 3 are the original copyright claimantAPI 1 API 1.1 ? Even worse if the APIs / Fragments are generic API 5 Leads to widespread paralysis API 4
  10. 10. Luckily...
  11. 11. Recent Judgements => No Copyright
  12. 12. US VerdictSo long as the specific code used toimplement a method is different, anyone isfree under the Copyright Act to write his orher own code to carry out exactly the samefunction or specification of any methodsused in the Java API. It does not matterthat the declaration or method header linesare identical.
  13. 13. European Verdict[... the Court holds that neither thefunctionality of a computer program nor theprogramming language and the format ofdata files used in a computer program inorder to exploit certain of its functionsconstitute a form of expression.Accordingly, they do not enjoy copyrightprotection.]
  14. 14. So, All Clear?
  15. 15. Not so Fast! • There is still uncertainty (EFF Appeal) • “Copyright” is still everywhere • Reuse can still be Plagiarism • There may be patents... help-us-make-case
  16. 16. E.g. Bad BehaviourCopy/Paste? -> Copyright still applies to some things + can still be plaigiarism
  17. 17. So What to do?• What should we do when designing APIs?• Should we be sharing rather than copyrighting?• What if you actually want to protect something?
  18. 18. And moreimportantly...
  19. 19. Actually Sharing wouldbe very powerful• Reduces coding hassle• Ups Re-use• Makes Better Interfaces Remind you of Open Source? But there is little API Interface sharing today
  20. 20. Things to think about
  21. 21. If you publish APIs• Think about how you feel about re-use• If you’re cool with sharing, find a way to signal it• If you think the technology is genuinely unique and worthy of protection: patent rather than copyright
  22. 22. If you want to “Re-use” APIs• Ask!• Attribute!• Contribute!• Get clarification on status of re-use• Figure out who the original Author is
  23. 23. As a Community• Think about how to better share interfaces• Consider an “interface commons” (or an creative commons for interfaces)• Play nice when re-using, attributing and sharing• Encourage clarity• Encourage convergence in interfaces
  24. 24. Ready to Share Creative Commons Public Github WADL / Swagger etc.
  25. 25. There are inherent Tensions in this...
  26. 26. It’s Hard +Difficult to Achieve but..
  27. 27. It’s Worth it• Start building a culture of open / reusable interfaces [100’s, 1000’s, ...]• Make API design better• Speed up pretty much everything Interested in people thoughts on how to get there!
  28. 28. Thank You & Discussion Contact: Steven Willmott steve@3scale.net @njyx