ETSI TS 103 410-4 V1.1.1 (2019-05)

ETSI TS 103 410-4 V1.1.1 (2019-05)






TECHNICAL SPECIFICATION
SmartM2M;
Extension to SAREF;
Part 4: Smart Cities Domain

---------------------- Page: 1 ----------------------
2 ETSI TS 103 410-4 V1.1.1 (2019-05)



Reference
DTS/SmartM2M-103410-4-SRF4CITY
Keywords
IoT, oneM2M, ontology, SAREF, semantic,
smart city

ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
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 at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
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 2019.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
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.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 103 410-4 V1.1.1 (2019-05)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definition of terms, symbols and abbreviations . 5
3.1 Terms . 5
3.2 Symbols . 5
3.3 Abbreviations . 6
4 SAREF4CITY ontology and semantics. 6
4.1 Introduction and overview . 6
4.2 SAREF4CITY . 7
4.2.1 General Overview . 7
4.2.2 Topology . 9
4.2.3 Administrative Area . 9
4.2.4 City Object . 10
4.2.5 Event . 11
4.2.6 Measurement. 11
4.2.7 Key Performance Indicator . 12
4.2.8 Public Service . 14
4.3 Instantiating SAREF4CITY . 14
Annex A (informative): Use recommendations . 17
Annex B (informative): Bibliography . 18
History . 19


ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 103 410-4 V1.1.1 (2019-05)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is 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 IPR Policy, no investigation, 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.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Smart Machine-to-Machine
communications (SmartM2M).
The present document is part 4 of a multi-part deliverable covering SmartM2M; Extension to SAREF, as identified
below:
Part 1: "Energy Domain";
Part 2: "Environment Domain";
Part 3: "Building Domain";
Part 4: "Smart Cities Domain";
Part 5: "Industry and Manufacturing Domains";
Part 6: "Smart Agriculture and Food Chain Domain".
Modal verbs terminology
In the present document "shall", "shall not", "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.

ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 103 410-4 V1.1.1 (2019-05)
1 Scope
The present document presents SAREF4CITY, an extension of SAREF for the Smart Cities domain.
2 References
2.1 Normative 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.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference/.
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 necessary for the application of the present document.
[1] ETSI TS 103 264 (V2.1.1) (2017-03): "SmartM2M; Smart Appliances; Reference Ontology and
oneM2M Mapping".
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] ETSI TR 103 506 (V1.1.1) (2018-09): "SmartM2M; SAREF extension investigation;
Requirements for Smart Cities".
[i.2] ETSI TS 103 264 (V3.1.1): "SmartM2M; Smart Applications; Reference Ontology and oneM2M
Mapping".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the following terms apply:
ontology: formal specification of a conceptualization, used to explicit capture the semantics of a certain reality
3.2 Symbols
Void.
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 103 410-4 V1.1.1 (2019-05)
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
API Application Programming Interface
DL Description Logic
ISA² Interoperability solutions for public administrations, businesses and citizens
KPI Key Performance Indicator
OWL Web Ontology Language
OWL-DL Web Ontology Language - Description Logic
RDF Resource Description Framework
RDF-S Resource Description Framework Schema
SAREF Smart Applications REFerence ontology
SAREF4CITY SAREF extension for the Smart Cities domain
TR Technical Report
TS Technical Specification
UML Unified Modeling Language
URI Uniform Resource Identifier
W3C World Wide Web Consortium
WGS84 World Geodetic System 1984
4 SAREF4CITY ontology and semantics
4.1 Introduction and overview
The present document is a technical specification of SAREF4CITY, an extension of SAREF for the Smart Cities
domain. This extension has been created by investigating resources from potential stakeholders of the ontology, such as
standardization bodies (e.g. Open Geospatial Consortium), associations (e.g. Spanish Federation of Municipalities
2
and Provinces), IoT platforms (e.g. FIWARE) and European projects and initiatives (e.g. ISA programme) as reported
in ETSI TR 103 506 [i.1]. In addition, the use cases defined in [i.1] were also taken into account, namely:
• Use case 1: eHealth and Smart Parking
• Use case 2: Air Quality Monitoring and Mobility
• Use case 3: Street Lighting, Air Quality Monitoring and Mobility
Taking into account ontologies, data models, standards and datasets provided by the identified stakeholders, a set of
requirements were identified and grouped in the following categories: Topology, Administrative Area, City Object,
Event, Measurement, Key Performance Indicator, and Public Service. Such requirements and categories were validated
th
during the "SAREF4CITY Validation Workshop" at the IoT Week in Bilbao on the 4 of June 2018. During the
workshop, attendees validated the use cases proposed above and the list of requirements for the above-mentioned
categories. According to the feedback and outcomes of the workshop, some actions were taken such as to discard some
requirements, to eliminate duplicates, to clarify requirements, or to add new ones. The concrete decisions were reported
in ETSI TR 103 506 [i.1]. The requirements listed in such document were taken as input for the ontology development.
More precisely, the ontology conceptualization was done in a modular way in which one pattern was defined for each of
the abovementioned categories.
After the first complete implementation of the ontology, a second validation workshop, the "Towards interoperability
nd
and harmonization of Smart City models with SAREF4CITY" one, took place on the 22 of November 2018 at the
European Commission premises in Brussels. During the workshop the ontology was presented to a variety of
stakeholders from industry to academia and public administration. Apart from observations and comments on the reuse
and alignment with other ontologies, the discussion addressed more general questions like how to promote the adoption
of SAREF or which is the technological and methodological support needed to create a SAREF ecosystem of
collaborative ontologies.
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 103 410-4 V1.1.1 (2019-05)
SAREF4CITY is an OWL-DL ontology that extends SAREF and reuses six other ontologies. SAREF4CITY includes
31 classes (13 defined in SAREF4CITY and 18 reused from the SAREF, time, geosp, geo, foaf, dcterms, org, cpsv, and
time ontologies), 36 object properties (20 defined in SAREF4CITY and 16 reused from the SAREF, geosp, geo, and
cpsv ontologies) and 7 data type properties (3 defined in SAREF4CITY and 4 reused from the SAREF ontology).
SAREF4CITY focuses on extending SAREF in order to create a common core of general concepts for smart city data
oriented to the IoT field. The main idea is to identify the core components, as mentioned, that could be extended for
particular smart city subdomains, for example, for public transport.
The prefixes and namespaces used in SAREF4CITY and in the present document are listed in Table 1.
Table 1: Prefixes and namespaces used within the SAREF4CITY ontology
Prefix Namespace
s4city https://w3id.org/def/saref4city#
saref https://w3id.org/saref#
cpsv http://purl.org/vocab/cpsv#
dcterms http://purl.org/dc/terms/
foaf http://xmlns.com/foaf/0.1/
geo http://www.w3.org/2003/01/geo/wgs84_pos#
geosp http://www.opengis.net/ont/geosparql#
owl http://www.w3.org/2002/07/owl#
time http://www.w3.org/2006/time#
rdf http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs http://www.w3.org/2000/01/rdf-schema#
xsd http://www.w3.org/2001/XMLSchema#

4.2 SAREF4CITY
4.2.1 General Overview
An overview of the SAREF4CITY ontology is provided in Figure 1. For all the entities described in the present
document, it is indicated whether they are defined in the SAREF4CITY extension or elsewhere by the prefix included
before their identifier, i.e. if the element is defined in SAREF4CITY, the prefix is s4city, while if the element is
reused from another ontology it is indicated by a prefix according to Table 1.
Arrows are used to represent properties between classes and to represent some RDF, RDF-S and OWL constructs, more
precisely:
• Plain arrows with white triangles represent the rdfs:subClassOf relation between two classes. The origin
of the arrow is the class to be declared as subclass of the class at the destination of the arrow.
• Dashed arrows between two classes indicate a local restriction in the origin class, i.e. that the object property
can be instantiated between the classes in the origin and the destination of the arrow. The identifier of the
object property is indicated within the arrow.
• Dashed arrows with identifiers between stereotype signs (i.e. "<< >>") refer to OWL constructs that are
applied to some ontology elements, that is, they can be applied to classes or properties depending on the OWL
construct being used.
• Dashed arrows with no identifier are used to represent the rdf:type relation, indicating that the element in
the origin of the arrow is an instance of the class in the destination of the arrow.
Datatype properties are denoted by rectangles attached to the classes, in an UML-oriented way. Dashed boxes represent
local restrictions in the class, i.e. datatype properties that can be applied to the class they are attached to.
Individuals are denoted by rectangles in which the identifier is underlined.
Note that Figure 1 aims at showing a global overview of the main classes of SAREF4CITY and their mutual relations.
More details on the different parts of Figure 1 are provided from clause 4.2.2 to clause 4.2.8.
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 103 410-4
...