<!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>LDAC</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Semantic Interoperability Using Ontologies and Standards for Building Product Properties</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>He Tan</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Rahel Kebede</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Annika Moscati</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Peter Johansson</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Computing, School of Engineering, Jönköping University</institution>
          ,
          <country country="SE">Sweden</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Department of Construction Engineering and Lighting Science, School of Engineering, Jönköping University</institution>
          ,
          <country country="SE">Sweden</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2024</year>
      </pub-date>
      <volume>12</volume>
      <fpage>13</fpage>
      <lpage>14</lpage>
      <abstract>
        <p>Both standards and ontologies are among the important components to realize the vision of BIM (Building Information Modeling). They provide a community consensus for interpretation, communication and interoperability of building data. This consensus is pivotal in enabling diverse stakeholders and systems to seamlessly collaborate and share data across the entire building life cycle. In this paper we describe the development of ontologies for building product properties, aligning with standards, and demonstrate their usage in achieving semantic interoperability. First, a top-domain ontology, BPPO (Buiding Product Property Ontology), is developed for building product properties. This top-domain ontology is used to guide the development of domain ontologies for properties in diferent categories of products or groups of product categories. Subsequently, a domain ontology, LPPO (Lighting Product Property Ontology), is built for lighting product properties, with guidance from BPPO, in this work. The ontological terminologies of both BPPO and LPPO are aligned with the standards set forth by the BIM community. Furthermore, the ontologies have been used in an application to support and enhance the interoperability between the manufacturer's product database and the BIM platform.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Ontology</kwd>
        <kwd>Standard</kwd>
        <kwd>Semantic Interoperability</kwd>
        <kwd>BIM</kwd>
        <kwd>Product Properties</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Today, BIM (Building Information Modeling) has evolved from level 0, which was focused on
