3 ms·
Is there a reason this just applies to software, or is the principle more general? In a sense, Wendy’s “reimplements” the “supersize my combo meal” interface.[
by SilasX 7y ago
Is there a reason this just applies to software, or is the principle more general?
In a sense, Wendy’s “reimplements” the “supersize my combo meal” interface.[1] They call it “biggie-sizing”, but...
Let’s say Wendy’s instructs employees that “if someone asks for a meal to be supersized, handle the request as if they had asked for it to be biggie-sized”. Could that conceivably be an API copyright violation?
[1] McDonald’s lets you “supersize” your order which means paying extra to get a larger drink and order of fries.
- MichaelApproved 7y ago"Super Size" is a McDonald's trademark, so it falls under different rules. I'm guessing many menu items are trademarked as well. https://trademarks.justia.com/744/51/super-size-74451719.html https://trademarks.justia.com/744/51/super-size-74451719.htm...
- SilasX 7y agoRight, but I think my example sidesteps the trademark complication because Wendy’s doesn’t brand it as supersizing; they just respond to “supersize” requests in accordance with McDonald’s public spec.
- MichaelApproved 7y agoYeah, I was being pedantic with my response.
- btilly 7y agoThe principle is more general. According to copyright law, you can copyright creative expression but not anything that is necessary to the functionality of what you're building. However those might be protected under patents, trademark, or trade secrets laws. Previous to this case, the code that implements the API can be copyrighted, since it is possible to implement the functionality with different code. But the code that specifies the API interface is absolutely required for compatibility if you want code that is written for one system to be compiled against the other. However a national precedent put down by the Federal Circuit (the same court that caused software patents to blossom out of control) decided that there is enough creative expression in API interfaces for them to be copyrighted, despite them being necessary for compatibility. Most people in software think that the previous precedent was better. Hopefully the Supreme Court will agree. (They overturn the Federal Circuit more often than not.) Going to your fast food example, I'm pretty sure that trademark law applies, which is quite a bit different. But you can't copyright or trademark the act of making the meal larger. (You could patent it..but McDonald's didn't. And even if they had, the patent would now be expired.) But you can trademark the term used to ask for it. And so Wendy's is not allowed to use that term. They can understand it, but not use it. However at some point if "supersize" falls into common use, Wendy's could file a lawsuit saying that it is generic, and THEN they could use it. (Losing trademark due to a term becoming generic is one of the differences between trademark law and copyright law.)
- SilasX 7y ago>They can understand it, but not use it. Right, and isn't that what Google is doing? "Hey, if you send a message in the Java language/API, we will understand it and do the same thing that a real java program will do." "Hey, if you request that a meal be supersized, we'll understand what you intend and execute the Biggie-size operation, which matches what McDonald's would do." Of course, there is the difference that, unlike Wendy's, Google is (analogous to) telling everyone "you can ask the cashier to supersize your meal" instead of just rolling their eyes and accommodating confused consumers. >Going to your fast food example, I'm pretty sure that trademark law applies, As in the sibling subthread, I think the example sidesteps the trademark complication because Wendy's doesn't ever use "supersize" in promotion, they just passively accept user-initiated requests that use the term, and do so in a way compatible with their McDonald's-derived expectations.
- withjive 7y agoAs an Android developer during the first G1 era, I feel that Google was really taking advantage of the well established Java developer base. Having developers already understand Java, was a huge thing for Android when it first came out. So when you say: > Wendy’s doesn’t ever use “supersize” in their promotions IANAL, So I’m not sure Google didn’t do the same... I also think Oracle is also not happy with that.
- SilasX 7y agoRight but what if the java API is nominally “secondary”: “oh use this Byzantine Android api we have ... but if you just treat it like java, it’ll guess what you mean, ruby-magic-method style”?
- kevin_thibedeau 7y agoThe more general principle is that interchangeable parts of a system aren't covered by IP outside of active patents. Magnuson-Moss guarantees that third-party replacement parts don't void a warranty. A brake disc that interfaces with a hub and caliper specification can be sourced from a variety of vendors. The OEM has no say in the matter unless there is patent or trademark infringement involved. I can also make and sell my own vehicle that is compatible with the same brake discs of an OEM provided there is no IP infringement. Just because Oracle used copyrighted IP to create a public interface doesn't mean that copyright can extend across that boundary. Copyright does not extend into the realm of mechanisms for information exchange. That's what patents are for.
- SilasX 7y agoOkay that's a rejection of API copyright entirely (which I mostly agree with), but I was more interested in the internal logic of it all: that is, if I accepted API copyright, and if it's a fully general concept (not just software), could you have a situation where Wendy's is prohibited from correctly guessing what you "really mean" by asking for your meal to be supersized?
- danShumway 7y agoThe fast food analogy feels weird to me because of trademark implications. The analogy I would use is, should the shape and usage of a steering wheel be copyrightable? Should a company be able to prevent someone else from building a car that has the same steering wheel, stick-shift, break on the left/gas on the right interface? After all, you could easily argue that building an intuitive car interface was a difficult, creative act. A ton of work has gone into making modern cars intuitive, and it's not like any of that design is obvious or trivial. The answer to that question has profound implications for the ability of businesses to compete, and much more profound implications for our general ability as consumers to get products that act the way we expect, and to avoid radical amounts of vendor lock in. Imagine a world where the interface for shifting gears was different for every car brand, or where notifications like turn signals, or errors like a check engine light couldn't be copied. It would make the automotive market uniformly more annoying, more dangerous, and less competitive.