Community Data License Agreement Sharing 1.0

Also known as CDLA Sharing 1.0, CDLA-Sharing-1.0, Community Data License Agreement - Sharing - Version 1.0.

Commercial use: allowed
Share alike: 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-Sharing-1.0

Permissions

Charge distribution fee from the text
Commercial use from the text
Derivative works from the text
Derive from the text
Duties
- Attribution from the text
- Modification notice from the text
- Notice from the text
- Share alike from the text
Display from the text
Distribute from the text
Duties
- Attribution from the text
- Notice from the text
- Share alike from the text
Extract or reuse a substantial part of a database from the text
Modified works from the text
Modify from the text
Duties
- Attribution from the text
- Modification notice from the text
- Notice from the text
Moral rights non-assertion from the text
Present from the text
Reproduce from the text
Sublicense from the text

Prohibitions

Change license from the text
Publication non-obstruction from the text

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)

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)

Further terms

These are the things the license says about itself beyond the acts it permits, forbids and requires: when it ends, how long there is to put a breach right, which law governs it, and so on. A term that comes from the DALICC vocabulary links to its definition.

Patent license ends if you sue: Yes. Not a ban on suing: a patent claim over the work ends the patent license, or the whole license, as the text provides.
Sublicense survival: Yes
Terminates on breach: Yes

Clauses

Warranty disclaimer

6.1 EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE DATA (INCLUDING ENHANCED DATA) IS PROVIDED ON AN “AS IS” BASIS, WITHOUT 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

6.2 NEITHER YOU NOR ANY DATA PROVIDERS 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 USE OR DISTRIBUTION OF THE DATA OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Additional clauses

2.1 Subject to the conditions set forth in Section 3 of this Agreement, Data Provider(s) hereby grant(s) to You a worldwide, non-exclusive, irrevocable (except as provided in Section 5) right to: (a) Use Data; and (b) Publish Data. 2.2 To the extent that the Data or the coordination, selection or arrangement of Data is protected or protectable under copyright, Sui Generis Database Rights, or other law, Data Provider(s) further agree(s) that such Data or coordination, selection or arrangement is hereby licensed to You and to anyone else who Receives Data under this Agreement for Use and Publication, subject to the conditions set forth in Section 3 of this Agreement. 2.3 Except for these rights and licenses expressly granted, no other intellectual property rights are granted or should be implied. (a) The Data (including the Enhanced Data) must be Published under this Agreement in accordance with this Section 3; and (b) You must cause any Data files containing Enhanced Data to carry prominent notices that You have changed those files; and (c) If You Publish Data You Receive, You must preserve all credit or attribution to the Data Provider(s). Such retained credit or attribution includes any of the following to the extent they exist in Data as You have Received it: legal notices or metadata; identification of the Data Provider(s); or hyperlinks to Data to the extent it is practical to do so. 3.2 You may not restrict or deter the ability of anyone who Receives the Data (a) to Publish the Data in a publicly-accessible manner or (b) if the project has designated a Ledger for recording Data or grants of rights in Data for purposes of this Agreement, to record the Data or grants of rights in Data in the Ledger. 3.3 If You Publish Data You Receive, You must do so under an unmodified form of this Agreement and include the text of this Agreement, the name of this Agreement and/or a hyperlink or other method reasonably likely to provide a copy of the text of this Agreement. You may not modify this Agreement or impose any further restrictions on the exercise of the rights granted under this Agreement, including by adding any restriction on commercial or non-commercial Use of Data (including Your Enhanced Data) or by limiting permitted Use of such Data to any particular platform, technology or field of endeavor. Notices that purport to modify this Agreement shall be of no effect. 3.4 You and each Data Provider agree that Enhanced Data shall not be considered a work of joint authorship by virtue of its relationship to Data licensed under this Agreement and shall not require either any obligation of accounting to or the consent of any Data Provider. 3.5 This Agreement imposes no obligations or restrictions on Your Use or Publication of Results. 4.1 Each Data Provider represents that the Data Provider has exercised reasonable care, to assure that: (a) the Data it Publishes was created or generated by it or was obtained from others with the right to Publish the Data under this Agreement; and (b) Publication of such Data does not violate any privacy or confidentiality obligation undertaken by the Data Provider. 5.1 All of Your rights under this Agreement will terminate, and Your right to Receive, Use or Publish the Data will be revoked or modified if You materially fail to comply with the terms and conditions of this Agreement and You do not cure such failure in a reasonable period of time after becoming aware of such noncompliance. If Your rights under this Agreement terminate, You agree to cease Receipt, Use and Publication of Data. However, Your obligations and any rights and permissions granted by You under this Agreement relating to Data that You Published prior to such termination will continue and survive. 5.2 If You institute litigation against a Data Provider or anyone else who Receives the Data (including a cross-claim in a lawsuit) based on the Data, other than a claim asserting breach of this Agreement, then any rights previously granted to You to Receive, Use and Publish Data under this Agreement will terminate as of the date such litigation is filed. 7.1 You agree that it is solely Your responsibility to comply with all applicable laws with regard to Your Use or Publication of Data, including any applicable privacy, data protection, security and export laws. You agree to take reasonable steps to assist a Data Provider fulfilling responsibilities to comply with applicable laws with regard to Use or Publication of Data Received hereunder. 7.2 You and Data Provider(s), collectively and individually, waive and/or agree not to assert, to the extent permitted by law, any moral rights You or they hold in Data. 7.5 The Community Data License Agreement workgroup under The Linux Foundation is the steward of this Agreement (“Steward”). No one other than the Steward has the right to modify or publish new versions of this Agreement. Each version will be given a distinguishing version number. You may Use and Publish Data Received hereunder under the terms of the version of the Agreement under which You originally Received the Data, or under the terms of any subsequent version published by the Steward. 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 succeeded, as well as other equivalent rights anywhere in the world.

