Topics

on license variability


dmg
 

First, some common equivalent words/phrases:

----------------------------------------------------------------------
license|licence
distributable|licensed|released|made available
can|may
terms and conditions|terms
library|program|software
developed|written
MERCHANTIBILITY|MERCHANTABILITY
is|are
do not|don<quotes>t
the copyright|that copyright
would|will
IN THE SOFTWARE
WITH THE SOFTWARE
deal in|deal with
----------------------------------------------------------------------
The quotes are also very different in different files:

quotes can be ``, '', ", '

----------------------------------------------------------------------
Finally, this is a subset of the way Ninka recognizes the BSD3
clauses. I believe this will cover most versions. The numbers preceding
the conditions are sometimes not there (Ninka drops them, or any bullets
before it continues with the processing).


Copyright (c) <field1>
All rights reserved\.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:

1\. Redistributions? of source code must retain the (above )?copyright
notice, this list of conditions(,)? and the following disclaimer(,
without modification)?.

2\. Redistributions in binary form must reproduce the above copyright
notice(\(s\))?, this list of conditions(,)? and the following
disclaimer(s)? in the documentation and/or other materials provided
with the distribution\.

3\. Neither the name(s)? of <field2> may be used to endorse or promote
products derived from this software without (specific )?prior written
permission:

THIS SOFTWARE IS PROVIDED BY <field3><quotes>AS IS<quotes> AND ANY
EXPRESS(ED)? OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANT(A|I)BILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED\. IN NO EVENT SHALL <field4> BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES \(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF (MIND, )?USE, DATA,( LIFE)? OR PROFITS; OR
BUSINESS INTERRUPTION\) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT \(INCLUDING NEGLIGENCE
OR OTHERWISE\) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE\.
----------------------------------------------------------------------


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


kate.stewart@...
 

The ? notation in the template, does it mean that what preceeds in brackets is optional. ie. (s)? means that the s could or could not appear?

Kate

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

From: D M German <dmg@...>
Subject: on license variability
To: spdx@...
Date: Thursday, September 16, 2010, 1:13 PM

First, some common equivalent words/phrases:

----------------------------------------------------------------------
license|licence
distributable|licensed|released|made available
can|may
terms and conditions|terms
library|program|software
developed|written
MERCHANTIBILITY|MERCHANTABILITY
is|are
do not|don<quotes>t
the copyright|that copyright
would|will
IN THE SOFTWARE
WITH THE SOFTWARE
deal in|deal with
----------------------------------------------------------------------
The quotes are also very different in different files:

quotes can be ``, '', ", '

----------------------------------------------------------------------
Finally, this is a subset of the way Ninka recognizes the
BSD3
clauses. I believe this will cover most versions. The
numbers preceding
the conditions are sometimes not there (Ninka drops them,
or any bullets
before it continues with the processing).


Copyright (c) <field1>
All rights reserved\.

Redistribution and use in source and binary forms, with or
without
modification, are permitted provided that the following
conditions are
met:

1\. Redistributions? of source code must retain the (above
)?copyright
notice, this list of conditions(,)? and the following
disclaimer(,
without modification)?.

2\. Redistributions in binary form must reproduce the above
copyright
notice(\(s\))?, this list of conditions(,)? and the
following
disclaimer(s)? in the documentation and/or other materials
provided
with the distribution\.

3\. Neither the name(s)? of <field2> may be used to
endorse or promote
products derived from this software without (specific
)?prior written
permission:

THIS SOFTWARE IS PROVIDED BY <field3><quotes>AS
IS<quotes> AND ANY
EXPRESS(ED)? OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANT(A|I)BILITY AND FITNESS FOR A
PARTICULAR
PURPOSE ARE DISCLAIMED\.  IN NO EVENT SHALL
<field4> BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL
DAMAGES \(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE
GOODS OR SERVICES; LOSS OF (MIND, )?USE, DATA,( LIFE)? OR
PROFITS; OR
BUSINESS INTERRUPTION\) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT \(INCLUDING
NEGLIGENCE
OR OTHERWISE\) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE\.
----------------------------------------------------------------------


--
--
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
 

Posix regular expressions. Yes, (s)? means that sometimes the s is not there.

