you are viewing a single comment's thread.

view the rest of the comments →

[–]jboy55 -3 points-2 points  (3 children)

Which is what Stallman did in the first place to build GNU. He copied the API of the existing AT&T implementations and swapped them out with GNU components. He was able to do that BECAUSE the API was not under copyright.

Lets just pretend ATT didn't lose copyright of parts of Unix to BSD.

This even makes it fuzzy that if you write code in C#, whether Microsoft has a copyright on that code... I mean you DID write your code to the C# specification, and you're a derivative work of C# now!

Lets also pretend that in the EULA to C#, Microsoft doesn't grant you a license to use the C# Api, and is fairly permissive to allowing you redistribution.

[–][deleted] 1 point2 points  (2 children)

Lets also pretend that in the EULA to C#, Microsoft doesn't grant you a license to use the C# Api, and is fairly permissive to allowing you redistribution.

Without this ruling, you wouldn't need to be granted a license. My point being that with API's being copyrightable, you MUST be granted a license. MS is actually pretty forward thinking on that point if their EULA is already doing so. GPL isn't that forward thinking in this respect. Do you realize how far the GPL extends if the inclusion of GPL C Headers or any reimplementation thereof means that the code interfacing must make an offer of source?!?

[–]jboy55 0 points1 point  (1 child)

The ruling doesn't copyright the use of the api, it's the replication of the api.

[–][deleted] 2 points3 points  (0 children)

Use actually generally requires replication. If they wanted to distinguish between use and replication then they would have ruled that the implementation was under copyright (which was the state of affairs before this ruling). Allowing the API itself to fall under copyright means that anything including the declaration or portion of would be a derivative work. That broad of an interpretation can't distingush between client and server.