Info

Target asset types: Creative work (i.e. text, picture, sound, movie), Dataset
Region / jurisdiction: Worldwide
Validity: Perpetual
Source: https://spdx.org/licenses/CDLA-Sharing-1.0.html
Legal code: https://cdla.io/sharing-1-0
This description is published under: Creative Commons Attribution 4.0 International
Publisher: The Linux Foundation
Attribution name: The Linux Foundation
SPDX identifier: CDLA-Sharing-1.0 on the SPDX license list
DALICC identifier: CDLA-Sharing-1.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-Sharing-1.0",
  "license-title": "Community Data License Agreement Sharing 1.0",
  "spdx-id": "CDLA-Sharing-1.0",
  "attribution": "Copyright (c) [year] [copyright holder]",
  "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-Sharing-1.0> .

RDF, JSON-LD

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

HTML attribution

<p>This work is licensed under <a href="https://dalicc.net/licenselibrary/CDLA-Sharing-1.0" rel="license">Community Data License Agreement Sharing 1.0</a>.</p>

This license asks for attribution, so the credit line is part of it.

Badge

Markdown

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

HTML

<a href="https://dalicc.net/license-library/CDLA-Sharing-1.0"><img src="https://dalicc.net/license-library/CDLA-Sharing-1.0/badge.svg" alt="License: Community Data License Agreement Sharing 1.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: 12 recorded, 7 applied to the record, 0 proposed

The reciprocal Community Data License Agreement: the data and any enhanced data must be published under this same agreement, unmodified, with the credit preserved and the changed files marked. The record carries cc:ShareAlike on odrl:distribute and odrl:derive rather than licence-wide, because the reciprocity is triggered by publication and not by use, and it prohibits dalicc:ChangeLicense, which its permissive sibling permits.

12 findings

minor Rubric 1 spdx:licenseId applied

The record carries the SPDX id CDLA-Sharing-1.0 and the SPDX name as dct:title, with the long dashes of the licence's own name replaced by plain hyphens in dct:alternative.
major Rubric 2 odrl:target applied

dcmitype:Dataset and dalicc:CreativeWork, for the same reason as on the CDLA-Permissive-1.0 record: Data is "the information (including copyrightable information, such as images or text)".
major Rubric 3 odrl:permission applied

