Functional Source License, Version 1.1, MIT Future License

Also known as FSL 1.1, FSL-1.1-MIT, Functional Source 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/FSL-1.1-MIT

Permissions

Commercial use from the text
Derivative works from the text
Derive from the text
Duties
- Notice from the text
- Share alike from the text
Display from the text
Distribute from the text
Duties
- Notice from the text
- Share alike from the text
Modified works from the text
Modify from the text
Duties
- Notice from the text
- Share alike from the text
Patent grant from the text
Present from the text
Reproduce from the text

Prohibitions

Change license from the text
Promote 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.

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.
Field of use restriction: any Permitted Purpose, which is any purpose other than a Competing Use
Reciprocity scope: all copies, modifications and derivatives of the Software

Clauses

Warranty disclaimer

THE SOFTWARE IS PROVIDED "AS IS" AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, TITLE OR NON-INFRINGEMENT.

Limitation of liability

IN NO EVENT WILL WE HAVE ANY LIABILITY TO YOU ARISING OUT OF OR RELATED TO THE SOFTWARE, INCLUDING INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES, EVEN IF WE HAVE BEEN INFORMED OF THEIR POSSIBILITY IN ADVANCE.

Additional clauses

The "Software" is each version of the software that we make available under these Terms and Conditions, as indicated by our inclusion of these Terms and Conditions with the Software.

Info

Target asset types: Software
Region / jurisdiction: Worldwide
Validity: Perpetual
Source: https://spdx.org/licenses/FSL-1.1-MIT.html
Legal code: https://fsl.software/FSL-1.1-MIT.template.md
This description is published under: Creative Commons Attribution 4.0 International
SPDX identifier: FSL-1.1-MIT on the SPDX license list
Version: 1.1
DALICC identifier: FSL-1.1-MIT

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/FSL-1.1-MIT",
  "license-title": "Functional Source License, Version 1.1, MIT Future License",
  "spdx-id": "FSL-1.1-MIT",
  "asset": null,
  "generated-by": "DALICC"
}

RDF, Turtle

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

<https://example.org/my-work>
    cc:license <https://dalicc.net/licenselibrary/FSL-1.1-MIT> .

RDF, JSON-LD

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

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

Badge

Markdown

