SIST EN 303 760 V1.1.1:2024
(Main)SmartM2M - SAREF Guidelines for IoT Semantic Interoperability - Develop, apply and evolve Smart Applications ontologies
SmartM2M - SAREF Guidelines for IoT Semantic Interoperability - Develop, apply and evolve Smart Applications ontologies
The present document gives guidance and provisions for making IoT smart applications and products interoperable at
the semantic level in compliance to the SAREF framework. It contains provisions about how to use SAREF, points to
the relevant existing Technical Reports and Technical Specifications and specifies a methodology to follow for showing
SAREF compliance according to the present SAREF EN. Further on, it describes how to contribute optionally to a new
SAREF extension (if what Users need is not yet in the SAREF framework).
The present document addresses parties involved in the development and manufacturing of IoT smart applications and
products, who might take different roles in their organization like:
• executives and product owners, who decide on to invest in a SAREF-compliant product;
• developers, who will implement a SAREF-compliant product as non-ontology experts or even ontology
experts.
Different roles imply different intentions and expectations when reading the present document according to their tasks
in the organization. The present document considers this by its implemented structure. Clause 4 provides guidance
about how to go throughout the present document in order to judge, which clauses might be essential for the special role
of the reader and which ones might be skipped.
The present document is structured as follows:
• Clauses 1 to 3 set the scene and provide references as well as definitions of terms, symbols and abbreviations,
which are used in the present document.
• Clause 4 defines the motivation and principles shared by those who are reading the present document also
serving as a checkpoint whether the reader is in the right place or not. It includes a brief reading guide as not
everyone needs to read every part of the present document, depending on the reader's role and expertise.
• Clause 5.1 provides guidance about the best practice of specifying use cases as the important basis for
deriving requirements from them.
• Clause 5.2 provides guidance/provisions about identifying core elements from the use cases defined in
clause 5.1.
• Clause 5.3 describes, how to get acquainted with SAREF.
• Clause 5.4 provides guidance /provisions about ensuring that the correct (latest) versions of the relevant
SAREF modules/patterns/extensions are selected. It illustrates, how to document the version of those SAREF
modules, which the product, application, or possible ontology extension is compliant to.
• Clause 6.1 provides guidance/provisions about the translation of data into SAREF.
• Clause 6.2 gives guidance about testing "SAREF-compliant data" in one example application of
interoperability exchange with another organization/manufacturer/brand.
• Clause 7.1 provides guidance/provisions about creating a new SAREF extension (or pattern).
• Clause 7.2 provides guidance/provisions about checking SAREF compliance of a new created SAREF
extension without going (yet) to an official standardization contribution to ETSI.
• Clause 8 describes the process of incorporating a new created SAREF extension according to clause 7 in the
official standardization process in ETSI, which will then result in a new official extension/pattern
(SAREF4abcd) under the ETSI SAREF namespace.
• Annex A contains an example of a possible use case to provide context to clause 5.1.
• Annex B contains examples of relevant core elements from use cases to provide context to clause 5.2.
• Annex C contains examples of translating data into SAREF-compliant data to provide context to clause 6.1.
• Annex D contains examples of testing SAREF data to provide context to clause 6.2.
• Annex E provides a short summary of SAREF ontology development methodology with figures and different
phases.
• Annex F provides a mechanism for the User of the present document (who is expected to be an entity involved
in the development and manufacturing of IoT smart applications and products) to give information about the
impl
SmartM2M - Smernice SAREF za semantično interoperabilnost IoT - Razvoj, uporaba in prenos ontologij za pametne aplikacije
Ta dokument podaja smernice in določbe za interoperabilnost pametnih aplikacij in izdelkov interneta stvari (IoT) na semantični ravni v skladu z okvirom SAREF. Vsebuje določbe o uporabi ontologije SAREF, opozarja na ustrezna obstoječa tehnična poročila in tehnične specifikacije ter določa metodologijo, ki jo je treba upoštevati za prikaz skladnosti SAREF v skladu s trenutnim modelom SAREF EN. V nadaljevanju je opisano, kako je mogoče prispevati k novi razširitvi SAREF (če tisto, kar uporabniki potrebujejo, še ni v okviru SAREF).
Ta dokument obravnava stranke, vključene v razvoj in proizvodnjo pametnih aplikacij in izdelkov interneta stvari, ki lahko prevzamejo različne vloge v svoji organizaciji, kot so:
• vodstveni delavci in lastniki izdelkov, ki se odločijo investirati v izdelek, skladen s SAREF;
• razvijalci, ki bodo implementirali izdelek, skladen s SAREF, kot strokovnjaki za neontologijo ali celo kot
strokovnjaki za ontologijo.
Različne vloge odražajo različne namere in pričakovanja pri branju tega dokumenta glede na njihove naloge v organizaciji. V tem dokumentu je to upoštevano z implementirano strukturo. Točka 4 vsebuje smernice o tem, kako s pregledom tega dokumenta oceniti, katere točke bi lahko bile bistvene za posebno vlogo bralca in katere se lahko preskočijo.
Ta dokument ima naslednjo strukturo:
• Točke 1 do 3 zagotavljajo splošen pregled in vsebujejo sklice ter definicije izrazov, simbolov in kratic,
ki se uporabljajo v tem dokumentu.
• Točka 4 opredeljuje motivacijo in načela, skupna tistim, ki berejo ta dokument, obenem pa lahko v njej bralec preveri, ali je na pravem mestu ali ne. Vključuje kratka navodila za branje, saj vsem ni treba prebrati vsakega dela tega dokumenta (to je odvisno od vloge in strokovnega znanja bralca).
• Točka 5.1 podaja smernice glede najboljše prakse določanja primerov uporabe, ki je pomembna osnova za izpeljavo zahtev iz njih.
• Točka 5.2 podaja smernice/določbe v zvezi s prepoznavanjem ključnih elementov iz primerov uporabe, opredeljenih v točki 5.1.
• Točka 5.3 opisuje, kako se seznaniti z ontologijo SAREF.
• Točka 5.4 podaja smernice/določbe v zvezi z izbiro pravilnih (najnovejših) različic ustreznih modulov/vzorcev/razširitev SAREF. Ponazarja, kako dokumentirati različico modulov SAREF, s katerimi je skladen izdelek, aplikacija ali morebitna razširitev ontologije.
• Točka 6.1 podaja smernice/določbe v zvezi s prevajanjem podatkov v ontologijo SAREF.
• Točka 6.2 podaja smernice za preskušanje »podatkov, skladnih s SAREF«, v enem primeru uporabe interoperabilne izmenjave z drugo organizacijo/proizvajalcem/blagovno znamko.
• Točka 7.1 podaja smernice/določbe v zvezi z ustvarjanjem nove razširitve (ali vzorca) SAREF.
• Točka 7.2 podaja smernice/določbe v zvezi s preverjanjem skladnosti novo ustvarjene razširitve SAREF
z ontologijo SAREF brez (še) uradnega prispevka k standardizaciji v ETSI.
• Točka 8 opisuje postopek vključitve novo ustvarjene razširitve SAREF v skladu s točko 7 v uradni postopek standardizacije v ETSI, posledica česar bo nova uradna razširitev/vzorec
(SAREF4abcd) v imenskem prostoru ETSI SAREF.
• Dodatek A vsebuje primer možnega primera uporabe za zagotavljanje konteksta za točko 5.1.
• Dodatek B vsebuje primere ustreznih ključnih elementov iz primerov uporabe za zagotavljanje konteksta za točko 5.2.
• Dodatek C vsebuje primere prevajanja podatkov v podatke, skladne s SAREF, za zagotavljanje konteksta za točko 6.1.
• Dodatek D vsebuje primere preskušanja podatkov SAREF za zagotavljanje konteksta za točko 6.2.
• Dodatek E vsebuje kratek povzetek metodologije razvoja ontologije SAREF s slikami in različnimi fazami.
• Dodatek F zagotavlja mehanizem za uporabnika tega dokumenta (od katerega se pričakuje, da bo subjekt, vključen v razvoj in proizvodnjo pametnih aplikacij in izdelkov interneta stvari), da poda informacije o izvajanju določb v tem dokumentu.
• Dodatek G vsebuje primer, kako izboljšati jedro ontologije SAREF z njenimi razširitvam
General Information
Standards Content (Sample)
Draft ETSI EN 303 760 V1.1.0 (2024-06)
EUROPEAN STANDARD
SmartM2M;
SAREF Guidelines for IoT Semantic Interoperability;
Develop, apply and evolve Smart Applications ontologies
2 Draft ETSI EN 303 760 V1.1.0 (2024-06)
Reference
DEN/SmartM2M-303760
Keywords
application, application layer, artificial intelligence,
interoperability, IoT, IoT platforms, methodology,
ontology, SAREF, semantic
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 - 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:
https://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
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
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.
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 Draft ETSI EN 303 760 V1.1.0 (2024-06)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
Introduction . 5
1 Scope . 7
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 9
3 Definition of terms, symbols and abbreviations . 10
3.1 Terms . 10
3.2 Symbols . 11
3.3 Abbreviations . 11
4 Motivation . 12
5 Getting started . 14
5.1 Define use cases . 14
5.2 Identify core elements . 15
5.3 Get acquainted with SAREF . 16
5.3.1 Introduction. 16
5.3.2 Get Familiar with SAREF Core . 16
5.3.3 Define the Domain of the Information that Require Structuring . 16
5.3.4 Get Familiar with the Selected SAREF Extensions . 16
5.3.5 Enhance SAREF Core with its Extensions . 17
5.4 Ensure use of correct SAREF version . 17
6 Use and instantiation of SAREF (data) . 18
6.1 Map data to SAREF-compliant data . 18
6.2 Test SAREF-compliant data . 19
7 Extension of SAREF . 20
7.1 Create a new SAREF extension . 20
7.2 Ensure compliance of an extension to SAREF . 21
8 Contribution to ETSI SAREF suite of ontologies . 21
8.1 Introduction . 21
8.2 Actors and workflow for starting the development of a new SAREF extension . 21
8.3 SAREF development framework and SAREF pipeline . 23
8.3.1 Introduction. 23
8.3.2 SAREF Project Version Specification and Documentation . 24
8.3.3 Quality Control and Requirements Verification with the SAREF Pipeline . 25
Annex A (informative): Example of a use case . 28
Annex B (informative): Example of relevant core elements from a use case . 31
Annex C (informative): Example of data translated into SAREF-compliant data. 37
Annex D (informative): Example of testing SAREF data . 39
Annex E (informative): SAREF methodology . 41
Annex F (informative): Implementation conformance statement pro forma . 42
Annex G (informative): Example of how to enhance SAREF Core with its Extensions . 45
History . 47
ETSI
4 Draft ETSI EN 303 760 V1.1.0 (2024-06)
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 draft European Standard (EN) has been produced by ETSI Technical Committee Smart Machine-to-Machine
communications (SmartM2M), and is now submitted for the combined Public Enquiry and Vote phase of the ETSI EN
Approval Procedure.
Proposed national transposition dates
Date of latest announcement of this EN (doa): 3 months after ETSI publication
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 6 months after doa
Date of withdrawal of any conflicting National Standard (dow): 6 months after doa
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
5 Draft ETSI EN 303 760 V1.1.0 (2024-06)
Introduction
Fragmentation of the IoT ecosystem in terms of standardization, architectures and available technologies and IoT
service platforms targeting specific applications or application domains impede the sharing of information between the
resulting silos. An increasing number of IoT devices located in different IoT networks generate greater quantities of
data to be shared across the IoT. Therefore, more and more devices and applications need to interoperate.
Manufacturers of IoT devices are faced with many standards and protocols to choose from. Consumers invest in smart
IoT products. In order to combine products from different vendors according to their needs, consumers want to make
sure that these products are interoperable with each other.
All of this underscores the need for open and standardized interfaces for products of different brands to interoperate and
to avoid vendor-lock in. Interoperability offers the business benefit, to unlock new added value services for consumers
from data integration, while manufacturers and other commercial parties can still maintain their competitive advantage
in offering their solutions (not everything needs to become open and interoperable).
In the past, interoperability used to be addressed at the technical communication level.
EXAMPLES:
- by using one agreed single data model, but nowadays there is too big fragmentation in existing data
models/protocols to choose from;
- by implementing ad-hoc translations between different data models/protocols, which turns to be very
expensive when there are so many standards/protocols that can be translated into each other.
In recent years, the interoperability challenge has been raised to the information level, where the common concepts for
all existing data models/protocols can be incorporated in an ontology (i.e. a common vo
...
EUROPEAN STANDARD
SmartM2M;
SAREF Guidelines for IoT Semantic Interoperability;
Develop, apply and evolve Smart Applications ontologies
2 ETSI EN 303 760 V1.1.1 (2024-10)
Reference
DEN/SmartM2M-303760
Keywords
application, application layer, artificial intelligence,
interoperability, IoT, IoT platforms, methodology,
ontology, SAREF, semantic
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 - 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.
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 EN 303 760 V1.1.1 (2024-10)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
Introduction . 5
1 Scope . 7
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 9
3 Definition of terms, symbols and abbreviations . 10
3.1 Terms . 10
3.2 Symbols . 11
3.3 Abbreviations . 11
4 Motivation . 12
5 Getting started . 14
5.1 Define use cases . 14
5.2 Identify core elements . 15
5.3 Get acquainted with SAREF . 16
5.3.1 Introduction. 16
5.3.2 Get Familiar with SAREF Core . 16
5.3.3 Define the Domain of the Information that Require Structuring . 16
5.3.4 Get Familiar with the Selected SAREF Extensions . 16
5.3.5 Enhance SAREF Core with its Extensions . 17
5.4 Ensure use of correct SAREF version . 17
6 Use and instantiation of SAREF (data) . 18
6.1 Map data to SAREF-compliant data . 18
6.2 Test SAREF-compliant data . 19
7 Extension of SAREF . 20
7.1 Create a new SAREF extension . 20
7.2 Ensure compliance of an extension to SAREF . 21
8 Contribution to ETSI SAREF suite of ontologies . 21
8.1 Introduction . 21
8.2 Actors and workflow for starting the development of a new SAREF extension . 21
8.3 SAREF development framework and SAREF pipeline . 23
8.3.1 Introduction. 23
8.3.2 SAREF Project Version Specification and Documentation . 24
8.3.3 Quality Control and Requirements Verification with the SAREF Pipeline . 25
Annex A (informative): Example of a use case . 28
Annex B (informative): Example of relevant core elements from a use case . 31
Annex C (informative): Example of data translated into SAREF-compliant data. 37
Annex D (informative): Example of testing SAREF data . 39
Annex E (informative): SAREF methodology . 41
Annex F (informative): Implementation conformance statement pro forma . 42
Annex G (informative): Example of how to enhance SAREF Core with its Extensions . 45
History . 47
ETSI
4 ETSI EN 303 760 V1.1.1 (2024-10)
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 European Standard (EN) has been produced by ETSI Technical Committee Smart Machine-to-Machine
communications (SmartM2M).
National transposition dates
Date of adoption of this EN: 25 September 2024
Date of latest announcement of this EN (doa): 31 December 2024
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 30 June 2025
Date of withdrawal of any conflicting National Standard (dow): 30 June 2025
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
5 ETSI EN 303 760 V1.1.1 (2024-10)
Introduction
Fragmentation of the IoT ecosystem in terms of standardization, architectures and available technologies and IoT
service platforms targeting specific applications or application domains impede the sharing of information between the
resulting silos. An increasing number of IoT devices located in different IoT networks generate greater quantities of
data to be shared across the IoT. Therefore, more and more devices and applications need to interoperate.
Manufacturers of IoT devices are faced with many standards and protocols to choose from. Consumers invest in smart
IoT products. In order to combine products from different vendors according to their needs, consumers want to make
sure that these products are interoperable with each other.
All of this underscores the need for open and standardized interfaces for products of different brands to interoperate and
to avoid vendor-lock in. Interoperability offers the business benefit, to unlock new added value services for consumers
from data integration, while manufacturers and other commercial parties can still maintain their competitive advantage
in offering their solutions (not everything needs to become open and interoperable).
In the past, interoperability used to be addressed at the technical communication level.
EXAMPLES:
- by using one agreed single data model, but nowadays there is too big fragmentation in existing data
models/protocols to choose from;
- by implementing ad-hoc translations between different data models/protocols, which turns to be very
expensive when there are so many standards/protocols that can be translated into each other.
In recent years, the interoperability challenge has been raised to the information level, where the common concepts for
all existing data models/protocols can be incorporated in an ontology (i.e. a common vocabulary). This captures the
meaning of a concept (i.e. semantics) rather than the specific data format in which the concept is encoded for data
exchange at the underlying communication layer.
The Smart Applications REFerence ontology (SAREF) developed and maintained by ETSI since 2015 provides a
mature, sustainabl
...
SLOVENSKI STANDARD
01-december-2024
SmartM2M - Smernice SAREF za semantično interoperabilnost IoT - Razvoj,
uporaba in prenos ontologij za pametne aplikacije
SmartM2M - SAREF Guidelines for IoT Semantic Interoperability - Develop, apply and
evolve Smart Applications ontologies
Ta slovenski standard je istoveten z: ETSI EN 303 760 V1.1.1 (2024-10)
ICS:
35.020 Informacijska tehnika in Information technology (IT) in
tehnologija na splošno general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EUROPEAN STANDARD
SmartM2M;
SAREF Guidelines for IoT Semantic Interoperability;
Develop, apply and evolve Smart Applications ontologies
2 ETSI EN 303 760 V1.1.1 (2024-10)
Reference
DEN/SmartM2M-303760
Keywords
application, application layer, artificial intelligence,
interoperability, IoT, IoT platforms, methodology,
ontology, SAREF, semantic
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 - 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.
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 EN 303 760 V1.1.1 (2024-10)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
Introduction . 5
1 Scope . 7
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 9
3 Definition of terms, symbols and abbreviations . 10
3.1 Terms . 10
3.2 Symbols . 11
3.3 Abbreviations . 11
4 Motivation . 12
5 Getting started . 14
5.1 Define use cases . 14
5.2 Identify core elements . 15
5.3 Get acquainted with SAREF . 16
5.3.1 Introduction. 16
5.3.2 Get Familiar with SAREF Core . 16
5.3.3 Define the Domain of the Information that Require Structuring . 16
5.3.4 Get Familiar with the Selected SAREF Extensions . 16
5.3.5 Enhance SAREF Core with its Extensions . 17
5.4 Ensure use of correct SAREF version . 17
6 Use and instantiation of SAREF (data) . 18
6.1 Map data to SAREF-compliant data . 18
6.2 Test SAREF-compliant data . 19
7 Extension of SAREF . 20
7.1 Create a new SAREF extension . 20
7.2 Ensure compliance of an extension to SAREF . 21
8 Contribution to ETSI SAREF suite of ontologies . 21
8.1 Introduction . 21
8.2 Actors and workflow for starting the development of a new SAREF extension . 21
8.3 SAREF development framework and SAREF pipeline . 23
8.3.1 Introduction. 23
8.3.2 SAREF Project Version Specification and Documentation . 24
8.3.3 Quality Control and Requirements Verification with the SAREF Pipeline . 25
Annex A (informative): Example of a use case . 28
Annex B (informative): Example of relevant core elements from a use case . 31
Annex C (informative): Example of data translated into SAREF-compliant data. 37
Annex D (informative): Example of testing SAREF data . 39
Annex E (informative): SAREF methodology . 41
Annex F (informative): Implementation conformance statement pro forma . 42
Annex G (informative): Example of how to enhance SAREF Core with its Extensions . 45
History . 47
ETSI
4 ETSI EN 303 760 V1.1.1 (2024-10)
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 European Standard (EN) has been produced by ETSI Technical Committee Smart Machine-to-Machine
communications (SmartM2M).
National transposition dates
Date of adoption of this EN: 25 September 2024
Date of latest announcement of this EN (doa): 31 December 2024
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 30 June 2025
Date of withdrawal of any conflicting National Standard (dow): 30 June 2025
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
5 ETSI EN 303 760 V1.1.1 (2024-10)
Introduction
Fragmentation of the IoT ecosystem in terms of standardization, architectures and available technologies and IoT
service platforms targeting specific applications or application domains impede the sharing of information between the
resulting silos. An increasing number of IoT devices located in different IoT networks generate greater quantities of
data to be shared across the IoT. Therefore, more and more devices and applications need to interoperate.
Manufacturers of IoT devices are faced with many standards and protocols to choose from. Consumers invest in smart
IoT products. In order to combine products from different vendors according to their needs, consumers want to make
sure that these products are interoperable with each other.
All of this underscores the need for open and standardized interfaces for products of different brands to interoperate and
to avoid vendor-lock in. Interoperability offers the business benefit, to unlock new added value services for consumers
from data integration, while manufacturers and other commercial parties can still maintain their competitive advantage
in offering their solutions (not everything needs to become open and interoperable).
In the past, interoperability used to be addressed a
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.