Eclipse Public License 1.0
Also known as EPL Version 1.0, EPL v1.0, EPL-1.0, Eclipse Public License Version 1.0.
- Commercial use
- allowed
- Share alike
- required
- Attribution
- required (keep the copyright and license notices)
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.
Permissions
-
Change license from the text Replacing the license of the work, or of an adaptation, with another license, or changing its terms.
-
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
- Attribution from the text Giving credit to the copyright holders or authors of the work, in the form the licensor asks for.
- Modification notice from the text Marking a changed work as changed, saying how it differs from the original and keeping earlier notices of change.
- Notice from the text Notice: keeping the license and copyright notices with every copy.
- Share alike from the text Adaptations have to be licensed under the same license or one the license names as compatible.
- Source code from the text Providing access to the source code of the work with every copy distributed.
-
Duties
- Attribution from the text Giving credit to the copyright holders or authors of the work, in the form the licensor asks for.
- Notice from the text Notice: keeping the license and copyright notices with every copy.
- Share alike from the text Adaptations have to be licensed under the same license or one the license names as compatible.
- Source code from the text Providing access to the source code of the work with every copy distributed.
-
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
- Attribution from the text Giving credit to the copyright holders or authors of the work, in the form the licensor asks for.
- Modification notice from the text Marking a changed work as changed, saying how it differs from the original and keeping earlier notices of change.
- Notice from the text Notice: keeping the license and copyright notices with every copy.
- Share alike from the text Adaptations have to be licensed under the same license or one the license names as compatible.
- Source code from the text Providing access to the source code of the work with every copy distributed.
-
Patent grant from the text Granting a license under the patent claims that a contributor holds and that the contribution necessarily infringes.
-
Present from the text Performing the work in public, including by broadcast or other communication to the public.
-
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.
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)
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.
Clauses
Warranty disclaimer
EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM 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. Each Recipient is solely responsible for determining the appropriateness of using and distributing the Program and assumes all risks associated with its exercise of rights under this Agreement , including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs or equipment, and unavailability or interruption of operations.
Limitation of liability
EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS 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 PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Info
- Target asset types
- Software
- Region / jurisdiction
- Worldwide
- Validity
- Perpetual
- Source
- http://opensource.org/licenses/EPL-1.0
- Legal code
- http://opensource.org/licenses/EPL-1.0
- This description is published under
- Creative Commons Attribution 4.0 International
- Publisher
- Eclipse
- Attribution name
- Eclipse
- SPDX identifier
-
EPL-1.0on the SPDX license list - DALICC identifier
EclipsePublicLicense10
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/EclipsePublicLicense10",
"license-title": "Eclipse Public License 1.0",
"spdx-id": "EPL-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/EclipsePublicLicense10> .
RDF, JSON-LD
{
"@context": {
"cc": "http://creativecommons.org/ns#"
},
"@id": "https://example.org/my-work",
"cc:license": {
"@id": "https://dalicc.net/licenselibrary/EclipsePublicLicense10"
}
}
HTML attribution
<p>This work is licensed under <a href="https://dalicc.net/licenselibrary/EclipsePublicLicense10" rel="license">Eclipse Public License 1.0</a>.</p>
This license asks for attribution, so the credit line is part of it.
Badge
Markdown
[](https://dalicc.net/license-library/EclipsePublicLicense10)
HTML
<a href="https://dalicc.net/license-library/EclipsePublicLicense10"><img src="https://dalicc.net/license-library/EclipsePublicLicense10/badge.svg" alt="License: Eclipse Public License 1.0"></a>
Review
- Status
- Reviewed against the license text
- Last checked
- 2026-09-15
- Reviewer
- Giray Havur
- Verdict
- corrected during the review
- Record changed since this review
- yes (version 2, 2026-09-24)
- Findings
- 7 recorded, 5 applied to the record, 1 proposed
The Eclipse Public License 1.0 requires source form to be made available under the same agreement and lets a contributor distribute object code under its own terms, subject to conditions. The record prohibited cc:ShareAlike, which reverses the first half, and did not model the second half at all. Both were corrected, the SPDX id was added, and the warranty and liability clauses were separated.
7 findings
-
minor Rubric 1
spdx:licenseIdappliedAdded EPL-1.0; the title matches the SPDX name.
-
major Rubric 5
odrl:prohibitionappliedSection 3 states: "When the Program is made available in source code form ... it must be made available under this Agreement". Prohibiting cc:ShareAlike asserts the opposite. Removed.
-
major Rubric 3
odrl:permissionappliedSection 3 also states: "A Contributor may choose to distribute the Program in object code form under its own license agreement, provided that ..." followed by four compliance conditions. That is dalicc:ChangeLicense with a dalicc:compliantLicense duty, exactly as the EPL-2.0 record models section 3.1(b). Added, which also brings the two Eclipse records into line.
-
minor Rubric 6
dalicc:WarrantyDisclaimerapplieddalicc:WarrantyDisclaimer held the text of section 6, DISCLAIMER OF LIABILITY, and there was no dalicc:LiabilityLimitation. Moved section 6 to the liability field and put section 5, NO WARRANTY, in the warranty field.
-
minor Rubric 4
odrl:prohibitionproposeddalicc:promote is prohibited although version 1.0 has no trademark clause; version 2.0 has none either and its record has no such prohibition. dalicc:addStatement is prohibited although section 3 expressly allows a contributor to add its own terms.
-
gap Rubric 8
vocabularynoneSection 2(b) grants a patent license and section 7 terminates it on patent litigation. Section 4 obliges a commercial distributor to indemnify the other contributors, which has no term either. Proposed: dalicc:patentGrant, dalicc:patentRetaliationTermination, dalicc:indemnifyContributors.
-
major Rubric 10
recordappliedStandard-license addition of 2026-09-15, decision 9: the record was corrected against its new siblings and versioned. The review's finding on family consistency and consolidation decision 4: the record modelled no reciprocity although section 3 says 'When the Program is made available in source code form: a) it must be made available under this Agreement', it made no patent statement although section 2(b) grants one and section 7 ends it on patent litigation, and dct:publisher and cc:attributionName both ended with a space.
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 content review of 2026-09-15 added 1 clause text, 1 identification detail and 1 permission, removed 1 prohibition, changed 1 clause text, recorded the relation to the record this one was adapted from and recorded the review state. Later changes brought it in line with its family and its text in the verification of 2026-09-15 and named the license the record itself is published under.
View version 2 JSON-LD Turtle RDF/XML
26 changes
-
added
dalicc:LiabilityLimitation "EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS 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 PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES."Review finding dalicc:WarrantyDisclaimer held the text of section 6, DISCLAIMER OF LIABILITY, and there was no dalicc:LiabilityLimitation. Moved section 6 to the liability field and put section 5, NO WARRANTY, in the warranty field.
-
changed
dalicc:WarrantyDisclaimer "EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM 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. Each Recipient is solely responsible for determining the appropriateness of using and distributing the Program and assumes all risks associated with its exercise of rights under this Agreement , including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs or equipment, and unavailability or interruption of operations."was
dalicc:WarrantyDisclaimer "EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS 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 PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES."Review finding dalicc:WarrantyDisclaimer held the text of section 6, DISCLAIMER OF LIABILITY, and there was no dalicc:LiabilityLimitation. Moved section 6 to the liability field and put section 5, NO WARRANTY, in the warranty field.
-
added
dalicc:reviewStatus dalicc:ReviewedReview state Every record records how far it has come in the editorial workflow and when it was last checked against the legal text.
-
added
dalicc:reviewedOn "2026-09-15"^^xsd:dateReview state Every record records how far it has come in the editorial workflow and when it was last checked against the legal text.
-
added
dalicc:variantKind "version"Port relation The 2026-09-15 review made the relation between a jurisdiction port and the record it was adapted from explicit in the data.
-
added
permission dalicc:ChangeLicense with duties [dalicc:compliantLicense]Review finding Section 3 also states: "A Contributor may choose to distribute the Program in object code form under its own license agreement, provided that ..." followed by four compliance conditions. That is dalicc:ChangeLicense with a dalicc:compliantLicense duty, exactly as the EPL-2.0 record models section 3.1(b). Added, which also brings the two Eclipse records into line.
-
removed
prohibition cc:ShareAlikeReview finding Section 3 states: "When the Program is made available in source code form ... it must be made available under this Agreement". Prohibiting cc:ShareAlike asserts the opposite. Removed.
-
added
spdx:licenseId "EPL-1.0"Review finding Added EPL-1.0; the title matches the SPDX name.
-
changed
cc:attributionName "Eclipse"was
cc:attributionName "Eclipse "Manual edit The review's finding on family consistency and consolidation decision 4: the record modelled no reciprocity although section 3 says 'When the Program is made available in source code form: a) it must be made available under this Agreement', it made no patent statement although section 2(b) grants one and section 7 ends it on patent litigation, and dct:publisher and cc:attributionName both ended with a space.
-
changed
dct:publisher "Eclipse"was
dct:publisher "Eclipse "Manual edit The review's finding on family consistency and consolidation decision 4: the record modelled no reciprocity although section 3 says 'When the Program is made available in source code form: a) it must be made available under this Agreement', it made no patent statement although section 2(b) grants one and section 7 ends it on patent litigation, and dct:publisher and cc:attributionName both ended with a space.
-
changed
permission dalicc:ChangeLicensewas
permission dalicc:ChangeLicense with duties [dalicc:compliantLicense]Manual edit The review's finding on family consistency and consolidation decision 4: the record modelled no reciprocity although section 3 says 'When the Program is made available in source code form: a) it must be made available under this Agreement', it made no patent statement although section 2(b) grants one and section 7 ends it on patent litigation, and dct:publisher and cc:attributionName both ended with a space.
-
added
permission dalicc:patentGrantManual edit The review's finding on family consistency and consolidation decision 4: the record modelled no reciprocity although section 3 says 'When the Program is made available in source code form: a) it must be made available under this Agreement', it made no patent statement although section 2(b) grants one and section 7 ends it on patent litigation, and dct:publisher and cc:attributionName both ended with a space.
-
changed
permission odrl:derive with duties [cc:ShareAlike]was
permission odrl:deriveManual edit The review's finding on family consistency and consolidation decision 4: the record modelled no reciprocity although section 3 says 'When the Program is made available in source code form: a) it must be made available under this Agreement', it made no patent statement although section 2(b) grants one and section 7 ends it on patent litigation, and dct:publisher and cc:attributionName both ended with a space.
-
changed
permission odrl:distribute with duties [cc:Attribution, cc:Notice, cc:ShareAlike, cc:SourceCode]was
permission odrl:distribute with duties [cc:Attribution, cc:Notice, cc:SourceCode]Manual edit The review's finding on family consistency and consolidation decision 4: the record modelled no reciprocity although section 3 says 'When the Program is made available in source code form: a) it must be made available under this Agreement', it made no patent statement although section 2(b) grants one and section 7 ends it on patent litigation, and dct:publisher and cc:attributionName both ended with a space.
-
changed
permission odrl:modify with duties [cc:ShareAlike, dalicc:modificationNotice]was
permission odrl:modify with duties [dalicc:modificationNotice]Manual edit The review's finding on family consistency and consolidation decision 4: the record modelled no reciprocity although section 3 says 'When the Program is made available in source code form: a) it must be made available under this Agreement', it made no patent statement although section 2(b) grants one and section 7 ends it on patent litigation, and dct:publisher and cc:attributionName both ended with a space.
-
added
prohibition dalicc:patentRetaliationTerminationManual edit The review's finding on family consistency and consolidation decision 4: the record modelled no reciprocity although section 3 says 'When the Program is made available in source code form: a) it must be made available under this Agreement', it made no patent statement although section 2(b) grants one and section 7 ends it on patent litigation, and dct:publisher and cc:attributionName both ended with a space.
-
changed
permission cc:DerivativeWorkswas
permission cc:DerivativeWorks with duties [cc:Attribution, cc:Notice, cc:SourceCode, dalicc:modificationNotice]Manual edit Weak-copyleft family alignment of 2026-09-15: the record is brought onto the shape of CPL-1.0 and IPL-1.0, which model the same text. Section 2(a) grants the right to 'reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution', so dalicc:sublicense replaces the older spelling odrl:grantUse and dalicc:ModifiedWorks is stated; the attribution, notice and source duties that sat on the derivative-works permission move onto odrl:modify and odrl:derive, where the rest of the family carries them; the unsupported dalicc:noWarrantyNotice permission and dalicc:addStatement prohibition go, because section 3 lets a distributor add its own notices rather than forbidding it; and the dalicc:promote prohibition goes, because this text has no trademark or endorsement clause at all.
-
added
permission dalicc:ModifiedWorksManual edit Weak-copyleft family alignment of 2026-09-15: the record is brought onto the shape of CPL-1.0 and IPL-1.0, which model the same text. Section 2(a) grants the right to 'reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution', so dalicc:sublicense replaces the older spelling odrl:grantUse and dalicc:ModifiedWorks is stated; the attribution, notice and source duties that sat on the derivative-works permission move onto odrl:modify and odrl:derive, where the rest of the family carries them; the unsupported dalicc:noWarrantyNotice permission and dalicc:addStatement prohibition go, because section 3 lets a distributor add its own notices rather than forbidding it; and the dalicc:promote prohibition goes, because this text has no trademark or endorsement clause at all.
-
removed
permission dalicc:noWarrantyNoticeManual edit Weak-copyleft family alignment of 2026-09-15: the record is brought onto the shape of CPL-1.0 and IPL-1.0, which model the same text. Section 2(a) grants the right to 'reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution', so dalicc:sublicense replaces the older spelling odrl:grantUse and dalicc:ModifiedWorks is stated; the attribution, notice and source duties that sat on the derivative-works permission move onto odrl:modify and odrl:derive, where the rest of the family carries them; the unsupported dalicc:noWarrantyNotice permission and dalicc:addStatement prohibition go, because section 3 lets a distributor add its own notices rather than forbidding it; and the dalicc:promote prohibition goes, because this text has no trademark or endorsement clause at all.
-
added
permission dalicc:sublicenseManual edit Weak-copyleft family alignment of 2026-09-15: the record is brought onto the shape of CPL-1.0 and IPL-1.0, which model the same text. Section 2(a) grants the right to 'reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution', so dalicc:sublicense replaces the older spelling odrl:grantUse and dalicc:ModifiedWorks is stated; the attribution, notice and source duties that sat on the derivative-works permission move onto odrl:modify and odrl:derive, where the rest of the family carries them; the unsupported dalicc:noWarrantyNotice permission and dalicc:addStatement prohibition go, because section 3 lets a distributor add its own notices rather than forbidding it; and the dalicc:promote prohibition goes, because this text has no trademark or endorsement clause at all.
-
changed
permission odrl:derive with duties [cc:Attribution, cc:Notice, cc:ShareAlike, cc:SourceCode, dalicc:modificationNotice]was
permission odrl:derive with duties [cc:ShareAlike]Manual edit Weak-copyleft family alignment of 2026-09-15: the record is brought onto the shape of CPL-1.0 and IPL-1.0, which model the same text. Section 2(a) grants the right to 'reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution', so dalicc:sublicense replaces the older spelling odrl:grantUse and dalicc:ModifiedWorks is stated; the attribution, notice and source duties that sat on the derivative-works permission move onto odrl:modify and odrl:derive, where the rest of the family carries them; the unsupported dalicc:noWarrantyNotice permission and dalicc:addStatement prohibition go, because section 3 lets a distributor add its own notices rather than forbidding it; and the dalicc:promote prohibition goes, because this text has no trademark or endorsement clause at all.
-
removed
permission odrl:grantUseManual edit Weak-copyleft family alignment of 2026-09-15: the record is brought onto the shape of CPL-1.0 and IPL-1.0, which model the same text. Section 2(a) grants the right to 'reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution', so dalicc:sublicense replaces the older spelling odrl:grantUse and dalicc:ModifiedWorks is stated; the attribution, notice and source duties that sat on the derivative-works permission move onto odrl:modify and odrl:derive, where the rest of the family carries them; the unsupported dalicc:noWarrantyNotice permission and dalicc:addStatement prohibition go, because section 3 lets a distributor add its own notices rather than forbidding it; and the dalicc:promote prohibition goes, because this text has no trademark or endorsement clause at all.
-
changed
permission odrl:modify with duties [cc:Attribution, cc:Notice, cc:ShareAlike, cc:SourceCode, dalicc:modificationNotice]was
permission odrl:modify with duties [cc:ShareAlike, dalicc:modificationNotice]Manual edit Weak-copyleft family alignment of 2026-09-15: the record is brought onto the shape of CPL-1.0 and IPL-1.0, which model the same text. Section 2(a) grants the right to 'reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution', so dalicc:sublicense replaces the older spelling odrl:grantUse and dalicc:ModifiedWorks is stated; the attribution, notice and source duties that sat on the derivative-works permission move onto odrl:modify and odrl:derive, where the rest of the family carries them; the unsupported dalicc:noWarrantyNotice permission and dalicc:addStatement prohibition go, because section 3 lets a distributor add its own notices rather than forbidding it; and the dalicc:promote prohibition goes, because this text has no trademark or endorsement clause at all.
-
removed
prohibition dalicc:addStatementManual edit Weak-copyleft family alignment of 2026-09-15: the record is brought onto the shape of CPL-1.0 and IPL-1.0, which model the same text. Section 2(a) grants the right to 'reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution', so dalicc:sublicense replaces the older spelling odrl:grantUse and dalicc:ModifiedWorks is stated; the attribution, notice and source duties that sat on the derivative-works permission move onto odrl:modify and odrl:derive, where the rest of the family carries them; the unsupported dalicc:noWarrantyNotice permission and dalicc:addStatement prohibition go, because section 3 lets a distributor add its own notices rather than forbidding it; and the dalicc:promote prohibition goes, because this text has no trademark or endorsement clause at all.
-
removed
prohibition dalicc:promoteManual edit Weak-copyleft family alignment of 2026-09-15: the record is brought onto the shape of CPL-1.0 and IPL-1.0, which model the same text. Section 2(a) grants the right to 'reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution', so dalicc:sublicense replaces the older spelling odrl:grantUse and dalicc:ModifiedWorks is stated; the attribution, notice and source duties that sat on the derivative-works permission move onto odrl:modify and odrl:derive, where the rest of the family carries them; the unsupported dalicc:noWarrantyNotice permission and dalicc:addStatement prohibition go, because section 3 lets a distributor add its own notices rather than forbidding it; and the dalicc:promote prohibition goes, because this text has no trademark or endorsement clause at all.
-
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
The version this model had before the content review of 2026-09-15.
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.