Unicode License v3

Also known as UNICODE LICENSE V3, Unicode License v3, Unicode-3.0.

Commercial use: allowed
Share alike: not 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/Unicode-3.0

Permissions

Change license by library convention
Duties
- Use a compliant license by library convention
Charge distribution fee from the text
Commercial use from the text
Derivative works from the text
Derive from the text
Duties
- Attribution from the text
- Notice from the text
Display from the text
Distribute from the text
Duties
- Attribution from the text
- Notice from the text
Grant use from the text
Modified works from the text
Modify from the text
Duties
- Attribution from the text
- Notice from the text
Present from the text
Reproduce from the text

Prohibitions

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.

Clauses

Warranty disclaimer

THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS.

Limitation of liability

IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THE DATA FILES OR SOFTWARE.

Additional clauses

NOTICE TO USER: Carefully read the following legal agreement. BY DOWNLOADING, INSTALLING, COPYING OR OTHERWISE USING DATA FILES, AND/OR SOFTWARE, YOU UNEQUIVOCALLY ACCEPT, AND AGREE TO BE BOUND BY, ALL OF THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF YOU DO NOT AGREE, DO NOT DOWNLOAD, INSTALL, COPY, DISTRIBUTE OR USE THE DATA FILES OR SOFTWARE. Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in these Data Files or Software without prior written authorization of the copyright holder.

Info

Target asset types: Dataset, Software
Region / jurisdiction: Worldwide
Validity: Perpetual
Source: https://spdx.org/licenses/Unicode-3.0.html
Legal code: https://www.unicode.org/license.txt
This description is published under: Creative Commons Attribution 4.0 International
Publisher: Unicode, Inc.
Attribution name: Unicode, Inc.
SPDX identifier: Unicode-3.0 on the SPDX license list
DALICC identifier: Unicode-3.0

This record is published under CC BY 4.0. Credit it as: DALICC License Library, DALICC - Verein zur Förderung der Rechtssicherheit in der Datenbewirtschaftung, https://dalicc.net, CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). The license it describes belongs to its publisher.

Use this license

Everything below is generated from this record. Replace the example address with the address of your own work.

JSON sidecar

