This again, could be handled as a conjunction of the license plus the
toggle quoted messageShow quoted text
clause that allows the upgrade.
Licenses for a given file: GPLv2 _AND_ Any_NEWER_VERSION or something like thatl
On Tue, Nov 9, 2010 at 10:16 AM, Jilayne Lovejoy <Jlovejoy@...> wrote:
I would agree with Peter's assessment below. To be clear, my
interpretation of this would be that this would remove the various "or
later" instances from the actual license list and then that option would
be handled elsewhere.
Does anyone else have any thoughts on this?
This is an easy update to make and I was hoping to upload a new license
list version with various updates this week, just prior to Friday's
* How do we want to handle LGPL/GPL "vXor later" versus LGPL/GPLvX?
I think this should not be handled at license level. There is no such
license as "GPL v2 or later". Rather, content is licensed under the
disjunctive set of all GPL licenses with a version greater than or equal
If licenses expressed their version relationships using dc:isVersionOf
and dc:replaces we could leverage that information. Using the version
relationships we could define a version based disjunctive license set.
This set would specify the minimum acceptable version of the license,
e.g. GPLv2. A license would be considered to be part of such a set if
it "replaces" and "isVersionOf", either directly or indirectly, the
minimum acceptable version.
Spdx mailing list