<!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 />
    <article-meta>
      <title-group>
        <article-title>Automated Ontology Matching in the Architecture, Engineering and Construction Domain - A Case Study</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Fraunhofer Institute for Building Physics IBP, Further Stra e 250</institution>
          ,
          <addr-line>90429 Nurnberg</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Technische Hochschule Nurnberg, Further Stra e 250</institution>
          ,
          <addr-line>90429 Nurnberg</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2033</year>
      </pub-date>
      <fpage>35</fpage>
      <lpage>49</lpage>
      <abstract>
        <p>The ontology-based modelling of the built environment is deemed promising to successfully integrate disparate knowledge silos and has gained signi cant attraction in industry and academia. This interest has led to a proliferating number of ontologies and the manual de nition of schema level alignments among them is a tedious task. Hence, this paper explores the possibilities of automated ontology matching methods in this regard. This work compares manually created and automatically generated alignments of six domain ontologies to the building topology ontology. The initial ndings of this case study indicate that current state of the art ontology matching tools are in principle capable of detecting automatically correct alignments and that their is a strong need to de ne domain speci c benchmarks.</p>
      </abstract>
      <kwd-group>
        <kwd>Automated Ontology Matching Architecture Engineering Construction Facility Management Heterogeneity Building Topology Ontology</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Ontology-based modelling and associated implementations based on Semantic
