DEVELOPMENT VERSION: This is an experimental DALICC environment. Features, data and APIs may change or be reset without notice. A stable version of this service, with a potentially different feature set, will be made available soon at dalicc.net.

2026

Community Data License Agreement Permissive 2.0

Also known as CDLA Permissive 2.0, CDLA-Permissive-2.0, Community Data License Agreement - Permissive - Version 2.0.

Commercial use
allowed
Share alike
not required
Attribution
required (keep the copyright and license notices)
Compare with… Add to the compatibility check Download JSON-LD Turtle RDF/XML Text

Write this as a license text (needs an account) DALICC reads the model above and writes what it permits, requires and prohibits in plain English. Without an account, the Text download above writes the model out from the vocabulary.

Canonical URI https://dalicc.net/licenselibrary/CDLA-Permissive-2.0

Permissions

  • Change license by library convention Library convention: family rule 15: Permissive records permit relicensing. Replacing the license of the work, or of an adaptation, with another license, or changing its terms.

    Duties

    • Use a compliant license by library convention Library convention: family rule 15: Permissive records permit relicensing. Choosing a replacement license that stays compliant with the terms of the original license.
  • Charge distribution fee from the text Charging a fee for the act of providing a copy of the work to someone else.
  • Commercial use from the text Using the work to generate income, directly or indirectly, for example by selling it or by using it in advertising.
  • Derivative works from the text Distributing an adaptation of the work and making it available to the public.
  • Derive from the text Creating a new work from the work, such as a translation, adaptation or arrangement of it or of a part of it.

    Duties

    • Notice from the text Notice: keeping the license and copyright notices with every copy.
  • Display from the text Showing the work to the public without making a copy the viewer keeps.
  • Distribute from the text Providing copies of the work to the public or to anyone else.

    Duties

    • Notice from the text Notice: keeping the license and copyright notices with every copy.
  • Modified works from the text Distributing a modified version of the work that does not amount to a new, derivative work.
  • Modify from the text Altering the work, for example by updating it, without creating a new work; an alteration that creates a new work is Derive.

    Duties

    • Notice from the text Notice: keeping the license and copyright notices with every copy.
  • Present from the text Performing the work in public, including by broadcast or other communication to the public.
  • Reproduce from the text Making copies of the work in any form.
  • Sublicense from the text Granting a third party rights in the work under a license of the licensee's own, rather than passing on the original license.
  • Use for model training from the text Using the licensed material to train, validate or tune an automated system that learns from data.

Prohibitions

This license states no prohibitions.

License-wide duties

This license states no duties that apply to the work as a whole.

What applies by default

The statements above are the library's reading of this license: each is marked with the sentence it rests on, or as a library convention where the text is not explicit. The statements below are the ones the DALICC reasoner supplies for acts the license says nothing about, from the default rules of the dependency graph it reasons with. Each one names the legal source it rests on. None of it is in the record.

  • Promote by default rule (adopted) Using the name or trademarks of the licensor or of contributors to endorse or promote a product.

    This license says nothing about Promote, and the graph applies this reading in all jurisdictions it covers: it is not permitted unless the license permits it.

    A licence that says nothing about endorsement is read as not allowing it: the licence gives the licensee no right to use the licensor's name or marks in a way that states or implies that the licensor endorses the licensee or its product, while stating truthfully that a work is based on or uses the licensed work is a different act that this rule does not decide. A copyright licence grants rights in the work, and the right to use a name or a trademark is a separate right under trademark law and the protection of names, which a silent copyright licence does not pass on. Combining a licence that is silent about endorsement with one that permits it shows a conflict marked as coming from this rule.

    Basis Trademark and name rights are separate from copyright: Regulation (EU) 2017/1001 article 9 lets the proprietor of an EU trade mark prevent all third parties not having his consent from using the sign in the course of trade, and Directive (EU) 2015/2436 article 10, 15 U.S.C. 1114 and 1125(a), section 12 BGB and section 43 ABGB protect marks and names in the same way. The library's evidence is Creative Commons 4.0 section 2(b)(2): Patent and trademark rights are not licensed under this Public License. A copyright licence that is silent grants no right to use the licensor's name or marks to suggest endorsement (Worldwide)

Clauses

Warranty disclaimer

THE DATA IS PROVIDED ON AN "AS IS" BASIS, WITHOUT REPRESENTATIONS, WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Limitation of liability

NO DATA PROVIDER SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), 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 DATA OR RESULTS, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Additional clauses

