5 ms·
If API are copyrightable how do clean room implementations work? It seems IBM could sue the clone makers for the BIOS API if that's the case.
by jandrese 9y ago
If API are copyrightable how do clean room implementations work? It seems IBM could sue the clone makers for the BIOS API if that's the case.
- lallysingh 9y agoI think because there are no identifiers. The BIOS API is: fill registers with these values, run this interrupt. That's different from openFileWithName(String fileName).
- mlindner 9y agoWhat? No those are the same thing. Why is an API suddenly not copyrightable if its 0x51234 offset 5 bits, vs human readable text? That is nonsense. Numbers and words should not be treated differently. What if I named my function 015342342(String 123949)? How does that change anything?
- jerf 9y agoCopyright has a creativity requirement. I can easily see a court ruling that 0x51234 bit 5 is not creative whereas SetBrickMode(true) has a spark of creativity in that it could have been named multiple things. Without endorsement, there is definitely a line between text in which one can be "creative" and numbers in copyright law as written. The problem here isn't the line between creative and non-creative, the problem here is the introduction of copyright, a concept created for expressive works, into a field that consists of functional works. It should not be a surprise to anyone, not even lawyers, that this isn't going to "just work". The surprise to me is that it has taken this long for this foundational clash to start emerging at a big scale.
- pbhjpbhj 9y agoThe number sequence to word differentiation you make is specious - you may not consider it creative but there's a creative spark in choice of a number, or choice of a location in memory that leads to choice of a number, etc., as you later intimate that creativity is technically lead. The choice of call name in an API are arbitrary, the reuse of those names to interface with that API is not a creative copy it's a technical requirement. If I make a toothed belt to fit a pair of gears, that's not an artistic expression no matter the the tooth pitch is an exact duplicate of that on the gears. If the gear is purple and orange spots, in a distinctive pattern, and I make my belt the same pattern then that's a copyright issue. If the API calls were like "thisIsTheSummerOfOurDiscoTents(banana)" - such that the names are sufficient to be individual works of art, and weren't following a technical function, then perhaps you have an argument that the API is a work of literature, or otherwise an artistic creation. It just sounds like a wrong decision was previously made and should now be overturned.
- jerf 9y agoThe key word in first bit of my post is "court". I think standing in front of a judge and explaining that your choice of 1,383,929,380 is "creative" is, well, something you're welcome to try. The real key point is in the second half, though. Arguing over whether or not a particular micro-decision is "creative" is the entirely wrong track to be taking when we're discussing something that is functional, that performs some real task in a way that a movie or song simply does not. Why would we expect standards based on "creativity" to apply to that in any sensible way?
- pbhjpbhj 9y agoJudges aren't fools (but some can be persuaded to be!). It's impossible for a collection of letters to be creative but for that collection of letters when represented numerically to be no longer creative. If I make up some BS for how there's a correspondence between these symbols and other symbols (1=alpha, 2=bravo, ...; or 1=sandwich, 2=wellington, ...) - then 1383() is just sandwichBiscuitAppleBiscuit(). Then it's clear the creative aspects of the program, API, or whatever, don't lie in the specific choice of tokens. Would a judge agree that providing a dictionary/key that says an arbitrary name for each number (easy to do programmatically) makes a program creative that otherwise wouldn't be. It's clearly ridiculous. Not least because it would mean that duplicating a work that was compressed, or represented in binary, would then no longer be a tort, because apparently numerical representation would rule out a work from being creative.
- s2g 9y agoYou can choose different interrupt numbers as well.
- ABCLAW 9y agoThis line of 'concern' has been running through the courts since the mid 80s. This isn't anything new. The cases themselves discuss the jurisprudence on either side, as well as the tests used to determine the magnitude of creativity and similarity as between software products.
- phkahler 9y agoThe thing is, any program that calls "SetBrickMode()" HAS to use that name. Nobody has ever claimed programs require the consent of the API creator under copyright law to use the API. EVER prior to this. And then once a bunch of software is created using the API (presumably without need of the copyright holder) someone else doing an alternative implementation for that software to run on has no choice but to use the same naming convention for those programs to run.
- cptskippy 9y agoopenFileWithName is a mnemonic that a software developer uses and which a machine translates into a literal location at compile time.
- s2g 9y agoIt's really not. If I take an API, mangle the names, and then provide a shim that translates calls is that suddenly radically different?
- 794CD01 9y agoif that happened today, they might, but until three years ago, APIs were not copyrightable. Or at least not thought to be by most developers.
- pera 9y agoThat was already decided back in 2014 (Oracle v Google): the jury concluded that Google did infringe Oracle's copyrights, but they deadlocked on Google's fair use defense. And yeah, I guess that IBM could start suing everybody... this whole situation is so ridiculous.
- jgh 9y agoDoes that mean all the cloud providers who are copying S3's API for object storage are violating some copyright?
- izacus 9y agoI'm sure Amazon would love that to be true and force any competitor to beg for licensing.
- jrochkind1 9y agoThat is what the new law established by that case seems to suggest...
- curt15 9y agoAfter all, the sole purpose of such reimplementations would be to take business away from Amazon.
- jrochkind1 9y agoYes, IBM can start suing them with some substantial chance of victory under the new law established by these cases. It's fucked. Or IBM could realize if they start doing that, it might show the insanity of the current law, and result in the law changing back to what it was and should be, API's not copyrightable.
- ABCLAW 9y agoYou actually do a clean room implementation rather than copying chunks of your competitor's work and then pretending it's allowed under fair use? Seems pretty straightforward.
- MertsA 9y agoThat statement is at odds to APIs being copyrightable. If the API itself can't be used then how exactly is a clean room implementation of that API supposed to avoid the copyright issues of implementing the API?
- eco 9y agoCool. So if I just make a Mickey Mouse cartoon from scratch I should be good.
- ZeroGravitas 9y agoOr a film about Snow White, Pinocchio, Rapunzel, Sleeping Beauty etc.
- hcknwscommenter 9y agoSure. If you managed to actually do that. Of course courts are free to infer as to the unlikelihood of that.
- monocasa 9y agoDisney's whole strategy was taking public domain works like those and making cartoon versions. There's nothing legally stopping you from doing the same; Disney does not own these stories.
- phkahler 9y agoGoogle did clean room implementation of almost all functions. They copied 9 lines of implementation code verbatim - out of thousands of lines. It does raise a question in my mind as to how that one function got copies, but it's also possible that it was re-implemented and happened to be done exactly the same without looking at the original - I honestly don't know but Google conceded it was a duplicate either way. 9 Lines. Not a wholesale infringement - seems pretty straightforward.
- Lazare 9y agoGoogle didn't do a clean room implementation, so it's difficult to speculate what this decision might indicate for some other case involving a clean room implementation. (And yes, I know: The overwhelming majority of the work was a clean room implementation, but not all. In retrospect, this was an unfortunate mistake by Google.)