Reciprocal Public License 1.1

Also known as RPL 1.1, RPL-1.1, Reciprocal Public License, Reciprocal Public License 1.1.

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/RPL-1.1

Permissions

Commercial use from the text
Derivative works from the text
Derive from the text
Duties
- Attribution from the text
- Include notice file from the text
- Modification notice from the text
- Notice from the text
- Rename from the text
- Source code from the text
Display from the text
Distribute from the text
Duties
- Attribution from the text
- Export control notice from the text
- Include notice file from the text
- Notice from the text
- Source code from the text
Modified works from the text
Modify from the text
Duties
- Attribution from the text
- Include notice file from the text
- Modification notice from the text
- Notice from the text
- Rename from the text
- Source code from the text
Network use trigger from the text
Duties
- Source code from the text
Patent grant from the text
Present from the text
Reproduce from the text

Prohibitions

Add limitation from the text
Change license from the text
Promote from the text

License-wide duties

Share alike from the text

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.

No default rule of that graph reaches this license: it speaks about every act the rules are about.

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.
Cure period: 30 days
Governing law: the law of the State of Colorado, United States
Or later version option: Yes
Source publication period: available at the time of deployment, and for as long as the extensions are deployed or at least twelve (12) months after deployment, whichever is longer
Terminates on breach: Yes

Clauses

Warranty disclaimer

LICENSED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE LICENSED SOFTWARE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. FURTHER THERE IS NO WARRANTY MADE AND ALL IMPLIED WARRANTIES ARE DISCLAIMED THAT THE LICENSED SOFTWARE MEETS OR COMPLIES WITH ANY DESCRIPTION OF PERFORMANCE OR OPERATION, SAID COMPATIBILITY AND SUITABILITY BEING YOUR RESPONSIBILITY. LICENSOR DISCLAIMS ANY WARRANTY, IMPLIED OR EXPRESSED, THAT ANY CONTRIBUTOR'S EXTENSIONS MEET ANY STANDARD OF COMPATIBILITY OR DESCRIPTION OF PERFORMANCE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LICENSED SOFTWARE IS WITH YOU. SHOULD LICENSED SOFTWARE PROVE DEFECTIVE IN ANY RESPECT, YOU (AND NOT THE LICENSOR OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. UNDER THE TERMS OF THIS LICENSOR WILL NOT SUPPORT THIS SOFTWARE AND IS UNDER NO OBLIGATION TO ISSUE UPDATES TO THIS SOFTWARE. LICENSOR HAS NO KNOWLEDGE OF ERRANT CODE OR VIRUS IN THIS SOFTWARE, BUT DOES NOT WARRANT THAT THE SOFTWARE IS FREE FROM SUCH ERRORS OR VIRUSES. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF LICENSED SOFTWARE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.

Limitation of liability

UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE LICENSOR, ANY CONTRIBUTOR, OR ANY DISTRIBUTOR OF LICENSED SOFTWARE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.

Accepting warranty or additional liability

You may choose to offer, and charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Licensed Software. However, You may do so only on Your own behalf, and not on behalf of the Licensor or any Contributor. You must make it clear that any such warranty, support, indemnity or liability obligation is offered by You alone, and You hereby agree to indemnify the Licensor and every Contributor for any liability plus attorney fees, costs, and related expenses due to any such action or claim incurred by the Licensor or such Contributor as a result of warranty, support, indemnity or liability terms You offer.

Additional clauses

"Deploy" means to use, Serve, sublicense or distribute Licensed Software other than for Your internal Research and/or Personal Use, and includes without limitation, any and all internal use or distribution of Licensed Software within Your business or organization other than for Research and/or Personal Use, as well as direct or indirect sublicensing or distribution of Licensed Software by You to any third party in any form or manner.

Info

Target asset types: Software
Region / jurisdiction: Worldwide
Validity: Perpetual
Source: https://opensource.org/license/RPL-1.1
Legal code: https://opensource.org/license/RPL-1.1
This description is published under: Creative Commons Attribution 4.0 International
Publisher: Technical Pursuit Inc.
SPDX identifier: RPL-1.1 on the SPDX license list
DALICC identifier: RPL-1.1

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/RPL-1.1",
  "license-title": "Reciprocal Public License 1.1",
  "spdx-id": "RPL-1.1",
  "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/RPL-1.1> .

RDF, JSON-LD

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

HTML attribution

<p>This work is licensed under <a href="https://dalicc.net/licenselibrary/RPL-1.1" rel="license">Reciprocal Public License 1.1</a>.</p>

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

Badge

Markdown

