5 ms·
APIs are interfaces. If an interface is truly innovative in some important way, the proper way to protect it is with a patent, not with copyright. Of course, th
by int_19h 7y ago
APIs are interfaces. If an interface is truly innovative in some important way, the proper way to protect it is with a patent, not with copyright. Of course, then you'll have to actually prove that it's sufficiently innovative - and, conversely, somebody could challenge your patent and strike it down by e.g. providing examples of prior art.
If all APIs are copyrighted, then interoperability goes out of the window. How far do you think would F/OSS have gone if it couldn't re-implement Unix enough to be reasonably compatible? The story of Linux vs Hurd tells volumes right there.
- boublepop 7y agoBooks are protected even if they are not innovative, programs are protected even if they are not innovative. Why should interfaces not be?
- dbtx 7y agoReferring to the article in [0], facts are not copyrightable. If you're going to write some code, then you usually choose to base your work on a particular language, which means you copy a lot of the design decisions and original work that went into it, and that is hopefully what everyone wanted ITFP. You (or O'Reilly) copyright a thorough description of the language's syntax, not the syntax itself. An API's function signatures are a more specific and elaborate kind of syntax, but all are just facts about the world now that someone published the thing. edit: I mean that the uncopyrightable fact is that "if you are going to use this thing, here is exactly the way it must be done". This goes much further than 'imitation is the sincerest form of flattery'. The reason e.g. Microsoft published the reference for MFC is because they wanted people to be able to use it, and actually use it. My shallow opinion is that interfaces are like that. You want people to build on top of it rather than making up a new and utterly foreign thing every time, so you want people to copy the exact things about it that make this possible, correctly. You could argue that Oracle didn't own any of the code that different bits of Android were interfacing with, so they didn't have any incentive there. But that only means Oracle forgot or doesn't care about that thing called 'mindshare'. People learning and using identical interfaces "should" have been something that Oracle wanted. (I don't mean to imply any notable similarity in the two cases, but people knowing when and where the trains were running-- so they could use those and keep on deciding to use those-- "should" be something that MTA wanted.) On the side, obsessing over protection is precisely what I've said is distasteful about the GPL. $0.02 [0] https://news.ycombinator.com/item?id=22002272 https://news.ycombinator.com/item?id=22002272
- jariel 7y ago"If you're going to write some code, then you usually choose to base your work on a particular language, which means you copy a lot of the design decisions and original work that went into it, and that is hopefully what everyone wanted ITFP. You (or O'Reilly) copyright a thorough description of the language's syntax, not the syntax itself." Yes, exactly like APIs. "An API's function signatures are a more specific and elaborate kind of syntax, but all are just facts about the world now that someone published the thing. " This is just plainly not true. Nobody on this thread has given a reasonable argument as to why APIs are not more or less like code. In fact, almost everyone's attempt to demonstrated that 'API s are different that code' have done the opposite, and highlighted how similar they are. I believe HNers just don't like copyright, and don't like Oracle.
- dbtx 7y ago> This is just plainly not true. This is DH3. [0] I need some more red meat. :) > Nobody on this thread has given a reasonable argument as to why APIs are not more or less like code. I think they did, though. An API is designed and written, and then it is "a design". (OK "an interface" but that's jargon, the design and formal requirements and patterns are what matters) Code is designed and written, then it is "an implementation". If there's anything special about your design so that you want to control how and whether people are legally allowed to implement it, you get a patent, not a copyright. Then (IINM which seems probable because IANAL) the separate (perhaps royalty-paying) patent licensee can still copyright their own implementation. Don't get me wrong-- I don't want even more patents around software, I just hope people will call things what they are. I have to admit that I could merely be mincing words, if only because that's what I want to accuse someone else of doing. I don't envy the court. [0] http://www.paulgraham.com/disagree.html http://www.paulgraham.com/disagree.html
- jariel 7y agoYes, that's actually a good attempt at making the case, along the lines of some some of the amicus brief filings. (Most of the arguments on this thread are missing the point). So here is where people are crossing streams I think: 'The interface' to something is not copyrightable as the law says today - fair enough. But the description of said interfaces may in fact be. In many cases, probably most, the API is literally part of the code - which is copyrighted already. So it might be possible that the articulation of an interface is a creative work like anything else, but the implementation is not. So you can release an implementation of some copyrighted platform - that does the exact same thing with the exact same interface, but the description of said interface in some descriptive language is copyrighted. The paradox of the fact that the API is often part of the copyrighted code ... is hard to get past.