<!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>Ontology-based Reasoning for Critical Incidents in Public Events</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Dimos Ntioudis</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Angelos Chatzimichail</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Georgios Meditskos</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Stefanos Vrochidis</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ioannis Kompatsiaris</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Information Technologies Institute, Centre for Research and Technology - Hellas</institution>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2020</year>
      </pub-date>
      <abstract>
        <p>One of the most critical challenges during critical incidents in big public events are the absence of real time information as well as the lack of ltering this information to meaningful knowledge in order to provide crisis decision support. Towards addressing those challenges, semantic technologies can provide a semantically data representation of the critical events, along with superior capabilities in reasoning to support the decision making. In this paper we describe the semantic reasoning framework of the DESMOS project, that could constitute the backbone of the decision support systems in public events.</p>
      </abstract>
      <kwd-group>
        <kwd>Ontologies Reasoning Security Internet of Things</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>The era of the Internet of Things (IoT) is upon us, with a huge number of
IoT devices already in everybody lives. A large number of applications in Smart
Cities, E-health, Security and other domains are exploiting the IoT technologies,
like sensors, smartphones and actuators. One of the most signi cant domains of
IoT is the safety and security, which IoT is used to save lives and mitigate
dangerous incidents.</p>
      <p>However, several challenges arose with the existing IoT technologies regarding
the interoperability of those di erent IoT technologies since their data is based
on proprietary formats and they do not use common formats or a vocabulary to
describe the interoperable data. The basic structure of the IoT is the
Machine-toMachine (M2M) communication. For example, the measurements of sensors are
required to be distributed and analyzed by other devices or sensors and not being
human readable without any kind of processing. Therefore, those measurements
should be understandable from one machine to another.</p>
      <p>In this paper, we describe the methodology and procedure that underpin the
development of reasoning rules in the DESMOS ontology. DESMOS is a novel
framework for the intelligent interconnection of smart infrastructures, mobile and
wearable devices and apps for the provision of a secure environment for citizens,
especially for visitors and tourists. The platform aims to promote the
collaboration between people and devices for protecting tourists, supporting timely
Copyright c 2020 for this paper by its authors. Use permitted under Creative</p>
      <p>Commons License Attribution 4.0 International (CC BY 4.0).
reporting of incidents, adaptation of the interconnected environments in case of
emergency, and the provision of assistance by empowering local authorities and
volunteers. The main research contribution of the paper is the combination of
the data processing modules (localization) with the semantic knowledge under
a common reasoning framework.</p>
      <p>The rest of the paper is organized as follows. In Section 2, we describe related
work. In Section 3 the Desmos framework and the main technical components.
Section 4 describes the Data Integration. rule-based semantic reasoning. In
Section 5 the Rule-based Reasoning is presented. Finally, Section 6 concludes the
paper.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Related Work</title>
      <p>The Internet of Things (IoT) is becoming more and more popular and its
applications are facing an enormous proliferation resulting in a new digital ecosystem.
IoT is based on a wide range of di erent heterogeneous technologies and devices,
there is not a uniform vocabulary for representation and processing of data. This
has led to a large number of incompatible IoT platforms. Through this way, it is
very di cult for data scientists to extract knowledge from the enormous number
of data producing every second through the IoT applications.</p>
      <p>Semantic web technologies tries to overcome such challenges. Semantic web
leverage web standards and semantic technologies to interconnect all types of
devices by transforming low-level sensor data into high-level knowledge that is
comprehensible to humans and machines. Semantic modelling produces a de nite
description of the data meaning in a structured way by combining application
knowledge and context-relevant information with sensor data. The ontology
based development, which is a domain of semantic modelling, of IoT frameworks
can lead to universal IoT solutions multiplying the bene ts of IoT.</p>
      <p>
        W3C (World Wide Web Consortium) suggested an ontology, the
