<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-title-group>
        <journal-title>WOP</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>SAREF4SYST: a SAREF Reference Ontology Pattern for Representing Systems and their Interconnections</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Maxime Lefrançois</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Mines Saint-Étienne, Univ Clermont Auvergne, INP Clermont Auvergne</institution>
          ,
          <addr-line>CNRS, UMR 6158 LIMOS, F - 42023 Saint-Étienne</addr-line>
          <country country="FR">France</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2023</year>
      </pub-date>
      <volume>14</volume>
      <fpage>0000</fpage>
      <lpage>0001</lpage>
      <abstract>
        <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 diferent domains related to cyberphysical systems, including electrical power systems, smart buildings and smart lifts, communication networks, and multiphysics simulations.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Ontology Design Pattern</kwd>
        <kwd>SAREF</kwd>
        <kwd>Topology</kwd>
        <kwd>Systems</kwd>
        <kwd>Connections</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>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" [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ], 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 diferent domains. Finally Section 4 discusses some of its influences and uptake.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Motivating Scenarios for SAREF4SYST</title>
      <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 diferent 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 diferent
domains. Note that modeling properties of features of interest is not part of SAREF4SYST.
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 diferent 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 diferent
configurations at a three-phase bus (phase 1-to-neutral, phase 2-to-neutral, phase 3-to-neutral).
Smart Building. Buildings, Storeys, Spaces, are diferent 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 diferent 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.
Communication networks. Smart devices contain microcontrollers with Input/Output ports
and RadioFrequency (RF) communication modules of diferent 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>
    </sec>
    <sec id="sec-3">
      <title>3. Ontological Description and Application Guidelines</title>
      <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 1 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>
      <p>hasSubSystem
&lt;&lt;transitive&gt;&gt;</p>
      <p>subSystemOf
&lt;&lt;transitive&gt;&gt;
&lt;&lt;inverseOf&gt;&gt;
connectedTo
&lt;&lt;symmetric&gt;&gt;
=1
connectionPointOf
connectsAt</p>
      <p>Connection
System
&lt;&lt;inverseOf&gt;&gt;</p>
      <p>ConnectionPoint
connectedThrough</p>
      <p>∃
connectsSystem
&lt;&lt;inverseOf&gt;&gt;</p>
      <p>∃ connectsSystemThrough
connectsSystemAt
&lt;&lt;inverseOf&gt;&gt;</p>
      <sec id="sec-3-1">
        <title>3.1. Systems and sub-systems</title>
        <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 2 illustrates classes and properties that can
be used to define connected systems and their sub-systems.</p>
        <p>
          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 [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]) describes a relationship between a system and a network it can connect to.
        </p>
        <p>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>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Connections between systems</title>
        <p>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.</p>
        <p>These core entities are defined as follows:
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>
      </sec>
      <sec id="sec-3-3">
        <title>3.3. Connections points of systems</title>
        <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 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, thermal
transmittance).</p>
        <p>These core entities are defined as follows:
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>
        <p>s4syst:connectsSystem ⊑ s4syst:connectsSystemAt  s4syst:connectionPointOf
s4syst:connectedThrough ⊑ s4syst:connectsAt  s4syst:connectsSystemThrough
(1)
(2)</p>
        <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>
      </sec>
      <sec id="sec-3-4">
        <title>3.4. Applications of the SAREF4SYST Pattern</title>
        <p>
          ETSI TS 103 548 [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ] 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.3.3.2])</p>
        <p>The technical specification also guides the users in choosing the type of axioms that may be
appropriate for the pattern application.</p>
        <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.3.3.2])
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>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Influences and Uptake</title>
      <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 [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ].
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 [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]) is the first extension that extensively
apply the SAREF4SYST pattern. Figure 5 illustrates how the core three classes have been
specialized. SAREF4LIFT furthermore uses the SAREF4SYST patterns to define sup-properties:
      </p>
      <p>Examples Smart Lift Installation1 and Smart Lift General Configuration 2 illustrate the use of