1.1. A Data Recipient may use, modify, and share the Data made available by Data Provider(s) under this agreement if that Data Recipient follows the terms of this agreement. 1.2. This agreement does not impose any restriction on a Data Recipient's use, modification, or sharing of any portions of the Data that are in the public domain or that may be used, modified, or shared under any other legal exception or limitation. 2.1. A Data Recipient may share Data, with or without modifications, so long as the Data Recipient makes available the text of this agreement with the shared Data. 3.1. This agreement does not impose any restriction or obligations with respect to the use, modification, or sharing of Results. 5.1. "Data" means the material received by a Data Recipient under this agreement. 5.4. "Results" means any outcome obtained by computational analysis of Data, including for example machine learning models and models' insights.

Info

Target asset types
Creative work (i.e. text, picture, sound, movie), Dataset
Region / jurisdiction
Worldwide
Validity
Perpetual
Source
https://spdx.org/licenses/CDLA-Permissive-2.0.html
Legal code
https://cdla.dev/permissive-2-0
This description is published under
Creative Commons Attribution 4.0 International
SPDX identifier
CDLA-Permissive-2.0 on the SPDX license list
DALICC identifier
CDLA-Permissive-2.0

This record is published under CC BY 4.0. Credit it as: DALICC License Library, DALICC - Verein zur Förderung der Rechtssicherheit in der Datenbewirtschaftung, https://dalicc.net, CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). The license it describes belongs to its publisher.

Use this license

Everything below is generated from this record. Replace the example address with the address of your own work.

JSON sidecar 

{
  "license-uri": "https://dalicc.net/licenselibrary/CDLA-Permissive-2.0",
  "license-title": "Community Data License Agreement Permissive 2.0",
  "spdx-id": "CDLA-Permissive-2.0",
  "asset": null,
  "generated-by": "DALICC"
}

RDF, Turtle 

@prefix cc: <http://creativecommons.org/ns#> .

<https://example.org/my-work>
    cc:license <https://dalicc.net/licenselibrary/CDLA-Permissive-2.0> .

RDF, JSON-LD 

{
  "@context": {
    "cc": "http://creativecommons.org/ns#"
  },
  "@id": "https://example.org/my-work",
  "cc:license": {
    "@id": "https://dalicc.net/licenselibrary/CDLA-Permissive-2.0"
  }
}

This license carries no attribution duty, so no credit line is offered here.

Badge DALICC badge for Community Data License Agreement Permissive 2.0

Markdown 

