Missing licence
Do not infer permission from a download button; find the producer’s licence or request clarification.
In-depth practical guides
Connect each resource to its exact licence and retain attribution, version and relevant obligations.
Updated :

AI-generated illustration
Public access does not mean unconditional reuse. A platform may host different licences; text, data, software, images and third-party material may follow different terms.
Open the used file or record page. Note named rights holder, licence, version and full text URL. Do not substitute portal terms for the file licence.
Licence Ouverte and CC BY require attribution under their terms. ODbL also sets conditions for adapted databases and certain public uses. Read the text for your reuse.
Prepare visible attribution, licence link and change notice when required. Check personal data, third-party rights and trademarks separately. A data licence does not settle all these issues.
Reading workshop
File DEMO-L04 prepares separate decisions for objects with different provenance on the same page.
Fictional data and records for learning: none of these results comes from a live service query.
CSV v1 carries a CC BY 4.0 notice. The chart filters columns and aggregates values; the adjacent photo has an explicit exclusion requiring an independent decision.
Open each proposition to compare its diagnosis. More checks may still be needed.
No: the image is explicitly excluded.
No: transformation does not make origin irrelevant.
Appropriate. Retain unresolved questions; this record is not blanket permission.
File: DEMO-L04 Resource: Table L04; DEMO author; v1 Fictional source: https://example.invalid/donnees/L04 Licence: CC BY 4.0 Changes: filtered columns and aggregation Planned credit: author, title, source, licence, changes Third-party photo: excluded; not reused
Link the credit to the file version used and the retained licence text. Record chart transformations and keep the photo exclusion in the object register.
Do not infer permission from a download button; find the producer’s licence or request clarification.
Distinguish map attribution from adapted database conditions; check ODbL terms and producer policy.
READING / ANNOTATED CASE
In this fictional case, “Atlas Demo” publishes table D-42 under CC BY 4.0 and explicitly excludes a third-party photograph. You plan a chart from two columns; its credit only says “Source: internet”. The table below prepares the review and grants no permission.
Fictional example · no observation of a service or client.
On small screens, scroll the table horizontally.
| Check | Source notice | Planned publication | Correction to prepare |
|---|---|---|---|
| Provenance | Atlas Demo · table D-42 · version v2. | “Source: internet”. | Name the organisation and link the exact table. |
| Licence | CC BY 4.0 for the table. | No licence link. | State the licence and link to it. |
| Changes | Two columns extracted from the table. | Chart with shortened labels. | Describe extraction and label changes; retain supplied notices. |
| Scope | Third-party photograph explicitly excluded. | Reuse of that photograph is planned. | Check its rights separately before use. |
No. In this example the photograph is excluded from the table licence. Its status needs a separate check.
Transformation does not remove the need to read applicable terms. For CC BY 4.0, check attribution and indication of changes in section 3 of the official legal code.
References accessed on
Worked exercise
Fictional example: the values and documents teach the method and do not describe a real organisation.
You want to publish a chart based on the CSV and reuse the photograph on the same page. Terms apply to the objects shown.
If the table exceeds the screen, scroll horizontally; arrow keys work when the region is focused.
| Object | Displayed terms |
|---|---|
| CSV | CC BY 4.0 |
| Photograph | Separate terms |
Treat two objects, not a blanket page permission. For CC BY material, prepare credit, reference and licence link with applicable change indications. Proximity does not give the photo that licence; assess its own reuse terms.
Third-party rights or personal data can require permissions the licence does not automatically supply.
Keep file, licence scope, text version, attribution and unresolved question.
Documentation reference : Creative Commons — CC BY 4.0 legal code · Consulted on
DOCUMENTED REFERENCE
An SPDX expression combines identifiers and operators. Link the declaration to an exact version and scope: repository, package or file. These expressions illustrate syntax; they do not state this website’s license.
| Reference | Value or form | What it identifies |
|---|---|---|
| MIT OR Apache-2.0 | OR | A choice between declared licenses. Obligations of the selected license still apply. |
| MIT AND BSD-3-Clause | AND | Both licenses apply together to the stated scope; AND does not mean choosing the more permissive one. |
| GPL-2.0-only WITH Classpath-exception-2.0 | WITH | A license with a named exception, not a general operator joining two independent licenses. |
| LicenseRef-23 | LicenseRef- | A reference to license text defined in the SPDX document. Retrieve the definition; the name alone is insufficient. |
| MIT AND (Apache-2.0 OR BSD-3-Clause) | ( ) | Parentheses require choosing within the group before combining with MIT. |
| WITH > AND > OR | precedence | WITH binds before AND, which binds before OR. Preserve uppercase operators and parentheses. |
Check license text, exceptions and covered files. A recognised identifier or valid expression does not establish the declarant’s rights, component compatibility, or identical licensing for software, content, data and trademarks.
Documentation consulted on .
Assess compatibility and each obligation. Keep resource-level provenance rather than assigning one licence without justification.
Access method and rights differ: check API terms and the data licence.
Access and reuse conditions are two distinct information. Find the references associated with the resource allows you to review the published framework without deducting it from its sole availability.
TOOLS / REGISTERS
Prepare visible attribution, licence link and change notice when required. Check personal data, third-party rights and trademarks separately. A data licence does not settle all these issues.
DOCUMENTED REFERENCE
RightsStatements.org describes the rights status of cultural objects. Statements complement a provider’s detailed information; they do not license your own creations. These three codes have different meanings.
| Reference | Value or form | What it identifies |
|---|---|---|
| InC | 1.0 | Copyright or related rights apply; uses beyond those permitted by law require permission. |
| NoC-OKLR | 1.0 | No copyright restriction, but other known legal restrictions apply in some jurisdictions; read institutional details. |
| CNE | 1.0 | Copyright status has not been evaluated, not “public domain”. |
| rights URI | Statement ≠ licence | Keep URI and version with the exact resource; a portal-wide notice does not replace object-level status. |
Identify whether the statement covers a reproduction, work, metadata or another resource. Preserve specific notices and reuse terms. For images or translations, check third-party information and intended use; a code is not universal permission.
No. That changes an unevaluated status into permission. Keep the published status and establish a reuse basis for your use. If that cannot be established, choose another resource with documented terms.
Documentation consulted on .
DOCUMENTED REFERENCE
Schema 4.7 describes rights without confusing a license name with its standardized identifier. These fields use JSON spelling; XML differs in places, for example rightsURI.
| Reference | Value or form | What it identifies |
|---|---|---|
| rightsList | 0…n | Rights information is optional and repeatable. Multiple entries can describe complex rights; absence grants no additional permission. |
| rights | license title | Readable text identifies the license or rights statement. Retain its full title and version where provided. |
| rightsUri | URI | The URI points to the license. Examine the actual link, not merely a word such as open in a description. |
| rightsIdentifier | CC-BY-4.0 | CC-BY-4.0 is an example of a standardized identifier, not evidence that all DataCite resources use that license. |
| rightsIdentifierScheme | SPDX | SPDX identifies the code system here, not the depositor or rights holder. |
| schemeUri | https://spdx.org/licenses/ | The code-system URI points to the SPDX directory and differs from the specific license URI. |
DataCite Commons builds its license graph from rightsIdentifier. An unknown category can therefore mean this structured field is absent even when information exists elsewhere. Check the version and third-party material actually reused.
No. This is the state of metadata used for that representation. Read the record and resource, retaining the information and scope found; do not turn unknown into inferred permission or prohibition.
Documentation consulted on .
DEEPER READING / PRACTICE
A dataset is publicly accessible but its reuse conditions are not immediately visible. The verification must find the text or reference associated with the resource concerned.
Updated on .
Keep file, file, license mention, version and date of consultation. Discover the differences between the terms of the portal, the dataset and the built-in content.
Accessibility does not demonstrate a general permission for reuse. A mention on a portal may not describe all the files or elements of the dataset.
The license note collects relevant references and passages, and then lists the unresolved questions. The conclusions remain limited to the effectively documented conditions.