SAREF v3.1.1 is a reference ontology for the IoT developed by ETSI SmartM2M in close interaction with the industry. SAREF contains core concepts that are common to several IoT domains and, to be able to handle specific data elements for a certain domain, dedicated extensions of SAREF have been created, for example SAREF4ENER [i.4], SAREF4ENVI [i.5], SAREF4BLDG [i.6], and SAREF4CITY [i.7], SAREF4INMA [i.8], SAREF4AGRI [i.9]. Each domain can have one or more extensions, depending on the complexity of the domain. As a reference ontology, SAREF serves as the means to connect the extensions in different domains. The earlier document ETSI TR 103 411 [i.10] specifies the rationale and methodology used to create, publish and maintain the SAREF extensions.
The present document is the technical specification of SAREF4SYST, a generic extension of ETSI TS 103 264 SAREF [1] that defines an ontology pattern which can be instantiated for different domains. SAREF4SYST defines Systems, Connections between systems, and Connection Points at which systems may be connected. These core concepts can be used generically to define the topology of features of interest, and can be specialized for multiple domains. The topology of features of interest is highly important in many use cases. If a room holds a lighting device, and if it is adjacent with an open window to a room whose luminosity is low, then by turning on the lighting device in the former room one may expect that the luminosity in the latter room will rise.
The SAREF4SYST ontology pattern can be instantiated for different domains. For example to describe zones inside a building (systems), that share a frontier (connections). Properties of systems are typically state variables (e.g. agent population, temperature), whereas properties of connections are typically flows (e.g. heat flow).
SAREF4SYST has two main aims: on the one hand, to extend SAREF with the capability or representing general topology of systems and how they are connected or interact and, on the other hand, to exemplify how ontology patterns may help to ensure an homogeneous structure of the overall SAREF ontology and speed up the development of extensions.
SAREF4SYST consists both of a core ontology, and guidelines to create ontologies following the SAREF4SYST ontology pattern. The core ontology is a lightweight OWL-DL ontology that defines 3 classes and 9 object properties.
Use cases for ontology patterns are described extensively in ETSI TR 103 549 [i.3]. Clauses 4.2 and 4.3 extract use cases for the SAREF4SYST ontology pattern.
Use case 1: Smart Energy
The present clause illustrates how SAREF4SYST can be used to homogeneously represent knowledge that is relevant for use cases in the Smart Energy domain:
- Electric power systems can exchange electricity with other electric power systems. The electric energy can flow both ways in some cases (from the Public Grid to a Prosumer), or in only one way (from the Public Grid to a Load). Electric power systems can be made up of different sub-systems. Generic sub-types of electric power systems include producers, consumers, storage systems, transmission systems.
- Electric power systems may be connected one to another through electrical connection points. An Electric power system may have multiple connection points (Multiple Winding Transformer generally have one single primary winding with two or more secondary windings). Generic sub-types of electrical connection points include plugs, sockets, direct-current, single-phase, three-phase, connection points.
- An Electrical connection may exist between two Electric power systems at two of their respective connection points. Generic sub-types of electrical connections include Single-phase Buses, Three-phase Buses. A single-phase electric power system can be connected using different configurations at a three-phase bus (RN, SN, TN types).
Use case 2: Smart Building
The present clause illustrates how SAREF4SYST can be used to homogeneously represent knowledge that is relevant for use cases in the Smart Building domain:
- Buildings, Storeys, Spaces, are different sub-types of Zones. Zones can contain sub-zones. Zones can be adjacent or intersect with other zones.
- Two zones may share one or more connections. For example some fresh air may be created inside a storey if it has two controllable openings to the exterior at different cardinal points.
General Overview
A graphical overview of the SAREF4SYST ontology is provided in Figure 1. In such figure:
- Rectangles are used to denote Classes. The label of the rectangle is the identifier of the Class.
- Plain arrows are used to represent Object Properties between Classes. The label of the arrow is the identifier of the Object Property. The origin of the arrow is the domain Class of the property, and the target of the arrow is the range Class of the property.
- Dashed arrows with identifiers between stereotype signs (i.e. "<< >>") refer to OWL axioms that are applied to some property. Four pairs of properties are inverse one of the other; the property s4syst:connectedTo is symmetric, and properties s4syst:hasSubSystem and s4syst:hasSubSystem are transitive.
- A symbol =1 near the target of an arrow denotes that the associated property is functional. A symbol ∃ denotes a local existential restriction.

Systems and sub-systems
A s4syst:System, is defined as a part of the universe that is virtually isolated from the environment.
NOTE:
The system properties are typically state variables (e.g. consumed or stored energy, agent population, temperature, volume, humidity).
Figure 2 illustrates classes and properties that can be used to define connected systems and their sub-systems.

A system may be connected to other systems that are part of its environment. This is modelled by a property named s4syst:connectedTo, which is symmetric.
Connections between systems
A connection between two s4syst:Systems, modelled by s4syst:connectedTo, describes the potential interactions between connected s4syst:Systems. A connection can be qualified using class s4syst:Connection.
Figure 3 illustrates classes and properties that can be used to qualify connections between s4syst:Systems.

Connection Points of systems
A s4syst:System connects to other s4syst:Systems at connection points. A connection point belongs to one and only one s4syst:System, and can be described using the class s4syst:ConnectionPoint.
Figure 4 illustrates the classes and the properties that can be used to describe connection points of a s4syst:System.
One can then associate a s4syst:ConnectionPoint with properties (saref:Property) that describe it (e.g. position and speed, voltage and intensity, thermic transmission coefficient).

Ontology Reference
s4syst:Connection — Connection top Classes ToC
The class of connections between systems. This class qualifies property s4syst:connectedTo. A connection describes potential interactions between systems. Any two connected systems are connected through a connection. A connection can connect more than two systems at the same time.
- has super-classes
-
s4syst:connectsSystem some
s4syst:System
s4syst:connectsSystemAt some s4syst:ConnectionPoint - is in domain of
-
s4syst:connectsSystem
s4syst:connectsSystemAt - is in range of
-
s4syst:connectedThrough
s4syst:connectsSystemThrough - is disjoint with
-
s4syst:ConnectionPoint
s4syst:System
s4syst:ConnectionPoint — Connection Point top Classes ToC
The class of connection points of systems, at which they may be connected to other systems. This class qualifies properties s4syst:connectsSystem and s4syst:connectedThrough. A connection point belongs to exactly one system. Any system connected through a connection is connected at one of its connection points to the connection. The system of a connection point that is connected through a connection is itself connected through the connection.
- has super-classes
- s4syst:connectionPointOf exactly 1
- is in domain of
-
s4syst:connectionPointOf
s4syst:connectsSystemThrough - is in range of
-
s4syst:connectsAt
s4syst:connectsSystemAt - is disjoint with
-
s4syst:Connection
s4syst:System
s4syst:System — System top Classes ToC
The class of systems, i.e., systems virtually isolated from the environment, whose behaviour and interactions with the environment are modeled. Systems can be connected to other systems. Connected systems interact in some ways. Systems can also have subsystems. Properties of subsystems somehow contribute to the properties of the supersystem.
- is in domain of
-
s4syst:connectedThrough
s4syst:connectedTo
s4syst:connectsAt
s4syst:hasSubSystem
s4syst:subSystemOf - is in range of
-
s4syst:connectedTo
s4syst:connectionPointOf
s4syst:connectsSystem
s4syst:hasSubSystem
s4syst:subSystemOf - is disjoint with
-
s4syst:Connection
s4syst:ConnectionPoint
Object Properties
s4syst:connectedThrough — connected through top Object Properties ToC
Links a system to one of its connections to other systems.
- has domain
- s4syst:System
- has range
- s4syst:Connection
- is inverse of
-
s4syst:connectsSystem
s4syst:connectsSystem - has sub-property chains
- ( s4syst:connectsAt o s4syst:connectsSystemThrough)
s4syst:connectedTo — connected to top Object Properties ToC
Links a system to a system it is connected to. Connected systems interact in some way. The exact meaning of "interact" is defined by sub properties of s4syst:connectedTo. Property s4syst:connectedTo is symmetric. This property can be qualified using class s4syst:Connection, which connects the two systems. If there is a connection between several systems, then one may infer these systems are pairwise connected.
- has characteristics
- symmetric
- has domain
- s4syst:System
- has range
- s4syst:System
s4syst:connectionPointOf — connection point to top Object Properties ToC
Links a connection point to the one and only one system it belongs to.
- has characteristics
- functional
- has domain
- s4syst:ConnectionPoint
- has range
- s4syst:System
- is inverse of
-
s4syst:connectsAt
s4syst:connectsAt
s4syst:connectsAt — connects at top Object Properties ToC
Links a system to one of the connection points at which it connects.
- has characteristics
- inverse functional
- has domain
- s4syst:System
- has range
- s4syst:ConnectionPoint
- is inverse of
-
s4syst:connectionPointOf
s4syst:connectionPointOf
s4syst:connectsSystem — connects system top Object Properties ToC
Links a connection to one of the systems it connects.
- has domain
- s4syst:Connection
- has range
- s4syst:System
- is inverse of
-
s4syst:connectedThrough
s4syst:connectedThrough - has sub-property chains
- ( s4syst:connectsSystemAt o s4syst:connectionPointOf)
s4syst:connectsSystemAt — connects system at top Object Properties ToC
Links a connection to one of the connection points at which it connects a system.
- has domain
- s4syst:Connection
- has range
- s4syst:ConnectionPoint
- is inverse of
-
s4syst:connectsSystemThrough
s4syst:connectsSystemThrough
s4syst:connectsSystemThrough — connects system through top Object Properties ToC
Links a connection point to one of the connections through which it connects its system.
- has domain
- s4syst:ConnectionPoint
- has range
- s4syst:Connection
- is inverse of
-
s4syst:connectsSystemAt
s4syst:connectsSystemAt
s4syst:hasSubSystem — has sub system top Object Properties ToC
Links a system to one of its sub systems.
- has characteristics
- transitive
- has domain
- s4syst:System
- has range
- s4syst:System
- is inverse of
-
s4syst:subSystemOf
s4syst:subSystemOf
s4syst:subSystemOf — sub system of top Object Properties ToC
Links a system to its super system. Properties of subsystems somehow contribute to the properties of the super system. The exact meaning of "contribute is defined by sub properties of s4syst:subSystemOf. Property s4syst:subSystemOf is transitive.
- has characteristics
- transitive
- has domain
- s4syst:System
- has range
- s4syst:System
- is inverse of
-
s4syst:hasSubSystem
s4syst:hasSubSystem
References
Normative references
- [0] ETSI TS 103 548 (V1.1.2): "SmartM2M;; SAREF consolidation with new reference ontology patterns, based on the experience from the SEAS project".
- [1] ETSI TS 103 264: "SmartM2M; Smart Applications; Reference Ontology and oneM2M Mapping".
Informative references
- [i.1] M. Lefrançois, J. Kalaoja, T. Ghariani, A. Zimmerman: "The SEAS Knowledge Model", ITEA2 12004 Smart Energy Aware Systems Deliverable 2.2, January 2017.
NOTE:
Available at http://w3id.org/seas/.
- [i.2] A. Haller, K. Janowicz, S. Cox, D. Le Phuoc, K. Taylor, M. Lefrançois, R. Atkinson, R. García-Castro, J. Lieberman, C. Stadler: "Semantic Sensor Network Ontology". W3C Recommendation, 19 October 2017.
NOTE:
Available at https://www.w3.org/TR/vocab-ssn/.
- [i.3] ETSI TR 103 549: "SmartM2M; Guidelines for consolidating SAREF with new reference ontology patterns, based on the experience from the ITEA SEAS project".
- [i.4] ETSI TS 103 410-1 (V1.1.1): "SmartM2M; Smart Appliances Extension to SAREF; Part 1: Energy Domain".
- [i.5] ETSI TS 103 410-2 (V1.1.1): "SmartM2M; Smart Appliances Extension to SAREF; Part 2: Environment Domain".
- [i.6] ETSI TS 103 410-3 (V1.1.1): "SmartM2M; Smart Appliances Extension to SAREF; Part 3: Building Domain".
- [i.7] ETSI TS 103 410-4 (V1.1.1): "SmartM2M; Extension to SAREF; Part 4: Smart Cities Domain".
- [i.8] ETSI TS 103 410-5 (V1.1.1): "SmartM2M; Extension to SAREF; Part 5: Industry and Manufacturing Domains".
- [i.9] ETSI TS 103 410-6 (V1.1.1): "SmartM2M; Extension to SAREF; Part 6: Smart Agriculture and Food Chain Domain".
- [i.10] ETSI TR 103 411 (V1.1.1): "SmartM2M; Smart Appliances; SAREF extension investigation".
- [i.11] M. Lefrançois, A. Zimmermann, N. Bakerally: "A SPARQL extension for generating RDF from heterogeneous formats", In Proc. Extended Semantic Web Conference, 2017.
Acknowledgements
The editors would like to thank the ETSI SmartM2M technical committee for providing guidance and expertise.
Also, many thanks to the ETSI staff and all other current and former active Participants of the ETSI SmartM2M group for their support, technical input and suggestions that led to improvements to this ontology.
Also, special thanks goes to the ETSI SmartM2M Technical Officer Guillemin Patrick for his help.