[![License: Community Data License Agreement Permissive 2.0](https://dalicc.net/license-library/CDLA-Permissive-2.0/badge.svg)](https://dalicc.net/license-library/CDLA-Permissive-2.0)

HTML 

<a href="https://dalicc.net/license-library/CDLA-Permissive-2.0"><img src="https://dalicc.net/license-library/CDLA-Permissive-2.0/badge.svg" alt="License: Community Data License Agreement Permissive 2.0"></a>

Review

Written from the license text by
Giray Havur
Written on
2026-09-15
Second review
not yet done
Record changed since this review
yes (version 2, 2026-09-24)
Findings
11 recorded, 9 applied to the record, 0 proposed

The permissive Community Data License Agreement, version 2.0: one page, one condition, the text of the agreement travels with the data. The record follows the CDLA-Permissive-1.0 record of this review group and differs from it where the text does: no attribution duty, no changed file notice, no database right, no termination, and no option to publish under a licence of your choice.

11 findings

  • minor Rubric 1 spdx:licenseId applied

    The record carries the SPDX id CDLA-Permissive-2.0 and the SPDX name as dct:title. dalicc:variantKind is "version": this is the later version of the text the CDLA-Permissive-1.0 record of this review group holds.

  • major Rubric 2 odrl:target applied

    dcmitype:Dataset and dalicc:CreativeWork, as on the 1.0 record, although version 2.0 shortens the definition to "the material received by a Data Recipient under this agreement" and no longer names images or text.

  • major Rubric 3 odrl:permission applied

    "A Data Recipient may use, modify, and share the Data made available by Data Provider(s) under this agreement if that Data Recipient follows the terms of this agreement." The record permits reproduce, distribute, display, present, modify, derive, commercial use, derivative works, modified works, the distribution fee and dalicc:sublicense, the last because sharing the data with the agreement attached is passing the same licence on. dalicc:useForModelTraining is permitted because the agreement says so expressly: Results are defined as "any outcome obtained by computational analysis of Data, including for example machine learning models and models' insights" and section 3.1 imposes no restriction or obligation on them. dalicc:suiGenerisDatabaseRights is not written: unlike version 1.0, this text names no database right.

  • major Rubric 4 odrl:prohibition applied

    One prohibition, dalicc:ChangeLicense, because the single condition of section 2.1 is that "the Data Recipient makes available the text of this agreement with the shared Data": the agreement travels with the data, which is the shape the library reads as a bar on relicensing. This is a real difference from version 1.0, whose section 3.1(a) expressly allows a licence of your choice, and it is the only modelled difference between the two records apart from the duties.

  • major Rubric 5 odrl:duty applied

    One duty, cc:Notice, on odrl:distribute, odrl:modify and odrl:derive. Version 2.0 drops the attribution condition of version 1.0 (3.1(c)) and the changed file notice (3.1(b)) entirely, so no cc:Attribution and no dalicc:modificationNotice is written. A reader comparing the two records sees exactly that.

  • minor Rubric 6 dalicc:WarrantyDisclaimer applied

    The first paragraph of section 4.1 goes into dalicc:WarrantyDisclaimer and the second into dalicc:LiabilityLimitation. dalicc:additionalClauses carries sections 1, 2, 3 and the definitions of Data and Results, which is most of the agreement: it is two pages long.

  • minor Rubric 7 cc:jurisdiction applied

    cc:jurisdiction stays dalicc:worldwide and dalicc:validityType dalicc:perpetual. Version 2.0 names no governing law, no territory, no term and, unlike version 1.0, no termination at all.

  • info Rubric 8 dalicc:useForModelTraining applied

    This is the first record in the library to carry dalicc:useForModelTraining. The term was defined by the review of 2026-09-15 and applied to no record; it is applied here, and on the two data use agreements of this review group, because those three texts are the only ones that say in their own words what happens to a model trained on the data.

  • info Rubric 9 record none

    The consistency check of app.services.composer with the axioms of dg_default returned an empty conflict list.

  • info Rubric 10 record none

    Family: version 2.0 is a rewrite, not an amendment. Against the CDLA-Permissive-1.0 record it drops attribution, the changed file notice, the database right, the moral rights waiver, the litigation termination and the steward clause, and it closes the licence of your choice option. The two records share only their permissive core and their warranty and liability wording.

  • major Rubric 3 odrl:permission applied

    Library convention 15: a licence that asks for no reciprocity and no source code asks only that the notice travels with the copy, which is a duty on the acts it governs and not a bar on putting the copy under other terms. dalicc:ChangeLicense is therefore a permission here, and the prohibition the earlier reading wrote is removed. The text reads: "A Data Recipient may use, modify, and share the Data made available by Data Provider(s) under this agreement if that Data Recipient follows the terms of this agreement." The permission carries the dalicc:compliantLicense duty, as Apache-2.0 does, because the notice has to survive the relicensing.

Report an issue The review record as JSON The review checks the model against the license text. It is not legal advice.

History

This license model has 2 versions. Version 2 is the one served today; every earlier version keeps its own address, so a conclusion drawn from one of them can still be checked against it.

  1. Version 2 current2026-09-24 Giray Havur

    The changes since version 1 recorded which sentence of the text each statement rests on and named the license the record itself is published under.

    View JSON-LD Turtle RDF/XML

    2 changes

    • changed permission dalicc:ChangeLicense with duties [dalicc:compliantLicense]

      was permission dalicc:ChangeLicense with duties [dalicc:compliantLicense]

      Manual edit The statement is marked as a library convention, family rule 15: Permissive records permit relicensing: the text does not state it in as many words. Its duty dalicc:compliantLicense is marked as a library convention, family rule 15: Permissive records permit relicensing.

    • added dct:license <https://creativecommons.org/licenses/by/4.0/>

      Manual edit Every record is published under CC BY 4.0. cc:license names the record DALICC keeps of that licence; dct:license now names it by the address Creative Commons publishes it at, so that a consumer matching the canonical IRI finds it.

  2. Version 1

    Created from the license text on 2026-09-15 (Community Data License Agreement).

    View JSON-LD Turtle RDF/XML

Every change names the reason behind it: a finding of the content review, one of its library-wide decisions, the metadata that review wrote onto every record, or a hand edit. None of it is legal advice.

Nothing on this page is legal advice. What a license means is decided by its text; ask a legal advisor before you rely on it.