|
|
|
|
|
by briantmaurer
4037 days ago
|
|
Programming is in this odd position somewhere between the structure of math and the creativity of writing. Some things feel as obvious as basic addition, which clearly should not be copyrightable, while other things feel as clever as complex poems, which clearly should be copyrightable. I am not a copyright expert, but in my opinion APIs usually fall closer to the structured math half of programming. ex. GET, POST, PUT, or DELETE to the following: /users /messages /comments /login /logout /signup /payments etc. Who gets those copyrights? |
|
But, there seems to be a balance, is the API of a single class copyrightable? No, probably not. Is the API of a large system like Java's copyrightable, I really do think so.
Having said that, I disagree with the protections an API suddenly gains once we say I have a monopoly on its use and license. E.g. This verdict likely just made every emulator an act of copyright infringement. Does intel own the API on the x86 instruction API and can lock out AMD?