3 ms·
To make a few more things clear: that APIs are not copyrighted has never been settled law either, so the chances of getting sued over copyright violation has al
by pron 11y ago
To make a few more things clear: that APIs are not copyrighted has never been settled law either, so the chances of getting sued over copyright violation has always existed. The only difference is that before (as Google did) you could make two arguments: 1) that APIs aren't copyrightable to begin with, and 2) if they are, then you're making fair use of them. Now only option 2 exists (with the caveat of the ruling serving as a precedent, as other commenters say).
Also, copyrighted APIs are only "language-level" APIs (or just APIs as we've always called them) -- not web APIs (or protocols, as we used to call them), simply because web APIs lack other prerequisites to be copyrightable.
To the question of fair use. There are several fair use defenses, but two apply to the industry in cases like this: 1/ non-profit use, 2/ use for the sake of compatibility (to prevent vendor lock-in). AFAIK, all third-party implementations of APIs happen to be one or the other (or both). Android is neither -- it is for profit and it is not compatible with Java programs. More than that: it wasn't even done to prevent vendor lock-in. So even if Google loses on the fair-use case, chances are that the defense still holds for all other cases of third-party implementation. Unlike the claims made by Google's PR, this ruling's effect on the industry are at worst tiny, and most likely nil.
- magicalist 11y ago> with the caveat of the ruling serving as a precedent, as other commenters say No, this is incorrect. Because it was a copyright case decided by the Federal Circuit, it is precedent nowhere. Literally no court will need to treat it as precedent. Please educate yourself further before making these lengthy posts in threads like this; you're spreading misinformation. > Also, copyrighted APIs are only "language-level" APIs... not web APIs (or protocols, as we used to call them) From this and your post below, this appears to be a distinction you have made up (to appeal to the audience here? I have no clue). "Structure, sequence and organization" are certainly aspects of web APIs that could be copyrightable under the Federal Circuit's ruling. Also, no one called web APIs "protocols" anymore than they called system calls "protocols". Unless you're talking about actual protocols, in which case I'd just stick to calling them "protocols" because that's what we still call them. > There are several fair use defenses, but two apply to the industry in cases like this: 1/ non-profit use, 2/ use for the sake of compatibility (to prevent vendor lock-in). Non-profit use is neither necessary or sufficient for fair use (see Google's recent book scanning ruling, for instance), and the compatibility argument is not with existing JVMs but with existing Java source code. As for the rest of you post on fair use, I would suggest other readers to take a look at the actual four factors of fair use in the US, as your summary is a poor one. One good source: http://fairuse.stanford.edu/overview/fair-use/four-factors/ http://fairuse.stanford.edu/overview/fair-use/four-factors/
- pron 11y ago> you're spreading misinformation. I am most certainly not. I concede that I am not clear on how much this serves as a precedent if at all, but that has little or no bearing on what I've said on the case. > From this and your post below, this appears to be a distinction you have made up (to appeal to the audience here? I have no clue). "Structure, sequence and organization" are certainly aspects of web APIs that could be copyrightable under the Federal Circuit's ruling. You can apply "structure, sequence and organization" to anything you like, but if you want it to be copyrighted, your work must be fixed. If it is not fixed -- as in the case of web "APIs" -- it cannot be copyrighted no matter what other properties it may have. If there is a piece of text long enough to be considered "a work" that must be replicated verbatim (or through some copyright-preserving transformation) for you to implement my web API, then that could be copyrighted. The problem is that even if you have a fixed media form you may not be eligible to copyright (which is where structure, sequence etc. applies). > and the compatibility argument is not with existing JVMs but with existing Java source code. Android is not compatible with Java sources. > I would suggest other readers to take a look at the actual four factors of fair use in the US, as your summary is a poor one. One good source That is indeed a much better summary of fair use than my poor attempt. Nevertheless, it has no bearing on my point, which is that the result of this lawsuit has little to no effect on any other players.
- magicalist 11y ago>> you're spreading misinformation. > I am most certainly not. I concede that I am not clear on how much this serves as a precedent if at all, but my comments are not predicated on that issue in the least (it is a minor point at best). This: > The only difference is that before (as Google did) you could make two arguments: 1) that APIs aren't copyrightable to begin with, and 2) if they are, then you're making fair use of them. Now only option 2 exists (with the caveat of the ruling serving as a precedent, as other commenters say). is incorrect. Whether or not your comments are predicated on, you know, your comments themselves, I don't care. > Android is not compatible with Java sources. There is a whole lot of code that works on Android because those 37 Java packages are API-compatible, which was pretty important back in 2008. You can argue that's creating an incompatible Java ecosystem in order to allow Google to bootstrap an Android ecosystem, but that is compatibility. As for your web APIs/protocol thing you're on about, I'd suggest defining what exactly you're talking about for anyone to discuss it with you. As it is you seem to be vaguely waving at something you've already defined to not be subject to copyright in order to give an example of something not subject to copyright...but now with a name that appeals to a broad audience (speaking of PR...)
- fidpd1 11y agoYou should abstain from speculating and posting your personal analysis in threads like these. When I say "you", I don't mean the indefinite second person form that stands in for saying "people in general"; I mean you in particular. Your understanding of the relevant statutory and case law is bad, and your comments are, at best, unhelpful. Realistically though, we can call them harmful. Better to just hold it in. If you're posting to satisfy an earnest effort to be productive and helpful, instead use the time that you would have otherwise spent writing these comments to go somewhere and ask questions in an attempt to better understand the area of discussion here. But don't do this.
- pron 11y agoWhile I am not a lawyer and I admit that my previous comment was too legal in nature for my own comfort, it is not any more harmful than Google's agitprop shrieks over a software apocalypse. I am familiar enough with the software industry to conclude that the ruling, for non-legal reasons, is likely to have little or no impact on the industry, which, aside from a few notable cases (each with their own very special circumstances) has not been in the habit of replicating proprietary library APIs wholesale for any purpose (let alone for purposes other than freedom from vendor lock-in) for quite some time. Others, of course, may have other opinions. While I myself have simplified some of the points regarding fair use defense, I also linked (in this comment: https://news.ycombinator.com/item?id=10851052 https://news.ycombinator.com/item?id=10851052) to a more nuanced discussion. The bottom line is that both interoperability and commercial use will play a central role in the debate over Google's fair-use claim (and any debate over API implementation). I also know that Google was encouraged to use OpenJDK for Android precisely in order to prevent the very predictable lawsuit (as well as for other reasons) long before it happened, but Google refused to use GPL software for that part of the Android runtime.