Semantic Sensor Network (SSN), as a human and machine-readable speci cation that
covers networks of sensors and their deployment on top of sensors and
observations [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. The target of this project was to face the problems that arose from
the heterogeneous data from di erent devices. However, there are limited
ontologies that annotate the time{space correlation between the sensor data and
the resources. In order to overcome that, the authors in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] deployed the Sensor,
Observation, Sample, and Actuator (SOSA) ontology providing a formal but
lightweight general-purpose speci cation for modelling the interaction between
the entities involved in the acts of observation, actuation, and sampling.
      </p>
      <p>
        One of the most important ontologies for event annotation is Event [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. This
ontology is centered around the notion of event, with cognitive agents classify
arbitrary time/space regions. The agent class was derived from the FOAF (Friend
of a Friend) ontology, a core ontology for the social relationships [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. In [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]
presented an ontology for situation awareness (SAW). These ontologies
annotated events with general situations and could be expanded with supplementary
ontologies. In [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], researchers developed a platform to assist citizens in
reporting security threats together with their severity and location. The information
about the threats were stored in a knowledge base of the system that allowed
for lightweight reasoning with the gathered facts.
      </p>
      <p>
        There are many research studies for semantic reasoning on critical event
response and management. In [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], developed a system based on semantic
technologies for monitoring social media for earthquake reports and weather alerts,
and for notifying the public in case of an emergency. Also, in [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], researchers
presented a novel approach to emergency response applications integrating a
formal semantic domain model into an event-based decision support system,
which supports reasoning on this model. A semantic web-based disaster trail
management ontology that covered all vital facets of disasters like disaster type,
disaster location, disaster time and so forth is presented in [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. The ontology was
assessed e caciously via competency questions, externally by the domain
experts and internally with the help of SPARQL queries. Finally, in [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] Semantic
Web Technologies applied for Decision Support in Climate-Related Crisis
Management, supporting crisis management systems in the domain of situational
awareness.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>DESMOS Framework</title>
      <p>In this section we are presenting the framework for encoding, aggregating and
semantically analysing information relevant to the DESMOS application domain.
The framework is presented in Figure 1. It consists of a) a Communication
Layer that allows the interactions between the system components, b) an
Ontology, that is used for semantically representing notions pertinent to the project,
c) a Knowledge Base Repository (KBR) that hosts the domain ontology, d) a
Knowledge Base Service that acts as the main interface to the ontology,
responsible for populating the ontology with incoming data as well as performing
rule-based reasoning over the knowledge base, e) Mobile Apps, Wearable Devices
and Sensors that feed the system with real-time data and nally f) a
Localization Module that retrieves the received signal strength indicator (RSSI) values
of the wearable devices from the KBR in order to calculate the distance based
on data analysis algorithms.
3.1</p>
      <sec id="sec-3-1">
        <title>Use Cases and User Requirements</title>
        <p>The basis for the development of an intelligent interconnected framework for
public security and protection are the needs and requirements of the domain
experts. The purpose of the requirements collection is to understand the needs of
the users and the problems they try to solve. A common methodology for de ning
the use cases and requirements has been used, starting from the identi cation of
the most common security and protection incidents in the pilot location, the ways
of dealing with them up to now, and the di culties encountered in managing
them.</p>
        <p>KNOWLEDGE BASE REPOSITORY</p>
        <sec id="sec-3-1-1">
          <title>GraphDB</title>
        </sec>
        <sec id="sec-3-1-2">
          <title>SPARQL RDF4J</title>
          <p>Mobile
Apps</p>
          <p>Wearables</p>
          <p>Locati on</p>
          <p>The use cases show in Table 1 were identi ed and studied by running several
focus group sessions between stakeholders concerned with integrated risk
management (municipal authorities, volunteers etc.) focusing on their needs. In
addition, requirements were identi ed and prioritized through interview questions
and focus group sessions between domain experts, end-users, lawyers and
software engineers. Table 2 contains an indicative subset of the user requirements.
These user requirements are catalogued as [UR xzz ], where x is the identi er of
the use case scenario in which the requirement originated (see Table 1), and zz
is the serial number of the requirement.
4</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Data Integration</title>
      <p>The Knowledge Base Service (KBS) in Figure 1 is a central component of the