2D CAD and exchange of paper-based drawings, to the level 3 which aims for a high level
of integration and interoperability between diferent stakeholders and systems using digital
and object-oriented building information models [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Ensuring interoperability among various
software tools and platforms used by diferent stakeholders, such as architects, engineers,
contractors, and facility managers, is crucial for the successful implementation and adoption
of BIM processes. To address this challenge in implementing the BIM maturity level 3, both
standards and ontologies play an important role.
      </p>
      <p>
        In BIM, properties are critical as they serve to define and describe building elements. They
provide essential information about the functions and characteristics of components, materials,
and systems used in the construction. For example, the classification systems, such as the
Uniclass 1, MasterFormat 2 and CoClass 3, organize and classify things based on their properties. To
support interoperability between diferent stakeholders and enhance the information exchange
and integration in BIM, properties need to be created in an agreed manner on their naming,
definition, measurement and other relevant aspects. In 2020 the EN ISO 23386 [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] was published
as a standard to guide on how to define properties used in construction.
      </p>
      <p>
        Product properties have been one of the central focuses within the context of BIM [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Building
product manufacturers are important actors in building realization processes. Many product
manufacturers have adopted BIM platforms to describe and share their product data through
BIM objects. However, this approach has its own set of challenges in achieving interoperability
between manufacturers’ databases and the BIM platform [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Facilitating the exchange and
integration of manufacturers’ product data in BIM platforms at an early stage of the building
life cycle is critical for the productivity of the construction processes.
      </p>
      <p>
        Standardization eforts have placed a significant amount of attention on the product
properties. Given the great amount of products used in the construction industry, one solution
is to undertake standardization work for diferent categories or groups of product categories.
For example, the standard Technical Specification (CEN/TS) SIS-CEN/TS 17623 [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], has been
developed specifically for the products used in lighting systems. Furthermore, building upon
EN ISO 23386:2020 as a foundation, the Technical Committee ISO/TC 274 Light and Lighting
in cooperation with CIE Joint Technical Committee 6 4 is currently conducting the work of
producing an ISO standard specifically for lighting product properties, based on this CEN/TS
SIS-CEN/TS 17623.
      </p>
      <p>
        Recently, many studies (e.g. [
        <xref ref-type="bibr" rid="ref6 ref7 ref8">6, 7, 8</xref>
        ]) have promoted ontology and the Semantic Web
technologies as potential solutions for supporting integration and interoperability in BIM. Specifically,
ontologies can provide a standardized vocabulary and framework for representing the data and
information, which will improve communication, collaboration, and decision-making among
stakeholders. The ontology languages for the Semantic Web, e.g., RDFS [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] and OWL languages
[
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], can express explicitly the concepts and terms and their semantic descriptions in a machine
readable manner. In addition to the ontology languages, the validation languages like SHACL
[
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] and rule languages such as SWRL [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ], can be used to evaluate and infer over the
specifications. For example, when digital BIM models are built and/or annotated using the concepts and
terms, ontology and ontology-enhanced technologies can improve the quality of the models on
their semantic descriptions and significantly increase the performance of accessing, integration
and interoperability of building data using the models [
        <xref ref-type="bibr" rid="ref13 ref14">13, 14</xref>
        ].
      </p>
      <p>In this paper we describe the development of ontologies for building product properties,
aligning with standards, and demonstrate their usage in achieving semantic interoperability.
First, a top domain ontology, Building Product Property Ontology (BPPO), was developed
according to the standard EN ISO 23386:2020. This ontology will serve as a foundational
knowledge for developing specific property ontologies for particular categories of products.
Then, with the guidance of the top domain ontology, an ontology was developed for lighting
product properties (LPPO). The development of the ontology LPPO also takes as the input the
1https://www.thenbs.com/our-tools/uniclass
2https://www.csiresources.org/standards/masterformat
3https://byggtjanst.se/tjanst/coclass
4https://cie.co.at/technical-work/division6/technical-committees
specifications identified in the standard SIS-CEN/TS 17623. Then the usage of the ontologies is
demonstrated in an application to support the interoperability between manufacturer’s product
databases and BIM platforms.</p>
      <p>The rest of this paper is organised as follows. In Section 2 we present the well-known
standards and ontologies developed for properties in the field of BIM, specially concerning
semantic interoperability. In Section 3 we describe the development of the ontologies BPPO and
LPPO with the guidance of standards and describe the ontologies. In Section 4 we presented
the usage of the developed ontologies to support semantic interoperability in an application.
Finally, the paper concludes in Section 5.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Related Work</title>
      <p>
        In the realm of BIM, foundational texts like the BIM Handbook (e.g. [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]) identifies the
significance of semantic interoperability in improving communication and collaboration in the
construction industry. Recently, it has been acknowledged wihtin BIM that using ontologies to
represent and organize BIM data is a solution to improving semantic interoperability [
        <xref ref-type="bibr" rid="ref16 ref17 ref7">7, 16, 17</xref>
        ].
Ongoing standardization eforts by organizations such as ISO and buildingSMART 5 also
underscores the importance of standards in achieving semantic interoperability. In other domains
that are more advanced in addressing issues of semantic interoperability than BIM, works
have also discussed various issues related to the development and application of standards
and ontologies. Additionally, they emphasize the importance of collaboration and integration
between ontologies and standards to support semantic interoperability [
        <xref ref-type="bibr" rid="ref18 ref19 ref20">18, 19, 20</xref>
        ]. Today,
much work has been done on developing ontologies to facilitate a common understanding of
building information, thereby supporting semantic interoperability. In this section we discuss
briefly well-known standards, data dictionaries and ontologies that are relevant for describing
properties, especially product properties, within BIM.
      </p>
      <sec id="sec-2-1">
        <title>2.1. Maintaining properties according to EN ISO 23386:2020</title>
        <p>The standard EN ISO 23386:2020 specifies the requirements on describing, authoring and
maintaining properties used in the construction industry. The standard intends to establish
interoperability between data dictionaries and build a network of the data dictionaries for
properties. The mappings between the terms used in the interconnected data dictionaries need
to be maintained. In the network, each property should be identified by a globally unique
identifier (GUID). Each property is described by a number of attributes. An attribute may follow
the management rules, such as "mandatory" and "calculated". The value of an attribute can be
a single value, an enumeration or multiple values of a certain type. Several properties can be
organized into a group.</p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Product Properties in Data Dictionaries</title>
        <p>
          In this section, we discuss how product properties are described in several well-known BIM data
dictionaries. The overview is presented in Table 1. All the data dictionaries are multi-disciplines
and are not specifically designed for product properties or any one particular category or groups
of categories of building products. The terms in these data dictionaries can be read by human,
by machine via machine languages or via APIs. Not all data dictionaries use GUID to identify
properties. Most of the data dictionaries have been used by the industry for many years and have
a well established coding system. bsDD has made efort to conform to EN ISO 23386:2020. It uses
URIs as GUID to uniquely identify terms. The mappings between the terms for interconnected
data dictionaries, i.e. "interconnected" in Table 1, are not well implemented in most of the data
dictionaries. Although most of the data dictionaries do not contains mapping to other data
dictionaries, the mapping is critical for semantic interoperability, specially when multiple data
dictionaries are used a BIM project. Thus, the mappings between the terms in several diferent
data dictionary have been studied in various research work, e.g. [
          <xref ref-type="bibr" rid="ref21 ref22">21, 22</xref>
          ].
        </p>
      </sec>
      <sec id="sec-2-3">
        <title>2.3. Ontologies for Product and Product Properties</title>
        <p>
          There has been a significant amount of efort to introduce ontology into BIM. For example, the
BIMSO ontology [
          <xref ref-type="bibr" rid="ref23">23</xref>
          ] was developed to encode all the elements from the UniFormat II using
OWL ontology language. ifcOWL [
          <xref ref-type="bibr" rid="ref24 ref25">24, 25</xref>
          ] has been a big project done by the International
buildingSmart consortium 6, which is to encode all the elements in the IFC Schema using
OWL ontology language. The Linked Building Data Community Group of the World Wide
Web Consortium (W3C) 7 developed an ontology for describing the core topological concepts
of a building, the Building Topology Ontology (BOT) [
          <xref ref-type="bibr" rid="ref26">26</xref>
          ]. It has focused on the high-level
description of storeys and spaces, the building elements they may contain, and their 3D geometry.
The Building Product Ontology (BPO) [
          <xref ref-type="bibr" rid="ref27">27</xref>
          ] was developed to provide a top level ontology for
describing building products. It has focused on providing a framework to describe assembly
structures and component interconnections of building product components, and enable to
attach properties to components. We have aligned the properties represented in our ontologies
to the class Product in the BPO. Oraskari [
          <xref ref-type="bibr" rid="ref28">28</xref>
          ] demonstrates an API which enables to generate
OWL ontology using the terms retrieved from bsDD data dictionaries for specific purposes.
        </p>
        <p>
          Representing properties using ontology is an important area of research within the context of
6https://www.buildingsmart.org/
7https://www.w3.org/community/lbd/
BIM. A number of work has been focused on representing properties using ontology. In [
          <xref ref-type="bibr" rid="ref21">21</xref>
          ] the
authors discussed the complexity of the property ontology when converting IFC to RDF data.
The BIMDO ontology (Building Design Ontology) extends the BIMSO ontology with the design
properties for building elements [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ]. The Ontology for Property Management (OPM) [
          <xref ref-type="bibr" rid="ref29">29</xref>
          ] is
an ontology developed to managing property changes of a building element. It has focused on
describing temporal properties that are subject to changes as the building design evolves. In [
          <xref ref-type="bibr" rid="ref30">30</xref>
          ]
the authors developed a top domain ontology, the Interconnected Data Dictionary Ontology
(IDDO), mainly to support NLP (natural language processing) methods to extract property
knowledge from unstructured guidelines or building codes into a structured class hierarchy.
        </p>
        <p>In the work presented in this paper the development of the top domain product property
ontology has been in accordance with the requirements and specifications identified in the
ISO standard that were developed to support the implementation of BIM. The ISO standard
gives the recommendations on how to describe properties including how to manage property
changes, status and versions. The aim for developing the top domain ontology is to facilitate
the development of specific ontologies for categories or category groups of products.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. The Building Product Property Ontology (BPPO) and the</title>
    </sec>
    <sec id="sec-4">
      <title>Lighting Product Property Ontology (LPPO)</title>
      <p>
        In general, the ontology development in this work has followed the NeOn ontology engineering
methodology [
        <xref ref-type="bibr" rid="ref31">31</xref>
        ] and has focused on applying scenario 2 (reusing and re-engineering
nonontological resources). We used OWL 2 DL as the representation language for the ontology.
During the development process, one knowledge engineer and one domain expert from the
area of building and construction were involved.
      </p>
      <p>As shown in Figure 1, the ontology development process is organized into two phases. In
the first step, a top domain ontology Building Product Property Ontology (BPPO) is developed.
It defines the representation of building product properties, conformed to the requirements
specified on properties in the standard EN ISO 23386:2020. This ontology will provide a
foundation for building more specialized property ontologies for a particular product category or
groups of product categories. Figure 2 shows the example attributes specified in the standard
for describing property. Each row in the table records one attribute. Each attribute is described
by a few parameters. The main transformation rules applied to create the ontology BPPO from
the tabular structured data in the standard is given as below:
Algorithm 1 Transform attributes in standard to ontology elements
create a class Property
for each attribute do
if Interconnected dictionaries management rule
or Request form management rule is mandatory then
create a property for the class Property
if Type is single-value then</p>
      <p>add the property range as specified in Type
else if Type is enumeration single value then
create a class to enumerate the values specified in List of values
add the class as the property range
else if Type is multiple-values then</p>
      <p>the property range will be defined in specific property ontology
end if
end if
add the description and example of the attribute using rdfs:comment</p>
      <p>and skos:example respectively
end for</p>
      <p>The fragment of the BPPO shown in Figure 3 represents the example property attributes
shown in Fig. 2. The class Property has the relation propertyOf to the class Product in the
BPO. Property has overlapping with the classes Attribute and RangedAttribute in the
BPO, but logically they are not equivalent and do not have subclass/superclass relationships,
so skos:related is used to represent the associations between them. The definition of
the class Status is given as Status ≡ {active, inactive}. The range of the property
usedInCountry is defined as owl:Thing, since the country list is specific to particular product
property ontology. For example, when a property is used in the countires Sweden and UK, the
range is defined using a class countriesUsingProperty given countriesUsingProperty
≡ {Sweden, UK}. As given the transformation rule, the optional attributes currently are not
represented in the BPPO. This was suggested by the domain expert. The standard SIS-CEN/TS
17623:2021 also shows that the optional attributes are not used.</p>
      <p>In the second step, the development of the property ontology for a particular category of
products is guided by the top-domain ontology BPPO. In this work an ontology for representing
the lighting product properties is developed. During the development, SIS-CEN/TS 17623:2021, a
standard for "BIM Properties for lighting – Luminaires and sensing devices” is the non-ontological
resource used to gain the knowledge. Currently, standards are being developed for diferent
categories of products. One of the product categories where this work have come rather far is
luminaires and sensing devices. Fig. 4 shows the example mechanical properties of lighting
product. Each row in the table records one property. 6 attributes defined in EN ISO 23386:2020
are used to describe each property in this standard. ID and symbol are the new attributes
introduced in this standard. In total there are 8 tables of which each organizes a set of properties
into a group. The ontology has been developed using the concepts and properties defined in the
BPPO. Fig. 5 shows a fragment of the LPPO which represent the property glow wire resistance
described in Fig. 4. The ontology fragment written in the format Turtle is given below.</p>
      <p>Availability: The ontologies have the permanent w3id http://w3id.org/ppon/bppo/ and
http://w3id.org/ppon/lppo/, and currently are maintained on the gitlab https://github.com/
tanhe-git/ppon.
:1LrBLaYtnCARKperF_2Ykh rdfs:subClassOf bppo:Property ;
bppo:memberOf :MechanicalProeprty;
bppo:hasGUID "1LrBLaYtnCARKperF_2Ykh";
:hasID "01-0017";
bppo:hasName "glow wire resistance"@en ;
bppo:description "The glow wire test for fire hazard (see EN
˓→ 60695-2-10) to test electrical products, assemblies or
˓→ individual components."@en ;
bppo:digitalFormat "(IE0, C)";
lppo:valueSet :glowWireResisteanceTemperatureValueSet;
rdfs:seeAlso "EN 60695-2-10".
:glowWireResistanceTemperatureValueSet owl:equivalentClass
[ rdf:type rdfs:Datatype;</p>
      <p>owl:oneOf ( "550C"^^xsd:string "650°C"^^xsd:string</p>
      <p>"750C"^^xsd:string "850C"^^xsd:string "960C^^xsd:string)</p>
    </sec>
    <sec id="sec-5">
      <title>4. Using the Ontologies to Support Semantic Interoperability</title>
      <p>
        Ontology evaluation has been a challenge in the area of ontology engineering for a long time
[
        <xref ref-type="bibr" rid="ref32 ref33 ref34 ref35">32, 33, 34, 35</xref>
        ]. In [
        <xref ref-type="bibr" rid="ref36 ref37">36, 37</xref>
        ], the authors argue that one way to evaluate an ontology is to assess
its usability or appicability in the tasks it targets. As described in Section 3, the BPPO is a top
domain ontology and serves as a foundational knowledge base to support the development
of specific ontologies for particular categories of products or groups of product categories.
In Section 3, we have presented this usage when the LPPO ontology is developed based on
the BPPO. In this section we will mainly present the usage of the LPPO to support semantic
interoperability between product manufactures’ database and BIM platform in a real world
example application.
      </p>
      <p>
        As illustrated in Figure 6, product property ontology acts as the reference to establish the
semantic relationships between the concepts and terms used in manufacturer’s database schema
and product description model used in BIM platform. Figure 7 details the architecture for
the semantic interoperability using ontology presented in Figure 6. The component Mapping
Generator in the architecture illustrated in Figure 7 will generate the mappings between
manufacturer’s database schema and the ontology, and between BIM platform’s product description
model and the ontology. The component Ontology-enabled Query Interface will rewrite
the query sent from BIM platform to a query readable and understandable by manufacturer’s
database API using the mappings, and rewrite the query result sent back from manufacturer’s
database API to the data model readable and understandable by BIM platform. A prototype
of the architecture shown in Fig 7 was implemented and presented in [
        <xref ref-type="bibr" rid="ref38">38</xref>
        ]. The prototype
aims to enable semantic interoperability between the BIM authoring tool Autodesk Revit 8
and an electric lighting product manufacturer’s database. Through this prototype, product
manufacturers share their data via the ontology-based query interface, eliminating the need to
outsource the data.
      </p>
      <p>Be more specific, the prototype was built to assist designers and architects to gain access to
product data that is specific to their use cases at hand regardless of their expertise at managing
data, and enables manufacturers to maintain their interest for data autonomy, while still giving
designers and architects access to data from their databases. In this prototype the manufacturer’s
database has been implemented as a RDF triplestore by populating the LPPO ontology. The
triplestore was implemented using Stardog 9. The database query API is a SPARQL endpoint.
The mappings are created using the LPPO and implemented as a part of the prototype. The
ontology-enabled query interface is implemented using visual programming in Dynamo 10 which
is a popular visual programming software packages supported by BIM platforms. Additionally,
Dynamo works with Python scripts. The Dynamo program 1) composes SPARQL query given a
product data search task, 2) connects to the manufacturer’s database, 3) parses the query results
and 4) loads the results to a Revit description model. In the steps 1) and 4) the mappings are
utilized. The prototype is demonstrated and evaluated in a real world use case in BIM project.
It is to support lighting engineer in simulating the number of lighting fixtures needed for a
conference room in Revit using lighting product properties. Four participants from the electric
lighting product manufacturer and a BIM consulting firm have participated the evaluation and
work on the simulation case using the prototype. The application has shown the efeciency of
the LPPO ontology to build semantic interoperability between manufacturer’ database and BIM
platform.</p>
    </sec>
    <sec id="sec-6">
      <title>5. Conclusions</title>
      <p>In this paper, we presented two ontologies of properties for products used in the construction