[![License: Functional Source License, Version 1.1, MIT Future License](https://dalicc.net/license-library/FSL-1.1-MIT/badge.svg)](https://dalicc.net/license-library/FSL-1.1-MIT)

HTML

<a href="https://dalicc.net/license-library/FSL-1.1-MIT"><img src="https://dalicc.net/license-library/FSL-1.1-MIT/badge.svg" alt="License: Functional Source License, Version 1.1, MIT Future License"></a>

Review

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

The record models the Functional Source License 1.1 with the MIT license as its future licence. The grant is wide, it covers use, copying, modification, derivative works, public performance, public display and redistribution, but only for a Permitted Purpose, which the text defines as any purpose other than a Competing Use. It is not an open source licence while that restriction is in force. Two years after a version is made available, the same version is also available under the MIT license.

11 findings

info Rubric 1 spdx:licenseId applied

File name, record identifier, SPDX identifier and IRI local name agree. cc:legalcode points at the template the publisher hosts and dct:source at the SPDX entry. dct:publisher is left out: the text names no steward, only 'we' and 'us'. The record is not modelled as a variant of MIT: the Functional Source License is a licence of its own that grants a second licence later, not a flavour of the later one.
info Rubric 2 odrl:target applied

dcmitype:Software only. The text defines 'the Software' as each version of the software made available under the terms.
major Rubric 3 odrl:permission applied

'We hereby grant you the right to use, copy, modify, create derivative works, publicly perform, publicly display and redistribute the Software for any Permitted Purpose identified below.' That gives odrl:reproduce, odrl:modify, odrl:derive, cc:DerivativeWorks, dalicc:ModifiedWorks, odrl:present, odrl:display and odrl:distribute. dalicc:patentGrant for 'To the extent your use for a Permitted Purpose would necessarily infringe our patents, the license grant above includes a license under our patents.' cc:CommercialUse is permitted, because the text lists internal use, non-commercial education and non-commercial research as examples of Permitted Purposes and bars only a Competing Use, which is itself defined as a commercial product or service that substitutes for the Software.
major Rubric 4 odrl:prohibition applied

dalicc:ChangeLicense for 'The Terms and Conditions apply to all copies, modifications and derivatives of the Software.' dalicc:promote for 'Except for displaying the License Details and identifying us as the origin of the Software, you have no right under these Terms and Conditions to use our trademarks, trade names, service marks or product names.' dalicc:patentRetaliationTermination for 'If you make a claim against any party that the Software infringes or contributes to the infringement of any patent, then your patent license to the Software ends immediately.'
major Rubric 5 odrl:duty applied

cc:Notice for 'you must include a copy of or a link to these Terms and Conditions and not remove any copyright notices provided in or with the Software' and cc:ShareAlike for 'The Terms and Conditions apply to all copies, modifications and derivatives of the Software.' Both hang on odrl:distribute, odrl:modify and odrl:derive, which is the reach the Redistribution clause gives them. dalicc:reciprocityScope says the same in words. No cc:Attribution: the text asks for copyright notices to be left in place, which is cc:Notice, and gives credit only as a permission under Trademarks.
major Rubric 6 dalicc:WarrantyDisclaimer applied

The Disclaimer section is two paragraphs, one disclaiming warranty and one limiting liability, so each goes into the property that names it. Nine further clauses are quoted in dalicc:additionalClauses, including the whole definition of a Permitted Purpose and the future-licence grant.
major Rubric 7 dalicc:validityType applied

dalicc:validityType stays dalicc:perpetual: the grant itself has no end date, and the future licence adds a second licence rather than ending this one. 'We hereby irrevocably grant you an additional license to use the Software under the MIT license that is effective on the second anniversary of the date we make the Software available.' dalicc:terminatesOnBreach is left out because the text carries no termination clause; compliance is written as a condition of the grant instead.
gap Rubric 8 dalicc:additionalClauses none

The future licence has no term. The clause is quoted. Proposed terms: dalicc:changeDate for the date on which the further licence takes effect and dalicc:changeLicense pointing at dalicclib:MIT. The date is relative to each version, so a term would have to hold a period rather than a date.
gap Rubric 8 dalicc:fieldOfUseRestriction none

The Competing Use bar has no term. dalicc:fieldOfUseRestriction is the nearest literal and names it; the definition is quoted in full. Proposed term: dalicc:competingUseRestriction, a rule action for making the licensed work available to others in a product or service that substitutes for it.
info Rubric 9 record none

The consistency check of app.services.composer, run against licensedata/dependencygraph/dg_default.ttl, returned no conflicts.
major Rubric 10 record none

FSL-1.1-MIT and FSL-1.1-ALv2 share one text and differ in one paragraph, the future licence, which is the MIT license here. The two records are therefore identical statement for statement and differ only in the identifier, the title, the alternatives and the quoted future-licence clause. Neither is modelled as a variant of the other, because SPDX lists them as two licences and neither is a flavour of the other.

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
5 changes
- changed permission odrl:derive with duties [cc:Notice, cc:ShareAlike]
  
  was permission odrl:derive with duties [cc:Notice, cc:ShareAlike]
  
  Manual edit Its duty cc:Notice quotes "If you redistribute any copies, modifications or derivatives of the Software, you must include a copy of or a link to these Terms and Conditions and not remove any copyright notices provided in or with the Software." Its duty cc:ShareAlike quotes "The Terms and Conditions apply to all copies, modifications and derivatives of the Software."
- changed permission odrl:distribute with duties [cc:Notice, cc:ShareAlike]
  
  was permission odrl:distribute with duties [cc:Notice, cc:ShareAlike]
  
  Manual edit Its duty cc:Notice quotes "If you redistribute any copies, modifications or derivatives of the Software, you must include a copy of or a link to these Terms and Conditions and not remove any copyright notices provided in or with the Software." Its duty cc:ShareAlike quotes "The Terms and Conditions apply to all copies, modifications and derivatives of the Software."
- changed permission odrl:modify with duties [cc:Notice, cc:ShareAlike]
  
  was permission odrl:modify with duties [cc:Notice, cc:ShareAlike]
  
  Manual edit Its duty cc:Notice quotes "If you redistribute any copies, modifications or derivatives of the Software, you must include a copy of or a link to these Terms and Conditions and not remove any copyright notices provided in or with the Software." Its duty cc:ShareAlike quotes "The Terms and Conditions apply to all copies, modifications and derivatives of the Software."
- changed prohibition dalicc:promote
  
  was prohibition dalicc:promote
  
  Manual edit The statement now quotes the sentence of the licence text it rests on: "Except for displaying the License Details and identifying us as the origin of the Software, you have no right under these Terms and Conditions to use our trademarks, trade names, service marks or product names."
- 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-22 (Source-available licences and riders).

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.