system architecture since it is the main interface to the DESMOS ontology also
referred to as the Knowledge Base (KB). The ontology is the knowledge
representation model for semantically representing notions pertinent to the project: (a)
location of the personnel, (b) location of automated external de brillators (AED)
(c) the RSSI observations made by mobile devices or xed nodes (i.e. hubs) both
listening for broadcasted addresses from Bluetooth Low Energy (BLE) devices
d) the results of the RSSI analysis service (i.e. Localization module), e) visitor
alert requests and f) personnel assignments to critical incidents.</p>
      <p>Hub</p>
      <p>subclassOf
Coordinates
coordinates
Location
Sensor
contains subclassOf
Sensor
BLE
rssi
RSSI
mac</p>
      <p>Agent
owns
Device
subclassOf
Transmitt</p>
      <p>er
MAC
subclassOf</p>
      <p>Human
hasRole</p>
      <p>Point
Irsse
u
lft
o</p>
      <p>Role
Visitor
subclassOfsubclassOf</p>
      <p>Volunteer
Notification
subclassOf
Action
requires</p>
      <p>Event
Trigger</p>
      <p>Beacon
takesAction
location
Volunteer
Observation</p>
      <p>Visitor
Notification
category
subclassOf
Health</p>
      <p>Issue
triggers
contains</p>
      <p>Category
subclassOf</p>
      <p>Loss
subclassOf
Missing
Person</p>
      <p>GEO</p>
      <p>FOAF</p>
      <p>Data
DESMOS
SSN/SOSA
have been reused. In addition, KBS features subscribe/publish capabilities to a
dedicated communication bus (MSB) allowing interactions of the KB with other
system components. In a sense, KBS accepts input from other components and
semantically integrates it into the ontology. It also handles the output of the
semantic reasoning process running on top of the KB and forwards the inferred,
high-level knowledge back to other interested system components.</p>
      <p>As shown in Figure 1, KBS consists of two sub-components, namely the
Knowledge Base Population (KBP) component, responsible for integrating data
into the KB, and the Events Crawler that is activated as soon as an event
is triggered. The interactions of the KBS with the KBR is achieved through
SPARQL queries or by using the RDF4J2 library tools.</p>
      <p>More speci cally, the communication layer allows the exchange of messages
in JSON format. These messages are analyzed by the KBS and are
semantically integrated into the appropriate classes considering the domain ontology.
The ontology itself as well as the data collected from the various system
components (e.g. sensors, mobile apps etc.) will be stored in the KB and the KBP
component is responsible for the data manipulation. Some indicative examples
of representing notions of the domain are given below (i.e. in RDF Triples). The
rst example depicts the representation of a Volunteer along with his location
consisting of the Volunteer's latest coordinates (i.e. latitude and longitude).</p>
      <p>Listing 1.1. RDF representation of a Volunteer in the KB.
&lt;volunteer/867325031117405/&gt; rdf:type desmos:Human ;
desmos:hasRole desmos:Volunteer ;
desmos:id "867325031117405"^^xsd:string ;
desmos:name "Volunteer_1."@en ;
sosa:hosts &lt;device/867325031117405&gt; ;
rdfs:label "Volunteer 1"@en .
geo:hasGeometry [geo:asWKT POINT(22.9954257 40.5654389)]</p>
      <p>Moreover, mobile devices belonging to Volunteers send regular messages
about registered wearable devices that are within their range. These messages are
also characterized by a unique identi er of the sending device that will allow the
information on the wearable device to be matched with the mobile device that
sent the message. Below is the representation of an rssi observation in the
ontology. Note how the last property in the representation, isObservedBy, matches
the corresponding observation with the mobile device.</p>
      <p>Listing 1.2. RDF representation of an RSSI Observation.
&lt;observation/E7:4E:C3:10:B4:D0/Obs_1&gt; rdf:type sosa:Observation;
sosa:observedProperty</p>
      <p>&lt;sensor/E7:4E:C3:10:B4:D0/powerSignalSensor/RSSI&gt;;
