Skip to content
Property · DCMI Metadata Terms: properties

dcterms:license explained: recording licenses as URIs, with examples

Published Formatory editorial team
http://purl.org/dc/terms/license

A legal document giving official permission to do something with the resource.

Recommended practice is to identify the license document with a URI. If this is not possible or feasible, a literal value that identifies the license may be provided.

Rights metadata used to be written for people: a sentence at the bottom of a record, read by someone deciding whether to reuse a file. dcterms:license is designed for machines as well. It names a legal document giving official permission to do something with the resource, and the comment asks for that document to be identified with a URI. A crawler, a data portal or a dependency checker can then tell, without parsing prose, whether a dataset can be redistributed or a library linked into a commercial product.

A narrower kind of rights statement

In DCMI Metadata Terms the property is a sub-property of dcterms:rights and of the original dc:rights. Its range is dcterms:LicenseDocument, which is itself a sub-class of dcterms:RightsStatement. Every license is therefore a rights statement, but most rights statements are not licenses.

The distinction is practical. “Copyright 2024 Parks Department” says who holds rights and grants nothing; it belongs in dcterms:rights or, as an agent, in dcterms:rightsHolder. “In copyright, educational use permitted” is a rights status label. A license is the document that actually grants a permission: CC BY 4.0, the Open Database License, the MIT License, a signed reuse agreement.

URI conventions that hold up

For content, Creative Commons deed URIs are the common case. The version is part of the identity: https://creativecommons.org/licenses/by/4.0/ and .../by/3.0/ are different documents, and some versions also exist as jurisdiction ports. A record stating only “CC BY” cannot be resolved to a specific set of terms.

For software, the SPDX License List provides identifiers like MIT, Apache-2.0 and GPL-3.0-or-later, with reference pages at spdx.org/licenses. SPDX distinguishes “only” from “or later” for GNU licenses, a difference that matters legally and that free-text fields routinely lose.

Two smaller habits help aggregation:

  • Keep the URI exactly as the license steward publishes it. http:// and https:// forms of the same Creative Commons URI, or a missing trailing slash, are different strings to a naive comparison.
  • Point to the license itself, not to a page on the local site that summarizes it. The summary is useful for readers but does not identify the license to software.

When no URI exists

The comment allows a literal when a URI is not possible or feasible. Bespoke agreements are the typical case: a donor contract, a commissioned photograph’s usage terms, a data sharing agreement with a partner. A short literal naming the agreement (“Data sharing agreement DSA-2023-14, Harbor Authority”) is acceptable. The document itself should live in an administrative system, and if it can be published, a URI to it is better than the name.

Literal values like “Open” or “Free to use” are the ones to avoid. They sound permissive and identify nothing, which leaves the user with no legal basis to rely on.

License, holder and publisher in one record

A clean record names the license, the rights holder and the publisher as three separate values, since they are frequently three different parties. A university may publish a dataset whose rights belong to a funding agency and which is released under CC BY. Collapsing those into one sentence works for a reader and defeats every filter.

Licenses also attach to specific resources. In DCAT the convention is to put dct:license on each distribution, because a dataset’s CSV export and its API may be offered under different terms. The same logic applies to digitized collections, where a public domain original and a newly written transcription can carry different licenses, each recorded on its own identifier and linked to the other through dcterms:relation or one of its sub-properties.

Dual licensing has no built-in expression. Two dcterms:license values only say that two licenses apply in some sense; whether the user may pick one or must satisfy both has to be explained in an accompanying rights note.

Example in RDF

@prefix dcterms: <http://purl.org/dc/terms/> .

<https://example.org/data/tree-survey-2024.csv>
    dcterms:license <https://creativecommons.org/licenses/by/4.0/> ;
    dcterms:rightsHolder <https://example.org/org/parks-department> .

<https://example.org/code/survey-tools-1.2.0.tar.gz>
    dcterms:license <https://spdx.org/licenses/Apache-2.0.html> .

Questions about dcterms:license

What does dcterms:license record?

It points to the legal document giving official permission to do something with the resource, such as a Creative Commons license for a dataset, an open source license for software or a specific agreement under which a file may be reused.

How does dcterms:license differ from dcterms:rights?

dcterms:rights covers any rights information, including copyright status and access conditions. dcterms:license is a sub-property of it for one narrower thing: a document that grants permission. A copyright notice alone is rights information, not a license.

Which URI should identify a Creative Commons license?

The canonical deed URI, including the version, such as https://creativecommons.org/licenses/by-sa/4.0/. Recording only CC BY without a version is ambiguous, since the 2.0, 3.0 and 4.0 versions differ in their legal terms.

How are software licenses identified?

The SPDX License List gives standard short identifiers such as MIT, Apache-2.0 or GPL-3.0-only, each with a page under spdx.org/licenses. Using those URIs makes licenses comparable across code repositories and software catalogs.

Can a resource have more than one license?

Yes. Dual-licensed software and datasets released under two alternative licenses carry one dcterms:license statement per license. Whether the user may choose either or must comply with both is not expressed by the property and needs explanatory text.

More from DCMI Metadata Terms: properties

All 13 in this group