Topics

Names of licenses we currently support

dmg
 

these the licenses we currently identify. Look particularly at the BSDs
and MIts. Some are not licenses but their exception statements. I have
the feeling that these cover around 75-86% of files in Debian/Fedora
(the source code files that have a license)

--dmg



AGPLv3+
Apachev1.1
Apachev2
artifex
ArtisticLicensev1
autoConfException
BeerWareVer42
BindMITX11Var
BisonException
boost
boostV1
BSD1
BSD2
BSD2AdvInsteadOfBinary
BSD2aic700
BSD2EndorseInsteadOfBinary
BSD2SoftAndDoc
BSD2var1
BSD2var2
BSD3
BSD3NoWarranty
BSD4
BSD4NoEndor
BSDCairoStyleWarr
BSDdovecotStyle
BSDOnlyAdv
CDDLic
CDDLicV1
CDDLv1orGPLv2
Cecill
ClassPathException
CPLv0.5
CPLv1
dovecotSeeCopying
DoWhatTheFuckYouWantv2
emacsLic
EPLv1
FreeType
GhostscriptGPL
GPLnoVersion
GPLv1
GPLv1+
GPLv1orArtistic
GPLv2
GPLv2+
GPLv2orLGPLv2.1
GPLv2orv3
GPLv2orv3qtException
GPLv3
GPLv3+
IBMv1
intelBSDLicense
InterACPILic
kerberos
LesserGPLnoVersion
LesserGPLv2
LesserGPLv2+
LesserGPLv2.1
LesserGPLv2.1+
LesserGPLv3
LesserGPLv3+
LGPLv2
LGPLv2+
LGPLv2_1
LGPLv2.1
LGPLv2.1+
LGPLv2_1orv3
LGPLv2MISTAKE
LGPLv2+MISTAKE
LGPLv2orv3
LGPLv3
LGPLv3+
LibGCJLic
LibraryGPLv2
LibraryGPLv2+
LinkException
LinkExceptionBison
LinkExceptionGPL
LinkExceptionLeGPL
LinkExceptionOpenSSL
MITandGPL
MITCMU
MITCMUvar2
MITCMUvar3
MITmodern
MITold
MIToldMichiganVersion
MIToldwithoutSell
MIToldwithoutSellandNoDocumentationRequi
MIToldwithoutSellCMUVariant
MITVariant
MITX11BSDvar
MITX11noNotice
MITX11NoSellNoDocDocBSDvar
MITX11simple
MPL1_1andLGPLv2_1
MPLGPL2orLGPLv2_1
MPL_LGPLsee
MPL-MIT-dual
MPLv1_0
MPLv1_1
MX4J
MX4JLicensev1
NCSA
NPLv1_0
NPLv1_1
openSSL
openSSLvar1
openSSLvar2
openSSLvar3
phpLicV3.01
Postfix
postgresql
publicDomain
QtGPLv2or3
QTv1
SameAsPerl
SameTermsAs
SeeFile
sequenceLic
SimpleLic
simpleLic
simpleLic2
simpleLicense1
SimpleOnlyKeepCopyright
SleepyCat
SSLeay
subversion
subversion+
subversionError
sunRPC
SunSimpleLic
svnkit
svnkit+
tmate+
W3CLic
WxException
X11
X11CMU
X11Festival
X11mit
zendv2
ZLIB
ZLIBref


--
--
Daniel M. German
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .

kate.stewart@...
 

Thanks Daniel. As the reference page for each license and its header emerge - cross checking against this is going to be useful.

Hmm, am a little concerned about putting some of them into the standard set of reference licenses. ... in particular some I think should be flagged as exceptions so they get looked at. ie. BeerWareV42 ;)
SameTermsAs and SeeFile are likely not licences but references to licenses.

Can I assume that the mapping of names to the actual license search strings can be found in Ninka sources?

In particular the BSD and MIT varients look worrisome. Any volunteers to review the details there and make some recommendations?

Kate

--- On Thu, 8/26/10, D M German <dmg@...> wrote:

From: D M German <dmg@...>
Subject: Names of licenses we currently support
To: spdx@...
Date: Thursday, August 26, 2010, 5:39 PM

these the licenses we currently identify. Look particularly
at the BSDs
and MIts. Some are not licenses but their exception
statements. I have
the feeling that these cover around 75-86% of files in
Debian/Fedora
(the source code files that have a license)

--dmg