On Thu, Sep 16, 2010 at 11:47 AM, <kate.stewart@...> wrote:
The ? notation in the template,  does it mean that what preceeds in brackets is optional.   ie. (s)?  means that the s could or could not appear?

Kate

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

From: D M German <dmg@...>
Subject: on license variability
To: spdx@...
Date: Thursday, September 16, 2010, 1:13 PM

First, some common equivalent words/phrases:

----------------------------------------------------------------------
license|licence
distributable|licensed|released|made available
can|may
terms and conditions|terms
library|program|software
developed|written
MERCHANTIBILITY|MERCHANTABILITY
is|are
do not|don<quotes>t
the copyright|that copyright
would|will
IN THE SOFTWARE
WITH THE SOFTWARE
deal in|deal with
----------------------------------------------------------------------
The quotes are also very different in different files:

quotes can be ``, '', ", '

----------------------------------------------------------------------
Finally, this is a subset of the way Ninka recognizes the
BSD3
clauses. I believe this will cover most versions. The
numbers preceding
the conditions are sometimes not there (Ninka drops them,
or any bullets
before it continues with the processing).


Copyright (c) <field1>
All rights reserved\.

Redistribution and use in source and binary forms, with or
without
modification, are permitted provided that the following
conditions are
met:

1\. Redistributions? of source code must retain the (above
)?copyright
notice, this list of conditions(,)? and the following
disclaimer(,
without modification)?.

2\. Redistributions in binary form must reproduce the above
copyright
notice(\(s\))?, this list of conditions(,)? and the
following
disclaimer(s)? in the documentation and/or other materials
provided
with the distribution\.

3\. Neither the name(s)? of <field2> may be used to
endorse or promote
products derived from this software without (specific
)?prior written
permission:

THIS SOFTWARE IS PROVIDED BY <field3><quotes>AS
IS<quotes> AND ANY
EXPRESS(ED)? OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANT(A|I)BILITY AND FITNESS FOR A
PARTICULAR
PURPOSE ARE DISCLAIMED\.  IN NO EVENT SHALL
<field4> BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL
DAMAGES \(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE
GOODS OR SERVICES; LOSS OF (MIND, )?USE, DATA,( LIFE)? OR
PROFITS; OR
BUSINESS INTERRUPTION\) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT \(INCLUDING
NEGLIGENCE
OR OTHERWISE\) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE\.
----------------------------------------------------------------------


--
--
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


Tom Incorvia
 

Hi Dan,

 

Regarding the equivalent terms.  I have seen different commercial legal interpretations based on two of the sets of "equivalent" terms below.  I believe that these need to be distinct.  With regards to library/program/software, I am OK if we remove “library”

 

-          distributable|licensed|released|made available

-          library|program|software

 

Tom

 

Tom Incorvia

tom.incorvia@...

Direct:  (512) 340-1336

Mobile: (408) 499 6850

 

-----Original Message-----
From: spdx-bounces@... [mailto:spdx-bounces@...] On Behalf Of D M German
Sent: Thursday, September 16, 2010 1:14 PM
To: spdx@...
Subject: on license variability

 

 

First, some common equivalent words/phrases:

 

----------------------------------------------------------------------

license|licence

distributable|licensed|released|made available

can|may

terms and conditions|terms

library|program|software

developed|written

MERCHANTIBILITY|MERCHANTABILITY

is|are

do not|don<quotes>t

the copyright|that copyright

would|will

IN THE SOFTWARE

WITH THE SOFTWARE

deal in|deal with

----------------------------------------------------------------------

The quotes are also very different in different files:

 

quotes can be ``, '', ", '

 

----------------------------------------------------------------------

Finally, this is a subset of the way Ninka recognizes the BSD3

clauses. I believe this will cover most versions. The numbers preceding

the conditions are sometimes not there (Ninka drops them, or any bullets

before it continues with the processing).

 

 

Copyright (c) <field1>

All rights reserved\.

 

Redistribution and use in source and binary forms, with or without

modification, are permitted provided that the following conditions are

met:

 

1\. Redistributions? of source code must retain the (above )?copyright

notice, this list of conditions(,)? and the following disclaimer(,

without modification)?.

 

2\. Redistributions in binary form must reproduce the above copyright

notice(\(s\))?, this list of conditions(,)? and the following