Web Technologies (SWT) [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] have gained attention by academia and
industry in the Architecture, Engineering, Construction and Facility Management
(AEC/FM) domain [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ]. A main motivation to use the technology is its
ability to successfully address the problem of integrating heterogeneous information
silos distributed across the AEC/FM domain [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>
        The spread of the technology has lead to a proliferating development of
domain ontologies (cf. reviews in [
        <xref ref-type="bibr" rid="ref23 ref25 ref7">7,23,25</xref>
        ]). This development poses the risk of
putting the bene ts of the technology at stake as the de ned ontologies
overlap and found ontological design patterns are reimplemented again and again
making a reuse di cult. 'Thus, merely using ontologies, like using XML, does
not reduce heterogeneity: it raises heterogeneity problems to a higher level.' [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
The principle of ontology reuse stipulated in well-known ontology engineering
methodologies [
        <xref ref-type="bibr" rid="ref14 ref19">19,14</xref>
        ] is frequently not followed, when designing domain
ontologies in the building domain. This makes it cumbersome for potential developers
to implement applications as again a heterogeneous landscape of domain models
appears.
      </p>
      <p>
        The Building Topology Ontology (BOT), initially de ned in [
        <xref ref-type="bibr" rid="ref25 ref26">25,26</xref>
        ] and
further developed by the members of the W3C Linked Building Data Community
Group (W3C LBD CG) [
        <xref ref-type="bibr" rid="ref32">32</xref>
        ], has been proposed to de ne commonly
reoccurring design patterns in domain ontologies of the AEC/FM domain. These design
patterns then can be reused by developers in their respective domains through
extending from BOT [
        <xref ref-type="bibr" rid="ref29">29</xref>
        ]. Following this approach, intrinsically a domain wide
interoperability can be ensured.
      </p>
      <p>
        The successful manual alignment of ve domain ontologies
(SAREF4Building [
        <xref ref-type="bibr" rid="ref24">24</xref>
        ], BRICK [
        <xref ref-type="bibr" rid="ref3 ref4">3,4</xref>
        ], DogOnt [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], ThinkHome [
        <xref ref-type="bibr" rid="ref27">27</xref>
        ], ifcOWL [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ]) to BOT
is presented in an initial e ort in Schneider [
        <xref ref-type="bibr" rid="ref29">29</xref>
        ]. The schema level alignment
of ontologies is a tedious task, which potentially is as challenging as ontology
engineering itself [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. There exists a strong need to use automated ontology
matching methods to automatically nd alignments [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Also ontologies tend to
evolve over time and alignments need to be updated and checked accordingly.
The analysis of the current state of the art presented in section 2 indicates that
the use of automated ontology matching methods has not been studied in depth
in the AEC/FM domain so far.
      </p>
      <p>
        The contributions of this paper are two fold. First, manual alignments
originally de ned in an earlier contribution [
        <xref ref-type="bibr" rid="ref29">29</xref>
        ] are revised and updated to re ect
the latest version of BOT (v0.3.0). Second, a study is conducted, where an
automated ontology matching method [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] is utilised to align the respective domain
ontologies to BOT. The generated alignments are compared to the manually
found ones.
      </p>
      <p>The remainder of this paper includes a review of existing work (Section 2)
related to the automated matching of ontologies in the AEC/FM domain. Then
in Section 3 a methodology is presented to compare manually de ned and
automated generated alignments of domain ontologies. Finally, in Section 4 revised
manual alignments are presented and the results of the comparison to
automatically generated alignments are presented in Section 5.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Related Work</title>
      <p>
        The eld of ontology matching has been around for a number of years and the
fundamentals of the technology are presented in Euzenat &amp; Shvaiko [
        <xref ref-type="bibr" rid="ref12 ref30">12,30</xref>
        ].
Speci c matching algorithms are developed actively and their performance is
evaluated yearly in benchmark tests under the supervision of the Ontology Alignment
Evaluation Initiative (OAEI), where the results of the most recent event are
presented in Algergawy et al. [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
      </p>
      <p>A, yet limited, number of contributions, which investigate the topic of
ontology matching in the context of the AEC/FM domain exist.</p>
      <p>
        In their demand for interoperability in the smart cities domain, Costin &amp;
Eastman [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] conduct a thorough review of existing contributions in this regard.
They conclude the ontology-based modelling of the domain based on SWT
provide means to address the prevalent heterogeneity. However, as the manual
alignment of domain ontologies is a tedious task, the demand for automated ontology
matching methods is made.
      </p>
      <p>
        Otero-Cerdeira et al. [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ] investigate the use of automated ontology
matching methods in the context of smart cities. The present OntoPhil a ontology
matching technique speci cally designed for the matching of disparate
knowledge sources in the context of smart cities. Beside the cited works no further
documentation or download possibility of the OntoPhil tool has been found.
      </p>
      <p>
        Bellini et al. [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] present a system for the integration of disparate data sources
in the context of smart cities. The system is designed to handle large data
volumes and integrates them by mapping the data to the Knowledge Model
for City (KM4City) ontology. The actual mapping is undertaken manually using
the Karma Data Integration tool [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ].
      </p>
      <p>
        Gyrard et al. [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] present an approach to enrich ontology catalogues with
domain ontologies of smart cities. Their approach aims for interoperability among
applications by providing an interface, the catalogue, to developers to easily nd
and reuse existing domain ontologies. An automated update is discussed 'but a
manual checking is preferred to handle synonyms' [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ].
      </p>
      <p>
        Espinoza-Arias et al. [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] review existing ontological representations of smart
city data. No explicit mappings are de ned among the ontologies but after a
characterisation a number of reoccurring ontology design patterns are de ned.
      </p>
      <p>The presented contributions indicate that automated ontology matching
methods seem to be promising to address heterogeneity of formats and formal models.
Most work reviewed focuses on ontology matching and alignment in the domain
of smart cities. The AEC/FM domain can be seen as a sub-domain of smart cities
but it has not been discussed in detail to the best of the authors knowledge.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Methodology</title>
      <p>
        A methodology is established to evaluate and compare the manual and
automated matching of ontologies in the AEC/FM domain. In the study the de
nition of alignments between BOT [
        <xref ref-type="bibr" rid="ref25 ref26">25,26</xref>
        ] and six domain ontologies is studied
(SAREF4Building [
        <xref ref-type="bibr" rid="ref24">24</xref>
        ], BRICK [
        <xref ref-type="bibr" rid="ref3 ref4">3,4</xref>
        ], DogOnt [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], ThinkHome [
        <xref ref-type="bibr" rid="ref27">27</xref>
        ], ifcOWL [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ],
DERI Room [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]). The namespaces used in the work are reported in Table 1. In
particular the following steps are conducted:
1. Manual de nition of alignments on class and object property level;
2. Use of the AgreementMakerLight [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] tool to automatically generate
alignments;
3. Comparison of the obtained manual and automatically created alignments.
      </p>
      <p>
        The manual de nition of alignments is an extension and revision of the work
documented in an earlier contribution [
        <xref ref-type="bibr" rid="ref29">29</xref>
        ]. The step involves the retrieval and
local storage of the most recent version of all involved ontologies. The de nition
of an alignment ontology which performs a full import (owl:import) of BOT and
the respective domain ontology. Finally, alignments are de ned manually through
the use of the Protege ontology editor [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. The de ned alignments mainly use
subsumption for alignment. This has been found bene cial in discussion within
the W3C LBD CG as the semantic implied by subsumption are less rigid as
compared the de nition of equivalences. Equivalence (e.g.
owl:equivalenceClass) implies that all statements on one class also are true for the other, which
might not always be the case. An OWL DL reasoner is invoked on the resulting
alignment ontology (Pellet [
        <xref ref-type="bibr" rid="ref31">31</xref>
        ]) to ensure the consistency. The de ned ontologies
are published in an online repository3.
      </p>
      <p>
        A large number of tools and associated algorithms exist to perform
automated ontology matching [
        <xref ref-type="bibr" rid="ref1 ref12 ref21">12,21,1</xref>
        ]. An an initial attempt here the
AgreementMakerLight tool [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] is chosen from an extensive list of available tools4. The
usage of the AgreementMakerLight tool has been found intuitive and the tool is
available open-source in as a compiled java library from a web repository. The
tool is used with default settings and BOT is always used as the source ontology.
4.1
      </p>
      <sec id="sec-3-1">
        <title>SAREF Extension for Building Devices</title>
        <p>
          The SAREF Extension for Building Devices (SAREF4Building) [
          <xref ref-type="bibr" rid="ref24">24</xref>
          ] ontology
is an ontology to extend the SAREF ontology [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ] into the buildings domain.
A description of the ontology can be found in its documentation and reviews
[
          <xref ref-type="bibr" rid="ref23 ref24 ref29">24,23,29</xref>
          ].
        </p>
        <p>The de ned alignments are reported in Table 2 and the rationale behind is
described in the following paragraph.</p>
        <p>SAREF4Building describes the concepts of s4bldg:Buildings and
s4bldg:Spaces, which can be de ned as specialisations of bot:Building and bot:Space.
As the focus of SAREF and its extension to the buildings domain focus on the
description of tangible devices, s4bldg:PhysicalObjects, s4bldg:Sensors and
s4bldg:Actuators qualify as bot:Elements, which again has been formalised
through subsumption.</p>
        <p>
          The, compared to the last iteration of alignments [
          <xref ref-type="bibr" rid="ref29">29</xref>
          ], newly introduced
high level relationships bot:containsZone and bot:containsElement re ect
on a high level the semantics of s4bldg:hasSpace and s4bldg:contains
object properties of SAREF4Building and are aligned through de ning them as
subproperties of the respective BOT object properties (see Table 2).
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>BRICK Uniform Schema for Representing Metadata in</title>
      </sec>
      <sec id="sec-3-3">
        <title>Buildings</title>
        <p>
          The BRICK ontology [
          <xref ref-type="bibr" rid="ref3 ref4">3,4</xref>
          ] is an ontology, which focuses on the description of
building management systems and their domain concepts such as data points,
HVAC equipment and the topology of the building. The de ned and revised
alignments are reported in Table 3 and explained in the following.
        </p>
        <p>The alignments are de ned by using subsumption on class and object
property level. A brick:Location is considered as a specialisation of bot:Zone as
it is used as a super-concept from other concepts describing topological
aspects of a building. Hence, the alignment of brick:Building, brick:Floor,
brick:Basement, brick:Outside, brick:Room, brick:Space and brick:Wing
is straightforward. A brick:Zone is considered to be a specialisation of a
bot:Space as BRICK uses this concepts to refer to HVAC zones often used in the
context of the control of a building. The brick:Equipment of a building and
brick:Points are considered as specialisations of bot:Element. In particular
this holds for the concept brick:Point as BRICK describes for instance sensors
or meters as tangible objects, which are located in some zone or space.</p>
        <p>
          The semantics of brick:contains can be directly mapped to
bot:containsElement and, hence, a specialisation is de ned. Interesting is the
brick:hasPart object property de ned in BRICK. The property can be used to relate
brick:Equipment to brick:Sensors, brick:Equipment to brick:Equipment or
brick:Locations to brick:Locations [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ], hence, it quali es for an extension of
bot:containsElement, bot:containsZone and bot:hasSubElement as de ned.
Similar semantics apply for the brick:hasPoint object property, which can be
specialised from bot:containsZone and bot:containsElement as it allows to
relate brick:Equipment to brick:Sensors and brick:Locations to
brick:Sensors.
4.3
        </p>
      </sec>
      <sec id="sec-3-4">
        <title>DogOnt - Ontology Modeling for Intelligent Domotic</title>
      </sec>
      <sec id="sec-3-5">
        <title>Environments</title>
        <p>
          DogOnt ontology is an ontology to formally describe the domain of domotic
devices in home appliances. It is initially described in Bonino &amp; Corno [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ] but
has since undergone many revision and extensions. The most recent version as
of writing (4.0.1) can be obtained from a remote repository5.
        </p>
        <p>A number of concepts of the ontology can be specialised from BOT. The
de ned alignments are reported in Table 4. In particular the ontology describes
the concepts dogont:Building, dogont:Storey, dogont:Room, which can be
mapped to respective BOT concepts. The general concept of
dogont:Environment can be seen of a generalisation of the bot:Zone concept as de ned.
Interesting is the de nition of the concepts dogont:Ceiling and dogont:Floor as
areas bounding a room. This complies to the de nition of bot:Interface and
can be aligned by specialisation. To re ect the di erent semantics the di erent
sub-concepts of dogont:UnControllable need to be separately specialised (e.g.
dogont:Furniture).</p>
        <p>In terms of aligning object properties a number of specialisation can be
found. The object property dogont:contains is used in DogOnt to describe
that some tangible object is fully contained in a dogont:BuildingEnviroment.
Essentially this is the semantics of bot:containsElement. The object properties
dogont:belongsTo and dogont:hasWallOpening allow to describe composition
of classes which specialised from bot:Element. Hence, they are specialised from
bot:hasSubElement, potentially its inverse where needed. Interesting are also
the dogont:floorOf and dogont:ceilingOf object properties, which qualify as
specialisation of bot:interfaceOf together with the specialisation of
dogont:Ceiling and dogont:Floor as bot:Interface as de ned above.
4.4</p>
      </sec>
      <sec id="sec-3-6">
        <title>ThinkHome Ontology</title>
        <p>
          The ThinkHome ontologies [
          <xref ref-type="bibr" rid="ref27">27</xref>
          ] are a family of ontologies to describe smart home
systems formally and link this with adjacent domains. A detailed description of
the ontologies can be found in its documentation and reviews [
          <xref ref-type="bibr" rid="ref22 ref27 ref28">27,22,28</xref>
          ].
Alignments are de ned to the BuildingOntology of the family of ontologies, which has
been derived from the gbXML format6.
        </p>
        <p>The common concepts of th:Campus, th:Building, th:BuildingStorey,
th:Opening, th:Space, th:Zone and th:Equipment can be specialised directly
from BOT. Interesting are the concepts th:Construction, th:Layer,
th:Material, which refer to di erent layers of a wall needed for instance in building
performance simulation. The semantics comply to bot:Interface and hence a
specialisation is de ned.</p>
        <p>A number of object properties are de ned in ThinkHome, which describe
the containment of an element in a zone, a zone in a zone or composition of
5 https://github.com/iot-ontologies/dogont, Last accessed: 20 May 2019
6 http://www.gbxml.org/, Last accessed: 20 May 2019</p>
        <p>Subject
bot:Building
bot:Storey
bot:Space
dog:Environment
bot:Zone
bot:Space
bot:Zone
bot:Zone
bot:Element
bot:Element
bot:Element
bot:Element
bot:Element
bot:Interface
bot:Interface
rdfs:subPropertyOf bot:containsElement
rdfs:subPropertyOf owl:inverseOf bot:hasSubElement
rdfs:subPropertyOf bot:interfaceOf
rdfs:subPropertyOf bot:interfaceOf
rdfs:subPropertyOf bot:adjacentElement
rdfs:subPropertyOf bot:hasSubElement
elements. Hence, the object properties are specialised from the respective object
properties in BOT as reported in Table 5.</p>
      </sec>
      <sec id="sec-3-7">
        <title>Industry Foundation Classes 4 Addendum 2</title>
        <p>
          No new or revised alignments to the OWL version of the Industry Foundation
Classes (IFC) [
          <xref ref-type="bibr" rid="ref17 ref22">17,22</xref>
          ] from BOT are found in this work in comparison to the
initial mapping [
          <xref ref-type="bibr" rid="ref29">29</xref>
          ]. However, the alignments are changed to subsumption as
mentioned above.
4.6
        </p>
      </sec>
      <sec id="sec-3-8">
        <title>DERI Room Ontology</title>
        <p>
          The DERI Room ontology [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ] has been added to this study as is represents
a light weight vocabulary, compared to the other ontologies, dedicated to the
description of buildings. The found alignments are documented in Table 7 and
almost all classes and object properties could be specialised from BOT.
The results of the manually de ned and revised alignments are summarised in
Table 8. The respective domain ontologies are denoted and the considered version
of the ontology, if applicable. All de ned mappings are de ned in a separated
ontology le and the respective ontology is checked for consistency by invoking a
OWL DL reasoner (Pellet [
          <xref ref-type="bibr" rid="ref31">31</xref>
          ]) and looking for inconsistencies. The total number
of alignments between concepts and object properties are reported. It should be
noted that the total number does not qualify as a metric to determine if BOT
can be extended very well to the respective domain. In comparison to the last
study [
          <xref ref-type="bibr" rid="ref29">29</xref>
          ] it is interesting that the number of ontologies, where a mapping on
the object property level is possible has been signi cantly increased.
5
        </p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Automated Alignment</title>
      <p>
        As described in Section 3 a study is conducted in this work using the tool
AgreementMakerLight [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] to automatically derive ontology alignments. Figure 1
shows as an example the result reported by the tool for matching BOT and the
ThinkHome ontology.
      </p>
      <p>The tool reports the found alignments in the graphical user interface as well
as exports them in RDF format. All automatically found alignments are reported
in Table 9. The automated ontology matching tool has found from zero up to
three alignments between concepts of the respective ontologies. No alignments
between object properties are found. The reported suggested alignment is always
equivalence. One false alignment is reported mapping a bot:Space to
ifc:IfcSpaceType.</p>
      <p>
        AgreementMakerLight implements three types of primary matching
algorithms: a lexical matcher, mediating matcher and word matcher and one
secondary type matching algorithm: a parametric string matcher [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. An in depth
treatment of the matching methods is beyond the scope of this paper. All
algorithms take as an input the two to-be-aligned ontologies. The primary matching
algorithms compare obtained terms and assert alignments if a similarity measure
exceeds a threshold with di erent complexities. Hence, it should be noted that
the chosen parameterisation of the thresholds, etc. has an impact on the results
and should be studied in more detail on a elaborated benchmark de ned for the
AEC/FM domain. In the initial experiments conducted in this study the default
suggested values are utilised.
Automated ontology matching is a well-known discipline and the topic is
researched since decades. A plethora of tools is available, see e.g. [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. In this study
only one tool has been used. A detailed study of methods and tools should be
conducted to further clarify the abilities of automated ontology matching
methods for their application in the AEC/FM domain.
      </p>
      <p>The ontologies considered in this study mainly reside from the building
automation domain. This is mainly motivated by the authors expertise and research
interest. However, other AEC/FM domains should be included in future studies
on automated ontology matching.</p>
    </sec>
    <sec id="sec-5">
      <title>Conclusion</title>
      <p>
        Within this paper manually de ned and automatically obtained alignments
between domain ontologies from the Architecture, Engineering, Construction/
Facility Management (AEC/FM) domain to the Building Topology Ontology (BOT)
[
        <xref ref-type="bibr" rid="ref25">25</xref>
        ] are compared. The manual de nition of alignments between ontologies is a
tedious task and almost as di cult as developing ontologies from scratch.
Initial experiments show that automated matching methods can support nding
alignments. The results are promising to also support not only the alignment of
domain ontologies but the revision of alignments, e.g. because of schema level
updates.
      </p>
      <p>The presented study can only be seen as a starting point and the following
open questions for future research remain:
{ There is a strong need for the de nition of a well-de ned benchmark from
AEC/FM domain, potentially including building product data, to establish
the attention of ontology matching experts;
{ Addittional sub-domains of the AEC/FM domain should be added in future
studies;
{ As ontologies evolve over time a future question is, if existing alignments can
be reused as a starting point ("hot-start") for matching methods.</p>
    </sec>
    <sec id="sec-6">
      <title>Acknowledgements</title>
      <p>This paper documents work conducted in a collaborative e ort by the W3C LBD
CG. The author gratefully acknowledges nancial support from MOEEBIUS
project, a Horizon 2020 research and innovation program under grant agreement
No. 680517 and the initiative Mittelstand 4.0 by the German Federal Ministry
for Economic A airs and Energy.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Algergawy</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cheatham</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Faria</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ferrara</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fundulaki</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          , et al.:
          <article-title>Results of the ontology alignment evaluation initiative 2018</article-title>
          .
          <source>In: Proc. of OM</source>
          . pp.
          <volume>1</volume>
          {
          <fpage>41</fpage>
          .
          <string-name>
            <surname>Monterey</surname>
          </string-name>
          , USA (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Anumba</surname>
            ,
            <given-names>C.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Issa</surname>
            ,
            <given-names>R.R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pan</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mutis</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          :
          <article-title>Ontology based information and knowledge management in construction</article-title>
          .
          <source>Construction Innovation</source>
          <volume>8</volume>
          (
          <issue>3</issue>
          ),
          <volume>218</volume>
          {
          <fpage>239</fpage>
          (
          <year>2008</year>
          ). https://doi.org/10.1108/14714170810888976
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Balaji</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bhattacharya</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fierro</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gao</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gluck</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hong</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Johansen</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Koh</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ploennigs</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Agarwal</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Berges</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Culler</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gupta</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          , Kj rgaard, M.B.,
          <string-name>
            <surname>Srivastava</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Whitehouse</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Brick: Towards a uni ed metadata schema for buildings</article-title>
          .
          <source>In: Proc. of BuildSys</source>
          . Palo Alto, USA (
          <year>2016</year>
          ). https://doi.org/10.1145/2993422.2993577
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Balaji</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bhattacharya</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fierro</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gao</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gluck</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hong</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Johansen</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Koh</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ploennigs</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Agarwal</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Berges</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Culler</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gupta</surname>
            ,
            <given-names>R.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kj</surname>
            <given-names>rgaard</given-names>
          </string-name>
          , M.B.,
          <string-name>
            <surname>Srivastava</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Whitehouse</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Brick : Metadata schema for portable smart building applications</article-title>
          .
          <source>Applied Energy</source>
          <volume>226</volume>
          ,
          <issue>1273</issue>
          {
          <fpage>1292</fpage>
          (
          <year>2018</year>
          ). https://doi.org/10.1016/j.apenergy.
          <year>2018</year>
          .
          <volume>02</volume>
          .091
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Bellini</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Benigni</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Billero</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nesi</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rauch</surname>
          </string-name>
          , N.:
          <article-title>Km4city ontology building vs data harvesting and cleaning for smart-city services</article-title>
          .
          <source>Journal of Visual Languages &amp; Computing</source>
          <volume>25</volume>
          (
          <issue>6</issue>
          ),
          <volume>827</volume>
          {
          <fpage>839</fpage>
          (
          <year>2014</year>
          ). https://doi.org/10.1016/j.jvlc.
          <year>2014</year>
          .
          <volume>10</volume>
          .023
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Bonino</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Corno</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          : DogOnt - Ontology
          <source>Modeling for Intelligent Domotic Environments. Lecture Notes in Computer Science</source>
          <volume>5318</volume>
          ,
          <issue>790</issue>
          {
          <fpage>803</fpage>
          (
          <year>2008</year>
          ). https://doi.org/10.1007/978-3-
          <fpage>540</fpage>
          -88564-1 51
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Costin</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Eastman</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Need for interoperability to enable seamless information exchanges in smart and sustainable urban systems</article-title>
          .
          <source>Journal of Computing in Civil Engineering</source>
          <volume>33</volume>
          (
          <issue>3</issue>
          ),
          <volume>1</volume>
          {
          <fpage>14</fpage>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Cyganiak</surname>
          </string-name>
          , R.:
          <article-title>Buildings and rooms vocabulary</article-title>
          . http://vocab.deri.ie/rooms, Last accessed: 20
          <source>May</source>
          <year>2019</year>
          (
          <year>2012</year>
          ), Digital Enterprise Research Institute (DERI), Galway, Ireland
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Daniele</surname>
          </string-name>
          , L.,
          <string-name>
            <surname>den Hartog</surname>
          </string-name>
          , F.,
          <string-name>
            <surname>Roes</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>Created in Close Interaction with the Industry: The Smart Appliances REFerence (SAREF) Ontology</article-title>
          . In: Cuel,
          <string-name>
            <given-names>R.</given-names>
            ,
            <surname>Young</surname>
          </string-name>
          ,
          <string-name>
            <surname>R</surname>
          </string-name>
          . (eds.)
          <source>Proc. of FOMI</source>
          . pp.
          <volume>100</volume>
          {
          <fpage>112</fpage>
          . Springer International Publishing, Cham,
          <source>Switzerland (August 5</source>
          <year>2015</year>
          ). https://doi.org/10.1007/978-3-
          <fpage>319</fpage>
          -21545-7 9
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Domingue</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fensel</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hendler</surname>
            ,
            <given-names>J.A.</given-names>
          </string-name>
          :
          <article-title>Handbook of semantic web technologies</article-title>
          . Springer, Berlin, Germany (
          <year>2011</year>
          ). https://doi.org/10.1007/978-3-
          <fpage>540</fpage>
          -92913-0
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Espinoza-Arias</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Poveda-Villalon</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Garcia-Castro</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Corcho</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          :
          <article-title>Ontological representation of smart city data: From devices to cities</article-title>
          .
          <source>Applied Sciences</source>
          <volume>9</volume>
          (
          <issue>1</issue>
          ) (
          <year>2018</year>
          ). https://doi.org/10.3390/app9010032
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Euzenat</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shvaiko</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Ontology matching</article-title>
          , vol.
          <volume>18</volume>
          . Springer, Heidelberg, Germany, 2nd edn. (
          <year>2013</year>
          ). https://doi.org/10.1007/978-3-
          <fpage>642</fpage>
          -38721-0
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Faria</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pesquita</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Santos</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Palmonari</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cruz</surname>
            ,
            <given-names>I.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Couto</surname>
            ,
            <given-names>F.M.:</given-names>
          </string-name>
          <article-title>The AgreementMakerLight Ontology Matching System</article-title>
          .
          <source>In: Proc. of ODBASE</source>
          . Springer, Berlin, Germany (
          <year>2013</year>
          ). https://doi.org/10.1007/978-3-
          <fpage>642</fpage>
          -41030-738
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Fernandez-Lopez</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gomez-Perez</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Juristo</surname>
          </string-name>
          , N.:
          <article-title>Methontology: from ontological art towards ontological engineering</article-title>
          .
          <source>In: Proc. of AAAI</source>
          . pp.
          <volume>33</volume>
          {
          <fpage>40</fpage>
          .
          <string-name>
            <surname>Stanford</surname>
          </string-name>
          ,
          <source>USA (March</source>
          <volume>24</volume>
          -26
          <year>1997</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Gupta</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Szekely</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Knoblock</surname>
            ,
            <given-names>C.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Goel</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Taheriyan</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Muslea</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Karma: A system for mapping structured sources into the semantic web</article-title>
          .
          <source>In: Proc. of ESWC</source>
          . pp.
          <volume>430</volume>
          {
          <issue>434</issue>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Gyrard</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zimmermann</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sheth</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Building iot-based applications for smart cities: How can ontology catalogs help</article-title>
          ?
          <source>IEEE Internet of Things Journal</source>
          <volume>5</volume>
          (
          <issue>5</issue>
          ),
          <volume>3978</volume>
          {3990 (Oct
          <year>2018</year>
          ). https://doi.org/10.1109/JIOT.
          <year>2018</year>
          .2854278
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17. ISO: ISO 16739
          <string-name>
            <surname>- Industry Foundation Classes</surname>
          </string-name>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Musen</surname>
            ,
            <given-names>M.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Team</surname>
            ,
            <given-names>T.P.</given-names>
          </string-name>
          : Protege Ontology Editor. In: Dubitzky,
          <string-name>
            <given-names>W.</given-names>
            ,
            <surname>Wolkenhauer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            ,
            <surname>Cho</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.H.</given-names>
            ,
            <surname>Yokota</surname>
          </string-name>
          , H. (eds.)
          <source>Encyclopedia of Systems Biology</source>
          . pp.
          <volume>1763</volume>
          {
          <fpage>1765</fpage>
          . Springer, New York, USA (
          <year>2013</year>
          ). https://doi.org/10.1007/978-1-
          <fpage>4419</fpage>
          - 9863-7 1104
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Noy</surname>
            ,
            <given-names>N.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McGuinness</surname>
            ,
            <given-names>D.L.</given-names>
          </string-name>
          :
          <article-title>Ontology Development 101: A Guide to Creating Your First Ontology</article-title>
          .
          <source>Tech. Rep. SMI-2001-0880</source>
          , Stanford University, Stanford, USA (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Otero-Cerdeira</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rodr</surname>
          </string-name>
          guez-Mart nez, F.,
          <string-name>
            <surname>Gomez-Rodr guez</surname>
          </string-name>
          , A.:
          <article-title>De nition of an ontology matching algorithm for context integration in smart cities</article-title>
          .
          <source>Sensors</source>
          <volume>14</volume>
          (
          <issue>12</issue>
          ),
          <volume>23581</volume>
          {
          <fpage>23619</fpage>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Otero-Cerdeira</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rodr</surname>
            guez-Mart nez,
            <given-names>F.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Valencia-Requejo</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <article-title>GomezRodr guez, A.: A new similarity measure for an ontology matching system</article-title>
          . In: Fred,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Dietz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.L.G.</given-names>
            ,
            <surname>Aveiro</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Liu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Filipe</surname>
          </string-name>
          ,
          <string-name>
            <surname>J</surname>
          </string-name>
          . (eds.)
          <article-title>Knowledge Discovery, Knowledge Engineering and Knowledge Management</article-title>
          . pp.
          <volume>257</volume>
          {
          <fpage>272</fpage>
          . Springer International Publishing, Cham, Switzerland (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Pauwels</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Terkaj</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          :
          <article-title>EXPRESS to OWL for construction industry: Towards a recommendable and usable ifcOWL ontology</article-title>
          .
          <source>Automation in Construction 63</source>
          ,
          <issue>100</issue>
          {
          <fpage>133</fpage>
          (
          <year>2016</year>
          ). https://doi.org/10.1016/j.autcon.
          <year>2015</year>
          .
          <volume>12</volume>
          .003
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Pauwels</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          , Zhang,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Lee</surname>
          </string-name>
          ,
          <string-name>
            <surname>Y.C.</surname>
          </string-name>
          :
          <article-title>Semantic web technologies in AEC industry: A literature overview</article-title>
          .
          <source>Automation in Construction 73</source>
          ,
          <issue>145</issue>
          {
          <fpage>165</fpage>
          (
          <year>2017</year>
          ). https://doi.org/10.1016/j.autcon.
          <year>2016</year>
          .
          <volume>10</volume>
          .003
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <given-names>Poveda</given-names>
            <surname>Villalon</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Garcia</surname>
          </string-name>
          <string-name>
            <surname>Castro</surname>
          </string-name>
          , R.:
          <article-title>SAREF extension for building devices (</article-title>
          <year>2017</year>
          ), http://ontoology.linkeddata.es/publish/saref4bldg/ index-en.html, [Online; last accessed 2017-
          <volume>09</volume>
          -12]
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <string-name>
            <surname>Rasmussen</surname>
            ,
            <given-names>M.H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pauwels</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hviid</surname>
            ,
            <given-names>C.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Karlsh</surname>
          </string-name>
          j, J.:
          <article-title>Proposing a Central AEC Ontology That Allows for Domain Speci c Extensions</article-title>
          .
          <source>In: Proc. of LC3</source>
          . vol.
          <volume>1</volume>
          , pp.
          <volume>237</volume>
          {
          <fpage>244</fpage>
          .
          <string-name>
            <surname>Heraklion</surname>
          </string-name>
          ,
          <string-name>
            <surname>Greece</surname>
          </string-name>
          (
          <year>2017</year>
          ). https://doi.org/10.24928/JC3-2017/0153
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          26.
          <string-name>
            <surname>Rasmussen</surname>
            ,
            <given-names>M.H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pauwels</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lefrancois</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schneider</surname>
            ,
            <given-names>G.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hviid</surname>
            ,
            <given-names>C.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Karlsh</surname>
          </string-name>
          j, J.:
          <article-title>Recent changes in the Building Topology Ontology</article-title>
          .
          <source>In: Proc. of LDAC. Dijon</source>
          , France (
          <year>November 2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          27.
          <string-name>
            <surname>Reinisch</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ko</surname>
            <given-names>er</given-names>
          </string-name>
          , M.J.,
          <string-name>
            <surname>Iglesias</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kastner</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          :
          <article-title>Thinkhome energy e ciency in future smart homes</article-title>
          .
          <source>EURASIP Journal on Embedded Systems 2011(1)</source>
          ,
          <volume>104617</volume>
          (
          <year>2011</year>
          ). https://doi.org/10.1155/
          <year>2011</year>
          /104617
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          28.
          <string-name>
            <surname>Schneider</surname>
            ,
            <given-names>G.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pauwels</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Steiger</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Ontology-based Modeling of Control Logic in Building Automation Systems</article-title>
          .
          <source>IEEE Transactions on Industrial Informatics</source>
          <volume>13</volume>
          (
          <issue>6</issue>
          ),
          <volume>3350</volume>
          {
          <fpage>3360</fpage>
          (
          <year>2017</year>
          ). https://doi.org/10.1109/TII.
          <year>2017</year>
          .2743221
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          29.
          <string-name>
            <surname>Schneider</surname>
            ,
            <given-names>G.F.</given-names>
          </string-name>
          :
          <article-title>Towards Aligning Domain Ontologies with the Building Topology Ontology</article-title>
          .
          <source>In: Proceedings of the 5th Linked Data in Architecture and Construction Workshop (LDAC)</source>
          . pp.
          <volume>1</volume>
          {
          <issue>8</issue>
          .
          <string-name>
            <surname>Dijon</surname>
          </string-name>
          , France (
          <year>2017</year>
          ). https://doi.org/10.13140
          <source>/RG.2.2.21802.52169</source>
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          30.
          <string-name>
            <surname>Shvaiko</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Euzenat</surname>
          </string-name>
          , J.:
          <article-title>Ontology matching: state of the art and future challenges</article-title>
          .
          <source>IEEE Transactions on knowledge and data engineering 25(1)</source>
          ,
          <volume>158</volume>
          {
          <fpage>176</fpage>
          (
          <year>2013</year>
          ). https://doi.org/10.1109/TKDE.
          <year>2011</year>
          .253
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          31.
          <string-name>
            <surname>Sirin</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parsia</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grau</surname>
            ,
            <given-names>B.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kalyanpur</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Katz</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          :
          <article-title>Pellet: A practical OWLDl reasoner</article-title>
          .
          <source>Web Semantics: science, services and agents on the World Wide Web</source>
          <volume>5</volume>
          (
          <issue>2</issue>
          ),
          <volume>51</volume>
          {
          <fpage>53</fpage>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          32.
          <article-title>W3C LBD CG: Building Data on the Web Working Group Charter</article-title>
          . https:// w3c-lbd-cg.github.io/lbd/charter/,
          <source>Last accessed: 20 May</source>
          <year>2019</year>
          (
          <year>2017</year>
          ),
          <source>last accessed: 11 July 2017</source>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>