<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">SAREF4SYST: a SAREF Reference Ontology Pattern for Representing Systems and their Interconnections</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author role="corresp">
							<persName><forename type="first">Maxime</forename><surname>Lefrançois</surname></persName>
							<email>maxime.lefrancois@emse.fr</email>
							<affiliation key="aff0">
								<orgName type="department">Mines Saint-Étienne</orgName>
								<orgName type="laboratory">UMR 6158 LIMOS</orgName>
								<orgName type="institution" key="instit1">Univ Clermont Auvergne</orgName>
								<orgName type="institution" key="instit2">INP Clermont Auvergne</orgName>
								<orgName type="institution" key="instit3">CNRS</orgName>
								<address>
									<postCode>F -42023</postCode>
									<settlement>Saint-Étienne</settlement>
									<country key="FR">France</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="department">International Semantic Web Conference</orgName>
								<address>
									<addrLine>November 06</addrLine>
									<postCode>2023</postCode>
									<settlement>Athens</settlement>
									<country key="GR">Greece</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">SAREF4SYST: a SAREF Reference Ontology Pattern for Representing Systems and their Interconnections</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">72BEE80C05B0521AF7849D99E6B020EB</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T16:30+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Ontology Design Pattern</term>
					<term>SAREF</term>
					<term>Topology</term>
					<term>Systems</term>
					<term>Connections</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>This paper introduces the SAREF reference ontology pattern SAREF4SYST, which defines systems, connections between systems, and connection points to which systems can be connected. These basic concepts can be used generically to define the topology of entities of interest and can be specialised for multiple domains. SAREF4SYST has already been reused or aligned to in different domains related to cyberphysical systems, including electrical power systems, smart buildings and smart lifts, communication networks, and multiphysics simulations.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><p>The Smart Applications REFerence ontology (SAREF) <ref type="bibr" target="#b0">[1,</ref><ref type="bibr" target="#b1">2]</ref> is a reference ontology for the Internet of Things (IoT) developed by the European Telecommunication Standards Institute (ETSI) SmartM2M Technical Committee (TC) 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 the domains of energy, building, environment, smart city, industry and manufacturing, agrifood, automotive, eHealth / ageing well, wearables, water, smart lifts <ref type="bibr" target="#b2">[3,</ref><ref type="bibr" target="#b3">4,</ref><ref type="bibr" target="#b4">5,</ref><ref type="bibr" target="#b5">6,</ref><ref type="bibr" target="#b6">7,</ref><ref type="bibr" target="#b7">8,</ref><ref type="bibr" target="#b8">9,</ref><ref type="bibr" target="#b9">10,</ref><ref type="bibr" target="#b10">11,</ref><ref type="bibr" target="#b11">12,</ref><ref type="bibr" target="#b12">13]</ref>. SAREF serves as the means to connect the extensions in different domains.</p><p>SAREF and its different extensions were developed quite independently by different teams of experts, sometimes in parallel. Sometimes different modelling decisions were made, with the result that SAREF extensions having important discrepancies. TC SmartM2M started to identify ontology patterns that may be used to homogenise the structure of SAREF extensions. Specialist Task Force (STF) 653 "SAREF Patterns" aims at homogenising and facilitating the use of SAREF and existing 11 SAREF extensions by grounding them using a set of SAREF reference ontology patterns, which consist of combination of an ontological definition, and specification of how to apply it to different domains. The ultimate goal is to help ensuring a homogeneous structure of the overall SAREF ontology, speed up the development of extensions, and improve semantic interoperability.</p><p>In this paper we introduce the first such SAREF reference ontology pattern SAREF4SYST, which defines systems, connections between systems, and connection points to which systems can be connected. SAREF4SYST has been published as ETSI Technical Specification (TS) 103 548 in 2019 as part of previous STF 556 "Consolidation of SAREF and its community of users, based on the experience of the EUREKA ITEA -12004 SEAS" <ref type="bibr" target="#b13">[14]</ref>, but it has not yet been presented to the community of researchers on pattern-based ontology engineering.</p><p>The rest of this paper is organised as follows. Section 2 provides general application scenarios for the pattern. Then Section 3 overviews the ontological description of the pattern and how it may be used in different domains. Finally Section 4 discusses some of its influences and uptake.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Motivating Scenarios for SAREF4SYST</head><p>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, which is knowledge relevant for use cases in various application domains of Cyber-Physical Systems.</p><p>SAREF4SYST can be used for example to describe zones inside a building (systems), that share frontiers of different types (connections). Properties of systems are typically state variables (e.g. temperature, volume, energy, mass), while those of connection points are typically interaction capacities and flows (e.g. thermal transmittance, energy flow, matter flow, impedance).</p><p>The following paragraphs illustrate the applicability of SAREF4SYST in three different domains. Note that modeling properties of features of interest is not part of SAREF4SYST.</p><p>Power Energy. 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.</p><p>Electric power systems may be connected one to another at 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.</p><p>An Electrical connection may exist between two Electric power systems through 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 (phase 1-to-neutral, phase 2-to-neutral, phase 3-to-neutral).</p><p>Smart Building. 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. Lifts have one or more openings, and evolve in a shaft. Storeys may have openings to the shaft. Both the lift openings and the storey openings may have doors that may be in an open or closed state.</p><p>Communication networks. Smart devices contain microcontrollers with Input/Output ports and RadioFrequency (RF) communication modules of different kinds. Wired communication may be established between two devices directly, and between two or more devices through some bus. RF communication from a sender to receivers may be established at a certain radiofrequency, with each party powering its RF module at a certain level, and receivers having a relative measure of the Received Signal Strengh Indicator (RSSI) and Signal-to-Noise Ratio (SNR).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Ontological Description and Application Guidelines</head><p>SAREF4SYST consists both of a core ontology, and guidelines to create ontologies applying the SAREF4SYST ontology pattern. The core ontology is a lightweight OWL-DL ontology that defines 3 classes and 9 object properties. It uses namespace https://saref.etsi.org/saref4syst/ prefixed as s4syst: and is available as open source at https://saref.etsi.org/sources/saref4syst/ under the ETSI BSD-3 license, and is submitted as Architectural ODP on the ontologydesignpatterns.org website as http://ontologydesignpatterns.org/wiki/Submissions:SAREF4SYST.</p><p>Figure <ref type="figure" target="#fig_0">1</ref> provides a general overview of these classes and properties. In this figure, rectangles are used to denote classes. Plain arrows are used to represent Object Properties between classes. The origin of the arrow is the domain of the property, and the target of the arrow is the range 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:subSystemOf are transitive. A symbol =1 near the target of an arrow denotes a cardinality of 1. A symbol ∃ denotes a local existential restriction. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1.">Systems and sub-systems</head><p>A s4syst:System is defined as a part of the universe that is virtually isolated from the environment. The system properties are typically state variables (e.g. consumed or stored energy, agent population, temperature, volume, humidity). Figure <ref type="figure" target="#fig_1">2</ref> illustrates classes and properties that can be used to define connected systems and their sub-systems. This module reuses the PartOf ODP. A connection between two s4syst:Systems, modelled by s4syst:connectedTo, describes the potential interactions between connected s4syst:Systems. For example s4lift:canConnectToNetwork, from the SAREF extension for Smart Lifts (SAREF4LIFT <ref type="bibr" target="#b12">[13]</ref>) describes a relationship between a system and a network it can connect to. s4syst:connectedTo is symmetric. Sub-properties, however, are not necessarily symmetric, and can be defined for example to model that some matter only flows from one system to the other. For example property s4lift:connectedToEmergencyBattery links a s4lift:ElectricPowerSystem system to another that is its emergency battery.</p><p>These core entities are defined as follows:</p><p>s4syst:System. 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. s4syst:connectedTo. 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. s4syst:subSystemOf. 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.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2.">Connections between systems</head><p>A connection can be qualified using class s4syst:Connection. Figure <ref type="figure" target="#fig_2">3</ref> illustrates classes and properties that can be used to qualify connections between s4syst:Systems. These core entities are defined as follows:</p><p>s4syst:Connection. 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. s4syst:connectsSystem. Links a connection to one of the systems it connects. s4syst:connectedThrough. Links a system to one of its connections to other systems.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.3.">Connections points of systems</head><p>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.</p><p>Figure <ref type="figure" target="#fig_3">4</ref> 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, thermal transmittance).</p><p>These core entities are defined as follows:</p><p>s4syst:ConnectionPoint. 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. s4syst:connectionPointOf. Links a connection point to the one and only one system it belongs to. s4syst:connectsAt. Links a system to one of the connection points at which it connects. s4syst:connectsSystemThrough. Links a connection point to one of the connections through which it connects its system. s4syst:connectsAt. Links a connection to one of the connection points at which it connects a system.</p><p>Furthermore, the following sub-property chain axioms are defined:</p><formula xml:id="formula_0">s4syst:connectsSystem ⊑ s4syst:connectsSystemAt 𝑜 s4syst:connectionPointOf (1) s4syst:connectedThrough ⊑ s4syst:connectsAt 𝑜 s4syst:connectsSystemThrough<label>(2)</label></formula><p>These allow to infer that a connection at a connection point necessarily connects the system of that connection point (Axiom 1), and that if a connection point connects its system through a connection, then the system is connected through this connection (Axiom 2).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.4.">Applications of the SAREF4SYST Pattern</head><p>ETSI TS 103 548 <ref type="bibr" target="#b13">[14]</ref> not only describes the terms and the axioms in the SAREF4SYST ontology, but also provides many examples of how the classes and properties may be extended. In addition, it devises guidelines for applying the pattern to verticals. Applications of the SAREF4SYST pattern are subsets of ontologies that define sub-classes and/or sub-properties of the classes and properties of SAREF4SYST. In particular, extensions should preserve the connective words in the name of properties (Of, At, Through).</p><p>The label of the sub-property should use the same morpho-syntactic structure as its super-property. ([14, Clause 5.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>3.3.2])</head><p>The technical specification also guides the users in choosing the type of axioms that may be appropriate for the pattern application. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Conclusion</head><p>SAREF4SYST is the first SAREF Reference Ontology pattern. It has proven to be useful to model various types of system, connection through which these systems interact in some way, and the connection point at which these systems connect. More patterns for SAREF are currently being discussed in the context of STF 578 "SAREF Patterns", and should be described beside SAREF4SYST in a new version of ETSI TS 103 548.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: Overview of the SAREF4SYST ontology pattern (adapted from [14])</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 2 :</head><label>2</label><figDesc>Figure 2: Systems, sub-systems</figDesc><graphic coords="4,193.47,170.83,208.34,107.12" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Figure 3 :</head><label>3</label><figDesc>Figure 3: Connections between systems through which systems connect.</figDesc><graphic coords="5,193.47,143.79,208.35,145.65" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>Figure 4 :</head><label>4</label><figDesc>Figure 4: Connection points of systems, where other systems connect</figDesc><graphic coords="6,130.96,84.19,333.35,161.33" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>Figure 5 :</head><label>5</label><figDesc>Figure 5: Overview of the SAREF4LIFT classes for systems and connections (Source: [13])</figDesc><graphic coords="8,110.13,84.19,374.98,370.64" type="bitmap" /></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">https://saref.etsi.org/saref4lift/v1.1.1/example/TS103735_Clause_6_4_SLInstallation.ttl</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">https://saref.etsi.org/saref4lift/v1.1.1/example/TS103735_Clause_6_5_SLConfiguration.ttl</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgments</head><p>This work has been partly supported the ETSI Specialist Task Forces 556 "Consolidation of SAREF and its community of users, based on the experience of the EUREKA ITEA -12004 SEAS", and CoSWoT projet (grant ANR-19-CE23-0012 from Agence Nationale de la Recherche, France).</p></div>
			</div>

			<div type="annex">
