11 ms·
Computer Scientists Ask Supreme Court to Rule APIs Can’t Be Copyrighted
- snarfy 12y agoMap makers should just copyright the lines that represent the borders of states, counties, and cities. Heck, copyright lines, points, and legends too.
- wavefunction 12y agoWho says they don't? http://www.esri.com/legal/redistribution-rights http://www.esri.com/legal/redistribution-rights
- GlennS 12y agoESRI is an interesting example. On the one hand they make have some seriously talented cartographers who have made some astonishingly beautiful maps, and surely they should be able to copyright that work. On the other, they actually do provide quite a lot of things (including access to their tile servers) for free or under permissive licenses. For anyone who wants to look at some pretty maps: http://leaflet-extras.github.io/leaflet-providers/preview/ http://leaflet-extras.github.io/leaflet-providers/preview/
- jofer 12y agoThis is actually a very major issue. They are copyrighted to varying degrees. The fact that feature "z" is located at "x,y" can't be copyrighted, but the data file that describes exactly that can be and is. (There are good reasons for this. It's not as simple as the straw man I set up there.) The US is very fortunate to require all government-produced cartographic data is solidly in the public domain. This is not the case in most countries. Now there are several public-domain global datasets, but not very long ago obtaining basic cartographic data for many parts of the world was fraught with copyright issues. It's rather annoying to have made a map of your study area and then find out that:, "Oh, wait. You can't publish that. Our license for the river locations only allows us to use the data internally. We can't publish a figure with that data on it!"
- andrewljohnson 12y agoThis issue is rapidly coming to a close. The disruption of the mapping companies (and sovereign mapping efforts) is going power law now because of mobile devices. Five years ago, www.OpenStreetMap.com started getting comparable to commercial maps in many places. And we have not even entered the golden age of OSM, when all of these sensor-laden devices we carry will be automatically feeding the map updates and corrections. Open data will be the best for nearly all applications on a 20-year timeframe. Google, TomTom, Russia, etc will not be able to make money on the actual map data.
- Nitramp 12y agoThe US is very fortunate to require all government-produced cartographic data is solidly in the public domain. This is not the case in most countries. You can make the argument that making these maps costs money, so those that benefit from the maps should actually pay the government for them - thus people who don't need these maps don't have to pay for them through their taxes. I'm not entirely sure I subscribe to that - often having something publicly available like some kind of a utility is more beneficial to everybody than properly allotting the cost. But I don't think it's clear cut in the case of maps, and in any case it's a reasonable argument to make.
- hawkice 12y agoSo, the census needs maps (and best we are able to double check that, as it is used to apportion representatives). But also: the modern nation-state is, in many ways, founded on the notion of maps. A nation exists not just by itself but instead of and in place of other government. So it's pretty reasonable to assume public maps come from a time where e.g. the western border of the country was fuzzy and who controlled what was information of great importance. For instance, if it's 1823 and I'm looking to farmstead, a map both legitimizes, in some way, American rule, and delineates reality about Comanche raids (which were not something you'd want to bump into). I generally like open government, but I think this particular practice may come from a history where maps were more interesting and relevant to the integrity of the nation-state.
- deleted 12y ago[deleted]
- smutticus 12y agoFacts cannot be copyrighted, only specific arrangements of facts can be copyrighted. https://en.wikipedia.org/wiki/Feist_v._Rural https://en.wikipedia.org/wiki/Feist_v._Rural
- DevX101 12y agoAlthough these issues are very important, something feels wrong about having the Supreme Court justices (avg. age ~70) rule on tech matters like this. We need a new legal system for arbitrating disputes in technical disciplines overseen by a panel of technical experts. Or perhaps a trial by jury where the selection criteria is employment in the relevant discipline for at least 10 years (academia or corporate).
- wyager 12y ago>Or perhaps a trial by jury where the selection criteria is employment in the relevant discipline for at least 10 years (academia or corporate). This could be egregiously abused without too much cleverness. "Oh, you're self employed in software? No jury duty for you." "Oh, you don't work for GE, the only company approved by the 'What Counts As Corporate Software' board? No jury duty for you." One must be very careful advocating for the creation of special courts. History is rife with examples of these being particularly corrupt and deplorable.
- DevX101 12y agoYou might be right. But our current system is already egregiously abused with minimal cleverness. One can predict with high accuracy a SC Justice's vote on most cases based on the political party of the president who appointed him/her.
- rpedela 12y agoOverall it seems to self-correct which sometimes takes decades. While flawed, it is pretty good.
- dragonwriter 12y ago> One can predict with high accuracy a SC Justice's vote on most cases based on the political party of the president who appointed him/her. Having taken a number of law and judicial politics courses, I can say this has been studied and its not at all true. You can tell with some accuracy a SC Justice's vote on issues that had high political salience at the time the individual justice was appointed by the position of the appointing administration on those issues, but predicting votes by party identification fails rather drastically for most other issues. There's a few evergreen issues that have had both high political salience and fairly consistent partisan breakdown of positions over a long time (e.g., abortion, gun control), and so these issues tend to be pretty consistently predictable by party ID. OTOH, most issues aren't like that (though issues that get lots of mainstream news coverage are disproportionately likely to be -- though even there many aren't), and issues like the particular one here (whether APIs are within the scope of copyright) haven't ever had high political salience.
- mooph 12y agoAPIs that simplify DDOS attacks from sites with JavaScript should not be copyrighted?
- JoshTheGeek 12y agoI don't understand how copyright would help in this case.
- mooph 12y agoI've created MOOPH module in JavaScript. Purpose of this module is to make it easy to code a pseudomultithreaded application (so it can be seen as API). This module can be used to create various creative content (games, editors, whatever...). However one of possible pseudothreads may include quickly content from external sites to DOM - making a DOS. If multiple users access such project, it could make a DDOS. I hope this module is copyright protected. I hope anyone who wants to use (publish on their site) this module must ask me (I am author) if I allow use of this module anywhere else than on my domains (where I've uploaded and publish my code, applying copyright). I don't think it's a good idea to turn off copyright protection of APIs, moving all of them to public domain. Some of them may be "public bad" instead of "public good" if they don't get managed using license agreements.
- marcosdumay 12y agoYou seem to be missing the meaning of the word API. I sugest you look it out.
- mooph 12y agoI've always understood API as "Application" (meaning application, program, something similar to script) "Programming" (creating code, writing) "Interface" (abstract definition of meaning of variables and functions, preferably with some code that makes those meanings "live", something real, "behind" those variable and function names). Maybe I'm wrong. However code is code, be it a library, module, framework, API, program or anything else...
- EGreg 12y agoMaybe someone should look up the stated reason for awarding a Copyright in the first place. Isn't it to "Promote the Progress of Science and the useful Arts?" http://en.m.wikipedia.org/wiki/Copyright_Clause http://en.m.wikipedia.org/wiki/Copyright_Clause In this case it would seem that in fast-moving industries, monopolies would retard, rather than promote, the progress. Especially seeing as how copyright can be extended to 100 years or more after the author's death, here the author being a corporation?
- acqq 12y agoSigned by 1. Harold Abelson.* 2. Alfred V. Aho 3. Tom Ball.* 4. John Perry Barlow 5. Brian Behlendorf 6. Richard A. Belgard 7. Jon Bentley 8. Matthew Bishop 9. Joshua Bloch 10. Dan Boneh 11. Gilad Bracha.* 12. Eric Brewer.* 13. Frederick Brooks 14. Rick Cattell 15. Vinton G. Cerf.* 16. William Cook 17. Ward Cunningham 18. Mark Davis.* 19. Jeffrey Dean.* 20. L Peter Deutsch 21. David L. Dill 22. Les Earnest 23. Brendan Eich 24. Dave Farber 25. Stuart Feldman.* 26. Edward W. Felten 27. Jeremiah Flerchinger 28. Martin Fowler 29. Neal Gafter 30. John Gage 31. Allan Gottlieb 32. Miguel de Icaza 33. John Hennessy.* 34. Tom Jennings 35. Mitchell Kapor 36. Alan Kay 37. Brian Kernighan.* 38. David Klausner 39. Ray Kurzweil.* 40. Kin Lane 41. Ed Lazowska 42. Doug Lea 43. Sheng Liang 44. Barbara Liskov 45. Paul Menchini 46. James H. Morris 47. Peter Norvig.* 48. Martin Odersky 49. Tim Paterson 50. David Patterson.* 51. Alex Payne 52. Tim Peierls 53. Simon Phipps 54. Bill Pugh 55. Larry Roberts 56. Guido van Rossum 57. Avi Rubin 58. Bruce Schneier 59. Curtis Schroeder 60. Barbara Simons 61. Dave Snigier 62. Alfred Z. Spector.* 63. Bjarne Stroustrup 64. Gerald Jay Sussman 65. Brad Templeton 66. Ken Thompson.* 67. Michael Tiemann 68. Andrew Tridgell 69. Josh Triplett 70. Jeff Ullman.* 71. John Villasenor 72. Jan Vitek 73. Phillip Wadler 74. James H. “Jim” Waldo 75. Dan Wallach 76. Peter Weinberger.* 77. Frank Yellin.* Asterisk: "presently Google employees, consultants, and/or directors. Those amici are signing this brief as individual computer scientists whose work in the field long preceded their affiliation with Google. They are not signing this brief on behalf of Google or at Google's request."
- rayiner 12y agoI think it was a tactical mistake to include the folks affiliated with Google. Amicus briefs are supposed to be from parties who have an interest in the dispute, but not a personal stake in either party. Including so many people affiliated with Google will come across negatively.
- justifier 12y ago> justices should review a disastrous appellate court decision finding that application programming interfaces (APIs) are copyrightable when the federal circuit originally ruled i read the ruling and walked away with a completely different understanding than the eff touts in their headlines this whole farce hinges on fair use stead copyrights in terms we understand : checkFairUse(GOOG_USE){ FAIR_USE=[http://www.copyright.gov/fls/fl102.html] for (rule in FAIR_USE) for ( usage in GOOG_USE) ) if ( usage < rule ) use="fair" else use="unfair" if ( use == "fair" ) return true else return false } GOOG_USE=[googSRC] if ( API_COPY == "left" || checkFairUse(GOOG_USE) ) print("allow legal use") else print("penalise") so alsup says that even though API_COPY==undefined the statement still passes because he found GOOG_USE to be "fair", the federal circuit is saying GOOG_USE!="fair" why does the eff consistently tout copyrightability of apis? this case has yet to rule on copyrights was alsup being clever attempting to end the suit quickly using the mature, uncontroversial fair use clause, or was it a spineless way to avoid making a ruling on the question that the tech community really wants: are apis copyrightable? slightly off topic, this whole debacle just screams avoid java at all costs because if you write anything financially successful in the language oracle is going to drag you through courts
- spullara 12y agoIn a world where people copyright the laws you are supposed to follow I can't imagine they won't let people copyright an API that absolutely is a creative work. Instead we should accept that they can be under copyright but make implementing and using them explicitly fair use.
- aragot 12y ago> copyright the laws That's an excellent point. If you run a service, you can use someone else's TOS and apply it to your customers. It is the outcome of intellectual work, for instance a lawyer's work, and it is under copyright. However, it is not clever to reuse someone else's contract anyway and you'd better use a lawyer to check its terms. Therefore I don't think the wording of contracts, norms, standards and laws should fall under copyright/patent. Think about a US law writer prosecuting Germany for "a law which proceeds the same way as one which was established in US" under patent infringement.
- charonn0 12y agoGovernment work products like statutory text is not typically protected by copyright. I think spullara was referring to model law codes written by private organizations and adopted verbatim by legislatures. This isn't necessarily bad (fire safety experts writing a model fire code, e.g.) but it does have the effect of putting the law under copyright.
- jrochkind1 12y agoWhatever you may think the wording of contracts [etc] pretty clearly falls under copyright protection in the US. The wording. What does not (or has not before) are the _meanings_. You in fact, can't, under US law, take someone elses TOS and just plain copy it. I'm not sure if you meant to say "can't" instead of "can" in your comment -- but in fact, you pretty clearly can't just copy the text of the TOS. What you can do is write your own TOS based on the exact same categories of allowed and unallowed behavior. > Think about a US law writer prosecuting Germany for "a law which proceeds the same way as one which was established in US" under patent infringement. Are you talking about patent or copyright? Two entirely different laws, which protect different things in different ways. You could -- quite clearly and uncontroversially -- _not_ accuse someone else of "proceeding the same way" and thus violating your copyright. Copyright simply doesn't protect "ways of proceeding". If you could get some government to issue you a patent on your law (which I don't _think_ you could, but who knows these days in the U.S. which seems happy to issue a patent on nearly anything), then you might be succesful in a patent infringement case. Patent and copyright are entirely different things. If they copied the exact text of your law, then that might be a copyright violation. Copying the "proceeding the same way"? The sorts of things you want to regulate or prohibit and the nature of the penalties or whatever? Nope. Copryight simply does not go there. (The fact that in the U.S., nothing created by the federal government is protected by copyright anyway -- is really a side-issue, something unique to U.S. law, and not really relevant to the present topic, although it is a thing).
- hdra 12y agoQuick question, where do Mono/Xamarin or similar projects stand on this whole API copyright? Aren't they essentially writing a library with the same API as the .NET or other single-platform framework? Or am I misunderstanding what they meant with API in this case?
- wmf 12y agoYes, this case is highly relevant to Mono/Xamarin, although in practice I think it would be suicide for Microsoft to start suing people who clone their technology. Note that Miguel de Icaza is a signatory.
- Blazespinnaker 12y agoMiguel/Xamarin is a very strong partner of Microsoft as well :)
- pjmlp 12y agoMicrosoft has issued a do not sue statement.
- kumarm 12y agoThat is not good enough. Sun Was bought by Oracle and things changed. If Microsoft declines further, whats stopping from Oracle or someone else repeating the same?
- thirdtruck 12y agoEstoppel. Since everyone acted in good faith when they availed themselves of Microsoft's pledge, the court will look very poorly on an attempt by Microsoft to rescind it.
- the_why_of_y 12y agoDid Sun ever make a public statement that anybody is allowed to independently re-implement (subsets of) the JRE class library APIs? I don't recall such a promise. Probably it's tied to the notorious TCK certification process that always was entirely at Sun's discretion. Actually many years ago Sun has successfully sued Microsoft over Microsoft's incomplete JRE implementation, but I guess that was more about breach-of-contract and trademarks than it was about copyright. What Sun has done is release (most of) their own JRE implementation with a GPL(+exception) license, which would of course imply a license to the API copyrights that Oracle is now speciously claiming... but Google is not using this implementation (because, as everyone knows, there are obvious legal risks to using GPL'd code); IIRC the class library implementation that Google uses comes mostly from Apache.
- forrestthewoods 12y agoThis world where judges are effectively used to write laws is bullshit and it sucks. Judicial activism sucks ass. Judges are not supposed to be lawmakers. If API's should not be protected by copyright then we should be writing letters to actual lawmakers who can write that explicitly into law. Not rely on interpretation of political appointees. Urgh.
- frostmatthew 12y ago> This world where judges are effectively used to write laws is bullshit and it sucks. Judges aren't writing laws - they're doing their job to "act as interpreters of statutes and the constitution by elaborating and precisely defining the broad language"[1]. There's a difference between "Judicial activism" and Common Law working as intended. [1] https://en.wikipedia.org/wiki/Common_law#States_of_the_United_States_.281600s_on.29 https://en.wikipedia.org/wiki/Common_law#States_of_the_Unite...
- forrestthewoods 12y agoPeople treat judges as a way to write laws. Many judges like to use their powers to make rulings on what the law should be rather than is. So I'd strongly argue that yes, in a roundabout way judges are in fact writing laws.
- TazeTSchnitzel 12y agoEr, just because they disagree with you on a law's interpretation doesn't mean they're making a ruling based on what the law "should be".
- UrMomReadsHN 12y ago"Many judges like to use their powers to make rulings on what the law should be rather than is." This is by design. Its checking the powers of the other branches of government so we don't end up with "tyranny of the majority." Without judicial review, legislators are free to pass any law they'd like without taking into consideration the constitution. No constitution or law can interpret or enforce itself. Without enforcement laws are just pieces of paper. Someone's gotta do it. Judges have the hard issue of interpretation of laws. Someone is probably going to disagree no matter what they do since every layman has an opinion and laws can sometimes be unclear. Just because your interpretation is different than theirs that doesn't mean that they are nessesarly wrong or trying to legislate. They may even thought they were right at the time but then time proved them wrong and then there must be reinterpretation. "Judicial activism" is, of course, entirely subjective. The other thing is times change. One interpretation might have worked 100 years ago but not today. The ethos of a populace are subject to change. New technology comes along. Interpretation can change with it. Sometimes legislatures go back and try to change the wording of laws after judicial review to make the meaning clearer or to come into compliance of the construction. Or even implement new laws for various reasons. It is an imperfect system. People are imperfect. They are subject to bias and the accepted values of the time period. The constitution and laws can also be vague. Some people even think the Constitution is deliberately vague in many area in order to allow it to be a "living document" so it evolves with the times, so to speak. Of course, like most things, this is controversial. Congress has the power... "To promote the Progress of Science and useful Arts, by securing for limited Times to Authors and Inventors the exclusive Right to their respective Writings and Discoveries." Article 1, Section 8, Clause 8 This is so vague that it practically begs for judicial interpretation.
- skylan_q 12y agooblig: But if you can't copyright APIs no one will make them!
- sillysaurus3 12y agoQuick question: Why can't an API be copyrighted? My understanding is that the purpose of a copyright is to protect a specific arrangement of ideas. A piece of music, a book, a painting. All of those things are an arrangement, and the arrangement itself is what's protected by copyright, not the physical object that was created. So, given that an API is an arrangement of ideas, and that copyright apparently protects arrangements of ideas, why is copyright inapplicable here? If the argument is that copyrights shouldn't apply to APIs, then I understand. It's probably more harmful than beneficial, and thus should be prevented. But if the argument is that copyright is incompatible with the domain of APIs, as if you were trying to copyright a taste like chocolate or copyright a smell, then I don't understand that at all. Would anyone mind clarifying?
- ewillbefull 12y agoThe Copyright Act states: "In no case does copyright protection for an original work of authorship extend to any idea, procedure, process, system, method of operation, concept, principle, or discovery, regardless of the form in which it is described, explained, illustrated, or embodied in such work." The common belief is that an API meets this "system or method of operation" standard.
- sillysaurus3 12y agoHmm... What's a "method of operation" in the context of computer programs? This isn't helpful: http://legal-dictionary.thefreedictionary.com/Method+of+operation http://legal-dictionary.thefreedictionary.com/Method+of+oper... I really don't understand how an API is a method of operation in any sense. It's an understanding between people about how to use a software library. The only sense that I could see it being a method of operation is literally "This is a description of how you operate the software library." In other words, an API is an instruction booklet for people, not computers. But in that case, why are instruction booklets copyrightable, but not software APIs?
- ewillbefull 12y agoHonestly, just read the brief, it goes into detail the precedent involved in their argument: https://www.eff.org/files/2014/11/07/google_v_oracle_computer-scientists-certpetition-amicus-brief_14-410_final.pdf https://www.eff.org/files/2014/11/07/google_v_oracle_compute... for example... Ninth Circuit law—which should have been controlling in this case—was the same: the “functional requirements for compatibility” between computer programs “are not protected by copyright.” Sega Enters., Ltd., v. Accolade, Inc. Also, an API is much more than you think. An API might be Windows' system APIs which applications use to interact with the operating system -- put a license behind that and WINE is gone overnight. An API is also totally indistinguishable from a network protocol, in both a technical and legal sense.
- christianbryant 12y agoWhile I personally fully support this, I wonder if we shouldn't be doing this in two stages, where the first stage is that we ask the penalties for perceived AIP copyright or intellectual property infringement be modified. Multi-million and multi-billion dollar lawsuits continue to be sickening in a world where these dollar amounts could be used to save human lives. Long live FLOSS, but we need to also be strategic and remember who our audience is.
- jrochkind1 12y agoMany in this thread seem to be wondering about the legal argument itself -- that API's being copyrightable is inconsistent with existing pretty well-established law. Which is, yes, a different thing than arguing about whether it's "a good idea" for society or innovation or whatever. The EFF summary focuses on the "good idea" thing, but the actual amicus brief addresses both -- although I bet you can find even more of the legal arguments in the first party brief. From the amicus brief, take a look at the original brief, starting on numbered page 4, "I. The Federal Circuit’s Decision Has Disrupted Decades of Settled Expectations That APIs Are Not Copyrightable" > That assumption was well-founded. It was based, in large part, on this Court’s own recognition, in 1996, that menu hierarchies that control functional capabilities are a method of operation, and thus uncopyrightable under 17 U.S.C. § 102(b). Lotus Dev. Corp. v. Borland Int’l, Inc., 49 F.3d 807, 815 (1st Cir. 1995), aff’d by an equally divided Court, 516 U.S. 233 (1996). Programmers and developers relied on that ruling for the proposition that APIs, like the menu hierarchy in Lotus, may not be copyrighted under § 102(b). Ninth Circuit law—which should have been controlling in this case—was the same: the “functional requirements for compatibility” between computer programs “are not protected by copyright.” Sega Enters., Ltd., v. Accolade, Inc., 977 F.2d 1510, 1522 (9th Cir. 1992); see alsoSony Computer Ent’mt, Inc. v. Connectix Corp., 203 F.3d 596, 599–600 (9th Cir. 2000) (describing Sony’s PlayStation BIOS as a “system interface procedure[]” that Connectix was entitled to reimplement under § 102(b)).
- throwawaykf05 12y agoI don't think the cited case law for exemptions for interoperability in interfaces applies to this case. For instance, the Sega and Sony cases apply for, as far as I can tell, computer systems interoperating with each other. Lotus applies to humans operating software applications running on computer systems. APIs on the other hand, are mainly for humans to communicate with each other when building systems that interoperate. As such, APIs are primarily a means of expression between humans - from those who provide the interface, to those who use it. So from a copyright perspective, I don't see how binary interoperability between systems or the GUI layouts can compare to textual expression between humans. Also, as others have mentioned, the whole "method of operation" argument is also a dangerous slope to be slipping down. What is all code anything other than a "method of operation" of the hardware it runs on? I've said it before, but copyright is not really a good mechanism for IP protection of code. Software was shoehorned under copyright because 1) other mechanisms were not available and 2) there is sometimes creative expression involved in writing code. It's only the potential of creative expression what grants copyright protection to any written code. By that standard, APIs are no different from any other code.
- Radim 12y agoMandatory link to the "What colour are your bits?" article: http://ansuz.sooke.bc.ca/entry/23 http://ansuz.sooke.bc.ca/entry/23 (law vs. computer science perspective on information; go read if you haven't yet!)
- WalterBright 12y ago> The list also includes designers of computer systems and programming languages I'll sign it, too. - designer of the D programming language
- judk 12y agoWhy was Microsoft's J thing an illegal Java bastardization, but Google's Dalvik/Android is not?
- gdwatson 12y agoMicrosoft had licensed Java, and had agreed to the terms of Sun's trademark license, including compatibility terms. Google avoided licensing Java entirely, hence the lawsuit.
- judk 12y agoBut licenses grant (limited) rights, not take rights way.
- lmm 12y agoMicrosoft was granted a right to use the Java trademarks under certain conditions - conditions which it then violated while continuing to use those trademarks, meaning it was violating Sun's Java trademark, not the copyright. Google avoids using the Java trademarks entirely. Trademark law is primarily to protect customers - people who bought "Microsoft Java" (yes, it was more complicated than handing cash to MS and getting Microsoft Java, but the point stands) thought they were getting Java, and they weren't (the whole point of Java was "write once, run anywhere", but programs written under Microsoft Java often wouldn't run on Sun Java). Whereas there is no such confusion when people buy "Google Dalvik".
- Oletros 12y agoBecause Microsoft called its implementation Java
- tzs 12y agoI'm a little confused by how precedent works here. Normally, in a copyright case, the appeals court for a case heard in the 9th Circuit would be the Court of Appeals for the 9th Circuit. The ruling of that court would then be binding precedent for future 9th Circuit cases. However, in this case the case in the district court was both a copyright case AND a patent case, and for patent cases the appeals court is the Court of Appeals for the Federal Circuit (they have exclusive subject matter jurisdiction over patent appeals). The CAFC only got the copyright case because it came along for the ride with the patent case. How does precedent work when the CAFC gets something that would normally not go through them? Do they still set national precedent for that, or do they just set precedent for subsequent cases that are appealed to CAFC (e.g., subsequent copyright cases that hitch a ride on something the CAFC has exclusive subject matter jurisdiction over)?
- zaroth 12y agoI really do hope we can't copyright a single function signature. But then, you expand it into an entire framework, or the perfectly designed kernel... What is software if not a collection of API calls? There's clearly something worth copyrighting at some point. I think what it comes down to is it's copyright, but there's an exception for compatibility. Like a 3rd party part in your car. You can't claim it's the other brand's product, but you can claim it's compatible with that brand. It happens all the time, in all industries. So why can't it be the same with software APIs? A copyright exception for "interfaces" sounds like a pretty safe approach. Unless their's a patent involved preventing someone from recreating a certain process or method, or a trademark preventing confusion, the act of creativity itself cannot be bounded. Copyright gives rights to the creator for their own creation. It can't prevent someone else from trying to create the same thing with their own hands.
- nimbosa 12y agoi Think the best analogy to this situation: Oracle (or its predecessor) published a cookbook and it tries to indemnify anyone profiting from it, like a restaurant or catering service that utilizes the same recipes compiled therein.. the cookbook in itself has copyright, but utilizing the instructions from it for your own food or business is not exactly the same as republishing the cookbook itself or redistributing it imagine if someone could copyright the way we make grilled cheese sandwiches