NDE Datasetbeschrijving
Describe one dataset according to NDE requirements (DCAT-AP-NL 3.0).
The NDE Dataset Description profile defines how Dutch heritage institutions register datasets in the NDE Dataset Register. It is based on DCAT-AP-NL 3.0 and uses Schema.org properties for submission; the register converts to RDF internally. Start with dataset metadata, then add access/distribution information and classification tags. Use canonical HTTP IRIs wherever possible — especially for publishers, licenses, and spatial/temporal coverage values.
Based on
- NDE Requirements for datasets: Netwerk Digitaal Erfgoed requirements for dataset and data catalog descriptions.
| Schema | https://sidedoc.app/schemas/0.2.4/nde-dataset-description.json |
| Profile id | nde:v00001 |
| Version | 0.2.4 |
| Help file | help/docs.nde-dataset-description.json |
| Exports | nde-requirements-datasets, dcat-ap-3.0.1 |
| Fields | 44 |
| Help | 38 of 44 fields have a short text, 38 an extended text, 0 a tooltip and 0 details (English). |
Types link to the type library. For what each fact means, see x-sidedoc keys and sheet columns.
Fields
| Field | Id | Type | Values | Required |
|---|---|---|---|---|
| Dataset metadata | nde:s00100 | Container (group of sub-fields) | 1..1 | yes |
| Dataset IRI | nde:f00100 | Url | 1..1 | yes |
| Name | nde:f00200 | Literal | 1..* | yes |
| Description | nde:f00300 | Literal | 1..* | yes |
| Version | nde:f01100 | string | 0..1 | |
| Language | nde:f01200 | string | 0..* | |
| Publisher | nde:f00400 | Agent | 1..1 | yes |
| Creator | nde:f00500 | Agent | 1..* | yes |
| Date published | nde:f00800 | Date | 0..1 | |
| Date created | nde:f00900 | Date | 0..1 | |
| Date modified | nde:f01000 | Date | 0..1 | |
| Subject and coverage | nde:s00400 | Container (group of sub-fields) | 0..1 | |
| Subject | nde:f01600 | Term | 0..* | |
| Keyword | nde:f01700 | Literal | 0..* | |
| Spatial coverage | nde:f01800 | Literal or Term | 0..* | |
| Temporal coverage | nde:f01900 | Literal | 0..* | |
| Access and distribution | nde:s00200 | Container (group of sub-fields) | 1..1 | yes |
| License | nde:f00600 | Term | 1..1 | yes |
| Access rights | nde:f02200 | Term | 0..1 | |
| Landing page | nde:f01300 | Url | 0..* | |
| Distribution | nde:f00700 | Container (group of sub-fields) | 0..* | |
| Distribution IRI | nde:f03200 | Url | 0..1 | |
| Distribution name | nde:f03300 | Literal | 0..1 | |
| Distribution description | nde:f03400 | Literal | 1..* | yes |
| Content URL | nde:f03500 | Url | 1..1 | yes |
| Encoding format | nde:f03600 | Term | 0..1 | |
| Distribution date published | nde:f03700 | Date | 0..1 | |
| Distribution date modified | nde:f03800 | Date | 0..1 | |
| Distribution language | nde:f03900 | string | 0..* | |
| Distribution license | nde:f04000 | Term | 0..1 | |
| Content size (bytes) | nde:f04100 | string | 0..1 | |
| Usage info | nde:f04200 | Url | 0..* | |
| Documentation | nde:f04300 | Url | 0..* | |
| Relations | nde:s00500 | Container (group of sub-fields) | 0..1 | |
| Is based on | nde:f01400 | Url | 0..* | |
| Has part | nde:f02000 | Url | 0..* | |
| Included in data catalog | nde:f02100 | Url | 0..* | |
| Data catalog | nde:f02300 | Container (group of sub-fields) | 0..1 | |
| Catalog IRI | nde:f02400 | Url | 0..1 | |
| Catalog name | nde:f02500 | Literal | 1..* | yes |
| Catalog description | nde:f02600 | Literal | 1..* | yes |
| Catalog publisher | nde:f02700 | Agent | 1..1 | yes |
| Catalog dataset | nde:f02800 | Url | 1..* | yes |
| Citation | nde:f01500 | Reference | 0..* |
Field reference
Dataset metadata
| Id | nde:s00100 |
| Path | datasetMetadata |
| Type | Container (group of sub-fields) |
| Values | 1..1 (required, one value) |
| Multilingual | no |
| Sub-fields | Dataset IRI, Name, Description, Version, Language, Publisher, Creator, Date published, Date created, Date modified |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Core identity and stewardship metadata for the dataset.
Extended help (level 3)
The durable identifier, name, description, version, language, publisher, creator and dates. Dataset IRI, Name, Description, Publisher and Creator are required.
Details (level 4)
Not written yet.
Dataset IRI
| Id | nde:f00100 |
| Path | datasetMetadata.datasetId |
| Type | Url |
| Values | 1..1 (required, one value) |
| Multilingual | no |
| UI hint | url |
| Validation | href: Starts with http:// or https:// ^https?:\/\/.+$As written in the sheet: {"href":"/^https?:\\/\\/.+$/"} |
| Part of | Dataset metadata |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Permanent HTTP(S) identifier for this dataset — the dataset's primary key in the NDE register.
Extended help (level 3)
The Dataset IRI must be a stable, resolvable HTTP or HTTPS URL. The NDE register uses this IRI to deduplicate, crawl, and link to the dataset description. It also functions as the @id in JSON-LD serialisation and as dct:identifier in the DCAT form. Avoid fragment identifiers (#) and prefer stable domain paths. Once published, do not change this IRI without redirecting the old URL.
Details (level 4)
Not written yet.
Name
| Id | nde:f00200 |
| Path | datasetMetadata.name |
| Type | Literal |
| Values | 1..* (required, repeatable) |
| Multilingual | yes |
| Part of | Dataset metadata |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Official dataset name. Provide at least one language variant.
Extended help (level 3)
The name identifies the dataset in search results, catalog browsing, and the NDE register portal. From v2.0 onwards, language-tagged strings (e.g. 'Schilderijen collectie'@nl) become mandatory. The field is repeatable so you can supply names in multiple languages. Keep the name concise while descriptive enough to distinguish this dataset from related ones in the same catalog.
Details (level 4)
Not written yet.
Description
| Id | nde:f00300 |
| Path | datasetMetadata.description |
| Type | Literal |
| Values | 1..* (required, repeatable) |
| Multilingual | yes |
| Part of | Dataset metadata |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Free-text overview of what the dataset contains. Currently recommended; required from NDE v2.0.
Extended help (level 3)
The description is the single most important factor for dataset discoverability in search engines (including Google Dataset Search) and the NDE register. Write for a mixed audience — both subject-matter specialists and curious non-experts. Describe what data the dataset contains, its scope, origin, and any important caveats. Aim for at least three sentences. From v2.0, language-tagged descriptions become mandatory and this field moves from Recommended to Required.
Details (level 4)
Not written yet.
Version
| Id | nde:f01100 |
| Path | datasetMetadata.version |
| Type | string |
| Values | 0..1 (optional, one value) |
| Multilingual | no |
| Part of | Dataset metadata |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Version identifier for this dataset, e.g. '2.1', '2024-01', or 'tweede editie'.
Extended help (level 3)
Versioning lets consumers track which edition of the data they are using and detect changes. The value is a free-text string — common choices include semantic versions ('1.0.0'), date strings ('2024-01'), or descriptive labels. DCAT-AP 3.0 stores this as dcat:version. If you maintain a version history, use Version Notes to describe what changed between editions.
Details (level 4)
Not written yet.
Language
| Id | nde:f01200 |
| Path | datasetMetadata.inLanguage |
| Type | string |
| Values | 0..* (optional, repeatable) |
| Multilingual | no |
| UI hint | language_code |
| Validation | A language tag, for example en, nl or en-GB ^[a-zA-Z]{2,3}(-[a-zA-Z0-9]+)*$As written in the sheet: /^[a-zA-Z]{2,3}(-[a-zA-Z0-9]+)*$/ |
| Part of | Dataset metadata |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Natural language(s) of the data within the dataset. Use BCP47 codes (e.g. 'nl', 'en', 'nl-NL').
Extended help (level 3)
This field describes the language(s) of the actual data records — not the language of the metadata description itself. BCP47 codes are used as literal strings in the NDE Schema.org form; the register converts them to dct:language with EU Languages Authority Table URIs. The field is repeatable for multilingual datasets. Do not confuse this with the language tags on name and description metadata fields.
Details (level 4)
Not written yet.
Publisher
| Id | nde:f00400 |
| Path | datasetMetadata.publisher |
| Type | Agent |
| Values | 1..1 (required, one value) |
| Multilingual | no |
| Identifier schemes | identifier: ORCID, VIAF, ISNI, ROR, Wikidata, GND |
| Part of | Dataset metadata |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Organisation or person responsible for making this dataset publicly available.
Extended help (level 3)
The publisher makes the dataset available to others — not necessarily the entity that created or owns the underlying data (that role belongs to Creator). NDE identifies it by an HTTP IRI: the export uses its first identifier that resolves to one (Wikidata, ROR, ISNI, …), else its homepage, so add a persistent identifier. Also add an e-mail address: it becomes the contact point, which NDE v2.0 requires for organisations. Including an ISIL code as identifier is recommended.
Details (level 4)
Not written yet.
Creator
| Id | nde:f00500 |
| Path | datasetMetadata.creator |
| Type | Agent |
| Values | 1..* (required, repeatable) |
| Multilingual | no |
| Identifier schemes | identifier: ORCID, VIAF, ISNI, ROR, Wikidata, GND |
| Part of | Dataset metadata |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Organisation or person that originally produced the dataset. Currently recommended; required from NDE v2.0.
Extended help (level 3)
Creator and Publisher are separate roles: the publisher makes the data available; the creator produced it. For example, a digitisation bureau might publish a dataset on behalf of a museum that created the underlying collection. Use the same structured Agent format as for Publisher. Multiple creators are allowed for jointly produced datasets.
Details (level 4)
Not written yet.
Date published
| Id | nde:f00800 |
| Path | datasetMetadata.datePublished |
| Type | Date |
| Values | 0..1 (optional, one value) |
| Multilingual | no |
| UI hint | date_picker |
| Part of | Dataset metadata |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Date on which this dataset was formally published. Use ISO 8601 (YYYY-MM-DD or datetime).
Extended help (level 3)
Date Published marks when the dataset became publicly available, as opposed to when it was created internally (see Date Created) or last updated (see Date Modified). ISO 8601 datetime values are preferred over plain dates. This date is used by harvesters and portals to sort datasets and identify new releases. From v2.0, ISO 8601 format becomes strictly required.
Details (level 4)
Not written yet.
Date created
| Id | nde:f00900 |
| Path | datasetMetadata.dateCreated |
| Type | Date |
| Values | 0..1 (optional, one value) |
| Multilingual | no |
| UI hint | date_picker |
| Part of | Dataset metadata |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Date on which this dataset description was originally created. Use ISO 8601 format.
Extended help (level 3)
This field records when the dataset (or its description) was first established — distinct from the date it was published. It helps establish provenance and shows consumers the age of the data. Stored as dct:created in the NDE register. Note: this describes the creation of the dataset description itself, not the historical period the data covers (use Temporal Coverage for that).
Details (level 4)
Not written yet.
Date modified
| Id | nde:f01000 |
| Path | datasetMetadata.dateModified |
| Type | Date |
| Values | 0..1 (optional, one value) |
| Multilingual | no |
| UI hint | date_picker |
| Part of | Dataset metadata |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Most recent date on which this dataset or its description was changed. Use ISO 8601 format.
Extended help (level 3)
Keeping Date Modified current is essential: portals, harvesters, and researcher tools use this timestamp to decide whether to re-harvest the dataset. Update this field whenever meaningful changes are made to the data or metadata. Datetime precision (xsd:dateTime) is preferred over date-only values. DCAT-AP 3.0 defines this as 'the most recent date on which the Dataset was changed or modified'.
Details (level 4)
Not written yet.
Subject and coverage
| Id | nde:s00400 |
| Path | subjectAndCoverage |
| Type | Container (group of sub-fields) |
| Values | 0..1 (optional, one value) |
| Multilingual | no |
| Sub-fields | Subject, Keyword, Spatial coverage, Temporal coverage |
Tooltip (level 1)
Not written yet.
Short help (level 2)
What the dataset is about, and the places and periods it covers.
Extended help (level 3)
Subjects are terms from a controlled vocabulary (for example the AAT); keywords are free text. Spatial and temporal coverage describe the places and periods the data is about, not where or when it was made. NDE uses these fields to make the dataset findable in the register.
Details (level 4)
Not written yet.
Subject
| Id | nde:f01600 |
| Path | subjectAndCoverage.about |
| Type | Term |
| Values | 0..* (optional, repeatable) |
| Multilingual | no |
| UI hint | term_lookup |
| Part of | Subject and coverage |
Tooltip (level 1)
Not written yet.
Short help (level 2)
What the dataset is about: subjects from a controlled vocabulary (IRIs), such as AAT or GTAA terms.
Extended help (level 3)
schema:about replaces schema:genre, which the NDE Requirements for Datasets no longer allow from v2.0. Pick terms with an IRI, for example from the AAT, GTAA or Brinkman thesauri via the Network of Terms; free text is not accepted. Exported as schema:about, and as dcat:theme in DCAT-AP. Genres in older documents export as subjects (terms) or keywords (free text).
Details (level 4)
Not written yet.
Keyword
| Id | nde:f01700 |
| Path | subjectAndCoverage.keywords |
| Type | Literal |
| Values | 0..* (optional, repeatable) |
| Multilingual | yes |
| Part of | Subject and coverage |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Free-text words or phrases that describe this dataset and aid discovery.
Extended help (level 3)
Keywords are plain-language terms users might search for — they complement URI-based subject classification. They do not require controlled vocabulary URIs. Provide multiple keywords covering the subject domain, material type, geographic focus, and time period. In the NDE register, these map to dcat:keyword. From v2.0, language-tagged strings become required (e.g. 'schilderijen'@nl).
Details (level 4)
Not written yet.
Spatial coverage
| Id | nde:f01800 |
| Path | subjectAndCoverage.spatialCoverage |
| Type | Literal or Term |
| Values | 0..* (optional, repeatable) |
| Multilingual | yes |
| Part of | Subject and coverage |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Geographic area the data pertains to. Pick a place term (an IRI, e.g. from GeoNames); NDE v2.0 requires one.
Extended help (level 3)
This field describes where the data is about, not where the publisher is located. Choose terms, for example https://sws.geonames.org/2750405/ for the Netherlands; the NDE recommends GeoNames via the Network of Terms. Text is still accepted, but fails validation from NDE v2.0. In DCAT-AP 3.0, this is dct:spatial. The field is repeatable for datasets covering multiple geographic areas.
Details (level 4)
Not written yet.
Temporal coverage
| Id | nde:f01900 |
| Path | subjectAndCoverage.temporalCoverage |
| Type | Literal |
| Values | 0..* (optional, repeatable) |
| Multilingual | yes |
| Part of | Subject and coverage |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Time period the data covers. Use ISO 8601 dates, intervals, or HTTP URIs.
Extended help (level 3)
Temporal coverage describes the historical or chronological scope of the data — not when the description was written. Accepted formats: ISO 8601 dates ('2011'), intervals ('2011/2012'), shortened ranges ('1889-06/07'), BCE dates ('-0431/-0404'), open-ended ranges ('1440/..'), and HTTP(S) URIs for named time periods. In DCAT-AP 3.0, this becomes a dct:PeriodOfTime with dcat:startDate and dcat:endDate. The field is repeatable for non-contiguous periods.
Details (level 4)
Not written yet.
Access and distribution
| Id | nde:s00200 |
| Path | accessAndDistribution |
| Type | Container (group of sub-fields) |
| Values | 1..1 (required, one value) |
| Multilingual | no |
| Sub-fields | License, Access rights, Landing page, Distribution |
Tooltip (level 1)
Not written yet.
Short help (level 2)
How consumers can access and reuse the dataset.
Extended help (level 3)
Provide licence terms, distribution channels, landing page, and access conditions. At minimum, fill in the Licence field — open licences (CC0, CC BY 4.0) are strongly recommended and required by DERA regulation for metadata.
Details (level 4)
Not written yet.
License
| Id | nde:f00600 |
| Path | accessAndDistribution.license |
| Type | Term |
| Values | 1..1 (required, one value) |
| Multilingual | no |
| UI hint | term_lookup |
| Vocabulary | SPDX License List (https://spdx.org/licenses/)Creative Commons Licenses ( https://creativecommons.org/)rightsstatements.org ( http://rightsstatements.org/vocab/)Enforcement: stores a Term (URI and label), only these schemes, own values allowed, custom labels allowed Binding: embedded in the schema |
| Part of | Access and distribution |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Licence under which this dataset may be used. The value must be a canonical licence URI.
Extended help (level 3)
Use the canonical URI for the licence, for example https://creativecommons.org/publicdomain/zero/1.0/ for CC0 or https://creativecommons.org/licenses/by/4.0/ for CC BY 4.0, with the trailing slash. Do not use free text. Open licences are strongly recommended; the DERA regulation requires openly licensed metadata. The NDE export writes Creative Commons licences in the http form the NDE register expects (http://creativecommons.org/licenses/by/4.0/). In DCAT-AP, distributions without their own licence get this one.
Details (level 4)
Not written yet.
Access rights
| Id | nde:f02200 |
| Path | accessAndDistribution.accessRights |
| Type | Term |
| Values | 0..1 (optional, one value) |
| Multilingual | no |
| UI hint | term_lookup |
| Vocabulary | Access rights (EU Authority) (https://sidedoc.app/vocabs/access-right)Enforcement: stores a Term (URI and label), only these schemes, only terms from the list, no custom labels Binding: embedded in the schema |
| Part of | Access and distribution |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Whether this dataset is publicly accessible, restricted, or not public. Defaults to PUBLIC.
Extended help (level 3)
Use one of three values from the EU Access Rights Named Authority List: PUBLIC (freely accessible), RESTRICTED (limited access by registration or agreement), or NON_PUBLIC (not publicly available). Access rights describe access conditions and differ from legal licence terms. If omitted, the NDE register defaults to PUBLIC. In DCAT-AP 3.0, the value must be a URI from the EU authority list.
Details (level 4)
Not written yet.
Landing page
| Id | nde:f01300 |
| Path | accessAndDistribution.mainEntityOfPage |
| Type | Url |
| Values | 0..* (optional, repeatable) |
| Multilingual | no |
| UI hint | url |
| Validation | href: Starts with http:// or https:// ^https?:\/\/.+$As written in the sheet: {"href":"/^https?:\\/\\/.+$/"} |
| Part of | Access and distribution |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Human-readable web page where users can learn about this dataset.
Extended help (level 3)
The landing page is an HTML page describing the dataset for human visitors — for example, a collection page on an institution's website. It is not the data file itself. Per NDE requirements, 'the human-readable description must be consistent with and include at least all details (such as distributions) from the RDF dataset description'. Point to the original data provider's page rather than an aggregator.
Details (level 4)
Not written yet.
Distribution
| Id | nde:f00700 |
| Path | accessAndDistribution.distribution |
| Type | Container (group of sub-fields) |
| Values | 0..* (optional, repeatable) |
| Multilingual | no |
| Part of | Access and distribution |
| Sub-fields | Distribution IRI, Distribution name, Distribution description, Content URL, Encoding format, Distribution date published, Distribution date modified, Distribution language, Distribution license, Content size (bytes), Usage info, Documentation |
Tooltip (level 1)
Not written yet.
Short help (level 2)
A specific access channel for this dataset — a download file, API endpoint, or SPARQL endpoint.
Extended help (level 3)
A distribution is 'a channel through which a dataset is made available, either for downloading (CSV, RDF dump) or for querying (SPARQL endpoint, OAI-PMH).' All distributions of a dataset must contain broadly the same underlying data. Each distribution must include at minimum a contentUrl and an encodingFormat (MIME type). For API endpoints such as SPARQL, a usageInfo link to the protocol specification is also required.
Details (level 4)
Not written yet.
Distribution IRI
| Id | nde:f03200 |
| Path | accessAndDistribution.distribution.id |
| Type | Url |
| Values | 0..1 (optional, one value) |
| Multilingual | no |
| UI hint | url |
| Validation | href: Starts with http:// or https:// ^https?:\/\/.+$As written in the sheet: {"href":"/^https?:\\/\\/.+$/"} |
| Part of | Distribution |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Stable identifier for this distribution.
Extended help (level 3)
Use a canonical HTTP URI for the distribution endpoint or download record. This IRI persists across metadata updates and uniquely identifies this specific access channel.
Details (level 4)
Not written yet.
Distribution name
| Id | nde:f03300 |
| Path | accessAndDistribution.distribution.name |
| Type | Literal |
| Values | 0..1 (optional, one value) |
| Multilingual | yes |
| Part of | Distribution |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Human-readable title for this distribution.
Extended help (level 3)
Provide a concise display name that distinguishes this distribution from others in the same dataset. For example: 'CSV export', 'SPARQL endpoint', or 'OAI-PMH feed'.
Details (level 4)
Not written yet.
Distribution description
| Id | nde:f03400 |
| Path | accessAndDistribution.distribution.description |
| Type | Literal |
| Values | 1..* (required, repeatable) |
| Multilingual | yes |
| Part of | Distribution |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Explain what this distribution provides.
Extended help (level 3)
Describe the content, packaging, compression, and access method. For APIs, note authentication requirements and usage limits.
Details (level 4)
Not written yet.
Content URL
| Id | nde:f03500 |
| Path | accessAndDistribution.distribution.contentUrl |
| Type | Url |
| Values | 1..1 (required, one value) |
| Multilingual | no |
| UI hint | url |
| Validation | href: Starts with http:// or https:// ^https?:\/\/.+$As written in the sheet: {"href":"/^https?:\\/\\/.+$/"} |
| Part of | Distribution |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Direct URL to retrieve this distribution.
Extended help (level 3)
Use the primary download, API root, or SPARQL endpoint URL. For file downloads, this should be the direct file URL, not a page URL. This maps to schema:contentUrl and dcat:downloadURL in DCAT-AP.
Details (level 4)
Not written yet.
Encoding format
| Id | nde:f03600 |
| Path | accessAndDistribution.distribution.encodingFormat |
| Type | Term |
| Values | 0..1 (optional, one value) |
| Multilingual | no |
| UI hint | term_lookup |
| Vocabulary | Media Types (https://www.iana.org/assignments/media-types)Enforcement: stores a Term (URI and label), only these schemes, own values allowed, custom labels allowed Binding: embedded in the schema |
| Part of | Distribution |
Tooltip (level 1)
Not written yet.
Short help (level 2)
MIME type of the distribution payload (e.g. 'text/csv', 'application/ld+json').
Extended help (level 3)
Select the IANA MIME type that best matches the delivered data representation. Use standard types: 'text/csv', 'application/json', 'application/ld+json', 'application/rdf+xml', 'text/turtle'. This maps to schema:encodingFormat and dcat:mediaType in DCAT-AP.
Details (level 4)
Not written yet.
Distribution date published
| Id | nde:f03700 |
| Path | accessAndDistribution.distribution.datePublished |
| Type | Date |
| Values | 0..1 (optional, one value) |
| Multilingual | no |
| UI hint | date_picker |
| Part of | Distribution |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Date on which this specific distribution became available.
Extended help (level 3)
Use ISO 8601 date values (YYYY-MM-DD). This may differ from the dataset-level Date Published if distributions were released at different times.
Details (level 4)
Not written yet.
Distribution date modified
| Id | nde:f03800 |
| Path | accessAndDistribution.distribution.dateModified |
| Type | Date |
| Values | 0..1 (optional, one value) |
| Multilingual | no |
| UI hint | date_picker |
| Part of | Distribution |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Most recent update date for this distribution.
Extended help (level 3)
Update this field whenever the distribution file or endpoint changes. Consumers use this timestamp to detect stale cached copies and trigger re-downloads.
Details (level 4)
Not written yet.
Distribution language
| Id | nde:f03900 |
| Path | accessAndDistribution.distribution.inLanguage |
| Type | string |
| Values | 0..* (optional, repeatable) |
| Multilingual | no |
| UI hint | language_code |
| Validation | A language tag, for example en, nl or en-GB ^[a-zA-Z]{2,3}(-[a-zA-Z0-9]+)*$As written in the sheet: /^[a-zA-Z]{2,3}(-[a-zA-Z0-9]+)*$/ |
| Part of | Distribution |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Language code(s) of the content delivered by this distribution.
Extended help (level 3)
Use BCP47 codes. Specify at distribution level when a dataset has distributions in different languages (e.g. a Dutch-language CSV and an English-language JSON-LD).
Details (level 4)
Not written yet.
Distribution license
| Id | nde:f04000 |
| Path | accessAndDistribution.distribution.license |
| Type | Term |
| Values | 0..1 (optional, one value) |
| Multilingual | no |
| UI hint | term_lookup |
| Vocabulary | SPDX License List (https://spdx.org/licenses/)Creative Commons Licenses ( https://creativecommons.org/)rightsstatements.org ( http://rightsstatements.org/vocab/)Enforcement: stores a Term (URI and label), only these schemes, own values allowed, custom labels allowed Binding: embedded in the schema |
| Part of | Distribution |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Distribution-specific licence when it differs from the dataset-level licence.
Extended help (level 3)
Leave empty if this distribution inherits the dataset-level licence. Fill in only when distribution-level rights differ — for example when a dataset's metadata is CC0 but its images are CC BY.
Details (level 4)
Not written yet.
Content size (bytes)
| Id | nde:f04100 |
| Path | accessAndDistribution.distribution.contentSize |
| Type | string |
| Values | 0..1 (optional, one value) |
| Multilingual | no |
| Validation | A whole number, zero or more ^\d+$As written in the sheet: /^\\d+$/ |
| Part of | Distribution |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Approximate size of this distribution in bytes.
Extended help (level 3)
Provide the size in bytes when known. For file downloads, use the exact size; for endpoints, provide an estimate of the full dataset export size. This helps consumers assess download feasibility.
Details (level 4)
Not written yet.
Usage info
| Id | nde:f04200 |
| Path | accessAndDistribution.distribution.usageInfo |
| Type | Url |
| Values | 0..* (optional, repeatable) |
| Multilingual | no |
| UI hint | url |
| Validation | href: Starts with http:// or https:// ^https?:\/\/.+$As written in the sheet: {"href":"/^https?:\\/\\/.+$/"} |
| Part of | Distribution |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Instructions or guidance for using this distribution, especially for API endpoints.
Extended help (level 3)
For SPARQL endpoints, include the endpoint URL, supported protocols, and example queries. For OAI-PMH, note the supported metadata prefixes. For file downloads, describe the data structure. Maps to schema:usageInfo in the NDE profile.
Details (level 4)
Not written yet.
Documentation
| Id | nde:f04300 |
| Path | accessAndDistribution.distribution.documentation |
| Type | Url |
| Values | 0..* (optional, repeatable) |
| Multilingual | no |
| UI hint | url |
| Validation | href: Starts with http:// or https:// ^https?:\/\/.+$As written in the sheet: {"href":"/^https?:\\/\\/.+$/"} |
| Part of | Distribution |
Tooltip (level 1)
Not written yet.
Short help (level 2)
A web page that documents this distribution: its structure, how to use it.
Extended help (level 3)
For a data dump, describe the files and the data model; for an API, the endpoints and example requests. Use an https URL. Exported as schema:documentation, and as foaf:page in DCAT-AP.
Details (level 4)
Not written yet.
Relations
| Id | nde:s00500 |
| Path | relations |
| Type | Container (group of sub-fields) |
| Values | 0..1 (optional, one value) |
| Multilingual | no |
| Sub-fields | Is based on, Has part, Included in data catalog, Data catalog, Citation |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Other datasets and catalogs this dataset is linked to, and works it cites.
Extended help (level 3)
Link to the datasets this one is based on or consists of, and to the catalogs that list it. Each link is the other dataset's or catalog's IRI. When that dataset or catalog is a document in your workspace, you can pick it from the list instead of typing the IRI, and the JSON-LD export includes its description.
Details (level 4)
Not written yet.
Is based on
| Id | nde:f01400 |
| Path | relations.isBasedOn |
| Type | Url |
| Values | 0..* (optional, repeatable) |
| Multilingual | no |
| UI hint | link_dataset |
| Validation | href: Starts with http:// or https:// ^https?:\/\/.+$As written in the sheet: {"href":"/^https?:\\/\\/.+$/"} |
| Part of | Relations |
Tooltip (level 1)
Not written yet.
Short help (level 2)
IRI of a dataset this dataset is derived from — for lineage and provenance tracing.
Extended help (level 3)
Use this field when the current dataset is a transformation, subset, enrichment, or derivative of another dataset. The value is the IRI of the source dataset. For example, a dataset of enhanced catalogue records derived from raw exports would reference that source here. In DCAT-AP 3.0, the equivalent is dct:source, defined as 'a related Dataset from which the described Dataset is derived'. Distinct from Citation, which links to publications about the dataset.
Details (level 4)
Not written yet.
Has part
| Id | nde:f02000 |
| Path | relations.hasPart |
| Type | Url |
| Values | 0..* (optional, repeatable) |
| Multilingual | no |
| UI hint | link_dataset |
| Validation | href: Starts with http:// or https:// ^https?:\/\/.+$As written in the sheet: {"href":"/^https?:\\/\\/.+$/"} |
| Part of | Relations |
Tooltip (level 1)
Not written yet.
Short help (level 2)
IRI of a sub-dataset that is part of this dataset and is also published separately.
Extended help (level 3)
Use Has Part when this dataset is a composite containing sub-collections each published with their own IRI and description. Models hierarchical dataset relationships — for example, a national photograph collection that has-part regional sub-collections. In DCAT-AP 3.0, this is dct:hasPart. The inverse relationship (this dataset is part of a larger whole) is expressed by dct:isPartOf.
Details (level 4)
Not written yet.
Included in data catalog
| Id | nde:f02100 |
| Path | relations.includedInDataCatalog |
| Type | Url |
| Values | 0..* (optional, repeatable) |
| Multilingual | no |
| UI hint | link_catalog |
| Validation | href: Starts with http:// or https:// ^https?:\/\/.+$As written in the sheet: {"href":"/^https?:\\/\\/.+$/"} |
| Part of | Relations |
Tooltip (level 1)
Not written yet.
Short help (level 2)
IRI of the data catalog this dataset belongs to. From NDE v2.0, must be an HTTP IRI.
Extended help (level 3)
This field creates a link from the dataset to its parent catalog, supporting cross-catalog discovery and aggregation. The value must be the IRI of a schema:DataCatalog (or dcat:Catalog) that has this dataset as a member. From v2.0, plain text is no longer accepted — the value must be an HTTP IRI. In DCAT-AP, catalog membership is typically expressed from the catalog side using dcat:dataset.
Details (level 4)
Not written yet.
Data catalog
| Id | nde:f02300 |
| Path | relations.dataCatalog |
| Type | Container (group of sub-fields) |
| Values | 0..1 (optional, one value) |
| Multilingual | no |
| Part of | Relations |
| Sub-fields | Catalog IRI, Catalog name, Catalog description, Catalog publisher, Catalog dataset |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Not written yet.
Extended help (level 3)
Not written yet.
Details (level 4)
Not written yet.
Catalog IRI
| Id | nde:f02400 |
| Path | relations.dataCatalog.id |
| Type | Url |
| Values | 0..1 (optional, one value) |
| Multilingual | no |
| UI hint | url |
| Validation | href: Starts with http:// or https:// ^https?:\/\/.+$As written in the sheet: {"href":"/^https?:\\/\\/.+$/"} |
| Part of | Data catalog |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Not written yet.
Extended help (level 3)
Not written yet.
Details (level 4)
Not written yet.
Catalog name
| Id | nde:f02500 |
| Path | relations.dataCatalog.name |
| Type | Literal |
| Values | 1..* (required, repeatable) |
| Multilingual | yes |
| Part of | Data catalog |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Not written yet.
Extended help (level 3)
Not written yet.
Details (level 4)
Not written yet.
Catalog description
| Id | nde:f02600 |
| Path | relations.dataCatalog.description |
| Type | Literal |
| Values | 1..* (required, repeatable) |
| Multilingual | yes |
| Part of | Data catalog |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Not written yet.
Extended help (level 3)
Not written yet.
Details (level 4)
Not written yet.
Catalog publisher
| Id | nde:f02700 |
| Path | relations.dataCatalog.publisher |
| Type | Agent |
| Values | 1..1 (required, one value) |
| Multilingual | no |
| Identifier schemes | identifier: ORCID, VIAF, ISNI, ROR, Wikidata, GND |
| Part of | Data catalog |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Not written yet.
Extended help (level 3)
Not written yet.
Details (level 4)
Not written yet.
Catalog dataset
| Id | nde:f02800 |
| Path | relations.dataCatalog.dataset |
| Type | Url |
| Values | 1..* (required, repeatable) |
| Multilingual | no |
| UI hint | link_dataset |
| Validation | href: Starts with http:// or https:// ^https?:\/\/.+$As written in the sheet: {"href":"/^https?:\\/\\/.+$/"} |
| Part of | Data catalog |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Not written yet.
Extended help (level 3)
Not written yet.
Details (level 4)
Not written yet.
Citation
| Id | nde:f01500 |
| Path | relations.citation |
| Type | Reference |
| Values | 0..* (optional, repeatable) |
| Multilingual | yes |
| Part of | Relations |
Tooltip (level 1)
Not written yet.
Short help (level 2)
Preferred citation or bibliographic reference for this dataset.
Extended help (level 3)
Specify how you want your dataset cited in academic papers, reports, and other contexts. The value can be a free-text preferred citation string or a URI pointing to a bibliographic record. In the NDE Schema.org form this is schema:citation; in DCAT-AP it maps to dct:isReferencedBy. Providing a citation lowers the barrier for researchers to properly attribute your data.
Details (level 4)
Not written yet.