But I think your example still doesn't quite capture what I mean ... even though, well, maybe it does, but let me explain ;-): What I had in mind is in particular that getting familiar with an API requires effort, so it's kindof an investment on the part of the developer. After all, an API is as much a human/machine interface as it is a machine/machine interface. As such, it is problematic to allow anyone to have a monopoly on that investment, essentially a monopoly on the use of those developers' knowledge. And protection of investments is one of the arguments (the argument?) for interoperability exceptions--so, why only for machine/machine interoperability and not also for human/machine interoperability?
I guess the "investment" aspect doesn't work that well for your example, but I still can see some value in the argument, in particular if you apply it to DRM (type) systems and culture in general.
To explain some more with my photograph comment: the photograph might have taken time and context and thought on behalf of an entire population of viewers to come to some "meaning"; maybe this is more obvious if we take a storyline from a popular television show: before the show people didn't care about the topic of the show, but after the investment, quality, and success of the show now people really like that topics and in particular the story progression that went along with it.
People are familiar with that story: to really allow those people to feel good about the new story, maybe it has to be similar to the old one? If you go down this path for a while, you start reading about idea/expression differences as they apply to literary and visual works: high-level plots and themes are not protected, but specific details and timelines are. The idea of organizing code into packages and classes is not, but the specific choice of what classes to put in what packages and what they are named are.
FWIW, I personally feel like a lot of the benefit of trying to be "interoperable" with someone's perception of how to program is sufficient to be at that higher "idea" level: when I use C# or Objective-C (which in many ways feel similar to Java and in the case of C# was pretty much designed as a direct replacement for Java) I am highly familiar with them despite not feeling like they are the same: I gain a lot of the benefit of C# and Java having similar ideas, despite the fact that they clearly have different expressions.
Now, that said? I continue to appreciate the idea that this is all a stupid distinction: but if you erase this distinction I am not certain where you still draw the line for claiming copyright on anything. Given the idea "investment in expression should be protected" (an admittedly-oversimplified version of "copyright"), I don't think you still have "investment by consumers in content should be inherently reusable by other creators". I could be wrong, however, and would love to hear more ideas.
http://www.fosspatents.com/2012/05/oracle-v-google-fair-use-...
http://www.fosspatents.com/2014/01/why-google-books-is-proba...
While I'm not a lawyer, it would make sense to me for API reimplementation not to be fair use when viewed from the perspective of copying "declaring code", even if interoperability is stronger or argued stronger. Incorporating part of a copyrighted work in a new work intended for exactly the same use, which competes with the original, is not "transformative", and certainly has an "effect of the [] value of the copyrighted work"; it doesn't look much at all like normal examples of fair use, such as thumbnails and quotations.
Also, I did read the decision itself, and the part about fair use didn't seem particularly friendly to Google's argument, even if the issue was remanded. In particular,
"We find this particularly true with respect to those core packages which it seems may be necessary for anyone to copy if they are to write programs in the Java language."
where "this" is relevance to fair use, reflects badly on the majority of packages which are not necessary to write programs in the Java language. (I think this definition of "language" is nonsense, as even though it's what a programmer would call the Java language, I think the analogy is to human languages, which were found to not be copyrightable; yet human languages include a large amount of vocabulary, which I find analogous to API declarations. However, it's what the court used.)
We will have to see what happens in the Android case, including appeals, as well as any future cases (though I'd say the former has a good chance of producing a chilling effect that will greatly decrease the probability of potential subjects of the latter from even being created), but I don't agree with your relatively positive assessment of the power of fair use.
Also, fair use determinations can, like in this case, be decided by the jury rather than the judge, and I trust juries far less than judges to weigh how the facts actually apply to the law rather than whether it feels like some company ripped off some other company.
More importantly, though: nor am I even certain I wish/hope that Google does win, as I have great sympathy for the argument that they were never intending to build an interoperable system. I tried very hard to not put a strong opinion in my comment on the other thread (as I really and truly can appreciate a number of other consistent positions, including ones as strong as "copyright is inherently wrong"), so I'm guessing you just assumed me to be arguing for the thing you wanted (which sounds like "Google should win"): I maintain my "relatively positive assessment" even in the situation where Google loses, as I think this case is materially different than ones I care about.
Finally, I will point out that you are preaching to the choir on "chilling effects": that is what my entire final paragraph both admits and (in the nod to the comment from grellas with respect to "uncertainty") laments. The only positive thing is that "interoperability" does have some status in the world of copyright, if nothing else in the DMCA's reverse engineering restrictions, and there is a wide pool of precedent for the legality of building systems based on the knowledge from said reverse engineering (so it isn't just that you get to reverse engineer things and then feel satisfied with the knowledge: you get to release production systems that embody that learned knowledge).
https://news.ycombinator.com/item?id=7723853