AGPLv3+
Apachev1.1
Apachev2
artifex
ArtisticLicensev1
autoConfException
BeerWareVer42
BindMITX11Var
BisonException
boost
boostV1
BSD1
BSD2
BSD2AdvInsteadOfBinary
BSD2aic700
BSD2EndorseInsteadOfBinary
BSD2SoftAndDoc
BSD2var1
BSD2var2
BSD3
BSD3NoWarranty
BSD4
BSD4NoEndor
BSDCairoStyleWarr
BSDdovecotStyle
BSDOnlyAdv
CDDLic
CDDLicV1
CDDLv1orGPLv2
Cecill
ClassPathException
CPLv0.5
CPLv1
dovecotSeeCopying
DoWhatTheFuckYouWantv2
emacsLic
EPLv1
FreeType
GhostscriptGPL
GPLnoVersion
GPLv1
GPLv1+
GPLv1orArtistic
GPLv2
GPLv2+
GPLv2orLGPLv2.1
GPLv2orv3
GPLv2orv3qtException
GPLv3
GPLv3+
IBMv1
intelBSDLicense
InterACPILic
kerberos
LesserGPLnoVersion
LesserGPLv2
LesserGPLv2+
LesserGPLv2.1
LesserGPLv2.1+
LesserGPLv3
LesserGPLv3+
LGPLv2
LGPLv2+
LGPLv2_1
LGPLv2.1
LGPLv2.1+
LGPLv2_1orv3
LGPLv2MISTAKE
LGPLv2+MISTAKE
LGPLv2orv3
LGPLv3
LGPLv3+
LibGCJLic
LibraryGPLv2
LibraryGPLv2+
LinkException
LinkExceptionBison
LinkExceptionGPL
LinkExceptionLeGPL
LinkExceptionOpenSSL
MITandGPL
MITCMU
MITCMUvar2
MITCMUvar3
MITmodern
MITold
MIToldMichiganVersion
MIToldwithoutSell
MIToldwithoutSellandNoDocumentationRequi
MIToldwithoutSellCMUVariant
MITVariant
MITX11BSDvar
MITX11noNotice
MITX11NoSellNoDocDocBSDvar
MITX11simple
MPL1_1andLGPLv2_1
MPLGPL2orLGPLv2_1
MPL_LGPLsee
MPL-MIT-dual
MPLv1_0
MPLv1_1
MX4J
MX4JLicensev1
NCSA
NPLv1_0
NPLv1_1
openSSL
openSSLvar1
openSSLvar2
openSSLvar3
phpLicV3.01
Postfix
postgresql
publicDomain
QtGPLv2or3
QTv1
SameAsPerl
SameTermsAs
SeeFile
sequenceLic
SimpleLic
simpleLic
simpleLic2
simpleLicense1
SimpleOnlyKeepCopyright
SleepyCat
SSLeay
subversion
subversion+
subversionError
sunRPC
SunSimpleLic
svnkit
svnkit+
tmate+
W3CLic
WxException
X11
X11CMU
X11Festival
X11mit
zendv2
ZLIB
ZLIBref


--
--
Daniel M. German           
     
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .
_______________________________________________
Spdx mailing list
Spdx@...
https://fossbazaar.org/mailman/listinfo/spdx

dmg
 

I agree, not all are licenses. Exceptions, for example, are treated as
a license, but to make sense, they have to accompany a
real one.

What I recommend people do, if really interested, is look at the
sources of posgresql (see my previous message) and see the different
variants of the BSD and MIT licenses we detect.

If you run ninka, look at each of the files it creates for a given
file analyzed. they will be very helpful in understanding our
identification.
of course, reading the paper helps.

--dmg

On Thu, Aug 26, 2010 at 4:30 PM, <kate.stewart@...> wrote:
Thanks Daniel.  As the reference page for each license and its header emerge - cross checking against this is going to be useful.

Hmm,  am a little concerned about putting some of them into the standard set of reference licenses.  ... in particular some I think should be flagged as exceptions so they get looked at.  ie. BeerWareV42   ;)
SameTermsAs and SeeFile are likely not licences but references to licenses.

Can I assume that the mapping of names to the actual license search strings can be found in Ninka sources?

In particular the BSD and MIT varients look worrisome.   Any volunteers to review the details there and make some recommendations?

Kate

--- On Thu, 8/26/10, D M German <dmg@...> wrote:

From: D M German <dmg@...>
Subject: Names of licenses we currently support
To: spdx@...
Date: Thursday, August 26, 2010, 5:39 PM

these the licenses we currently identify. Look particularly
at the BSDs
and MIts. Some are not licenses but their exception
statements. I have
the feeling that these cover around 75-86% of files in
Debian/Fedora
(the source code files that have a license)

--dmg



AGPLv3+
Apachev1.1
Apachev2
artifex
ArtisticLicensev1
autoConfException
BeerWareVer42
BindMITX11Var
BisonException
boost
boostV1
BSD1
BSD2
BSD2AdvInsteadOfBinary
BSD2aic700
BSD2EndorseInsteadOfBinary
BSD2SoftAndDoc
BSD2var1
BSD2var2
BSD3
BSD3NoWarranty
BSD4
BSD4NoEndor
BSDCairoStyleWarr
BSDdovecotStyle
BSDOnlyAdv
CDDLic
CDDLicV1
CDDLv1orGPLv2
Cecill
ClassPathException
CPLv0.5
CPLv1
dovecotSeeCopying
DoWhatTheFuckYouWantv2
emacsLic
EPLv1
FreeType
GhostscriptGPL
GPLnoVersion
GPLv1
GPLv1+
GPLv1orArtistic
GPLv2
GPLv2+
GPLv2orLGPLv2.1
GPLv2orv3
GPLv2orv3qtException
GPLv3
GPLv3+
IBMv1
intelBSDLicense
InterACPILic
kerberos
LesserGPLnoVersion
LesserGPLv2
LesserGPLv2+
LesserGPLv2.1
LesserGPLv2.1+
LesserGPLv3
LesserGPLv3+
LGPLv2
LGPLv2+
LGPLv2_1
LGPLv2.1
LGPLv2.1+
LGPLv2_1orv3
LGPLv2MISTAKE
LGPLv2+MISTAKE
LGPLv2orv3
LGPLv3
LGPLv3+
LibGCJLic
LibraryGPLv2
LibraryGPLv2+
LinkException
LinkExceptionBison
LinkExceptionGPL
LinkExceptionLeGPL
LinkExceptionOpenSSL
MITandGPL
MITCMU
MITCMUvar2
MITCMUvar3
MITmodern
MITold
MIToldMichiganVersion
MIToldwithoutSell
MIToldwithoutSellandNoDocumentationRequi
MIToldwithoutSellCMUVariant
MITVariant
MITX11BSDvar
MITX11noNotice
MITX11NoSellNoDocDocBSDvar
MITX11simple
MPL1_1andLGPLv2_1
MPLGPL2orLGPLv2_1
MPL_LGPLsee
MPL-MIT-dual
MPLv1_0
MPLv1_1
MX4J
MX4JLicensev1
NCSA
NPLv1_0
NPLv1_1
openSSL
openSSLvar1
openSSLvar2
openSSLvar3
phpLicV3.01
Postfix
postgresql
publicDomain
QtGPLv2or3
QTv1
SameAsPerl
SameTermsAs
SeeFile
sequenceLic
SimpleLic
simpleLic
simpleLic2
simpleLicense1
SimpleOnlyKeepCopyright
SleepyCat
SSLeay
subversion
subversion+
subversionError
sunRPC
SunSimpleLic
svnkit
svnkit+
tmate+
W3CLic
WxException
X11
X11CMU
X11Festival
X11mit
zendv2
ZLIB
ZLIBref


--
--
Daniel M. German

http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .
_______________________________________________
Spdx mailing list
Spdx@...
https://fossbazaar.org/mailman/listinfo/spdx
--
--dmg

---
Daniel M. German
http://turingmachine.org

dmg
 

kate> In particular the BSD and MIT varients look worrisome. Any
kate> volunteers to review the details there and make some
kate> recommendations?

If SPDX is interested, look at the data for postgresql that I send few
days ago. You'll see samples of the following licenses:

BSD2
BSD3
BSD3NoWarranty
BSDOnlyEndorseNoWarranty
GPLv2+,BisonException
MIToldwithoutSellandNoDocumentationRequi
MITX11noNotice
MITX11NoSellNoDocDocBSDvar
postgresql
postgresqlRef
publicDomain
SameAsPerl

Perhaps Postgresql is a good example of a project to document using
SPDX. It is not too large, but it uses a fair number of licenses, some
well know, and some not.

kate> Kate

--
--
Daniel M. German
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .