ETSI GR CIM 048 V1.1.1 (2024-09)

Context Information Management (CIM); Handling of data catalogues and data services with NGSI-LD

DGR/CIM-0048

General Information

• Status: Not Published
• Technical Committee: CIM - cross-cutting Context Information Management
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Due Date: 26-Sep-2024
• Completion Date: 20-Sep-2024

Standards Content (Sample)

GROUP REPORT
Context Information Management (CIM);
Handling of data catalogues and data services with NGSI-LD
Disclaimer
The present document has been produced and approved by the cross-cutting Context Information Management (CIM) ETSI
Industry Specification Group (ISG) and represents the views of those members who participated in this ISG.
It does not necessarily represent the views of the entire ETSI membership.

2 ETSI GR CIM 048 V1.1.1 (2024-09)

Reference
DGR/CIM-0048
Keywords
API, NGSI-LD
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format on ETSI deliver.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2024.
All rights reserved.
ETSI
3 ETSI GR CIM 048 V1.1.1 (2024-09)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
Introduction . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definition of terms, symbols and abbreviations . 6
3.1 Terms . 6
3.2 Symbols . 6
3.3 Abbreviations . 6
4 DCAT-AP model for describing datasets and data services. 7
4.0 Introduction . 7
4.1 Prefixes and namespace . 8
5 DCAT-AP concepts to NGSI-LD mapping . . 8
5.0 Foreword . 8
5.1 DCAT-AP main classes . 9
5.1.0 Foreword . 9
5.1.1 Catalogue . 9
5.1.2 Dataset . 13
5.1.3 Dataset Series . 18
5.1.4 Distribution . 21
5.1.5 Data Service . 26
5.1.6 Agent . 29
5.1.7 Location . 30
5.1.8 Catalogue Record . 32
5.1.9 Catalogued Resource . 34
5.1.10 Checksum . 34
6 NGSI-LD handling of DCAT-AP Location entities . 35
7 NGSI-LD handling of DCAT-AP based entities . . 36
7.0 Foreword . 36
7.1 Creation of Data Services, Datasets and Dataset Series . 36
7.1.0 Foreword . 36
7.1.1 Data Services . 38
7.1.2 Datasets . 41
7.1.3 Dataset Series . 44
7.2 Data Services creation upon Context Source registration . 48
7.3 Handling temporal data . 50
Annex A: Mapping examples . 56
A.0 Foreword . 56
A.1 Catalogue entity . 56
A.2 Dataset entity . 59
A.3 Distribution entity . 63
A.4 Data Service entity . 65
A.5 Dataset Series entity . 67
A.6 Location entity . 68
ETSI
4 ETSI GR CIM 048 V1.1.1 (2024-09)
A.7 Catalogue Record entity . 69
A.8 @context files for DCAT-AP NGSI-LD entities . 70
Annex B: DCAT-AP Entities JSON Schemas . 74
B.0 Foreword . 74
B.1 Catalogue entity JSON Schema . 74
B.2 Dataset entity JSON Schema . 82
B.3 Dataset Series entity JSON Schema . 97
B.4 Distribution entity JSON Schema . 102
B.5 Data Service entity JSON Schema . 111
B.6 Agent entity JSON Schema . 117
B.7 Location entity JSON Schema . 119
B.8 Catalogue Record entity JSON Schema . 120
B.9 Checksum entity JSON Schema . 125
Annex C: Change history . 127
History . 128

ETSI
5 ETSI GR CIM 048 V1.1.1 (2024-09)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (https://ipr.etsi.org/).
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its

Members. 3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and of the 3GPP
Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the ®
oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This Group Report (GR) has been produced by ETSI Industry Specification Group (ISG) cross-cutting Context
Information Management (CIM).
Modal verbs terminology
In the present document "should", "should not", "may", "need not", "will", "will not", "can" and "cannot" are to be
interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
Introduction
The DCAT Application Profile (DCAT-AP) is a specification based on World Wide Web Consortium's Data Catalog
vocabulary (DCAT) for describing public sector and other open datasets in Europe. Its basic use case is to enable a
cross-data portal search for datasets and make public sector data better searchable across borders and sectors. The
present document proposes a mapping to enrich NGSI-LD datasets with metadata aligned with DCAT/DCAT-AP
definitions.
ETSI
6 ETSI GR CIM 048 V1.1.1 (2024-09)
1 Scope
The present document aims at recommending an approach to encode dataset and data services metadata within an
NGSI-LD format using Data Catalog Vocabulary (DCAT) and its Application Profile (DCAT-AP) representation.
2 References
2.1 Normative references
Normative references are not applicable in the present document.
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long-term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area. ®
[i.1] W3C Recommendation 22 August 2024: "Data Catalog Vocabulary (DCAT) - Version 3".
[i.2] SEMIC community: "DCAT-AP 3.0", 14 June 2024.
NOTE: See also https://joinup.ec.europa.eu/collection/semic-support-centre/solution/dcat-application-profile-
data-portals-europe/release/300.
[i.3] ETSI GS CIM 009 (V1.8.1): "Context Information Management (CIM); NGSI-LD API".
3 Definition of terms, symbols and abbreviations
3.1 Terms
Void.
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
API Application Programming Interface
DCAT Data CATalog vocabulary
DCAT-AP DCAT - Application Profile
DOI Digital Object Identifier
ELI European Legislation Identifier
ETSI European Telecommunications Standards Institute
EU European Union
ETSI
7 ETSI GR CIM 048 V1.1.1 (2024-09)
EZID Identifiers made easy
HTTP HyperText Transfer Protocol
IANA Internet Assigned Numbers Authority
IRI Internationalized Resource Identifier
ISG CIM Industry Specification Group on cross-cutting Context Information Management
JSON JavaScript Object Notation
LD Linked Data
MAST Mikulski Archive for Space Telescopes
NAL Named Authority Lists
NGSI Next Generation Service Interfaces
NGSI-LD Next Generation Service Interface - Linked Data
ODRL Open Digital Rights Language
OGC Open Geospatial Consortium
PROV-O The PROV Ontology
RDF Resource Description Framework
TB Technical Board
URI Uniform Resource Identifier
URL Uniform Resource Locator ®
Permanent Identifier
W3ID W3C
WFS Web Feature Service
XML eXtensible Markup Language
4 DCAT-AP model for describing datasets and data
services
4.0 Introduction
The exponential number of published datasets creates an ever-increasing and more complex data environment for a user
to navigate. Data on its own, without contextual information or links to other similar sources, often proves difficult to
analyse or interpret.
In Europe, a developing open government data ecosystem is employing various technologies and platforms to foster
both data publication and data usability. A common metadata standard, the DCAT-AP specification, serves as the
universal language amidst this otherwise fragmented environment. This standard-based approach fosters the subsidiarity
principle, empowering open data portal owners to select platforms and internal structures tailored to their needs.
Nevertheless, these owners are required to furnish DCAT-AP compliant metadata exports for their stored datasets.
"Data Catalog Vocabulary (DCAT) is a Resource Description Framework (RDF) vocabulary designed to facilitate
interoperability between data catalogs published on the Web" [i.1]. DCAT is meant for the description of datasets and
data services using a standard model and vocabulary. DCAT provides RDF classes and properties to allow datasets and
data services to be described and included in a catalogue. This can increase the discoverability of datasets and data
services. It also enables having a decentralized approach to publishing and discovering data catalogues.
Furthermore, the DCAT vocabulary can be extended by adding classes and properties for metadata fields not covered in
the DCAT specification. Each of these new specifications constitutes a DCAT profile, i.e. a named set of constraints
based on DCAT. In fact, there are already a number of profiles that have been created to extend it for application in data
catalogues in different domains.
"DCAT-AP is a DCAT profile for sharing information about catalogues containing datasets and data services
descriptions in Europe" [i.2]. This Application Profile provides a minimal common basis within Europe to share
datasets and data services cross-border and cross-domain.
ETSI
8 ETSI GR CIM 048 V1.1.1 (2024-09)
In this respect, an important clarification that has to be done to correctly understand the scope of DCAT-AP is that data
described in a catalogue can come in many formats, ranging from spreadsheets, through XML and RDF to various
specialized formats. DCAT does not make any assumptions about these serialization formats of the datasets but it does
distinguish between the abstract dataset and its different manifestations or distributions. Thus, it is important to
differentiate between the dataset (i.e. the entities containing the context information, for example, temperature,
humidity, etc.) and the dataset description (i.e. the entities containing the metadata that describes which entities
compose the dataset, for example, Catalogue, Dataset, DataService, Distribution, etc.). DCAT-AP's scope is on the
dataset description (i.e. the metadata associated to the actual data).
Thus, the main classes in DCAT-AP are thus the classes Catalogue, Dataset, Distribution and Data Service, which can
be combined for the description of each catalogue as necessary, usually as a mixture of datasets and data services. In the
most recent version of the DCAT-AP specification, dataset series are introduced to further organise the datasets within a
catalogue. DCAT-AP provides a plethora of properties, vocabularies and guidelines to extensively express information
about Open Data.
In this sense, it is important to highlight that within the DCAT-AP specification the term Entities is actually employed
to define the classes that can be leveraged to describe a catalogue and the datasets and/or data services contained in it.
However, the present document is referring to them using the term Classes in order to not conflict with the concept of
Entity that is used in the ETSI ISG CIM NGSI-LD standard [i.3] when specifying the mapping between DCAT-AP
Entities (also known as DCAT-AP Classes) and the respective NGSI-LD Entities.
4.1 Prefixes and namespace
For the purposes of the present document, the following prefixes apply:
adms http://www.w3.org/ns/adms#
dcat http://www.w3.org/ns/dcat#
dcatap http://data.europa.eu/r5r/
dct http://purl.org/dc/terms/
foaf http://xmlns.com/foaf/0.1/
locn http://www.w3.org/ns/locn#
odrl http://www.w3.org/ns/odrl/2/
owl http://www.w3.org/2002/07/owl#
prov http://www.w3.org/ns/prov#
rdfs http://www.w3.org/2000/01/rdf-schema#
skos http://www.w3.org/2004/02/skos/core#
spdx http://spdx.org/rdf/terms#
vcard http://www.w3.org/2006/vcard/ns#
5 DCAT-AP concepts to NGSI-LD mapping
5.0 Foreword
This clause introduces the rules for describing DCAT-AP classes using NGSI-LD.
The objective is to be able to describe the metadata related to NGSI-LD datasets (i.e. context information available
through an NGSI-LD Context Broker) using the conceptual classes defined in the DCAT-AP model.
ETSI
9 ETSI GR CIM 048 V1.1.1 (2024-09)
5.1 DCAT-AP main classes
5.1.0 Foreword
First the key classes from the DCAT-AP model are mapped into an NGSI-LD data model.
5.1.1 Catalogue
Figure 1 shows the attributes and class hierarchy for the main DCAT-AP class, the Catalogue class.

Figure 1: Attributes and class hierarchy for the Catalogue class
This class is meant for describing a catalogue or repository that hosts the Datasets or Data Services being described. It
has the following properties: applicableLegislation, catalogue, creator, dataset, description, geographicalCoverage,
hasPart, homepage, language, licence, modificationDate, publisher, record, releaseDate, rights, service,
temporalCoverage, themes, and title.
Table 1 summarizes these properties as on which type of NGSI-LD property they are mapped into, its description and
usage recommendation, its cardinality and the range for each of them.
ETSI
10 ETSI GR CIM 048 V1.1.1 (2024-09)
Table 1: Details on the Catalogue entities' properties
Property NGSI-LD type Description and Usage Card Range
applicableLegislation
Property The legislation that mandates the creation 0.* eli:LegalResource
or management of the Catalogue.
catalogue Relationship A catalogue whose contents are of interest 0.* dcat:Catalogue
in the context of this catalogue.
creator Relationship An entity responsible for the creation of the 0.1 foaf:Agent
catalogue.
dataset Relationship A Dataset that is part of the Catalogue. As 0.* dcat:Dataset
empty Catalogues are usually indications of
problems, this property should be combined
with the property service to implement an
empty Catalogue check.
description Property A free-text account of the Catalogue. This 1.* rdfs:Literal
property can be repeated for parallel
language versions of the description.
geographicalCoverage Relationship A geographical area covered by the 0.* dct:Location
Catalogue. It can be represented using a
controlled vocabulary or with geographic
coordinates. The EU Vocabularies Name
Authority Lists have to be used for
continents, countries and places that are in
those lists; if a particular location is not in
one of the mentioned Named Authority
Lists, Geonames URIs have to be used.
hasPart
Relationship A related Catalogue that is part of the 0.* dcat:Catalogue
described Catalogue.
homepage Property A web page that acts as the main page for 0.1 foaf:Document
the Catalogue.
language Property A language used in the textual metadata 0.* dct:LinguisticSystem
describing titles, descriptions, etc. of the
Datasets in the Catalogue. This property
can be repeated if the metadata is provided
in multiple languages. EU Vocabularies
Languages Named Authority List
(http://publications.europa.eu/resource/auth
ority/language).
license Property A licence under which the Catalogue can 0.1 dct:LicenseDocument
be used or reused.
modificationDate Property The most recent date on which the 0.1 rdfs:Literal
Catalogue was modified.
publisher
Relationship An entity (organisation) responsible for 1 foaf:Agent
making the Catalogue available.
record Relationship A Catalogue Record that is part of the 0.* dcat:CatalogueRecor
Catalogue. d
releaseDate Property The date of formal issuance (e.g. 0.1 rdfs:Literal
publication) of the Catalogue.
rights Property A statement that specifies rights associated 0.1 dct:RightsStatement
with the Catalogue.
service
Relationship A site or end-point (Data Service) that is 0.* dcat:DataService
listed in the Catalogue. As empty
Catalogues are usually indications of
problems, this property should be combined
with the property dataset to implement an
empty Catalogue check.
temporalCoverage Property A temporal period that the Catalogue 0.* dct:PeriodOfTime
covers.
ETSI
11 ETSI GR CIM 048 V1.1.1 (2024-09)
Property NGSI-LD type Description and Usage Card Range
themes Property A knowledge organization system used to 0.* skos:ConceptScheme
classify the Resources that are in the
Catalogue. This property refers to a
knowledge organization system used to
classify the Catalogue's Datasets. It needs
to have at least the value NAL:data-theme
as this is the mandatory controlled
vocabulary for dcat:theme. The values to be
used for this property are the URIs of the
concepts in the Dataset Theme Vocabulary
(http://publications.europa.eu/resource/auth
ority/data-theme).
title Property A name given to the Catalogue. This 1.* rdfs:Literal
property can be repeated for parallel
language versions of the name.

Listing 1 shows an excerpt of the schema for the NGSI-LD mapping for the DCAT-AP Catalogue class. The complete
JSON Schema can be found in Annex B.
Listing 1: Snippet of the JSON Schema for the NGSI-LD Catalogue entity
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$schemaVersion": "1.0.1",
"$id": "DCAT-AP_NGSI-LD_Mapping/Catalogue/schema.json",
"title": "Catalogue DCAT-AP",
"description": "Catalogue of datasets compliant with DCAT-AP specification version 3.0.0.",
"type": "object",
"properties": {
"type": {
"description": "Property. Model:'https://schema.org/Text'. It has to be Catalogue",
"type": "string",
"enum": ["Catalogue"]
},
"id": {
"description": " Identifier format of any NGSI entity of type Catalogue.",
"type": "string",
"minLength": 1,
"maxLength": 256,
"pattern": "^[\\w\\-\\.\\{\\}\\$\\+\\*\\[\\]`|~^@!,:\\\\]+$"
},
"applicableLegislation": {
"description": "Property. Model:'http://data.europa.eu/eli/ontology#LegalResource'. The
legislation that mandates the creation or management of the Catalog",
…
},
"catalogue": {
"description": "Relationship. Model:'http://www.w3.org/ns/dcat#Catalog'. This relationship
refers to the catalogue(s) whose contents are of interest in the context of this catalogue",
…
},
"creator": {
"description": "Relationship. Model:'http://xmlns.com/foaf/0.1/Agent'. The entities
primarily responsible for producing the catalogue",
…
},
"dataset": {…
"description": "Relationship. Model:'http://www.w3.org/ns/dcat#dataset'. This relationship
links the Catalogue with the Dataset(s) that is(are) part of the Catalogue",
…
},
"description": {
"description": "Property. Model:'http://www.w3.org/2000/01/rdf-schema#Literal'. This
property contains a free-text account of the Catalogue. This property can contain parallel
language versions of the description.",
…
},
"geographicalCoverage": {
"description": "Relationship. Model:'http://purl.org/dc/terms/Location'. This relationship
refers to a geographical area covered by the Catalogue",
…
},
ETSI
12 ETSI GR CIM 048 V1.1.1 (2024-09)
"hasPart": {
"description": "Relationship. Model:'http://www.w3.org/ns/dcat#Catalog'. This relationship
refers to a related Catalogue that is part of the described Catalogue",
…
},
"homepage": {
"description": "Property. Model:'http://xmlns.com/foaf/0.1/homepage'. This property refers
to a web page that acts as the main page for the Catalogue",
…
},
"language": {
"description": "Property. Model:'http://purl.org/dc/terms/LinguisticSystem'. This property
refers to a language used in the textual metadata describing titles, descriptions, etc. of the
Datasets in the Catalogue. This property can include multiple references if the metadata is
provided in multiple languages. DCAT-AP specification mandates the use of EU Vocabularies
Languages Named Authority List",
…
},
"license": {
"description": "Relationship. Model:'http://purl.org/dc/terms/LicenseDocument'. This
relationship links to the licence under which the Catalogue can be used or reused",
…
},
"modificationDate": {
"description": "Property. Model:'http://www.w3.org/2000/01/rdf-schema#Literal'. This
property contains the most recent date on which the Catalogue was modified",
…
},
"publisher": {
"description": "Relationship. Model:'http://xmlns.com/foaf/0.1/#term_Agent'. This
relationship links to an entity (organisation) responsible for making the Catalogue available",
…
},
"record": {
"description": "Relationship. Model:'http://www.w3.org/ns/dcat#CatalogRecord'. This
relationship refers to the Catalogue Record(s) that is(are) part of the Catalogue",
…
},
"releaseDate": {
"description": "Property. Model:'http://www.w3.org/2000/01/rdf-schema#Literal'. This
property contains the date of formal issuance (e.g., publication) of the Catalogue",
…
},
"rights": {
"description": "Property. Model:'http://purl.org/dc/terms/RightsStatement'. This property
refers to a statement that specifies rights associated with the Catalogue. DCAT-AP specification
mandates the use of Access Rights Named Authority List vocabulary",
…
},
"service": {
"description": "Relationship. Model:'http://www.w3.org/ns/dcat#DataService'. This
relationship refers to the site(s) or end-point(s) (Data Service) that is(are) listed in the
Catalogue",
…
},
"temporalCoverage": {
"description": "Property. Model:'http://purl.org/dc/terms/PeriodOfTime'. This property
refers to the temporal period that the Catalogue covers",
…
},
"themes": {
"description": "Property. Model:'http://www.w3.org/2004/02/skos/core#ConceptScheme'. This
property refers to the knowledge organization system(s) used to classify the Catalogue's Datasets.
DCAT-AP specification mandates the use of Dataset Theme Vocabulary",
…
},
"title": {
"description": "Property. Model:'http://www.w3.org/2000/01/rdf-schema#Literal'. This
property contains a name given to the Catalogue. This property can contain parallel language
versions of the title",
…
},
"@context": {
"type": "array"
}
},
"required": [
"id",
ETSI
13 ETSI GR CIM 048 V1.1.1 (2024-09)
"type",
"description",
"publisher",
"title"
]
}
Some examples of the usage of the NGSI-LD entity of type Catalogue can be found in Annex A.
5.1.2 Dataset
Figure 2 shows the attributes and class hierarchy for the DCAT-AP Dataset class.

