2 ms·
In terms of scope I can agree that there is a bit of a difference, in that we're talking about whether you can copyright an entire library design versus a speci
by _delirium 15y ago
In terms of scope I can agree that there is a bit of a difference, in that we're talking about whether you can copyright an entire library design versus a specific limited set of interconnection points. But even that would be problematic and contrary to existing practice; for example, Wine's reimplementation of the Win32 API would be a copyright violation if the Win32 API (and not just the code implementing it) is copyrightable. It contradicts the assumptions behind clean-room reverse engineering as well, which are that how-something-works documentation doesn't taint copyright of a new implementation that follows it as a spec.
- rwolf 15y agoI have no problem with the idea that being able to copyright library APIs might affect other kinds of APIs. See http://news.ycombinator.com/item?id=2916969 http://news.ycombinator.com/item?id=2916969 for a longer description of why I think the article is talking about how apple-y oranges are.
- deleted 15y ago[deleted]
- ismarc 15y agoThere's also the middle ground of the mysql api that has long been claimed as being under the gpl (but never tested in court as far as I know). There is a real danger here that could affect emulators, compatability layers, really any interoperability in place of proprietary systems and would be a real step backwards. But, we are not the audience of the article and web apis are easier to explain to non-developers.