APIDays Paris Main track talk on the state of API Copyright and how to work together to create more open APIs. Steven Willmott

1. How to Survive the API Copyright Apocalypse
(and supercharge the API Economy)
Steven Willmott, API Days Paris, 14th December 2016
Paris France
https://creativecommons.org/licenses/by-sa/3.0/us/

2. https://creativecommons.org/licenses/by-sa/3.0/us/

3. Steven Willmott, Former CEO of 3scale
Senior Director and Head of API Infrastructure
http://www.redhat.com / http://www.3scale.net
Twitter: @njyx
See us at the Red Hat Booth

4. 4
Cloud
Containers
Microservices
DevOps
RED HAT TECHNOLOGY
Storage
App Delivery
Integration
API Management

5. Before we start…

6. Copyright potential is everywhere

7. The API Copyright Apocalypse

9. Google v’s Oracle
Java API Copyright Lawsuit

10. • The Structure of
the Interface is
what is at issue
• Paths,
Parameters,
Return Types
etc.
Example

11. Google won…

12. So, we’re good…?

13. • Not so fast!
• Google ”won”
but….
• Lots of
consequences
• There will be an
appeal
• @sarahjeong
Sarah Jeong
Image Credit: @wiredferret (Heidi at

14. Copyrighting an idea of
something – not it’s expression
Copyrighting every possible
implementation of that thing
Makes building any new API
Hard
Could make integration
impossible
Claims would be extremely hard
to validate
What is complex enough?
It’s not clear what type of
modifications are ok
There is no way to search
current state of the art
Impact of Copyright Enforcement

15. It is Even Bad for those that Enforce Copyright
Copyrighting one version
protects it
However, APIs evolve and the
next version may intersect with
other APIs
Asserting copyright may force
prior art owners to do the same
API Maintenance now becomes
a legal issue

16. Chilling effect on re-use
Increase risk in publishing APIs
and uncertainty in using them
Financial burden of searching for
prior art or fighting troll cases
Long term: gridlock for APIs
Long term: non-documentation
of APIs
Long term: API specs could be
amassed like patent portfolios
=> No Profit!
Worst Impacts
Legal costs concerning potential
issues

17. How to Survive the Apocalypse

18. API Copyright is similar to a plague

19. Even if you survive, it’s not fun to be
the last one standing

20. Solution requires individual action at
a collective scale

21. Solution:
Share API definitions, don’t
Copyright them

22. How to:
Open Source (Liberal License)
Creative Commons
Signal these changes

23. Interface becomes a better bet
for their users
Others can help evolve it as well
as write clients / back-ends
Signal to developers they are
making a safe choice
Become a platform leader in
your space
More and more shared
definitions
Common patterns become
established
Better scrutiny of designs
Building up libraries for clients
and back-ends
Why do this?

24. Ask!
Attribute!
Contribute
Get clarification of status /
rules
If you “Re-Use” an Interface
Common
Courtesy!

25. http://apicommons.org
(first attempt at an API Definition sharing process)

26. Developer View

27. Copyright free: less risk of lock
in
Copyright free: more chance of
other implementation
Copyright free: ensures the right
to implement clients
Copyright free: community
oriented provider
Developer View
Preferred API
Provider!

28. Actual Zombies?

29. 1. Aim for the head
2. Run for the hills
3. Always pack plenty of snacks
4. Avoid large groups of people
5. Use fire (but be careful with TNT)
6. No time for sentiment, kill the infected
7. Stay in Shape!

30. Help us take on the Zombies!
http://apicommons.com

31. Conclusions

32. Some Good News this Week
http://www.autoblog.com/2016/10/31/copyright-dmca-allows-owners-fix-cars/
“US Copyright
Office officially
allows owners
to work on
their own car”
But: only owners, not third parties

33. Things to Do
1. Determine real API value
2. Look at role and evolution of the design
3. Consider Open Source and Copyright Free
4. Contribute to the Commons
5. (Beware of Zombies!)

34. Good
Luck!
@njyx
@3scale
@redhatnews

35. 35
Cloud
Containers
Microservices
DevOps
RED HAT BRINGS IT
ALL TOGETHER
Storage
App Delivery
Integration
API Management

36. plus.google.com/+RedHat
linkedin.com/company/red-hat
youtube.com/user/RedHatVideos
facebook.com/redhatinc
twitter.com/RedHatNews
THANK YOU
36

37. • 1st Zombie Photo: Daniel Hollister - https://www.flickr.com/photos/dhollister/2596483147/
• Zombie Survivor Couple: David Willis - https://www.flickr.com/photos/dwilliss/7861502966/
• Zombie Trio: https://www.flickr.com/photos/necrocake/5796749951/
• Cover slide Zombie: https://www.flickr.com/photos/peymanz/11140184813/
• Worker photo re-use from linked URL from Autoblog
All images copyright their owners
Attributions