{
  "license-uri": "https://dalicc.net/licenselibrary/Unicode-3.0",
  "license-title": "Unicode License v3",
  "spdx-id": "Unicode-3.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/Unicode-3.0> .

RDF, JSON-LD

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

HTML attribution

<p>This work is licensed under <a href="https://dalicc.net/licenselibrary/Unicode-3.0" rel="license">Unicode License v3</a>.</p>

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

Badge

Markdown

[![License: Unicode License v3](https://dalicc.net/license-library/Unicode-3.0/badge.svg)](https://dalicc.net/license-library/Unicode-3.0)

HTML

<a href="https://dalicc.net/license-library/Unicode-3.0"><img src="https://dalicc.net/license-library/Unicode-3.0/badge.svg" alt="License: Unicode License v3"></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: 9 recorded, 8 applied to the record, 0 proposed

Models the Unicode License v3 of 2023, which replaced the 2016 data files and software agreement. It is an MIT style grant over data files and software together, so the record follows the MIT record and carries both dcmitype:Dataset and dcmitype:Software as targets. Nothing here is legal advice.

9 findings

minor Rubric 2 odrl:target applied

The licence covers "data files and any associated documentation (the Data Files) or software and any associated documentation (the Software)", so the asset collection carries dcmitype:Dataset next to dcmitype:Software. That is wider than the plain MIT record, which names software only.
major Rubric 3 odrl:permission applied

The grant reads "Permission is hereby granted, free of charge, to any person obtaining a copy of data files ... to deal in the Data Files or Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Data Files or Software, and to permit persons to whom the Data Files or Software are furnished to do so". The closing limb is modelled as odrl:grantUse, which is how the MIT record models the same wording.
major Rubric 4 odrl:prohibition applied

The closing paragraph states "Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in these Data Files or Software without prior written authorization of the copyright holder", modelled as a dalicc:promote prohibition. No dalicc:ChangeLicense statement is made, following the MIT record: a grant to deal in the work without restriction does not bar relicensing.
minor Rubric 5 odrl:duty applied

The single condition is "provided that either (a) this copyright and permission notice appear with all copies of the Data Files or Software, or (b) this copyright and permission notice appear in associated Documentation". Both limbs require the same notice, so cc:Attribution and cc:Notice hang off odrl:distribute, odrl:modify and odrl:derive, and the choice of place is left to the quoted text.
minor Rubric 6 dalicc:additionalClauses applied

The acceptance notice that opens the agreement and the advertising sentence are quoted in dalicc:additionalClauses; the warranty and liability paragraphs are quoted word for word in their own predicates.
info Rubric 7 cc:jurisdiction applied

The text names no legal system and sets no term, so cc:jurisdiction is dalicc:worldwide and dalicc:validityType is dalicc:perpetual.
info Rubric 9 record none

The consistency check of app.services.composer with the dependency graph dg_default returned an empty conflict list.
major Rubric 10 record applied

Unicode-3.0 replaced Unicode-DFS-2016 in 2024 and both are modelled in this review group. The deontic models are identical; the 2016 text adds the directory listings that define which files are Data Files and which are Software, and the 2023 text drops them. Two records are justified because the two texts are separately cited, and dalicc:variantKind "version" records the chain.
major Rubric 3 odrl:permission applied

Library convention 15: a licence that asks for no reciprocity and no source code asks only that the notice travels with the copy, which is a duty on the acts it governs and not a bar on putting the copy under other terms. dalicc:ChangeLicense is therefore a permission here, and the prohibition the earlier reading wrote is removed. The text reads: "Permission is hereby granted, free of charge, to any person obtaining a copy of data files and any associated documentation (the "Data Files") or software and any associated documentation (the "Software") to deal in the Data Files or Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies." The permission carries the dalicc:compliantLicense duty, as Apache-2.0 does, because the notice has to survive the relicensing.

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, named the license the record itself is published under and removed the quotes that do not name the act they support.

View version 2 JSON-LD Turtle RDF/XML
10 changes
- changed permission dalicc:ChangeLicense with duties [dalicc:compliantLicense]
  
  was permission dalicc:ChangeLicense with duties [dalicc:compliantLicense]
  
  Manual edit The statement is marked as a library convention, family rule 15: Permissive records permit relicensing: the text does not state it in as many words. Its duty dalicc:compliantLicense is marked as a library convention, family rule 15: Permissive records permit relicensing.
- changed permission odrl:derive with duties [cc:Attribution, cc:Notice]
  
  was permission odrl:derive with duties [cc:Attribution, cc:Notice]
  
  Manual edit Its duty cc:Attribution quotes "Permission is hereby granted, free of charge, to any person obtaining a copy of data files and any associated documentation (the "Data Files") or software and any associated documentation (the "Software") to deal in the Data Files or Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Data Files or Software, and to permit persons to whom the Data Files or Software are furnished to do so, provided that either (a) this copyright and permission notice appear with all copies of the Data Files or Software, or (b) this copyright and permission notice appear in associated Documentation." Its duty cc:Notice quotes "Permission is hereby granted, free of charge, to any person obtaining a copy of data files and any associated documentation (the "Data Files") or software and any associated documentation (the "Software") to deal in the Data Files or Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Data Files or Software, and to permit persons to whom the Data Files or Software are furnished to do so, provided that either (a) this copyright and permission notice appear with all copies of the Data Files or Software, or (b) this copyright and permission notice appear in associated Documentation."
- changed permission odrl:distribute with duties [cc:Attribution, cc:Notice]
  
  was permission odrl:distribute with duties [cc:Attribution, cc:Notice]
  
  Manual edit The statement now quotes the sentence of the licence text it rests on: "Permission is hereby granted, free of charge, to any person obtaining a copy of data files and any associated documentation (the "Data Files") or software and any associated documentation (the "Software") to deal in the Data Files or Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Data Files or Software, and to permit persons to whom the Data Files or Software are furnished to do so, provided that either (a) this copyright and permission notice appear with all copies of the Data Files or Software, or (b) this copyright and permission notice appear in associated Documentation." Its duty cc:Attribution quotes "Permission is hereby granted, free of charge, to any person obtaining a copy of data files and any associated documentation (the "Data Files") or software and any associated documentation (the "Software") to deal in the Data Files or Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Data Files or Software, and to permit persons to whom the Data Files or Software are furnished to do so, provided that either (a) this copyright and permission notice appear with all copies of the Data Files or Software, or (b) this copyright and permission notice appear in associated Documentation." Its duty cc:Notice quotes "Permission is hereby granted, free of charge, to any person obtaining a copy of data files and any associated documentation (the "Data Files") or software and any associated documentation (the "Software") to deal in the Data Files or Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Data Files or Software, and to permit persons to whom the Data Files or Software are furnished to do so, provided that either (a) this copyright and permission notice appear with all copies of the Data Files or Software, or (b) this copyright and permission notice appear in associated Documentation."
- changed permission odrl:grantUse
  
  was permission odrl:grantUse
  
  Manual edit The statement now quotes the sentence of the licence text it rests on: "Permission is hereby granted, free of charge, to any person obtaining a copy of data files ... to deal in the Data Files or Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Data Files or Software, and to permit persons to whom the Data Files or Software are furnished to do so"
- changed permission odrl:modify with duties [cc:Attribution, cc:Notice]
  
  was permission odrl:modify with duties [cc:Attribution, cc:Notice]
  
  Manual edit Its duty cc:Attribution quotes "Permission is hereby granted, free of charge, to any person obtaining a copy of data files and any associated documentation (the "Data Files") or software and any associated documentation (the "Software") to deal in the Data Files or Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Data Files or Software, and to permit persons to whom the Data Files or Software are furnished to do so, provided that either (a) this copyright and permission notice appear with all copies of the Data Files or Software, or (b) this copyright and permission notice appear in associated Documentation." Its duty cc:Notice quotes "Permission is hereby granted, free of charge, to any person obtaining a copy of data files and any associated documentation (the "Data Files") or software and any associated documentation (the "Software") to deal in the Data Files or Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Data Files or Software, and to permit persons to whom the Data Files or Software are furnished to do so, provided that either (a) this copyright and permission notice appear with all copies of the Data Files or Software, or (b) this copyright and permission notice appear in associated Documentation."
- changed prohibition dalicc:promote
  
  was prohibition dalicc:promote
  
  Manual edit The statement now quotes the sentence of the licence text it rests on: "Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in these Data Files or Software without prior written authorization of the copyright holder."
- 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.
- changed permission odrl:derive with duties [cc:Attribution, cc:Notice]
  
  was permission odrl:derive with duties [cc:Attribution, cc:Notice]
  
  Manual edit Removed the quoted evidence of duty cc:Attribution on odrl:derive, duty cc:Attribution on odrl:distribute, duty cc:Attribution on odrl:modify: the quoted sentence does not name the act. The statements stay, read from the text without a linked quote.
- changed permission odrl:distribute with duties [cc:Attribution, cc:Notice]
  
  was permission odrl:distribute with duties [cc:Attribution, cc:Notice]
  
  Manual edit Removed the quoted evidence of duty cc:Attribution on odrl:derive, duty cc:Attribution on odrl:distribute, duty cc:Attribution on odrl:modify: the quoted sentence does not name the act. The statements stay, read from the text without a linked quote.
- changed permission odrl:modify with duties [cc:Attribution, cc:Notice]
  
  was permission odrl:modify with duties [cc:Attribution, cc:Notice]
  
  Manual edit Removed the quoted evidence of duty cc:Attribution on odrl:derive, duty cc:Attribution on odrl:distribute, duty cc:Attribution on odrl:modify: the quoted sentence does not name the act. The statements stay, read from the text without a linked quote.
Version 1

Created from the license text on 2026-09-15 (Python, PHP, Unicode and W3C).

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.