user debian-pol...@packages.debian.org usertags 697134 normative issue thanks
Le Tue, Jan 01, 2013 at 12:41:57PM -0800, Jonathan Nieder a écrit : > > Russ Allbery wrote[1]: > > Jonathan Nieder <jrnie...@gmail.com> writes: > >>> Jonathan Nieder <jrnie...@gmail.com> writes: > >>>> Russ Allbery wrote: > > >>>>> It might be worthwhile to recognize some sort of syntax similar to > >>>>> license exceptions so that one can tag the license as "BSD-3-Clause by > >>>>> <copyright holder>" or the like. > >> [...] > >>>> The next sentence "IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE > >>>> LIABLE" also varies, and not always in the same way as the first. > [...] > >> If we change the syntax a little to allow arbitrary identifiers for > >> each variant, à la "BSD-3-Clause, MIT variant #1", then I think I was > >> just taking a long time to agree completely with your proposed change. > >> ;-) > > > > Oh, yes, that would work. I missed that my proposed "by" syntax implied > > that the only thing that changed was the copyright holder. Maybe > > "variant" would be a better keyword, taking an arbitrary label. > > Filing to avoid forgetting. Hello everybody, there was an interesting thread about "the variability of BSD and MIT licenses" on the SPDX mailing list. http://lists.spdx.org/pipermail/spdx/2012-December/000785.html I think that licenses that do not have the same terms are not the same licenses. It can be useful to group licenses that are sufficiently similar, but let's not underestimate the difficulty. It will be important to define the aim of this grouping. Focusing on variants underlines which license texts are derivative of each other, which is not directly relevant to the users who only want to know what they have to do to comply with a license. Such groupings will need to be complemented by safeguards to ensure that close variants with signicant differences are not grouped together. If the goal is to help automated analysis of license terms, then the approach above is quite imperfect as it will be hard to generalise beyond the BSD variants. More structured descriptions would be needed, with a complexity in between http://creativecommons.org/ns and http://www.w3.org/ns/radion. Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130101220451.ga15...@falafel.plessy.net