Figure 2: Attributes and class hierarchy for the Dataset class
This class is meant for describing a conceptual entity that represents the information published. It has the following
properties: accessRights, applicableLegislation, conformsTo, contactPoint, creator, datasetDistribution, description,
documentation, frequency, geographicalcoverage, hasVersion, identifier, inSeries, isReferencedBy, keyword,
landingPage, language, modificationDate, otherIdentifier, provenance, publisher, qualifiedAttribution,
qualifiedRelation, relatedResource, releaseDate, sample, source, spatialResolution, temporalCoverage,
temporalResolution, theme, title, type, version, versionNotes, and wasGeneratedBy.
Table 2 summarizes these properties as on which type of NGSI-LD property they are mapped into, its description and
usage recommendation, its cardinality and the range for each of them.
ETSI
14 ETSI GR CIM 048 V1.1.1 (2024-09)
Table 2: Details on the Dataset entities' properties
Property NGSI-LD type Description and Usage Card. Range
accessRights
Property Information that indicates whether the 0.1 dct:RightsStatement
Dataset is publicly accessible, has
access restrictions or is not public.
applicableLegislation Property The legislation that mandates the 0.* eli:LegalResource
creation or management of the Dataset.
conformsTo Property An implementing rule or other 0.* dct:Standard
specification.
contactPoint
Relationship Contact information that can be used 0.* vcard:Kind
for sending comments about the
Dataset.
creator Relationship An entity responsible for producing the 0.* foaf:Agent
dataset.
datasetDistribution Relationship An available Distribution for the 0.* dcat:Distribution
Dataset.
description Property A free-text account of the Dataset. This 1.* rdfs:Literal
property can be repeated for parallel
language versions of the description.
documentation Property A page or document about this Dataset. 0.* foaf:Document
frequency Property The frequency at which the Dataset is 0.1 dct:Frequency
updated. EU Vocabularies Frequency
Named Authority List
(http://publications.europa.eu/resource/
authority/frequency).
geographicalCoverage Relationship A geographic region that is covered by 0.* dct:Location
the Dataset. It can be represented
using a controlled vocabulary or with
geographic coordinates. The EU
Vocabularies Name Authority Lists
have to be used for continents,
countries and places that are in those
lists; if a particular location is not in one
of the mentioned Named Authority
Lists, Geonames URIs have to be used.
hasVersion Relationship A related Dataset that is a version, 0.* dcat:Dataset
edition, or adaptation of the described
Dataset.
inSeries
Relationship A dataset series of which the dataset is 0.* dcat:DatasetSeries
part.
isReferencedBy Relationship A related resource, such as a 0.* rdfs:Resource
publication, that references, cites, or
otherwise points to the dataset.
keyword Property A keyword or tag describing the 0.* rdfs:Literal
Dataset.
landingPage
Property A web page that acts as the main page 0.* foaf:Document
for the Catalogue. It is intended to point
to a landing page at the original data
provider, not to a page on a site of a
third party, such as an aggregator.
language Property A language of the Dataset. This 0.* dct:LinguisticSystem
property can be repeated if there are
multiple languages in the Dataset. EU
Vocabularies Languages Named
Authority List
(http://publications.europa.eu/resource/
authority/language).
modificationDate Property The most recent date on which the 0.1 rdfs:Literal
Dataset was changed or modified.
otherIdentifier Property A secondary identifier of the Dataset. 0.* rdfs:Literal
Examples are DataCite, DOI, EZID or
W3ID.
provenance
Property A statement about the lineage of a 0.* dct:ProvenanceStatement
Dataset.
ETSI
15 ETSI GR CIM 048 V1.1.1 (2024-09)
Property NGSI-LD type Description and Usage Card. Range
publisher Relationship An entity (organisation) responsible for 0.1 foaf:Agent
making the Dataset available.
qualifiedAttribution Relationship An Agent having some form of 0.* dcat:Attribution
responsibility for the resource.
qualifiedRelation Relationship A description of a relationship with 0.* dcat:Relationship
another resource.
relatedResource
Relationship A related resource. 0.* rdfs:Resource
releaseDate
Property The date of formal issuance (e.g. 0.1 rdfs:Literal
publication) of the Dataset.
sample Relationship A sample distribution of the dataset. 0.* dcat:Distribution
source
Relationship A related Dataset from which the 0.* dcat:Dataset
described Dataset is derived.
spatialResolution Property The minimum spatial separation 0.* xsd:decimal
resolvable in a dataset, measured in
meters.
temporalCoverage Property A temporal period that the Dataset 0.* dcat:PeriodOfTime
covers.
temporalResolution
Property The minimum time period resolvable in 0.* xsd:duration
the dataset.
theme
Property A category of the Dataset. A Dataset 0.* skos:Concept
may be associated with multiple
themes. The values to be used for this
property are the URIs of the concepts in
the Dataset Theme Vocabulary
(http://publications.europa.eu/resource/
authority/data-theme).
title
Property A name given to the Dataset. This 1.* rdfs:Literal
property can be repeated for parallel
language versions of the name.
datasetType Property A type of the Dataset. A recommended 0.1 skos:Concept
controlled vocabulary data-type is
foreseen.
version Property The version indicator (name or 0.* rdfs:Literal
identifier) of a resource.
versionNotes Property A description of the differences 0.* rdfs:Literal
between this version and a previous
version of the Dataset. This property
can be repeated for parallel language
versions of the version notes.
wasGeneratedBy Relationship An activity that generated, or provides 0.* prov:Activity
the business context for, the creation of
the dataset.
Listing 2 shows an excerpt of the schema for the NGSI-LD mapping for the DCAT-AP Dataset class. The complete
JSON Schema can be found in Annex B.
Listing 2: Snippet of the JSON Schema for the NGSI-LD Dataset entity
{
"$schema": " https://json-schema.org/draft/2020-12/schema ",
"$schemaVersion": "1.0.1",
"$id": "DCAT-AP_NGSI-LD_Mapping/Dataset/schema.json",
"title": "Dataset DCAT-AP",
"description": "Datasets compliant with DCAT-AP specification version 3.0.0.",
"type": "object",
"properties": {
"type": {
"description": "Property. Model:'https://schema.org/Text'. It has to be Dataset",
"type": "string",
"enum": ["Dataset"]
},
"id": {
"description": " Identifier format of any NGSI entity of type Dataset.",
…
},
ETSI
16 ETSI GR CIM 048 V1.1.1 (2024-09)
"accessRights": {
"description": "Property. Model:'http://purl.org/dc/terms/RightsStatement'. This property
refers to a statement that specifies rights associated with the Dataset. The Access Rights Named
Authority List is the recommended vocabulary provided at
http://publications.europa.eu/resource/authority/access-right",
…
},
"applicableLegislation": {
"description": "Property. Model:'http://data.europa.eu/eli/ontology#LegalResource'. The
legislation that mandates the creation or management of the Dataset. It is aligned with the
ontology included in Council conclusions inviting the introduction of the European Legislation
Identifier (ELI). In this data specification the use is restricted to instances of this class that
follow the (ELI) URI guidelines.",
…
},
"conformsTo": {
"description": "Relationship. Model:'http://purl.org/dc/terms/Standard'. An implementing
rule or other specification.",
…
},
"contactPoint": {
"description": "Relationship. Model:'vcard\thttp://www.w3.org/2006/vcard/ns#Kind'. Contact
information that can be used for sending comments about the Dataset. Note that the class Kind is
the parent class for the four explicit types of vCard (Individual, Organization, Location,
Group).",
…
},
"creator": {
"description": "Relationship. Model:'http://xmlns.com/foaf/0.1/Agent'. The entities
primarily responsible for producing the dataset",
…
},
"datasetDistribution": {
"description": "Relationship. Model:'http://www.w3.org/ns/dcat#dataset'. This relationship
links to available Distribution(s) for the Dataset.",
…
},
"description": {
"description": "Property. Model:'http://www.w3.org/2000/01/rdf-schema#Literal'. This
property contains a free-text account of the Dataset. This property can be repeated for parallel
language versions of the description.",
…
},
"documentation": {
"description": "Property. Model:'http://xmlns.com/foaf/0.1/homepage'. This property refers
to a page or document about this Dataset.",
…
},
"frequency": {
"description": "Property. Model:'http://purl.org/dc/terms/Frequency'. This property refers
to the frequency at which the Dataset is updated. The EU Vocabularies Frequency Named Authority
List is the recommended vocabulary provided at
http://publications.europa.eu/resource/authority/frequency",
…
},
"geographicalCoverage": {
"description": "Relationship. Model:'http://purl.org/dc/terms/Location'. This relationship
refers to a geographical area covered by the Catalogue",
…
},
"hasVersion": {
"desc
...