no call this week

[J Lovejoy]

Hi All, Given that many of us are in Prague for Open Source Summit, we will follow the lead of the tech team and cancel this week's call.  Let's continue progress on the various tasks for the next release (thanks to Alexios and Gary for getting the next big step done!) and we will continue the discussion on the only/or later issue on the next call, on Nov 9thCheers,Jilayne
___
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
https://lists.spdx.org/mailman/listinfo/spdx-legal

Re: New License/Exception Request: CDLA-Permissive-1.0

[Dennis Clark]

Mike, Legal Team,

Request for CDLA-Permissive-1.0  added to the SPDX Licenses and Exceptions
Under Consideration google sheet:

https://docs.google.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=695212681

Regards,
Dennis Clark
nexB Inc.

On Tue, Oct 24, 2017 at 8:50 AM, Michael Dolan 
wrote:

> Provide a proposed Full Name for the license or exception.
>
> Community Data License Agreement - Permissive - Version 1.0
>
> Provide a proposed Short Identifier. CDLA-Permissive-1.0
>
> Provide a functioning url reference to the license or exception text,
> either from the author or a community recognized source.
>
> https://cdla.io/permissive-1-0
>
> Create and attach a text file with the license or exception text from the
> url provided in #3.
>
> See attached.
>
> Indicate whether the license is OSI-approved (see:
> http://www.opensource.org/licenses/alphabetical) or whether it has been
> submitted for approval to the OSI and is currently under review.
>
> This has not been submitted to OSI.
>
> Provide a short explanation regarding the need for this license or
> exception to be included on the SPDX License List, including identifying at
> least one program that uses this license.
>
> It is a new license for open data. We would like to have an SPDX
> identifier early on in its adoption if possible so that early adopters can
> use it.
>
> Thanks,
>
> Mike Dolan
>
> ___
> Spdx-legal mailing list
> Spdx-legal@lists.spdx.org
> https://lists.spdx.org/mailman/listinfo/spdx-legal
>
>
___
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
https://lists.spdx.org/mailman/listinfo/spdx-legal

New License/Exception Request: CDLA-Sharing-1.0

[Michael Dolan]

Provide a proposed Full Name for the license or exception.

Community Data License Agreement - Sharing - Version 1.0

Provide a proposed Short Identifier. CDLA-Sharing-1.0

Provide a functioning url reference to the license or exception text,
either from the author or a community recognized source.

https://cdla.io/sharing-1-0

Create and attach a text file with the license or exception text from the
url provided in #3.

See attached.

Indicate whether the license is OSI-approved (see:
http://www.opensource.org/licenses/alphabetical) or whether it has been
submitted for approval to the OSI and is currently under review.

Has not been submitted.

Provide a short explanation regarding the need for this license or
exception to be included on the SPDX License List, including identifying at
least one program that uses this license.

It is a new license for open data. We would like to have an SPDX identifier
early on in its adoption if possible so that early adopters can use it.

Thanks,

Mike Dolan
Community Data License Agreement – Sharing – Version 1.0

This is the Community Data License Agreement – Sharing, Version 1.0 
(“Agreement”).  Data is provided to You under this Agreement by each of the 
Data Providers.  Your exercise of any of the rights and permissions granted 
below constitutes Your acceptance and agreement to be bound by the terms and 
conditions of this Agreement.

The benefits that each Data Provider receives from making Data available and 
that You receive from Data or otherwise under these terms and conditions shall 
be deemed sufficient consideration for the formation of this Agreement.  
Accordingly, Data Provider(s) and You (the “Parties”) agree as follows:

Section 1.  Definitions

1.1 “Add” means to supplement Data with Your own or someone else’s Data, 
resulting in Your “Additions.”  Additions do not include Results.

1.2 “Computational Use” means Your analysis (through the use of computational 
devices or otherwise) or other interpretation of Data.  By way of example and 
not limitation, “Computational Use” includes the application of any 
computational analytical technique, the purpose of which is the analysis of any 
Data in digital form to generate information about Data such as patterns, 
trends, correlations, inferences, insights and attributes.

1.3 “Data” means the information (including copyrightable information, such as 
images or text), collectively or individually, whether created or gathered by a 
Data Provider or an Entity acting on its behalf, to which rights are granted 
under this Agreement.

1.4 “Data Provider” means any Entity (including any employee or contractor of 
such Entity authorized to Publish Data on behalf of such Entity) that Publishes 
Data under this Agreement prior to Your Receiving it.

1.5 “Enhanced Data” means the subset of Data that You Publish and that is 
composed of (a) Your Additions and/or (b) Modifications to Data You have 
received under this Agreement.

1.6 “Entity” means any natural person or organization that exists under the 
laws of the jurisdiction in which it is organized, together with all other 
entities that control, are controlled by, or are under common control with that 
entity.  For the purposes of this definition, “control” means (a) the power, 
directly or indirectly, to cause the direction or management of such entity, 
whether by contract or otherwise, (b) the ownership of more than fifty percent 
(50%) of the outstanding shares or securities, (c) the beneficial ownership of 
such entity or, (d) the ability to appoint, whether by agreement or right, the 
majority of directors of an Entity.

1.7 “Ledger” means a digital record of Data or grants of rights in Data 
governed by this Agreement, using any technology having functionality to record 
and store Data or grants, contributions, or licenses to Data governed by this 
Agreement.

1.8 “Modify” means to delete, erase, correct or re-arrange Data, resulting in 
“Modifications.”  Modifications do not include Results.

1.9 “Publish” means to make all or a subset of Data (including Your Enhanced 
Data) available in any manner which enables its Use, including by providing a 
copy on physical media or remote access.  For any form of Entity, that is to 
make the Data available to any individual who is not employed by that Entity or 
engaged as a contractor or agent to perform work on that Entity’s behalf.  A 
“Publication” occurs each time You Publish Data.

1.10 “Receive” or “Receives” means to have been given access to Data, locally 
or remotely.

1.11 “Results” means the outcomes or outputs that You obtain from Your 
Computational Use of Data.  Results shall not include more than a de minimis 
portion of the Data on which the Computational Use is based.

1.12 “Sui Generis Database Rights” means rights, other than copyright, 
resulting from Directive 96/9/EC of the European Parliament and of the Council 
of 11 March 1996 on the legal protection of databases, as amended and/or 

New License/Exception Request: CDLA-Permissive-1.0

[Michael Dolan]

Provide a proposed Full Name for the license or exception.

Community Data License Agreement - Permissive - Version 1.0

Provide a proposed Short Identifier. CDLA-Permissive-1.0

Provide a functioning url reference to the license or exception text,
either from the author or a community recognized source.

https://cdla.io/permissive-1-0

Create and attach a text file with the license or exception text from the
url provided in #3.

See attached.

Indicate whether the license is OSI-approved (see:
http://www.opensource.org/licenses/alphabetical) or whether it has been
submitted for approval to the OSI and is currently under review.

This has not been submitted to OSI.

Provide a short explanation regarding the need for this license or
exception to be included on the SPDX License List, including identifying at
least one program that uses this license.

It is a new license for open data. We would like to have an SPDX identifier
early on in its adoption if possible so that early adopters can use it.

Thanks,

Mike Dolan
Community Data License Agreement – Permissive – Version 1.0

This is the Community Data License Agreement – Permissive, Version 1.0 
(“Agreement”).  Data is provided to You under this Agreement by each of the 
Data Providers.  Your exercise of any of the rights and permissions granted 
below constitutes Your acceptance and agreement to be bound by the terms and 
conditions of this Agreement.

The benefits that each Data Provider receives from making Data available and 
that You receive from Data or otherwise under these terms and conditions shall 
be deemed sufficient consideration for the formation of this Agreement.  
Accordingly, Data Provider(s) and You (the “Parties”) agree as follows:

Section 1.  Definitions

1.1 “Add” means to supplement Data with Your own or someone else’s Data, 
resulting in Your “Additions.”  Additions do not include Results.

1.2 “Computational Use” means Your analysis (through the use of computational 
devices or otherwise) or other interpretation of Data.  By way of example and 
not limitation, “Computational Use” includes the application of any 
computational analytical technique, the purpose of which is the analysis of any 
Data in digital form to generate information about Data such as patterns, 
trends, correlations, inferences, insights and attributes.

1.3 “Data” means the information (including copyrightable information, such as 
images or text), collectively or individually, whether created or gathered by a 
Data Provider or an Entity acting on its behalf, to which rights are granted 
under this Agreement.

1.4 “Data Provider” means any Entity (including any employee or contractor of 
such Entity authorized to Publish Data on behalf of such Entity) that Publishes 
Data under this Agreement prior to Your Receiving it.
1.5 “Enhanced Data” means the subset of Data that You Publish and that is 
composed of (a) Your Additions and/or (b) Modifications to Data You have 
received under this Agreement.

1.6 “Entity” means any natural person or organization that exists under the 
laws of the jurisdiction in which it is organized, together with all other 
entities that control, are controlled by, or are under common control with that 
entity.  For the purposes of this definition, “control” means (a) the power, 
directly or indirectly, to cause the direction or management of such entity, 
whether by contract or otherwise, (b) the ownership of more than fifty percent 
(50%) of the outstanding shares or securities, (c) the beneficial ownership of 
such entity or, (d) the ability to appoint, whether by agreement or right, the 
majority of directors of an Entity.

1.7 “Modify” means to delete, erase, correct or re-arrange Data, resulting in 
“Modifications.”  Modifications do not include Results.

1.8 “Publish” means to make all or a subset of Data (including Your Enhanced 
Data) available in any manner which enables its Use, including by providing a 
copy on physical media or remote access.  For any form of Entity, that is to 
make the Data available to any individual who is not employed by that Entity or 
engaged as a contractor or agent to perform work on that Entity’s behalf.  A 
“Publication” occurs each time You Publish Data.

1.9 “Receive” or “Receives” means to have been given access to Data, locally or 
remotely.

1.10 “Results” means the outcomes or outputs that You obtain from Your 
Computational Use of Data.  Results shall not include more than a de minimis 
portion of the Data on which the Computational Use is based.

1.11 “Sui Generis Database Rights” means rights, other than copyright, 
resulting from Directive 96/9/EC of the European Parliament and of the Council 
of 11 March 1996 on the legal protection of databases, as amended and/or 
succeeded, as well as other equivalent rights anywhere in the world.

1.12 “Use” means using Data (including accessing, copying, studying, reviewing, 
adapting, analyzing, evaluating, or making Computational Use of it),