sosa:hasFeatureOfInterest &lt;powerSignal/E7:4E:C3:10:B4:D0&gt;;
sosa:madeBySensor &lt;sensor/E7:4E:C3:10:B4:D0/powerSignalSensor&gt;;
2 https://rdf4j.org/
sosa:resultTime "2019-05-29T12:52:01Z "^^xsd:dateTime;
sosa:usedProcedure &lt;MeasuringPowerSignal&gt;;
desmos:signal_strength "-51"^^xsd:double;
sosa:isObservedBy &lt;device/867325031117405&gt;.</p>
      <p>In addition, Visitors of the park may use the application that they have
previously installed in their mobile devices and send a request that will trigger
an Event. This request may refer either to a Health Issue or a Missing Person
situation. The following example depicts the representation of a Health Issue
event in the ontology.</p>
      <p>Listing 1.3. RDF representation of a Health Issue Event.
&lt;event/0a990cf5-8c3f-4484&gt; rdf:type desmos:HealthIssue;
desmos:id "0a990cf5-8c3f-4484"^^xsd:string ;
geo:hasGeometry [geo:asWKT POINT(22.9879934 40.57327)]</p>
      <p>It is worth mentioning that there is an initialization phase where the ontology
is populated with the volunteer pro les together with the necessary information
about their mobile devices, the exact location of the xed nodes that listen for
broadcasted addresses from BLE devices as well as the location of the AED
systems that are available in the area. Once this data are populated in the
ontology, the KBS can perform reasoning to infer new knowledge, and then
update the interested components.
5</p>
    </sec>
    <sec id="sec-5">
      <title>Rule-based Reasoning</title>
      <p>In addition, in order to search for incoming messages and handling their
semantic representation and integration into the KB, KBS also incorporates a
reasoning mechanism to infer underlying knowledge and discover connections
between ontology entities during various events occurring in space, such as the
disappearance of a person, or various medical incidents. This mechanism is
rulebased and consists of a set of SPARQL queries. These queries were constructed
by following the approach that is described in the following subsection.
5.1</p>
      <sec id="sec-5-1">
        <title>Competency Questions</title>
        <p>
          The user requirements in Table 2 were rst mapped to ontology's Competency
Questions (CQs). A competency question is a natural language sentence that
expresses a pattern for a type of question people expect an ontology to answer
[
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]. The answerability of CQs hence becomes a functional requirement of the
ontology. Based on the list of user requirements above, the ontology is able to
respond to several CQs, such as providing the location of a speci c person (e.g. a
patient, a lost child), or detect the closest AED. Following the methodology
proposed in [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ], we translated the list of CQs into respective SPARQL queries [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]
and evaluated the retrieved results. The following tables represent an indicative
set of CQs along with their SPARQL translation.
        </p>
        <p>Given a Visitor's request request that is related to UC 1 (i.e. request for
medical help) and consists of a request id and the coordinates of the user
requesting for help, the following queries (Queries 1.4, 1.5) calculate the nearest
Volunteer and the nearest AED respectively.</p>
        <p>Listing 1.4. (UC 1): Who is the nearest Volunteer?
SELECT ?imei WHERE {
?not rdf:type desmos:VisitorNotification ;
geo:hasGeometry [ geo:asWKT ?point1 ] ;
desmos:id ?not_id.
?volunteer desmos:hasRole desmos:Volunteer ;
geo:hasGeometry [ geo:asWKT ?point2 ] ;
desmos:imei ?imei.</p>
        <p>BIND((geof:distance(?point1, ?point2, uom:metre)) as ?dist) .
FILTER(?not_id = STR(not_id)) .
} ORDER BY ASC(?dist)
LIMIT 1</p>
        <p>Listing 1.5. (UC 1): What is the nearest AED?
SELECT ?aed_id WHERE {
?not rdf:type desmos:VisitorNotification ;
geo:hasGeometry [ geo:asWKT ?point1 ] ;
desmos:id ?not_id.
?aed rdf:type desmos:AED ;
geo:hasGeometry [ geo:asWKT ?point2 ] ;
desmos:id ?aed_id.</p>
        <p>BIND((geof:distance(?point1, ?point2, uom:metre)) as ?dist) .
FILTER(?not_id = STR(not_id)) .
} ORDER BY ASC(?dist)
LIMIT 1</p>
        <p>Similarly, given a Visitor's request that is related to UC 2 (i.e. request help
