4 ms·
This question or questions very close to it must have come up in the endless litigation surrounding things like IBM BIOS/x86 ISA/Apple ][ ROMs/PS1 emulators, ri
by pvg 11y ago
This question or questions very close to it must have come up in the endless litigation surrounding things like IBM BIOS/x86 ISA/Apple ][ ROMs/PS1 emulators, right?
What makes this case different? That APIs aren't protectable has been bandied about as gospel truth in the nerdosphere for decades. Was that assumption just wrong all along or is there something about this case that seems to make it subject to re-litigation?
- harryh 11y agoDidn't Intel & AMD sign a licensing agreement allowing AMD to implement the x86 ISA? That would explain one of your examples. Very good question though.
- pvg 11y agoI was thinking of NEC v Intel although that one is pretty murky too, to the nonspecialist - NEC already had certain licenses, etc.
- gsnedders 11y agoThe former Intel & AMD agreements were about patents, as far as I'm aware. (The latest actually expired a year or two ago. Still, neither will sue the other because it's mutually assured destruction.)
- rayiner 11y agoCopyright doesn't say anything about "APIs." It protects any "work fixed in a tangible medium." In the BIOS cases, you just had to connect certain code to known interrupt vectors. The code itself was totally clean-room implemented, and an interrupt vector table that exists transiently in memory isn't "fixed" and "tangible." But a Java API is much more than that. You have tangible permanent source code files containing classes that have specific names and members that have specific names. Copying a Java API involves copying these things. Moreover, here it was clear that Google did have access to the JDK code while developing the Android JVM. I appreciate that this feels like an arbitrary distinction from the programmer's point of view. The way to think about it, I think, is this: what creativity is required to design the API? Designing a class with particular methods and appropriate names requires at least minimal creativity. Putting the disk I/O routines at INT 13h instead of INT 12h doesn't; it's arbitrary.
- nitrogen 11y agoNo, you don't have to copy the source code to replicate an API. Method and class names are just aliases for memory addresses, which like a phone book, would not be copyrightable.
- rayiner 11y agoYou don't, but Google did. And unlike the flat interrupt map of a BIOS, there is non-trivial structure and organization to the set of aliases comprising a Java API.
- EdHominem 11y agoNot really, the words are descriptive. To be creative, Sunshine.Unicorn13(spaceshipIsFunnyPants); would be how you'd set permissions on a directory. Do you see why? No, of course not - if it was at all obvious it wouldn't be creative.
- mikeryan 11y agoCopyright doesn't say anything about "APIs." This is still very much an open question and right now not true. Core to this case (and a ruling Oracle has won) is the copyright of the Java API itself. https://www.eff.org/deeplinks/2015/06/bad-news-supreme-court-refuses-review-oracle-v-google-api-copyright-decision https://www.eff.org/deeplinks/2015/06/bad-news-supreme-court...
- pvg 11y agoI appreciate that this feels like an arbitrary distinction from the programmer's point of view. The way to think about it, I think, is this: what creativity is required to design the API? Designing a class with particular methods and appropriate names requires at least minimal creativity. Putting the disk I/O routines at INT 13h instead of INT 12h doesn't; it's arbitrary. I think that's the crux of it or at least, of my confusion because I don't see the fundamental distinction in creativity (or really, fixedness of media although that seems like an easily avoided technicality). A BIOS API is still an API in purpose and intent. It has structure, design choices (parameters and returns, what calls to and not to provide), a specification, etc. Is the legally significant difference really that methods in classes have names and interrupts don't?