Covered Work definition.
This commit is contained in:
parent
07a02b0b1c
commit
1eef642eff
1 changed files with 8 additions and 11 deletions
19
gpl-lgpl.tex
19
gpl-lgpl.tex
|
@ -2309,18 +2309,15 @@ set forth in GPLv3~\S5, as described later in this tutorial in its
|
|||
rights, and then this definition of ``modify'' is used to define ``modified
|
||||
version of'' and ``work based on,'' as synonyms.
|
||||
|
||||
\section{The Covered Work}
|
||||
|
||||
%FIXME: transition
|
||||
|
||||
While ``covered by this license'' is a phrase found in GPLv2, defining it
|
||||
more complete in a single as ``covered work'' enables some of the wording in
|
||||
GPLv3 to be simpler and clearer than its GPLv2 counterparts.
|
||||
|
||||
|
||||
%FIXME: should we keep this? maybe a footnote?
|
||||
|
||||
|
||||
%FIXME: GPLv3, reword a bit.
|
||||
GPLv3 uses a common license drafting technique of building upon simpler
|
||||
definitions to make complex ones. The Program is a defined term found
|
||||
throughout GPLv2, and the word ``covered'' and the phrase ``covered by this
|
||||
license'' are used in tandem with the Program in GPLv2, but not as part of a
|
||||
definition. GPLv3 offers a single term ``covered work'', which enables some
|
||||
of the wording in GPLv3 to be simpler and clearer than its GPLv2
|
||||
counterparts.
|
||||
|
||||
|
||||
% FIXME: does propagate definition still work the same way in final draft?
|
||||
|
|
Loading…
Reference in a new issue