for lost child) and consists of the request id and the mac address of the child's
wearable device, the following queries (Queries 1.6, 1.7) are calculating the
latest observers of the missing child (i.e. Volunteers) and their distance from the
lost child respectively. More speci cally, query 1.6 nds the 3 nearest observers
while query 1.7 uses the latter information as input (i.e. through FILTER) and
calculates the respective distance of each observer.</p>
        <p>Note that the distance between the Volunteers and the lost child is
calculated based on RSSI-based localization techniques that are performed by the
Localization Module. More speci cally in UC 2 children are wearing wearable
equipment emitting a Radio Frequency (RF) signal with an RSSI that is
received from the the volunteers' devices as well as from several xed points (i.e.
hubs) scattered around the pilot area. The RSSI values are then used to
calculate the respective distance in meters (in the Localization module) and this
information is integrated into the KB and enriches the existing knowledge.</p>
        <p>The localization module analyzes the RSSI values based on a kalman ltering
and a regression method that transforms the RSSI values to distances. After that,
given the coordinates of the closest Volunteers and Hubs from the KB, namely
A; B; C with coordinates (x1; y1); (x2; y2); (x3; y3) respectively, whose distance
from the point of interest (i.e. lost child) is d1; d2; d3 respectively which was
estimated before, we can then calculate the coordinates of the point of interest
(x; y) using the following equations:</p>
        <p>Listing 1.6. (UC 2): Who are the child's latest observers?
SELECT ?imei (MAX(?time) as ?instanceTime) {
?s rdf:type sosa:Observation ;
sosa:isObservedBy ?o ;
desmos:isDataOf ?p ;
sosa:resultTime ?time .
?vol sosa:hosts ?o ;</p>
        <p>desmos:imei ?imei .
?p desmos:mac ?mac .</p>
        <p>FILTER(?mac = STR(mac))
} GROUP BY ?imei
ORDER BY DESC(?instanceTime)
LIMIT 3
Listing 1.7. (UC 2): What is the location of the lost child's observers and their
respective distance from the lost child?
SELECT ?imei ?lat ?long ?distance {
?s rdf:type sosa:Observation ;
sosa:isObservedBy ?o ;
desmos:isDataOf ?p ;
sosa:resultTime ?time ;
desmos:distance ?distance .
?vol sosa:hosts ?o ;
desmos:imei ?imei ;
desmos:lat ?lat ;
desmos:long ?long .
?p desmos:mac ?mac .</p>
        <p>FILTER(?imei = STR(imei) &amp;&amp; ?time = time)
}
6</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>Conclusion</title>
      <p>In this paper, we have discussed and demonstrated an ontology-based reasoning
framework for the management of critical incidents in public events. We have
presented the main components of the DESMOS semantic reasoning framework
and how this has been incorporated in the DESMOS main framework. For future
work, the framework will be tested and validated in two pilots in two di erent
public places which protection and security challenges are higher.
7</p>
    </sec>
    <sec id="sec-7">
      <title>Acknowledgements</title>
      <p>This research has been co- nanced by the European Union and Greek national