The grant of section 2.1 is word for word that of the permissive agreement, "a worldwide, non-exclusive, irrevocable (except as provided in Section 5) right to: (a) Use Data; and (b) Publish Data", and section 2.2 licenses the Sui Generis Database Rights. The record permits the same acts as the CDLA-Permissive-1.0 record, with dalicc:suiGenerisDatabaseRights, dalicc:moralRightsNonAssertion and dalicc:sublicense, the last because section 3.1(a) requires the data to be published under this same agreement, which is passing the licence on unchanged.
major Rubric 4 odrl:prohibition applied

Two prohibitions. dalicc:ChangeLicense comes from section 3.3: "If You Publish Data You Receive, You must do so under an unmodified form of this Agreement ... You may not modify this Agreement or impose any further restrictions on the exercise of the rights granted under this Agreement". dalicc:patentRetaliationTermination comes from section 5.2, as on the permissive record, and is again wider than its name: any litigation based on the Data ends the rights.
major Rubric 5 odrl:duty applied

cc:ShareAlike hangs off odrl:distribute and odrl:derive, not off the odrl:Set, because the reciprocity attaches to publication: "The Data (including the Enhanced Data) must be Published under this Agreement in accordance with this Section 3". Using or modifying the data privately triggers nothing, which is why odrl:modify carries cc:Attribution, cc:Notice and dalicc:modificationNotice but no cc:ShareAlike. The attribution and notice duties are those of the permissive agreement.
minor Rubric 6 dalicc:WarrantyDisclaimer applied

Sections 6.1 and 6.2 go into dalicc:WarrantyDisclaimer and dalicc:LiabilityLimitation. dalicc:additionalClauses carries the grant, the five conditions of section 3, including the no-deterrence clause and the ledger sentence, the representations, both termination clauses, the compliance and moral rights paragraphs and the definition of Sui Generis Database Rights.
minor Rubric 7 cc:jurisdiction applied

cc:jurisdiction stays dalicc:worldwide, from section 2.1, and dalicc:validityType dalicc:perpetual. The agreement names no governing law.
gap Rubric 8 dalicc:additionalClauses none

Section 3.2 forbids restricting or deterring a recipient from publishing the data publicly or from recording it in a designated Ledger. Neither the no-deterrence duty nor the ledger has a term; both are quoted. Proposed term dalicc:publicationNonObstruction.
gap Rubric 8 dalicc:additionalClauses none

Section 3.3 also forbids imposing further restrictions, including a restriction on commercial or non-commercial use or a limitation to a platform, technology or field of endeavour. dalicc:addLimitation exists but is used by no record as a prohibition, which review group 1 already raised as an open question, so it was not written; the clause is quoted.
gap Rubric 8 dalicc:additionalClauses none

Section 5.1 terminates the rights on an uncured material breach and keeps what was published before alive. Quoted; proposed terms dalicc:terminatesOnBreach and dalicc:sublicenseSurvival.
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: CDLA-Sharing-1.0 is CDLA-Permissive-1.0 with section 3.1(a) turned round. Everything else, the definitions, the grant, the warranty and liability sections and the litigation termination, is shared, and the two records differ in exactly three statements: the share-alike duties, the dalicc:ChangeLicense prohibition and the absence of a dalicc:ChangeLicense permission.

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.

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 version 2 JSON-LD Turtle RDF/XML
2 changes
- changed permission dalicc:suiGenerisDatabaseRights
  
  was permission dalicc:suiGenerisDatabaseRights
  
  Manual edit The statement now quotes the sentence of the licence text it rests on: "2.2 To the extent that the Data or the coordination, selection or arrangement of Data is protected or protectable under copyright, Sui Generis Database Rights, or other law, Data Provider(s) further agree(s) that such Data or coordination, selection or arrangement is hereby licensed to You and to anyone else who Receives Data under this Agreement for Use and Publication, subject to the conditions set forth in Section 3 of this Agreement."
- 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.
Version 1

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

View version 1 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.