From 1eef642effa9438840708c7af7941c172313c52d Mon Sep 17 00:00:00 2001 From: "Bradley M. Kuhn" Date: Thu, 20 Mar 2014 05:25:22 -0400 Subject: [PATCH] Covered Work definition. --- gpl-lgpl.tex | 19 ++++++++----------- 1 file changed, 8 insertions(+), 11 deletions(-) diff --git a/gpl-lgpl.tex b/gpl-lgpl.tex index 3f41f45..8623f30 100644 --- a/gpl-lgpl.tex +++ b/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?