|
|
|
|
|
|
by BHSPitMonkey
4037 days ago
|
|
|
I think you're describing the client side of the API. A way of looking at REST APIs in the context of this Oracle case would be to imagine a Stripe clone appearing with an identical API to Stripe's, to the point of being interoperable with existing Stripe client code/libraries. Could Stripe claim copyright over the way their API is designed in this situation? If Oracle gets its way, then perhaps. |
|
|
Oracle isn't trying to copyright the way their API is designed. They're trying to copyright the API. A REST protocol, unlike an API, isn't a text (or any fixed work). What isn't fixed can't be copyrighted, but it could possibly be patented (a way of doing something may be patented).
You can't copyright an idea, but you can copyright a text (or a photo, a video, or a recording). An API is a text; Stripe's protocol (or "API") isn't (though Stripe's specific documentation page describing their protocol is probably copyrighted).