the SAREF4SYST pattern and its diferent classes and properties.</p>
      <sec id="sec-4-1">
        <title>Sub-properties of s4syst:hasSubSystem: s4lift:hasAlarmSOSSystem</title>
      </sec>
      <sec id="sec-4-2">
        <title>Sub-properties of s4syst:connectedTo: s4lift:canConnectToNetwork,</title>
        <p>s4lift:connectedToEmergencyBattery</p>
      </sec>
      <sec id="sec-4-3">
        <title>Sub-properties of s4syst:connectsAt: s4lift:hasMainPowerSupply,</title>
        <p>s4lift:hasStandardPowerSupply</p>
      </sec>
      <sec id="sec-4-4">
        <title>Sub-properties of s4syst:connectedThrough: s4lift:hasCarService</title>
        <p>Several works have closely or remotely adopted the patterns behind SAREF4SYST.</p>
        <p>
          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
lfow between systems and components, and the composition of such systems [
          <xref ref-type="bibr" rid="ref16 ref17">16, 17</xref>
          ].
        </p>
        <p>
          SAREF4SYST is used by Bjørnskov and Jradi [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ] to model interconnected systems in the
Digital Twin of a building, and simulate its behaviour.
        </p>
        <p>
          Roxin et. al. in [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ] 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.
1https://saref.etsi.org/saref4lift/v1.1.1/example/TS103735_Clause_6_4_SLInstallation.ttl
2https://saref.etsi.org/saref4lift/v1.1.1/example/TS103735_Clause_6_5_SLConfiguration.ttl
        </p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Conclusion</title>
      <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>
    </sec>
    <sec id="sec-6">
      <title>Acknowledgments</title>
      <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>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>R.</given-names>
            <surname>García-Castro</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Lefrançois</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Poveda-Villalón</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Daniele</surname>
          </string-name>
          ,
          <article-title>The ETSI SAREF Ontology for Smart Applications: A Long Path of Development and Evolution</article-title>
          , Wiley-IEEE Press,
          <year>2023</year>
          , pp.
          <fpage>183</fpage>
          -
          <lpage>215</lpage>
          . doi:
          <volume>10</volume>
          .1002/9781119899457.ch7.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>ETSI</given-names>
            <surname>,</surname>
          </string-name>
          <article-title>SmartM2M; Smart Applications; Reference Ontology and</article-title>
          oneM2M Mapping,
          <source>ETSI Technical Specification 103 264 V3.1</source>
          .1.,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>ETSI</given-names>
            <surname>,</surname>
          </string-name>
          <article-title>SmartM2M; Extension to SAREF; Part 1: Energy Domain</article-title>
          ,
          <source>ETSI Technical Specification</source>
          <volume>103</volume>
          <fpage>410</fpage>
          -
          <lpage>1</lpage>
          V1.1.2.,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>ETSI</given-names>
            <surname>,</surname>
          </string-name>
          <article-title>SmartM2M; Extension to SAREF; Part 3: Building Domain</article-title>
          ,
          <source>ETSI Technical Specification</source>
          <volume>103</volume>
          <fpage>410</fpage>
          -
          <lpage>3</lpage>
          V1.1.2.,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>ETSI</given-names>
            <surname>,</surname>
          </string-name>
          <article-title>SmartM2M; Extension to SAREF; Part 2: Environment Domain</article-title>
          ,
          <source>ETSI Technical Specification</source>
          <volume>103</volume>
          <fpage>410</fpage>
          -
          <lpage>2</lpage>
          V1.1.2.,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>ETSI</given-names>
            <surname>,</surname>
          </string-name>
          <article-title>SmartM2M; Extension to SAREF; Part 4: Smart Cities Domain</article-title>
          ,
          <source>ETSI Technical Specification</source>
          <volume>103</volume>
          <fpage>410</fpage>
          -
          <lpage>4</lpage>
          V1.1.2.,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>ETSI</given-names>
            <surname>,</surname>
          </string-name>
          <article-title>SmartM2M; Extension to SAREF; Part 5: Industry and Manufacturing Domain</article-title>
          ,
          <source>ETSI Technical Specification</source>
          <volume>103</volume>
          <fpage>410</fpage>
          -
          <lpage>5</lpage>
          V1.1.2.,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>ETSI</given-names>
            <surname>,</surname>
          </string-name>
          <article-title>SmartM2M; Extension to SAREF; Part 6: Smart Agriculture and Food Chain Domains</article-title>
          ,
          <source>ETSI Technical Specification</source>
          <volume>103</volume>
          <fpage>410</fpage>
          -
          <lpage>6</lpage>
          V1.1.2.,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>ETSI</given-names>
            <surname>,</surname>
          </string-name>
          <article-title>SmartM2M; Extension to SAREF; Part 7: Automotive Domain</article-title>
          ,
          <source>ETSI Technical Speciifcation</source>
          <volume>103</volume>
          <fpage>410</fpage>
          -
          <lpage>7</lpage>
          V1.1.1.,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10] ETSI,
          <article-title>SmartM2M; Extension to SAREF; Part 8: eHealth/Ageing-well Domain</article-title>
          ,
          <source>ETSI Technical Specification</source>
          <volume>103</volume>
          <fpage>410</fpage>
          -
          <lpage>8</lpage>
          V1.1.1.,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11] ETSI, SmartM2M; Extension to SAREF; Part 9:
          <string-name>
            <surname>Wearables</surname>
            <given-names>Domain</given-names>
          </string-name>
          ,
          <source>ETSI Technical Specification</source>
          <volume>103</volume>
          <fpage>410</fpage>
          -
          <lpage>9</lpage>
          V1.1.1.,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12] ETSI, SmartM2M; Extension to SAREF; Part 10:
          <string-name>
            <surname>Water</surname>
            <given-names>Domain</given-names>
          </string-name>
          ,
          <source>ETSI Technical Specification</source>
          <volume>103</volume>
          <fpage>410</fpage>
          -
          <lpage>10</lpage>
          V1.1.1.,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13] ETSI, SmartM2M; Extension to SAREF; Part 11:
          <string-name>
            <surname>Lift</surname>
            <given-names>Domain</given-names>
          </string-name>
          ,
          <source>ETSI Technical Specification</source>
          <volume>103</volume>
          <fpage>410</fpage>
          -
          <lpage>11</lpage>
          V1.1.1.,
          <year>2021</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14] ETSI,
          <article-title>SmartM2M; SAREF consolidation with new reference ontology patterns, based on the experience from the SEAS project</article-title>
          ,
          <source>ETSI Technical Specification 103 548 V1.1</source>
          .2.,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>M.</given-names>
            <surname>Lefrançois</surname>
          </string-name>
          ,
          <article-title>Planned ETSI SAREF extensions based on the W3C&amp;OGC SOSA/SSNcompatible SEAS ontology patterns</article-title>
          , in: Workshop on semantic interoperability
          <article-title>and standardization in the IoT</article-title>
          , SIS-IoT,
          <year>2017</year>
          , p.
          <fpage>11p</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>V.</given-names>
            <surname>Kukkonen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Kücükavci</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Seidenschnur</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. H.</given-names>
            <surname>Rasmussen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K. M.</given-names>
            <surname>Smith</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. A.</given-names>
            <surname>Hviid</surname>
          </string-name>
          ,
          <article-title>An ontology to support flow system descriptions from design to operation of buildings, Automation in Construction 134 (</article-title>
          <year>2022</year>
          )
          <fpage>104067</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>N.</given-names>
            <surname>Pauen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Kukkonen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Kücükavci</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. H.</given-names>
            <surname>Rasmussen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Seidenschnur</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Schlütter</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. A.</given-names>
            <surname>Hviid</surname>
          </string-name>
          , C. van
          <string-name>
            <surname>Treeck</surname>
          </string-name>
          ,
          <article-title>A roadmap toward a unified ontology for building service systems in the aeco industry: Tso and fso</article-title>
          ,
          <source>in: LDAC</source>
          <year>2022</year>
          ,
          <article-title>CEUR-</article-title>
          <string-name>
            <surname>WS</surname>
          </string-name>
          ,
          <year>2022</year>
          , pp.
          <fpage>53</fpage>
          -
          <lpage>64</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>J.</given-names>
            <surname>Bjørnskov</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Jradi</surname>
          </string-name>
          ,
          <article-title>An ontology-based innovative energy modeling framework for scalable and adaptable building digital twins</article-title>
          ,
          <source>Energy and Buildings</source>
          <volume>292</volume>
          (
          <year>2023</year>
          )
          <fpage>113146</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>A.</given-names>
            <surname>Roxin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Dudhee</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Vukovic</surname>
          </string-name>
          ,
          <article-title>Investigating potential alignments between modelica standard library and saref ontologies</article-title>
          ,
          <source>in: CIB W78-LDAC</source>
          <year>2021</year>
          ,
          <year>2021</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>