industry. BPPO is a top domain ontology which represents the attributes standardized in an ISO
standard developed by the BIM community for describing properties. This ontology provides the
classes and properties to support modeling of the properties for particular categories of products
in a standardized manner. The ontology LPPO represents and standardizes the properties that
describe the characteristics of electric lighting products using the classes and properties defined
in BPPO. Further, we showed the use of the LPPO to support the interoperability between
manufacturer’s product database and BIM platform.</p>
      <p>As suggested by EN ISO 23386:2020, there is a need to build a network of interconnected data
dictionaries to describe, author and maintain properties in the construction industry. Ideally,
each data dictionary in the network defines the properties for particular category of products
or group of product categories. To address this need, we have followed the suggestion put forth
in EN ISO 23386:2020 and developed the top domain ontology BPPO and the domain ontology
LPPO. One direction of the future work is on expanding and enhancing the network of product
property ontologies to cover a wider range of building product categories.</p>
    </sec>
    <sec id="sec-7">
      <title>Acknowledgments</title>
      <p>This work has been conducted in the research project "Manufactured products’ information
provision for light environments (MAP4Light), which is financially supported by the Swedish
Knowledge Foundation, and the research project "Prototype for products’ information flow
(ProFlow)" , which is funded by Vinnova (the Sweden’s innovation agency). The authors would
like to thank all participants from industrial partners Fagerhult Belysning,
Informationsbyggnarna, OBOS and Inwido.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>M.</given-names>
            <surname>Bew</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.</surname>
          </string-name>
          <article-title>Richards, BIM maturity model, strategy paper for the government construction client group</article-title>
          , Department of Business, Innovation and Skills, London, UK. (
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <source>[2] ISO</source>
          <volume>23386</volume>
          :
          <year>2020</year>
          , ISO 23386:
          <year>2020</year>
          <article-title>Building information modelling and other digital processes used in construction - Methodology to describe, author and maintain properties in interconnected data dictionarie</article-title>
          , Standard, International Organization for Standardization,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>S.</given-names>
            <surname>Palos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Kiviniemi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Kuusisto</surname>
          </string-name>
          ,
          <article-title>Future perspectives on product data management in building information modeling</article-title>
          ,
          <source>Construction Innovation</source>
          <volume>14</volume>
          (
          <year>2014</year>
          )
          <fpage>52</fpage>
          -
          <lpage>68</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>F.</given-names>
            <surname>Abanda</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Tah</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Cheung</surname>
          </string-name>
          ,
          <article-title>Bim in of-site manufacturing for buildings</article-title>
          ,
          <source>Journal of building engineering 14</source>
          (
          <year>2017</year>
          )
          <fpage>89</fpage>
          -
          <lpage>102</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <article-title>[5] SIS-CEN/TS17623:2021, SIS-CEN/TS17623:2021 BIM Properties for lighting - Luminaires and sensing devices</article-title>
          , Standard, Swedish Institute for Standards,
          <year>2021</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>Q.</given-names>
            <surname>Yang</surname>
          </string-name>
          ,
          <string-name>
            <surname>Y. Zhang,</surname>
          </string-name>
          <article-title>Semantic interoperability in building design: Methods and tools</article-title>
          ,
          <source>Computer-Aided Design</source>
          <volume>38</volume>
          (
          <year>2006</year>
          )
          <fpage>1099</fpage>
          -
          <lpage>1112</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>P.</given-names>
            <surname>Pauwels</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Zhang</surname>
          </string-name>
          , Y.-
          <string-name>
            <given-names>C.</given-names>
            <surname>Lee</surname>
          </string-name>
          ,
          <article-title>Semantic web technologies in AEC industry: A literature overview</article-title>
          ,
          <source>Automation in construction 73</source>
          (
          <year>2017</year>
          )
          <fpage>145</fpage>
          -
          <lpage>165</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>R. Z.</given-names>
            <surname>Kebede</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Moscati</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Johansson</surname>
          </string-name>
          ,
          <article-title>Semantic web for information exchange between the building and manufacturing industries: a literature review</article-title>
          ,
          <source>in: 37th International Conference of CIB W78</source>
          ,
          <string-name>
            <surname>Sao</surname>
          </string-name>
          Paulo-online,
          <source>Brazil</source>
          ,
          <fpage>18</fpage>
          -
          <issue>20</issue>
          <year>August</year>
          ,
          <year>2020</year>
          , pp.
          <fpage>248</fpage>
          -
          <lpage>265</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>B.</given-names>
            <surname>McBride</surname>
          </string-name>
          ,
          <article-title>The resource description framework (RDF) and its vocabulary description language RDFS</article-title>
          , in: Handbook on ontologies, Springer,
          <year>2004</year>
          , pp.
          <fpage>51</fpage>
          -
          <lpage>65</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>D. L. McGuinness</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          <string-name>
            <surname>Van Harmelen</surname>
          </string-name>
          , et al.,
          <article-title>OWL web ontology language overview</article-title>
          ,
          <source>W3C recommendation 10</source>
          (
          <year>2004</year>
          )
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>H.</given-names>
            <surname>Knublauch</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Kontokostas</surname>
          </string-name>
          ,
          <article-title>Shapes constraint language (SHACL), W3C recommendation (</article-title>
          <year>2017</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>I.</given-names>
            <surname>Horrocks</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P. F.</given-names>
            <surname>Patel-Schneider</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Boley</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Tabet</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Grosof</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Dean</surname>
          </string-name>
          , et al.,
          <article-title>SWRL: A semantic web rule language combining OWL and RuleML</article-title>
          ,
          <source>W3C Member submission 21</source>
          (
          <year>2004</year>
          )
          <fpage>1</fpage>
          -
          <lpage>31</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>G.</given-names>
            <surname>Gao</surname>
          </string-name>
          , Y.-S. Liu,
          <string-name>
            <given-names>P.</given-names>
            <surname>Lin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Gu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.-H.</given-names>
            <surname>Yong</surname>
          </string-name>
          ,
          <article-title>BIMTag: Concept-based automatic semantic annotation of online BIM product resources</article-title>
          ,
          <source>Advanced Engineering Informatics</source>
          <volume>31</volume>
          (
          <year>2017</year>
          )
          <fpage>48</fpage>
          -
          <lpage>61</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <surname>A</surname>
          </string-name>
          .
          <string-name>
            <surname>-H. Hamdan</surname>
            ,
            <given-names>R. J.</given-names>
          </string-name>
          <string-name>
            <surname>Scherer</surname>
          </string-name>
          ,
          <article-title>Integration of BIM-related bridge information in an ontological knowledgebase</article-title>
          .,
          <source>in: LDAC</source>
          ,
          <year>2020</year>
          , pp.
          <fpage>77</fpage>
          -
          <lpage>90</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>R.</given-names>
            <surname>Sacks</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Eastman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Lee</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Teicholz</surname>
          </string-name>
          ,
          <article-title>BIM handbook: A guide to building information modeling for owners, designers, engineers, contractors, and facility managers</article-title>
          , John Wiley &amp; Sons,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>M.</given-names>
            <surname>Niknam</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Karshenas</surname>
          </string-name>
          ,
          <article-title>A shared ontology approach to semantic representation of BIM data, Automation in Construction 80 (</article-title>
          <year>2017</year>
          )
          <fpage>22</fpage>
          -
          <lpage>36</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>F.</given-names>
            <surname>Sadeghineko</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Kumar</surname>
          </string-name>
          ,
          <article-title>Application of semantic web ontologies for the improvement of information exchange in existing buildings</article-title>
          ,
          <source>Construction Innovation</source>
          <volume>22</volume>
          (
          <year>2022</year>
          )
          <fpage>444</fpage>
          -
          <lpage>464</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>H.</given-names>
            <surname>Mi</surname>
          </string-name>
          , P. D. Thomas,
          <article-title>Ontologies and standards in bioscience research: for machine or for human, Frontiers in Physiology 2 (</article-title>
          <year>2011</year>
          )
          <article-title>5</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>B.</given-names>
            <surname>Henderson-Sellers</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Gonzalez-Perez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>McBride</surname>
          </string-name>
          ,
          <string-name>
            <surname>G. Low,</surname>
          </string-name>
          <article-title>An ontology for ISO software engineering standards: 1) Creating the infrastructure</article-title>
          ,
          <source>Computer Standards &amp; Interfaces</source>
          <volume>36</volume>
          (
          <year>2014</year>
          )
          <fpage>563</fpage>
          -
          <lpage>576</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <given-names>C.</given-names>
            <surname>Gonzalez-Perez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Henderson-Sellers</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>McBride</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G. C.</given-names>
            <surname>Low</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Larrucea</surname>
          </string-name>
          ,
          <article-title>An Ontology for ISO software engineering standards: 2) Proof of concept and application</article-title>
          ,
          <source>Computer Standards &amp; Interfaces</source>
          <volume>48</volume>
          (
          <year>2016</year>
          )
          <fpage>112</fpage>
          -
          <lpage>123</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <given-names>M.</given-names>
            <surname>Bonduel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Oraskari</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Pauwels</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Vergauwen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Klein</surname>
          </string-name>
          ,
          <article-title>The IFC to linked building data converter-current status</article-title>
          ,
          <source>in: Proceedings of the 6th Linked Data in Architecture and Construction Workshop (LDAC</source>
          <year>2018</year>
          ), volume
          <volume>2159</volume>
          , CEUR Workshop Proceedings,
          <year>2018</year>
          , pp.
          <fpage>34</fpage>
          -
          <lpage>43</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <string-name>
            <given-names>X.</given-names>
            <surname>Ding</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Yang</surname>
          </string-name>
          , L. Liu,
          <string-name>
            <given-names>W.</given-names>
            <surname>Huang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Wu</surname>
          </string-name>
          ,
          <string-name>
            <surname>Integrating</surname>
            <given-names>IFC</given-names>
          </string-name>
          and
          <article-title>CityGML model at schema level by using linguistic and text mining techniques</article-title>
          ,
          <source>Ieee Access</source>
          <volume>8</volume>
          (
          <year>2020</year>
          )
          <fpage>56429</fpage>
          -
          <lpage>56440</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <string-name>
            <given-names>M.</given-names>
            <surname>Niknam</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Jalaei</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Karshenas</surname>
          </string-name>
          ,
          <article-title>Integrating BIM and product manufacturer data using the semantic web technologies</article-title>
          ,
          <source>Journal of Information Technology in Construction 24</source>
          (
          <year>2019</year>
          )
          <fpage>424</fpage>
          -
          <lpage>439</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [24]
          <string-name>
            <given-names>J.</given-names>
            <surname>Beetz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. Van</given-names>
            <surname>Leeuwen</surname>
          </string-name>
          ,
          <string-name>
            <surname>B. De Vries</surname>
          </string-name>
          ,
          <article-title>ifcOWL: A case of transforming EXPRESS schemas into ontologies</article-title>
          ,
          <source>Ai</source>
          Edam
          <volume>23</volume>
          (
          <year>2009</year>
          )
          <fpage>89</fpage>
          -
          <lpage>101</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          [25]
          <string-name>
            <given-names>P.</given-names>
            <surname>Pauwels</surname>
          </string-name>
          , W. Terkaj,
          <article-title>EXPRESS to OWL for construction industry: Towards a recommendable and usable ifcOWL ontology</article-title>
          ,
          <source>Automation in construction 63</source>
          (
          <year>2016</year>
          )
          <fpage>100</fpage>
          -
          <lpage>133</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          [26]
          <string-name>
            <given-names>M. H.</given-names>
            <surname>Rasmussen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Lefrançois</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G. F.</given-names>
            <surname>Schneider</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Pauwels</surname>
          </string-name>
          ,
          <string-name>
            <surname>BOT:</surname>
          </string-name>
          <article-title>The building topology ontology of the W3C linked building data group</article-title>
          ,
          <source>Semantic Web</source>
          <volume>12</volume>
          (
          <year>2021</year>
          )
          <fpage>143</fpage>
          -
          <lpage>161</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          [27]
          <string-name>
            <given-names>A.</given-names>
            <surname>Wagner</surname>
          </string-name>
          , U. Rüppel,
          <article-title>BPO: the building product ontology for assembled products</article-title>
          ,
          <source>in: Proceedings of the 7th Linked Data in Architecture and Construction workshop (LDAC</source>
          <year>2019</year>
          )
          <article-title>'</article-title>
          , Lisbon, Portugal,
          <year>2019</year>
          , p.
          <fpage>12</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          [28]
          <string-name>
            <given-names>J.</given-names>
            <surname>Oraskari</surname>
          </string-name>
          ,
          <article-title>Live Web Ontology for buildingSMART Data Dictionary</article-title>
          , in: Forum Bauinformatik,
          <year>2021</year>
          , pp.
          <fpage>166</fpage>
          -
          <lpage>173</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          [29]
          <string-name>
            <given-names>M.</given-names>
            <surname>Holten Rasmussen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Lefrançois</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Bonduel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Anker Hviid</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Karlshøj</surname>
          </string-name>
          ,
          <string-name>
            <surname>OPM:</surname>
          </string-name>
          <article-title>An ontology for describing properties that evolve over time</article-title>
          ,
          <source>in: CEUR Workshop Proceedings</source>
          , volume
          <volume>2159</volume>
          , CEUR Workshop Proceedings,
          <year>2018</year>
          , pp.
          <fpage>24</fpage>
          -
          <lpage>33</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          [30]
          <string-name>
            <given-names>S.</given-names>
            <surname>Zentgraf</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Hagedorn</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.</surname>
          </string-name>
          <article-title>König, Multi-requirements ontology engineering for automated processing of document-based building codes to linked building data properties</article-title>
          ,
          <source>in: IOP Conference Series: Earth and Environmental Science</source>
          , volume
          <volume>1101</volume>
          ,
          <string-name>
            <given-names>IOP</given-names>
            <surname>Publishing</surname>
          </string-name>
          ,
          <year>2022</year>
          , p.
          <fpage>092007</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          [31]
          <string-name>
            <given-names>M. C.</given-names>
            <surname>Suárez-Figueroa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Gómez-Pérez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Fernandez-Lopez</surname>
          </string-name>
          ,
          <article-title>The NeOn methodology framework: A scenario-based methodology for ontology development</article-title>
          ,
          <source>Applied ontology 10</source>
          (
          <year>2015</year>
          )
          <fpage>107</fpage>
          -
          <lpage>145</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          [32]
          <string-name>
            <given-names>A.</given-names>
            <surname>Gómez-Pérez</surname>
          </string-name>
          ,
          <article-title>Ontology evaluation</article-title>
          , in: Handbook on ontologies, Springer,
          <year>2004</year>
          , pp.
          <fpage>251</fpage>
          -
          <lpage>273</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          [33]
          <string-name>
            <given-names>J.</given-names>
            <surname>Brank</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Grobelnik</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Mladenic</surname>
          </string-name>
          ,
          <article-title>A survey of ontology evaluation techniques</article-title>
          ,
          <source>in: Proceedings of the conference on data mining and data warehouses (SiKDD</source>
          <year>2005</year>
          ), Citeseer,
          <year>2005</year>
          , pp.
          <fpage>166</fpage>
          -
          <lpage>170</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref34">
        <mixed-citation>
          [34]
          <string-name>
            <given-names>D.</given-names>
            <surname>Vrandečić</surname>
          </string-name>
          ,
          <article-title>Ontology evaluation</article-title>
          , in: Handbook on ontologies, Springer,
          <year>2009</year>
          , pp.
          <fpage>293</fpage>
          -
          <lpage>313</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref35">
        <mixed-citation>
          [35]
          <string-name>
            <given-names>J.</given-names>
            <surname>Raad</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Cruz</surname>
          </string-name>
          ,
          <article-title>A survey on ontology evaluation methods</article-title>
          ,
          <source>in: Proceedings of the International Conference on Knowledge Engineering and Ontology Development, part of the 7th International Joint Conference on Knowledge Discovery, Knowledge Engineering and Knowledge Management</source>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref36">
        <mixed-citation>
          [36]
          <string-name>
            <given-names>R.</given-names>
            <surname>Porzel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Malaka</surname>
          </string-name>
          ,
          <article-title>A task-based approach for ontology evaluation</article-title>
          ,
          <source>in: ECAI Workshop on Ontology Learning and Population</source>
          , Valencia, Spain, volume
          <volume>1</volume>
          ,
          <string-name>
            <surname>Citeseer</surname>
            <given-names>Valencia</given-names>
          </string-name>
          , Spain,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref37">
        <mixed-citation>
          [37]
          <string-name>
            <given-names>H.</given-names>
            <surname>Tan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Lambrix</surname>
          </string-name>
          ,
          <article-title>Selecting an ontology for biomedical text mining</article-title>
          ,
          <source>in: Proceedings of the BioNLP 2009 Workshop</source>
          ,
          <year>2009</year>
          , pp.
          <fpage>55</fpage>
          -
          <lpage>62</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref38">
        <mixed-citation>
          [38]
          <string-name>
            <given-names>R.</given-names>
            <surname>Kebede</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Moscati</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Tan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Johansson</surname>
          </string-name>
          ,
          <article-title>Integration of manufacturers' product data in BIM platforms using semantic web technologies</article-title>
          ,
          <source>Automation in Construction</source>
          <volume>144</volume>
          (
          <year>2022</year>
          )
          <fpage>104630</fpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>