Changeset - 6b106e6a9ae3
[Not reviewed]
0 1 0
vbejdo - 4 years ago 2020-06-16 19:33:38
bejdo@uw.edu
Minor edits (grammar, use) until I.4.2.2.
1 file changed with 5 insertions and 5 deletions:
0 comments (0 inline, 0 general)
gpl-lgpl.tex
Show inline comments
...
 
@@ -1153,16 +1153,16 @@ the primary unit of consideration under most copyright rules -- is not a unit
 
of computer programming. In order to determine whether a ``routine'' an
 
``object'', a ``function'', a ``library'' or any other unit of software is
 
part of one ``work'' when combined with other GPL'd code, we must ask a
 
question that copyright law will not directly answer in the same technical
 
terms.
 

	
 
Therefore, this chapter digresses from  discussion of GPL's exact text to
 
Therefore, this chapter digresses from a discussion of GPL's exact text to
 
consider the matter of combined and/or derivative works --- a concept that we must
 
understand fully before considering GPLv2~\S\S2--3\@.  At least under USA
 
copyright law, The GPL, and Free
 
copyright law, the GPL, and Free
 
Software licensing in general, relies critically on the concept of
 
``derivative work'' since software that is ``independent,'' (i.e., not
 
``derivative'') of Free Software need not abide by the terms of the
 
applicable Free Software license. As much is required by \S~106 of the
 
Copyright Act, 17 U.S.C. \S~106 (2002), and admitted by Free Software
 
licenses, such as the GPL, which (as we have seen) states in GPLv2~\S0 that ``a
...
 
@@ -1171,19 +1171,19 @@ work under copyright law.'' It is being a derivative work of Free Software
 
that triggers the necessity to comply with the terms of the Free Software
 
license under which the original work is distributed. Therefore, one is
 
left to ask, just what is a ``derivative work''? The answer to that
 
question differs depending on which court is being asked.
 

	
 
The analysis in this chapter sets forth the differing definitions of
 
derivative work by the circuit courts. The broadest and most
 
derivative work set out by United States circuit courts. The broadest and most
 
established definition of derivative work for software is the
 
abstraction, filtration, and comparison test (``the AFC test'') as
 
created and developed by the Second Circuit. Some circuits, including
 
the Ninth Circuit and the First Circuit, have either adopted narrower
 
versions of the AFC test or have expressly rejected the AFC test in
 
favor of a narrower standard. Further, several other circuits have yet
 
favor of narrower standards. Further, several other circuits have yet
 
to adopt any definition of derivative work for software.
 

	
 
As an introductory matter, it is important to note that literal copying of
 
a significant portion of source code is not always sufficient to establish
 
that a second work is a derivative work of an original
 
program. Conversely, a second work can be a derivative work of an original
...
 
@@ -1193,13 +1193,13 @@ protection does not always extend to all portions of a program's code,
 
while, at the same time, it can extend beyond the literal code of a
 
program to its non-literal aspects, such as its architecture, structure,
 
sequence, organization, operational modules, and computer-user interface.
 

	
 
\section{The Copyright Act}
 

	
 
The copyright act is of little, if any, help in determining the definition
 
The Copyright Act is of little, if any, help in determining the definition
 
of a derivative work of software. However, the applicable provisions do
 
provide some, albeit quite cursory, guidance. Section 101 of the Copyright
 
Act sets forth the following definitions:
 

	
 
\begin{quotation}
 
A ``computer program'' is a set of statements or instructions to be used
0 comments (0 inline, 0 general)