funds through the Operational Program Competitiveness, Entrepreneurship and
Innovation, under the call RESEARCH-CREATE-INNOVATE (project code:
T1EDK-03487).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Compton</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <article-title>The SSN ontology of the W3C semantic sensor network incubator group</article-title>
          ,
          <source>J. Web Semant</source>
          .
          <volume>17</volume>
          ,
          <issue>25</issue>
          {
          <fpage>32</fpage>
          ,
          <year>2012</year>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Janowicz</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Haller</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Cox</surname>
            ,
            <given-names>S.; Le</given-names>
          </string-name>
          <string-name>
            <surname>Phuoc</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ; Lefrancois,
          <string-name>
            <surname>M.</surname>
          </string-name>
          <article-title>SOSA: A lightweight ontology for sensors, observations, samples, and actuators</article-title>
          , J. Web Semant.,
          <volume>17</volume>
          , 1{
          <fpage>10</fpage>
          ,
          <year>2018</year>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Raimond</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          <string-name>
            <surname>Event Ontology</surname>
          </string-name>
          , Motools.sourceforge.net.
          <year>2019</year>
          , Available online: http://motools.sourceforge.net/event/event.
          <source>html (accessed on 31 January</source>
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Brickley</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Miller</surname>
            ,
            <given-names>L. FOAF</given-names>
          </string-name>
          <article-title>Vocabulary Speci cation</article-title>
          , Motools, Available online: http://xmlns.com/foaf/spec/ (accessed on 31
          <source>January</source>
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Matheus</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Kokar</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Baclawski</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <article-title>A core ontology for situation awareness</article-title>
          ,
          <source>In Proceedings of the Sixth International Conference of Information Fusion</source>
          , Cairns, Australia,
          <volume>8</volume>
          {
          <fpage>11</fpage>
          ,
          <string-name>
            <surname>July</surname>
            <given-names>2003</given-names>
          </string-name>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Bobek</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ; Nalepa,
          <string-name>
            <surname>G.</surname>
          </string-name>
          <article-title>Uncertain context data management in dynamic mobile environments</article-title>
          , In Future Generation Computer Systems; Elsevier: Amsterdam, The Netherlands, , pp.
          <volume>110</volume>
          {
          <fpage>124</fpage>
          , (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Pandey</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bansal</surname>
            ,
            <given-names>S. K.</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>A Semantic</given-names>
            <surname>Safety</surname>
          </string-name>
          <article-title>Check System for Emergency Management</article-title>
          .
          <source>Open Journal of Semantic Web (OJSW)</source>
          ,
          <volume>4</volume>
          (
          <issue>1</issue>
          ),
          <fpage>35</fpage>
          -
          <lpage>50</lpage>
          , (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Hristoskova</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ongenae</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>De Turck</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          <article-title>Semantic reasoning for intelligent emergency response applications</article-title>
          ,
          <source>In 2013 11th IEEE International Conference on Industrial Informatics (INDIN)</source>
          (pp.
          <fpage>547</fpage>
          -
          <lpage>554</lpage>
          ), IEEE, (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Ahmad</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Othman</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fauzan</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Ilyas</surname>
            ,
            <given-names>Q. M.</given-names>
          </string-name>
          <article-title>A Semantic Ontology for Disaster Trail Management System,</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Kontopoulos</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mitzias</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dasiopoulou</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mo</surname>
            <given-names>graber</given-names>
          </string-name>
          , J.,
          <string-name>
            <surname>Mille</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hertweck</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          , ... &amp;
          <string-name>
            <surname>Kompatsiaris</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          <article-title>Applying Semantic Web Technologies for Decision Support in Climate-Related Crisis Management</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Uschold</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Gruninger</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <article-title>Ontologies: Principles, methods and applications, The knowledge engineering review</article-title>
          ,
          <volume>11</volume>
          (
          <issue>2</issue>
          ),
          <fpage>93</fpage>
          -
          <lpage>136</lpage>
          , (
          <year>1996</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Zemmouchi-Ghomari</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Ghomari</surname>
            ,
            <given-names>A. R.</given-names>
          </string-name>
          <article-title>Translating natural language competency questions into SPARQLQueries: a case study</article-title>
          .
          <source>In The First International Conference on Building and Exploring Web Based Environments</source>
          (pp.
          <fpage>81</fpage>
          -
          <lpage>86</lpage>
          ), (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Harris</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Seaborne</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Prud'hommeaux</surname>
          </string-name>
          ,
          <source>E. SPARQL 1</source>
          .
          <article-title>1 query language</article-title>
          ,
          <source>W3C recommendation</source>
          ,
          <volume>21</volume>
          (
          <issue>10</issue>
          ),
          <volume>778</volume>
          , (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>