<div xmlns="http://www.tei-c.org/ns/1.0"><p>A sub-property of the s4syst:connectedThrough property may have an inverse property. If defined, the English-tagged labels and comments of these two properties shall reflect this aspect. ([14, Clause 5. <ref type="bibr" target="#b2">3</ref></p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>.3.2])</head><p>A sub-class of the s4syst:System class may have an existential restriction on a sub-property of s4syst:connectedThrough to some sub-class of s4syst:Connection ([14, Clause 5.3.3.2])</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Influences and Uptake</head><p>SAREF4SYST is the result of incorporating the seas:SystemOntology ontology into SAREF, which is one of the core modules of the Smart Energy Aware Systems (SEAS) ontology <ref type="bibr" target="#b14">[15]</ref>. SAREF4SYST relaxes the SEAS Systems pattern as seas:subSystemOf was defined as a functional, and s4syst:subSystemOf is not.</p><p>The SAREF extension for Smart Lifts (SAREF4LIFT <ref type="bibr" target="#b12">[13]</ref>) is the first extension that extensively apply the SAREF4SYST pattern. Figure <ref type="figure">5</ref> illustrates how the core three classes have been specialized. SAREF4LIFT furthermore uses the SAREF4SYST patterns to define sup-properties:</p><p>Examples Smart Lift Installation 1 and Smart Lift General Configuration 2 illustrate the use of the SAREF4SYST pattern and its different classes and properties. Sub-properties of s4syst:hasSubSystem: s4lift:hasAlarmSOSSystem Sub-properties of s4syst:connectedTo: s4lift:canConnectToNetwork, s4lift:connectedToEmergencyBattery Sub-properties of s4syst:connectsAt: s4lift:hasMainPowerSupply, s4lift:hasStandardPowerSupply Sub-properties of s4syst:connectedThrough: s4lift:hasCarService Several works have closely or remotely adopted the patterns behind SAREF4SYST. The TUBES System Ontology (TSO) and the Flow System Ontology (FSO) align to SAREF4SYST for the description of flow systems in buildings. TSO aims to explicitly define the hierarchical, structural, and functional aspects of interconnected building service systems in the Architecture Engineering, and Construction (AEC) industry and their relationships to spatial entities throughout their whole life cycle. FSO aims to describe the matter and energy flow between systems and components, and the composition of such systems <ref type="bibr" target="#b15">[16,</ref><ref type="bibr" target="#b16">17]</ref>.</p><p>SAREF4SYST is used by Bjørnskov and Jradi <ref type="bibr" target="#b17">[18]</ref> to model interconnected systems in the Digital Twin of a building, and simulate its behaviour.</p><p>Roxin et. al. in <ref type="bibr" target="#b18">[19]</ref> investigates potential alignment between SAREF ontologies, including SAREF4SYST, and the Modelica system modeling language for modeling of cyber-physical systems supporting acausal connection of components governed by mathematical equations. SAREF4SYST naturally aligns to the system modeling in Modelica.</p></div>			</div>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<title level="m" type="main">The ETSI SAREF Ontology for Smart Applications: A Long Path of Development and Evolution</title>
		<author>
			<persName><forename type="first">R</forename><surname>García-Castro</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Lefrançois</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Poveda-Villalón</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Daniele</surname></persName>
		</author>
		<idno type="DOI">10.1002/9781119899457.ch7</idno>
		<imprint>
			<date type="published" when="2023">2023</date>
			<publisher>Wiley-IEEE Press</publisher>
			<biblScope unit="page" from="183" to="215" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">SmartM2M; Smart Applications; Reference Ontology and oneM2M Mapping</title>
		<author>
			<persName><surname>Etsi</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">ETSI Technical Specification</title>
		<imprint>
			<biblScope unit="volume">103</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page">264</biblScope>
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<author>
			<persName><surname>Etsi</surname></persName>
		</author>
		<idno>V1.1.2</idno>
	</analytic>
	<monogr>
		<title level="m">SmartM2M; Extension to SAREF; Part 1: Energy Domain</title>
				<imprint>
			<date type="published" when="2020">2020</date>
			<biblScope unit="volume">103</biblScope>
			<biblScope unit="page" from="410" to="411" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<author>
			<persName><surname>Etsi</surname></persName>
		</author>
		<idno>- tion 103 410-3 V1.1.2</idno>
	</analytic>
	<monogr>
		<title level="m">SmartM2M; Extension to SAREF; Part 3: Building Domain</title>
		<title level="s">ETSI Technical Specifica</title>
		<imprint>
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<author>
			<persName><surname>Etsi</surname></persName>
		</author>
		<idno>V1.1.2</idno>
	</analytic>
	<monogr>
		<title level="m">SmartM2M; Extension to SAREF; Part 2: Environment Domain</title>
				<imprint>
			<date type="published" when="2020">2020</date>
			<biblScope unit="volume">103</biblScope>
			<biblScope unit="page" from="410" to="412" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">SmartM2M; Extension to SAREF; Part 4: Smart Cities Domain</title>
		<author>
			<persName><surname>Etsi</surname></persName>
		</author>
		<idno>V1.1.2</idno>
	</analytic>
	<monogr>
		<title level="j">ETSI Technical Specification</title>
		<imprint>
			<biblScope unit="volume">103</biblScope>
			<biblScope unit="page" from="410" to="414" />
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Industry and Manufacturing Domain</title>
		<idno>V1.1.2</idno>
	</analytic>
	<monogr>
		<title level="j">ETSI, SmartM2M; Extension to SAREF; Part</title>
		<imprint>
			<biblScope unit="volume">5</biblScope>
			<biblScope unit="page" from="410" to="415" />
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
	<note>ETSI Technical Specification</note>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Part 6: Smart Agriculture and Food Chain Domains</title>
		<idno>V1.1.2</idno>
	</analytic>
	<monogr>
		<title level="j">ETSI, SmartM2M; Extension to SAREF</title>
		<imprint>
			<biblScope unit="volume">103</biblScope>
			<biblScope unit="page" from="410" to="416" />
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
	<note>ETSI Technical Specification</note>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Automotive Domain</title>
		<idno>103 410-7 V1.1.1</idno>
	</analytic>
	<monogr>
		<title level="j">ETSI, SmartM2M; Extension to SAREF; Part</title>
		<imprint>
			<biblScope unit="volume">7</biblScope>
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">SmartM2M; Extension to SAREF; Part 8: eHealth/Ageing-well Domain</title>
		<author>
			<persName><surname>Etsi</surname></persName>
		</author>
		<idno>V1.1.1</idno>
	</analytic>
	<monogr>
		<title level="j">ETSI Technical Specification</title>
		<imprint>
			<biblScope unit="volume">103</biblScope>
			<biblScope unit="page" from="410" to="418" />
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<idno>103 410-9 V1.1.1</idno>
	</analytic>
	<monogr>
		<title level="m">Wearables Domain</title>
				<imprint>
			<date type="published" when="2020">2020</date>
			<biblScope unit="volume">9</biblScope>
		</imprint>
	</monogr>
	<note>ETSI Technical Specification</note>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<idno>V1.1.1</idno>
	</analytic>
	<monogr>
		<title level="m">Water Domain</title>
				<imprint>
			<date type="published" when="2020">2020</date>
			<biblScope unit="volume">10</biblScope>
			<biblScope unit="page" from="410" to="410" />
		</imprint>
	</monogr>
	<note>ETSI Technical Specification</note>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
	</analytic>
	<monogr>
		<title level="m">Lift Domain</title>
				<imprint>
			<date type="published" when="2021">2021</date>
			<biblScope unit="volume">11</biblScope>
			<biblScope unit="page" from="410" to="411" />
		</imprint>
	</monogr>
	<note>ETSI Technical Specification</note>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">SmartM2M; SAREF consolidation with new reference ontology patterns, based on the experience from the SEAS project</title>
		<author>
			<persName><surname>Etsi</surname></persName>
		</author>
		<idno>548 V1.1.2</idno>
	</analytic>
	<monogr>
		<title level="j">ETSI Technical Specification</title>
		<imprint>
			<biblScope unit="volume">103</biblScope>
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">Planned ETSI SAREF extensions based on the W3C&amp;OGC SOSA/SSNcompatible SEAS ontology patterns</title>
		<author>
			<persName><forename type="first">M</forename><surname>Lefrançois</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Workshop on semantic interoperability and standardization in the IoT</title>
				<imprint>
			<publisher>SIS-IoT</publisher>
			<date type="published" when="2017">2017</date>
			<biblScope unit="page">11</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">An ontology to support flow system descriptions from design to operation of buildings</title>
		<author>
			<persName><forename type="first">V</forename><surname>Kukkonen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Kücükavci</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Seidenschnur</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">H</forename><surname>Rasmussen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><forename type="middle">M</forename><surname>Smith</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">A</forename><surname>Hviid</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Automation in Construction</title>
		<imprint>
			<biblScope unit="volume">134</biblScope>
			<biblScope unit="page">104067</biblScope>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">A roadmap toward a unified ontology for building service systems in the aeco industry: Tso and fso</title>
		<author>
			<persName><forename type="first">N</forename><surname>Pauen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Kukkonen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Kücükavci</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">H</forename><surname>Rasmussen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Seidenschnur</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Schlütter</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">A</forename><surname>Hviid</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Van Treeck</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">LDAC 2022</title>
				<imprint>
			<date type="published" when="2022">2022</date>
			<biblScope unit="page" from="53" to="64" />
		</imprint>
	</monogr>
	<note>CEUR-WS</note>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">An ontology-based innovative energy modeling framework for scalable and adaptable building digital twins</title>
		<author>
			<persName><forename type="first">J</forename><surname>Bjørnskov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Jradi</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Energy and Buildings</title>
		<imprint>
			<biblScope unit="volume">292</biblScope>
			<biblScope unit="page">113146</biblScope>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<analytic>
		<title level="a" type="main">Investigating potential alignments between modelica standard library and saref ontologies</title>
		<author>
			<persName><forename type="first">A</forename><surname>Roxin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Dudhee</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Vukovic</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">CIB W78-LDAC 2021</title>
				<imprint>
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
