NBNL Profile Group Data Exchange Standard
Standard which describes how datasets ought to be represented to be exchanged in a FAIR way between Dutch DSOs and other parties.
- Author
-
Bart Kleijngeld
- Version
-
1.0
- Artifacts
- See also
-
Building the Data Sets :: NBNL Modellen — Modelling Guidelines, a more detailed guide for users.
Conformance
The key words "MUST", MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
For recommendations — i.e. "SHOULD (NOT)" and "(NOT) RECOMMENDED" — the principle of "comply or explain" applies: not complying is allowed but requires explaining why.
Anatomy
Each dataset MUST be encoded as an RDF dataset which contains exactly two graphs:
-
a named graph containing the data, which will be referred to as the data graph
-
the default graph containing the dataset (meta)data
The RDF dataset SHOULD be serialized as a JSON-LD document.
"@id": ..., (1)
"@type": "dcat:Dataset", (2)
(3)
"@graph": [
... (4)
]
| 1 | The IRI of the dataset. |
| 2 | The type of the dataset is dcat:Dataset. |
| 3 | Metadata about the dataset. These statements are contained in the default graph. |
| 4 | The data graph object. These statements are contained in the data graph. |
Metadata
A dataset MUST declare an IRI which dentifies it. This IRI is RECOMMENDED to be a URN wrapping a UUIDv4 using the uuid namespace.
Furthermore, a dataset MUST assert its type to be dcat:Dataset.
If the dataset type is not asserted to be dcat:Dataset, automated validation will not be able to target the data properly and yield false positive results.
|
Finally, the following metadata properties SHOULD be provided by each dataset:
| Label | IRI | Type | Allowed cardinality | Description |
|---|---|---|---|---|
Issued |
|
|
1 |
Date the dataset was issued, i.e. start of the period of its validity. |
Title |
|
|
0..1 |
Title of the dataset. |
Publisher |
|
IRI from Market Parties |
1 |
The publisher of the dataset. |
Conforms to |
|
IRI or |
0..n |
Reference standards, vocabularies or models this dataset conforms to. |
References |
|
IRI |
0..n |
Other datasets or data products this dataset references (depends on). For any non-boundary datasets this is the |
Validation
The metadata requirements have been encoded as constraints in the Dataset Metadata SHACL which can be used to automatically validate whether datasets satisfy the metadata requirements.
| SHACL validators expect graphs, not RDF datasets. When an RDF dataset is passed as data graph to validate, many validators will use its default graph. |
Appendix A: Example: Empty dataset
Here are the contents of the empty dataset example (JSON-LD):
{
"@context": {
"dcat": "http://www.w3.org/ns/dcat#",
"dcterms": "http://purl.org/dc/terms/",
"market-parties": "https://modellen.netbeheernederland.nl/controlled-vocabularies/market-parties#",
"xsd": "http://www.w3.org/2001/XMLSchema#"
},
"@id": "urn:uuid:2d3088c1-2b9a-4cbc-84fa-c0670e0e8ecc",
"@type": "dcat:Dataset",
"dcterms:title": "Low Voltage (LV) JSON-LD instance data",
"dcterms:issued": {
"@value": "2025-12-05T12:34:567Z",
"@type": "xsd:dateTime"
},
"dcterms:publisher": {
"@id": "market-parties:LIANDER"
},
"dcterms:conformsTo": [
{
"@id": "https://modellen.netbeheernederland.nl/nbnl-equipment/1.0"
},
{
"@id": "https://modellen.netbeheernederland.nl/nbnl-data-exchange/1.0"
}
],
"dcterms:references": [
{
"@id": "urn:uuid:4562ba86-b5e0-470b-8e36-dae55428d77f"
}
],
"@graph": []
}
References
-
[RFC2119] S. Bradner. 1997. Key words for use in RFCs to Indicate Requirement Levels.