LaTeX Project Public License, Version 1.3c
Also known as LPPL-1.3c.
- Commercial use
- allowed
- Share alike
- not 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
-
Add statement from the text Attaching terms, notices or statements of one's own to the work or to one's modifications when passing it on.
-
Change license from the text The text says: "A Derived Work may be distributed under a different license provided that license itself honors the conditions listed in Clause 6 above, in regard to the Work, though it does not have to honor the rest of the conditions in this license." Replacing the license of the work, or of an adaptation, with another license, or changing its terms.
Duties
- Use a compliant license from the text The text says: "A Derived Work may be distributed under a different license provided that license itself honors the conditions listed in Clause 6 above, in regard to the Work, though it does not have to honor the rest of the conditions in this license." 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 The text says: "If you are not the Current Maintainer of the Work, you may modify your copy of the Work, thus creating a Derived Work based on the Work, and compile this Derived Work, thus creating a Compiled Work based on the Derived Work." Distributing an adaptation of the work and making it available to the public.
-
Derive from the text The text says: "If you are not the Current Maintainer of the Work, you may modify your copy of the Work, thus creating a Derived Work based on the Work, and compile this Derived Work, thus creating a Compiled Work based on the Derived Work." Creating a new work from the work, such as a translation, adaptation or arrangement of it or of a part of it.
Duties
- Modification notice from the text Marking a changed work as changed, saying how it differs from the original and keeping earlier notices of change.
- Original version offer from the text Giving every recipient of a modified work a way back to the original: the unmodified version itself, a difference file, or instructions for obtaining it.
- Source code from the text Providing access to the source code of the work with every copy distributed.
-
Duties
- Notice from the text Notice: keeping the license and copyright notices with every copy.
- 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
- Modification notice from the text Marking a changed work as changed, saying how it differs from the original and keeping earlier notices of change.
- Original version offer from the text Giving every recipient of a modified work a way back to the original: the unmodified version itself, a difference file, or instructions for obtaining it.
- Source code from the text Providing access to the source code of the work with every copy distributed.
-
Present from the text Performing the work in public, including by broadcast or other communication to the public.
Prohibitions
-
Add limitation from the text Not permitted: Add limitation. Adding further limitations or restrictions to the license terms when passing the work on.
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
There is no warranty for the Work. Except when otherwise stated in writing, the Copyright Holder provides the Work `as is', without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of the Work is with you. Should the Work prove defective, you assume the cost of all necessary servicing, repair, or correction.
Limitation of liability
In no event unless required by applicable law or agreed to in writing will The Copyright Holder, or any author named in the components of the Work, or any other party who may distribute and/or modify the Work as permitted above, be liable to you for damages, including any general, special, incidental or consequential damages arising out of any use of the Work or out of inability to use the Work (including, but not limited to, loss of data, data being rendered inaccurate, or losses sustained by anyone as a result of any failure of the Work to operate with any other programs), even if the Copyright Holder or said author or said other party has been advised of the possibility of such damages.
Accepting warranty or additional liability
The Work has the status `author-maintained' if the Copyright Holder explicitly and prominently states near the primary copyright notice in the Work that the Work can only be maintained by the Copyright Holder or simply that it is `author-maintained'. The Work has the status `maintained' if there is a Current Maintainer who has indicated in the Work that they are willing to receive error reports for the Work (for example, by supplying a valid e-mail address). It is not required for the Current Maintainer to acknowledge or act upon these error reports. The Work changes from status `maintained' to `unmaintained' if there is no Current Maintainer, or the person stated to be Current Maintainer of the work cannot be reached through the indicated means of communication for a period of six months, and there are no other significant signs of active maintenance. You can become the Current Maintainer of the Work by agreement with any existing Current Maintainer to take over this role. If the Work is unmaintained, you can become the Current Maintainer of the Work through the following steps: Make a reasonable attempt to trace the Current Maintainer (and the Copyright Holder, if the two differ) through the means of an Internet or similar search. If this search is successful, then enquire whether the Work is still maintained. If it is being maintained, then ask the Current Maintainer to update their communication data within one month. If the search is unsuccessful or no action to resume active maintenance is taken by the Current Maintainer, then announce within the pertinent community your intention to take over maintenance. (If the Work is a LaTeX work, this could be done, for example, by posting to comp.text.tex.) If the Current Maintainer is reachable and agrees to pass maintenance of the Work to you, then this takes effect immediately upon announcement. If the Current Maintainer is not reachable and the Copyright Holder agrees that maintenance of the Work be passed to you, then this takes effect immediately upon announcement. If you make an `intention announcement' as described in 2b. above and after three months your intention is challenged neither by the Current Maintainer nor by the Copyright Holder nor by other people, then you may arrange for the Work to be changed so as to name you as the (new) Current Maintainer. If the previously unreachable Current Maintainer becomes reachable once more within three months of a change completed under the terms of 3b) or 4), then that Current Maintainer must become or remain the Current Maintainer upon request provided they then update their communication data within one month. A change in the Current Maintainer does not, of itself, alter the fact that the Work is distributed under the LPPL license. If you become the Current Maintainer of the Work, you should immediately provide, within the Work, a prominent and unambiguous statement of your status as Current Maintainer. You should also announce your new status to the same pertinent community as in 2b) above.
Info
- Target asset types
- Creative work (i.e. text, picture, sound, movie), Software
- Region / jurisdiction
- Worldwide
- Validity
- Perpetual
- Source
- http://opensource.org/licenses/LPPL-1.3c
- Legal code
- http://opensource.org/licenses/LPPL-1.3c
- This description is published under
- Creative Commons Attribution 4.0 International
- Publisher
- LaTeX3 Project
- Attribution name
- LaTeX3 Project
- SPDX identifier
-
LPPL-1.3con the SPDX license list - DALICC identifier
LatexProjectPublicLicenseVersion13c
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/LatexProjectPublicLicenseVersion13c",
"license-title": "LaTeX Project Public License, Version 1.3c",
"spdx-id": "LPPL-1.3c",
"asset": null,
"generated-by": "DALICC"
}
RDF, Turtle
@prefix cc: <http://creativecommons.org/ns#> .
<https://example.org/my-work>
cc:license <https://dalicc.net/licenselibrary/LatexProjectPublicLicenseVersion13c> .
RDF, JSON-LD
{
"@context": {
"cc": "http://creativecommons.org/ns#"
},
"@id": "https://example.org/my-work",
"cc:license": {
"@id": "https://dalicc.net/licenselibrary/LatexProjectPublicLicenseVersion13c"
}
}
This license carries no attribution duty, so no credit line is offered here.
Badge
Markdown
[](https://dalicc.net/license-library/LatexProjectPublicLicenseVersion13c)
HTML
<a href="https://dalicc.net/license-library/LatexProjectPublicLicenseVersion13c"><img src="https://dalicc.net/license-library/LatexProjectPublicLicenseVersion13c/badge.svg" alt="License: LaTeX Project Public License, Version 1.3c"></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
- 8 recorded, 5 applied to the record, 2 proposed
The LaTeX Project Public License lets anyone modify the Work and distribute the Derived Work, provided every component carries a change notice, replacement components identify themselves as modified, and the unmodified Work stays obtainable. The record prohibited derivative works outright, which reverses clauses 5 and 6. Those prohibitions were replaced by the permissions and duties the text sets, and the clause 10 right to relicense a Derived Work was added.
8 findings
-
major Rubric 3
odrl:prohibitionappliedClause 5 states: "If you are not the Current Maintainer of the Work, you may modify your copy of the Work, thus creating a Derived Work", and clause 6 then sets out how a Derived Work may be distributed. The record prohibited odrl:derive and cc:DerivativeWorks, so a compatibility check treated every LaTeX package fork as forbidden. Removed both and added the permissions with the duties of clause 6.
-
major Rubric 3
odrl:permissionappliedClause 10(a) states: "A Derived Work may be distributed under a different license provided that license itself honors the conditions listed in Clause 6 above". That is dalicc:ChangeLicense with a dalicc:compliantLicense duty. Added.
-
minor Rubric 1
spdx:licenseIdappliedAdded LPPL-1.3c and the missing dct:source. Verified rather than assumed: cc:legalcode already points at the Open Source Initiative page that the SPDX entry lists under seeAlso, and the fetched text is version 1.3c.
-
major Rubric 5
odrl:dutyproposedClause 6(a) requires a replacement component to "clearly and unambiguously identify itself as a modified version of this component to the user when used interactively". That is dalicc:rename plus a runtime identification the vocabulary cannot express. The rename half could be added; it is proposed because clause 6(a) is about runtime identification rather than the file name.
-
minor Rubric 4
odrl:prohibitionproposedcc:ShareAlike is prohibited although clause 10(a) allows a different license and nothing forbids using this one. dalicc:promote is prohibited although the license has no trademark clause; clause 6(c) is about not implying that the original authors provide support.
-
gap Rubric 8
vocabularynoneThe Current Maintainer construction, which gives one party rights that everyone else lacks (clause 4 versus clauses 5 to 7), cannot be expressed: the model has one assignee. Proposed term: dalicc:maintainerRole. Clause 6(a) runtime identification is a second gap.
-
minor Rubric 10
recordappliedStandard-license addition of 2026-09-15, decision 9 and 10: the record was corrected against its new siblings and versioned. Library convention 10: the disclaimer paragraph held the liability sentence, which begins 'IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL THE COPYRIGHT HOLDER ... BE LIABLE'.
-
minor Rubric 4
odrl:prohibitionapplieddalicc:promote was prohibited and no sentence of this text supports it. The statement was the library's reading of a legal default, that a copyright licence which says nothing about endorsement grants no right to it, and it sat in 519 of 581 records as a house convention. That reading is now an adopted dalicc:DefaultRule of the core dependency graph, which supplies it to every licence that is silent about the action, so a compatibility check reaches the same answer and the record states only what the text states. Removed on 2026-09-23; see section 13 of docs/LICENSE_REVIEW.md.
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 2 identification details and 4 permissions, removed 2 prohibitions and recorded the review state. Later changes brought it in line with its family and its text in the verification of 2026-09-15, corrected it against its text on 2026-09-23, left endorsement to the default rule of the core dependency graph, 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
23 changes
-
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
dct:source osl:LPPL-1.3cReview finding Added LPPL-1.3c and the missing dct:source. Verified rather than assumed: cc:legalcode already points at the Open Source Initiative page that the SPDX entry lists under seeAlso, and the fetched text is version 1.3c.
-
added
permission cc:DerivativeWorksReview finding Clause 5 states: "If you are not the Current Maintainer of the Work, you may modify your copy of the Work, thus creating a Derived Work", and clause 6 then sets out how a Derived Work may be distributed. The record prohibited odrl:derive and cc:DerivativeWorks, so a compatibility check treated every LaTeX package fork as forbidden. Removed both and added the permissions with the duties of clause 6.
-
added
permission dalicc:ChangeLicense with duties [dalicc:compliantLicense]Review finding Clause 10(a) states: "A Derived Work may be distributed under a different license provided that license itself honors the conditions listed in Clause 6 above". That is dalicc:ChangeLicense with a dalicc:compliantLicense duty. Added.
-
added
permission dalicc:ModifiedWorksReview finding Clause 5 states: "If you are not the Current Maintainer of the Work, you may modify your copy of the Work, thus creating a Derived Work", and clause 6 then sets out how a Derived Work may be distributed. The record prohibited odrl:derive and cc:DerivativeWorks, so a compatibility check treated every LaTeX package fork as forbidden. Removed both and added the permissions with the duties of clause 6.
-
added
permission odrl:derive with duties [cc:SourceCode, dalicc:modificationNotice]Review finding Clause 5 states: "If you are not the Current Maintainer of the Work, you may modify your copy of the Work, thus creating a Derived Work", and clause 6 then sets out how a Derived Work may be distributed. The record prohibited odrl:derive and cc:DerivativeWorks, so a compatibility check treated every LaTeX package fork as forbidden. Removed both and added the permissions with the duties of clause 6.
-
removed
prohibition cc:DerivativeWorksReview finding Clause 5 states: "If you are not the Current Maintainer of the Work, you may modify your copy of the Work, thus creating a Derived Work", and clause 6 then sets out how a Derived Work may be distributed. The record prohibited odrl:derive and cc:DerivativeWorks, so a compatibility check treated every LaTeX package fork as forbidden. Removed both and added the permissions with the duties of clause 6.
-
removed
prohibition odrl:deriveReview finding Clause 5 states: "If you are not the Current Maintainer of the Work, you may modify your copy of the Work, thus creating a Derived Work", and clause 6 then sets out how a Derived Work may be distributed. The record prohibited odrl:derive and cc:DerivativeWorks, so a compatibility check treated every LaTeX package fork as forbidden. Removed both and added the permissions with the duties of clause 6.
-
added
spdx:licenseId "LPPL-1.3c"Review finding Added LPPL-1.3c and the missing dct:source. Verified rather than assumed: cc:legalcode already points at the Open Source Initiative page that the SPDX entry lists under seeAlso, and the fetched text is version 1.3c.
-
added
dalicc:LiabilityLimitation "In no event unless required by applicable law or agreed to in writing will The Copyright Holder, or any author named in the components of the Work, or any other party who may distribute and/or modify the Work as permitted above, be liable to you for damages, including any general, special, incidental or consequential damages arising out of any use of the Work or out of inability to use the Work (including, but not limited to, loss of data, data being rendered inaccurate, or losses sustained by anyone as a result of any failure of the Work to operate with any other programs), even if the Copyright Holder or said author or said other party has been advised of the possibility of such damages."Manual edit Library convention 10: the disclaimer paragraph held the liability sentence, which begins 'IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL THE COPYRIGHT HOLDER ... BE LIABLE'.
-
changed
dalicc:WarrantyDisclaimer "There is no warranty for the Work. Except when otherwise stated in writing, the Copyright Holder provides the Work `as is', without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of the Work is with you. Should the Work prove defective, you assume the cost of all necessary servicing, repair, or correction."was
dalicc:WarrantyDisclaimer " There is no warranty for the Work. Except when otherwise stated in writing, the Copyright Holder provides the Work `as is', without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of the Work is with you. Should the Work prove defective, you assume the cost of all necessary servicing, repair, or correction. In no event unless required by applicable law or agreed to in writing will The Copyright Holder, or any author named in the components of the Work, or any other party who may distribute and/or modify the Work as permitted above, be liable to you for damages, including any general, special, incidental or consequential damages arising out of any use of the Work or out of inability to use the Work (including, but not limited to, loss of data, data being rendered inaccurate, or losses sustained by anyone as a result of any failure of the Work to operate with any other programs), even if the Copyright Holder or said author or said other party has been advised of the possibility of such damages. "Manual edit Library convention 10: the disclaimer paragraph held the liability sentence, which begins 'IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL THE COPYRIGHT HOLDER ... BE LIABLE'.
-
changed
dalicc:WarrantyOrLiabilityAcceptance "The Work has the status `author-maintained' if the Copyright Holder explicitly and prominently states near the primary copyright notice in the Work that the Work can only be maintained by the Copyright Holder or simply that it is `author-maintained'. The Work has the status `maintained' if there is a Current Maintainer who has indicated in the Work that they are willing to receive error reports for the Work (for example, by supplying a valid e-mail address). It is not required for the Current Maintainer to acknowledge or act upon these error reports. The Work changes from status `maintained' to `unmaintained' if there is no Current Maintainer, or the person stated to be Current Maintainer of the work cannot be reached through the indicated means of communication for a period of six months, and there are no other significant signs of active maintenance. You can become the Current Maintainer of the Work by agreement with any existing Current Maintainer to take over this role. If the Work is unmaintained, you can become the Current Maintainer of the Work through the following steps: Make a reasonable attempt to trace the Current Maintainer (and the Copyright Holder, if the two differ) through the means of an Internet or similar search. If this search is successful, then enquire whether the Work is still maintained. If it is being maintained, then ask the Current Maintainer to update their communication data within one month. If the search is unsuccessful or no action to resume active maintenance is taken by the Current Maintainer, then announce within the pertinent community your intention to take over maintenance. (If the Work is a LaTeX work, this could be done, for example, by posting to comp.text.tex.) If the Current Maintainer is reachable and agrees to pass maintenance of the Work to you, then this takes effect immediately upon announcement. If the Current Maintainer is not reachable and the Copyright Holder agrees that maintenance of the Work be passed to you, then this takes effect immediately upon announcement. If you make an `intention announcement' as described in 2b. above and after three months your intention is challenged neither by the Current Maintainer nor by the Copyright Holder nor by other people, then you may arrange for the Work to be changed so as to name you as the (new) Current Maintainer. If the previously unreachable Current Maintainer becomes reachable once more within three months of a change completed under the terms of 3b) or 4), then that Current Maintainer must become or remain the Current Maintainer upon request provided they then update their communication data within one month. A change in the Current Maintainer does not, of itself, alter the fact that the Work is distributed under the LPPL license. If you become the Current Maintainer of the Work, you should immediately provide, within the Work, a prominent and unambiguous statement of your status as Current Maintainer. You should also announce your new status to the same pertinent community as in 2b) above."was
dalicc:WarrantyOrLiabilityAcceptance " The Work has the status `author-maintained' if the Copyright Holder explicitly and prominently states near the primary copyright notice in the Work that the Work can only be maintained by the Copyright Holder or simply that it is `author-maintained'. The Work has the status `maintained' if there is a Current Maintainer who has indicated in the Work that they are willing to receive error reports for the Work (for example, by supplying a valid e-mail address). It is not required for the Current Maintainer to acknowledge or act upon these error reports. The Work changes from status `maintained' to `unmaintained' if there is no Current Maintainer, or the person stated to be Current Maintainer of the work cannot be reached through the indicated means of communication for a period of six months, and there are no other significant signs of active maintenance. You can become the Current Maintainer of the Work by agreement with any existing Current Maintainer to take over this role. If the Work is unmaintained, you can become the Current Maintainer of the Work through the following steps: Make a reasonable attempt to trace the Current Maintainer (and the Copyright Holder, if the two differ) through the means of an Internet or similar search. If this search is successful, then enquire whether the Work is still maintained. If it is being maintained, then ask the Current Maintainer to update their communication data within one month. If the search is unsuccessful or no action to resume active maintenance is taken by the Current Maintainer, then announce within the pertinent community your intention to take over maintenance. (If the Work is a LaTeX work, this could be done, for example, by posting to comp.text.tex.) If the Current Maintainer is reachable and agrees to pass maintenance of the Work to you, then this takes effect immediately upon announcement. If the Current Maintainer is not reachable and the Copyright Holder agrees that maintenance of the Work be passed to you, then this takes effect immediately upon announcement. If you make an `intention announcement' as described in 2b. above and after three months your intention is challenged neither by the Current Maintainer nor by the Copyright Holder nor by other people, then you may arrange for the Work to be changed so as to name you as the (new) Current Maintainer. If the previously unreachable Current Maintainer becomes reachable once more within three months of a change completed under the terms of 3b) or 4), then that Current Maintainer must become or remain the Current Maintainer upon request provided they then update their communication data within one month. A change in the Current Maintainer does not, of itself, alter the fact that the Work is distributed under the LPPL license. If you become the Current Maintainer of the Work, you should immediately provide, within the Work, a prominent and unambiguous statement of your status as Current Maintainer. You should also announce your new status to the same pertinent community as in 2b) above. "Manual edit Four corrections the text supports. The cc:ShareAlike prohibition goes, because no sentence of the licence forbids a share-alike condition and clause 10(a) lets a Derived Work go under another licence that honours clause 6. Clause 6(d) is the dalicc:originalVersionOffer duty on modify and derive: "You distribute at least one of the following with the Derived Work: 1. A complete, unmodified copy of the Work ... 2. Information that is sufficient to obtain a complete, unmodified copy of the Work." The target gains dalicc:CreativeWork, because the licence governs "Any work being distributed under this License" and not only a program. The padding spaces inside dalicc:WarrantyOrLiabilityAcceptance are stripped and dct:title carries its language tag.
-
changed
dct:title "LaTeX Project Public License, Version 1.3c"@enwas
dct:title "LaTeX Project Public License, Version 1.3c"Manual edit Four corrections the text supports. The cc:ShareAlike prohibition goes, because no sentence of the licence forbids a share-alike condition and clause 10(a) lets a Derived Work go under another licence that honours clause 6. Clause 6(d) is the dalicc:originalVersionOffer duty on modify and derive: "You distribute at least one of the following with the Derived Work: 1. A complete, unmodified copy of the Work ... 2. Information that is sufficient to obtain a complete, unmodified copy of the Work." The target gains dalicc:CreativeWork, because the licence governs "Any work being distributed under this License" and not only a program. The padding spaces inside dalicc:WarrantyOrLiabilityAcceptance are stripped and dct:title carries its language tag.
-
changed
permission odrl:derive with duties [cc:SourceCode, dalicc:modificationNotice, dalicc:originalVersionOffer]was
permission odrl:derive with duties [cc:SourceCode, dalicc:modificationNotice]Manual edit Four corrections the text supports. The cc:ShareAlike prohibition goes, because no sentence of the licence forbids a share-alike condition and clause 10(a) lets a Derived Work go under another licence that honours clause 6. Clause 6(d) is the dalicc:originalVersionOffer duty on modify and derive: "You distribute at least one of the following with the Derived Work: 1. A complete, unmodified copy of the Work ... 2. Information that is sufficient to obtain a complete, unmodified copy of the Work." The target gains dalicc:CreativeWork, because the licence governs "Any work being distributed under this License" and not only a program. The padding spaces inside dalicc:WarrantyOrLiabilityAcceptance are stripped and dct:title carries its language tag.
-
changed
permission odrl:modify with duties [cc:SourceCode, dalicc:modificationNotice, dalicc:originalVersionOffer]was
permission odrl:modify with duties [cc:SourceCode, dalicc:modificationNotice]Manual edit Four corrections the text supports. The cc:ShareAlike prohibition goes, because no sentence of the licence forbids a share-alike condition and clause 10(a) lets a Derived Work go under another licence that honours clause 6. Clause 6(d) is the dalicc:originalVersionOffer duty on modify and derive: "You distribute at least one of the following with the Derived Work: 1. A complete, unmodified copy of the Work ... 2. Information that is sufficient to obtain a complete, unmodified copy of the Work." The target gains dalicc:CreativeWork, because the licence governs "Any work being distributed under this License" and not only a program. The padding spaces inside dalicc:WarrantyOrLiabilityAcceptance are stripped and dct:title carries its language tag.
-
removed
prohibition cc:ShareAlikeManual edit Four corrections the text supports. The cc:ShareAlike prohibition goes, because no sentence of the licence forbids a share-alike condition and clause 10(a) lets a Derived Work go under another licence that honours clause 6. Clause 6(d) is the dalicc:originalVersionOffer duty on modify and derive: "You distribute at least one of the following with the Derived Work: 1. A complete, unmodified copy of the Work ... 2. Information that is sufficient to obtain a complete, unmodified copy of the Work." The target gains dalicc:CreativeWork, because the licence governs "Any work being distributed under this License" and not only a program. The padding spaces inside dalicc:WarrantyOrLiabilityAcceptance are stripped and dct:title carries its language tag.
-
changed
target asset types [dalicc:CreativeWork, dcmitype:Software]was
target asset types [dcmitype:Software]Manual edit Four corrections the text supports. The cc:ShareAlike prohibition goes, because no sentence of the licence forbids a share-alike condition and clause 10(a) lets a Derived Work go under another licence that honours clause 6. Clause 6(d) is the dalicc:originalVersionOffer duty on modify and derive: "You distribute at least one of the following with the Derived Work: 1. A complete, unmodified copy of the Work ... 2. Information that is sufficient to obtain a complete, unmodified copy of the Work." The target gains dalicc:CreativeWork, because the licence governs "Any work being distributed under this License" and not only a program. The padding spaces inside dalicc:WarrantyOrLiabilityAcceptance are stripped and dct:title carries its language tag.
-
removed
prohibition dalicc:promoteManual edit The endorsement prohibition rested on no sentence of the text; the default rule for endorsement now supplies it.
-
changed
permission cc:DerivativeWorkswas
permission cc:DerivativeWorksManual edit The statement now quotes the sentence of the licence text it rests on: "If you are not the Current Maintainer of the Work, you may modify your copy of the Work, thus creating a Derived Work based on the Work, and compile this Derived Work, thus creating a Compiled Work based on the Derived Work."
-
changed
permission dalicc:ChangeLicense with duties [dalicc:compliantLicense]was
permission dalicc:ChangeLicense with duties [dalicc:compliantLicense]Manual edit The statement now quotes the sentence of the licence text it rests on: "A Derived Work may be distributed under a different license provided that license itself honors the conditions listed in Clause 6 above, in regard to the Work, though it does not have to honor the rest of the conditions in this license." Its duty dalicc:compliantLicense quotes "A Derived Work may be distributed under a different license provided that license itself honors the conditions listed in Clause 6 above, in regard to the Work, though it does not have to honor the rest of the conditions in this license."
-
changed
permission odrl:derive with duties [cc:SourceCode, dalicc:modificationNotice, dalicc:originalVersionOffer]was
permission odrl:derive with duties [cc:SourceCode, dalicc:modificationNotice, dalicc:originalVersionOffer]Manual edit The statement now quotes the sentence of the licence text it rests on: "If you are not the Current Maintainer of the Work, you may modify your copy of the Work, thus creating a Derived Work based on the Work, and compile this Derived Work, thus creating a Compiled Work based on the Derived Work."
-
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.