disclaimer(s)? in the documentation and/or other materials provided

with the distribution\.

 

3\. Neither the name(s)? of <field2> may be used to endorse or promote

products derived from this software without (specific )?prior written

permission:

 

THIS SOFTWARE IS PROVIDED BY <field3><quotes>AS IS<quotes> AND ANY

EXPRESS(ED)? OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

IMPLIED WARRANTIES OF MERCHANT(A|I)BILITY AND FITNESS FOR A PARTICULAR

PURPOSE ARE DISCLAIMED\.  IN NO EVENT SHALL <field4> BE LIABLE FOR ANY

DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

DAMAGES \(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE

GOODS OR SERVICES; LOSS OF (MIND, )?USE, DATA,( LIFE)? OR PROFITS; OR

BUSINESS INTERRUPTION\) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,

WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT \(INCLUDING NEGLIGENCE

OR OTHERWISE\) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,

EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE\.

----------------------------------------------------------------------

 

 

--

--

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

 

 

This message has been scanned for viruses by MailController - www.MailController.altohiway.com


Gary O'Neall
 

I agree with Tom’s comment – some of these are defined terms within the license itself (e.g. in GPL 3.0, “The Program” has a specific definition), so we should be careful about making these terms equivalent.  Whether these words are equivalent may well depend on the specific license.

 

Gary

 

From: spdx-bounces@... [mailto:spdx-bounces@...] On Behalf Of Tom Incorvia
Sent: Friday, September 17, 2010 4:30 AM
To: dmg@...; spdx@...
Subject: RE: on license variability

 

Hi Dan,

 

Regarding the equivalent terms.  I have seen different commercial legal interpretations based on two of the sets of "equivalent" terms below.  I believe that these need to be distinct.  With regards to library/program/software, I am OK if we remove “library”

 

-          distributable|licensed|released|made available

-          library|program|software

 

Tom

 

Tom Incorvia

tom.incorvia@...

Direct:  (512) 340-1336

Mobile: (408) 499 6850

 

-----Original Message-----
From: spdx-bounces@... [mailto:spdx-bounces@...] On Behalf Of D M German
Sent: Thursday, September 16, 2010 1:14 PM
To: spdx@...
Subject: on license variability

 

 

First, some common equivalent words/phrases:

 

----------------------------------------------------------------------

license|licence

distributable|licensed|released|made available

can|may

terms and conditions|terms

library|program|software

developed|written

MERCHANTIBILITY|MERCHANTABILITY

is|are

do not|don<quotes>t

the copyright|that copyright

would|will

IN THE SOFTWARE

WITH THE SOFTWARE

deal in|deal with

----------------------------------------------------------------------

The quotes are also very different in different files:

 

quotes can be ``, '', ", '

 

----------------------------------------------------------------------

Finally, this is a subset of the way Ninka recognizes the BSD3

clauses. I believe this will cover most versions. The numbers preceding

the conditions are sometimes not there (Ninka drops them, or any bullets

before it continues with the processing).

 

 

Copyright (c) <field1>

All rights reserved\.

 

Redistribution and use in source and binary forms, with or without

modification, are permitted provided that the following conditions are

met:

 

1\. Redistributions? of source code must retain the (above )?copyright

notice, this list of conditions(,)? and the following disclaimer(,

without modification)?.

 

2\. Redistributions in binary form must reproduce the above copyright

notice(\(s\))?, this list of conditions(,)? and the following

disclaimer(s)? in the documentation and/or other materials provided

with the distribution\.

 

3\. Neither the name(s)? of <field2> may be used to endorse or promote

products derived from this software without (specific )?prior written

permission:

 

THIS SOFTWARE IS PROVIDED BY <field3><quotes>AS IS<quotes> AND ANY

EXPRESS(ED)? OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

IMPLIED WARRANTIES OF MERCHANT(A|I)BILITY AND FITNESS FOR A PARTICULAR

PURPOSE ARE DISCLAIMED\.  IN NO EVENT SHALL <field4> BE LIABLE FOR ANY

DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

DAMAGES \(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE

GOODS OR SERVICES; LOSS OF (MIND, )?USE, DATA,( LIFE)? OR PROFITS; OR

BUSINESS INTERRUPTION\) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,

WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT \(INCLUDING NEGLIGENCE

OR OTHERWISE\) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,

EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE\.

----------------------------------------------------------------------

 

 

--

--

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

 

 

This message has been scanned for viruses by MailController - www.MailController.altohiway.com


Mark Radcliffe
 

I agree, distribute and make available have very different legal implications. I also believe that licensed and released are not equivalent to distribute


From: spdx-bounces@... [mailto:spdx-bounces@...] On Behalf Of Tom Incorvia
Sent: Friday, September 17, 2010 4:30 AM
To: dmg@...; spdx@...
Subject: RE: on license variability

Hi Dan,

 

Regarding the equivalent terms.  I have seen different commercial legal interpretations based on two of the sets of "equivalent" terms below.  I believe that these need to be distinct.  With regards to library/program/software, I am OK if we remove “library”

 

-          distributable|licensed|released|made available

-          library|program|software

 

Tom

 

Tom Incorvia

tom.incorvia@...

Direct:  (512) 340-1336

Mobile: (408) 499 6850

 

-----Original Message-----
From: spdx-bounces@... [mailto:spdx-bounces@...] On Behalf Of D M German
Sent: Thursday, September 16, 2010 1:14 PM
To: spdx@...
Subject: on license variability

 

 

First, some common equivalent words/phrases:

 

----------------------------------------------------------------------

license|licence

distributable|licensed|released|made available

can|may

terms and conditions|terms

library|program|software

developed|written

MERCHANTIBILITY|MERCHANTABILITY

is|are

do not|don<quotes>t

the copyright|that copyright

would|will

IN THE SOFTWARE

WITH THE SOFTWARE

deal in|deal with

----------------------------------------------------------------------

The quotes are also very different in different files:

 

quotes can be ``, '', ", '

 

----------------------------------------------------------------------

Finally, this is a subset of the way Ninka recognizes the BSD3

clauses. I believe this will cover most versions. The numbers preceding

the conditions are sometimes not there (Ninka drops them, or any bullets

before it continues with the processing).

 

 

Copyright (c) <field1>

All rights reserved\.

 

Redistribution and use in source and binary forms, with or without

modification, are permitted provided that the following conditions are

met:

 

1\. Redistributions? of source code must retain the (above )?copyright

notice, this list of conditions(,)? and the following disclaimer(,

without modification)?.

 

2\. Redistributions in binary form must reproduce the above copyright

notice(\(s\))?, this list of conditions(,)? and the following

disclaimer(s)? in the documentation and/or other materials provided

with the distribution\.

 

3\. Neither the name(s)? of <field2> may be used to endorse or promote

products derived from this software without (specific )?prior written

permission:

 

THIS SOFTWARE IS PROVIDED BY <field3><quotes>AS IS<quotes> AND ANY

EXPRESS(ED)? OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

IMPLIED WARRANTIES OF MERCHANT(A|I)BILITY AND FITNESS FOR A PARTICULAR

PURPOSE ARE DISCLAIMED\.  IN NO EVENT SHALL <field4> BE LIABLE FOR ANY

DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

DAMAGES \(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE

GOODS OR SERVICES; LOSS OF (MIND, )?USE, DATA,( LIFE)? OR PROFITS; OR

BUSINESS INTERRUPTION\) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,

WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT \(INCLUDING NEGLIGENCE

OR OTHERWISE\) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,

EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE\.

----------------------------------------------------------------------

 

 

--

--

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

 

 

This message has been scanned for viruses by MailController - www.MailController.altohiway.com

Please consider the environment before printing this email.


The information contained in this email may be confidential and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please reply to the sender and destroy all copies of the message. To contact us directly, send to postmaster@.... Thank you.


dmg
 

On Fri, Sep 17, 2010 at 10:00 AM, Gary O'Neall <gary@...> wrote:
I agree with Tom’s comment – some of these are defined terms within the
license itself (e.g. in GPL 3.0, “The Program” has a specific definition),
so we should be careful about making these terms equivalent.  Whether these
words are equivalent may well depend on the specific license.

The main problem is that these terms are not really context free. If you see:

"This (program|library|software) is (release|made available) under the
GPL version 2", you will all probably agree that
they are equivalent.

But in general, they are not.

So I agree, they are context dependent.

--
--dmg

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