[![License: Reciprocal Public License 1.1](https://dalicc.net/license-library/RPL-1.1/badge.svg)](https://dalicc.net/license-library/RPL-1.1)

HTML

<a href="https://dalicc.net/license-library/RPL-1.1"><img src="https://dalicc.net/license-library/RPL-1.1/badge.svg" alt="License: Reciprocal Public License 1.1"></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: 14 recorded, 5 applied to the record, 0 proposed

Models the Reciprocal Public License, whose point is that deployment, not only distribution, triggers the duty to publish source. The record follows OSL-3.0 and GPL-2.0-only for whole-work reciprocity and quotes the Deploy and Serve definitions, because the library has no term for a network-use trigger. A reader should treat the quoted definitions as the operative part of this licence.

14 findings

info Rubric 1 spdx:licenseId none

File name, license id, SPDX id and IRI agree. dct:publisher is 'Technical Pursuit Inc.', named in the copyright line of the text.
info Rubric 2 odrl:target none

dcmitype:Software only, following OSL-3.0 and MozillaPublicLicenseVersion20.
major Rubric 3 odrl:permission applied

Section 3.1 grants the right to 'Use, reproduce, modify, display, perform, sublicense and distribute Licensed Software and Your Extensions in both Source Code form or as an executable program' and 3.3 grants a patent licence. The record carries reproduce, distribute, modify, derive, display, present, derivative works, modified works, commercial use and dalicc:patentGrant. odrl:grantUse is deliberately not written although the text says 'sublicense': the composer treats a share-alike duty and a grant-use permission as a direct conflict, and the share-alike duty is the statement that carries the compatibility answer.
minor Rubric 3 dalicc:chargeDistributionFee applied

No distribution-fee permission. Section 6.1 caps what may be charged: 'You may not charge a fee for any copy of the Source Code distributed under this Section in excess of Your actual cost of duplication and distribution of said copy.' The clause is quoted instead.
major Rubric 4 odrl:prohibition applied

dalicc:promote for section 5.0 ('No right is granted to the trademarks of Licensor or any Contributor even if such marks are included in the Licensed Software'), dalicc:addLimitation for the last sentence of section 6.0, dalicc:patentRetaliationTermination for section 12.2 and dalicc:ChangeLicense for the reciprocity of section 6.0.
major Rubric 5 odrl:duty applied

cc:ShareAlike is license-wide: 'any Modifications, Derivative Works, or Required Components (collectively Extensions) that You create or to which You contribute are governed by the terms of this License'. cc:SourceCode, cc:Attribution, cc:Notice and dalicc:includeNoticeFile (section 6.3, the human-readable file that must accompany a distribution) hang off distribute, modify and derive; dalicc:modificationNotice and dalicc:rename ('Any Extensions You make and Deploy must have a distinct title') are added to modify and derive.
minor Rubric 6 dalicc:WarrantyOrLiabilityAcceptance applied

Sections 8.0 and 9.0 are quoted verbatim into dalicc:WarrantyDisclaimer and dalicc:LiabilityLimitation and section 6.5 into dalicc:WarrantyOrLiabilityAcceptance, each with its section number stripped and nothing else changed.
gap Rubric 8 dalicc:additionalClauses none

The licence is triggered by deployment or by serving the work over a network, not only by distribution. The vocabulary has no term for that trigger, so the definition is quoted in dalicc:additionalClauses and the source-code duty is attached to distribute, modify and derive. Proposed term: dalicc:networkUseTrigger. Text: '"Deploy" means to use, Serve, sublicense or distribute Licensed Software other than for Your internal Research and/or Personal Use' and '"Serve" means to deliver Licensed Software and/or Your Extensions by means of a computer network to one or more computers for purposes of execution'.
gap Rubric 8 dalicc:additionalClauses none

The source-code duty carries a deadline and a minimum availability period. cc:SourceCode cannot hold a period, so the clause is quoted in dalicc:additionalClauses. Proposed term: dalicc:sourcePublicationPeriod as a literal qualifier on a cc:SourceCode duty. Text: section 6.1, which sets a one-month publication deadline and a twelve-month minimum availability period.
gap Rubric 7 cc:jurisdiction none

The grant itself is worldwide, so cc:jurisdiction stays dalicc:worldwide; only the governing law is national. The vocabulary has no property for a governing law that is separate from the territory of the grant, so the clause is quoted in dalicc:additionalClauses. Proposed term: dalicc:governingLaw. Text: 'This License shall be governed by Colorado law provisions (except to the extent applicable law, if any, provides otherwise), excluding its conflict-of-law provisions.' (section 13.8)
gap Rubric 8 dalicc:additionalClauses none

Automatic termination on breach has no property that a record can carry: dalicc:terminationOnBreach is a policy quality with no predicate. The clause is quoted in dalicc:additionalClauses. Proposed term: dalicc:terminatesOnBreach as a boolean property on odrl:Set, with the cure period as a literal. Text: 'This License and the rights granted hereunder will terminate automatically if You fail to comply with the terms herein and fail to cure such breach within thirty (30) days of becoming aware of the breach.' (section 12.1)
gap Rubric 8 dalicc:additionalClauses none

Section 13.7 puts the licensee on notice of United States export control. There is no term for an export-control notice; the clause is quoted. Proposed term: dalicc:exportControlNotice.
info Rubric 9 record none

The consistency check of app.services.composer, run with the 39 axioms of licensedata/dependencygraph/dg_default.ttl, returned no conflicts.
info Rubric 10 record none

RPL-1.1 and RPL-1.5 are a version chain and both carry dalicc:variantKind "version". Against 1.5 this record lacks the per-file License Notice of Exhibit A, the User-Visible Attribution Notice of Exhibit B and the duty to notify the software community rather than the licensor; its duty set therefore has no dalicc:addStatement. Two records are justified: the notice duties differ and they bind a distributor differently.

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
3 changes
- changed duty cc:ShareAlike
  
  was duty cc:ShareAlike
  
  Manual edit The statement now quotes the sentence of the licence text it rests on: "In consideration of, and as an express condition to, the licenses granted to You under this License You hereby agree that any Modifications, Derivative Works, or Required Components (collectively Extensions) that You create or to which You contribute are governed by the terms of this License including, without limitation, Section 4."
- changed prohibition dalicc:promote
  
  was prohibition dalicc:promote
  
  Manual edit The statement now quotes the sentence of the licence text it rests on: "No right is granted to the trademarks of Licensor or any Contributor even if such marks are included in the Licensed Software."
- 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 (Reciprocal and source-available).

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.