What legal theory would make a user of an API a derivative work if the API is not itself copyrightable?

On 06/11/2012 12:37 AM, Rick Moen wrote:
I belive I heard that his holding is that
Google wrote or commissioned independent code implementations of all
37, leaving only the question of whether the designs and names of the
functions in the reference API packages are covered by copyright.
He said they weren't -- which does not strike me as very surprising,
given the uncopyrightabilty of names and the idea/expression dichotomy
(patent/copyright division).   Other than giving clarification that
claiming an API is inherently copyrightable isn't going to fly, it
doesn't seem likely to cast light on other areas of copyright law.
In particular, it cases none on what suffices to create a new work and
what is a derivative work.

<<attachment: bruce.vcf>>

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
License-discuss mailing list
License-discuss@opensource.org
http://projects.opensource.org/cgi-bin/mailman/listinfo/license-discuss

Reply via email to