# Achieving Semantic Interoperability in Emergency Management Domain

Mert GençTürk, Enver Evci, Arda Guney, Yildiray Kabak, Gokce Erturkmen

► To cite this version:

Mert GençTürk, Enver Evci, Arda Guney, Yildiray Kabak, Gokce Erturkmen. Achieving Semantic Interoperability in Emergency Management Domain. 12th International Symposium on Environmental Software Systems (ISESS), May 2017, Zadar, Croatia. pp.279-289, 10.1007/978-3-319-89935-0_23 . hal-01852611

HAL Id: hal-01852611

https://inria.hal.science/hal-01852611

Submitted on 2 Aug 2018

HAL is a multi-disciplinary open access
archive for the deposit and dissemination of sci-
entific research documents, whether they are pub-
lished or not. The documents may come from
teaching and research institutions in France or
abroad, or from public or private research centers.

L'archive ouverte pluridisciplinaire HAL, est
destinée au dépôt et à la diffusion de documents
scientifiques de niveau recherche, publiés ou non,
émanant des établissements d'enseignement et de
recherche français ou étrangers, des laboratoires
publics ou privés.

<figure><img src="image_1.png" /></figure>
# Achieving Semantic Interoperability in Emergency Management Domain

Mert Genççek<fnref n="1" />,<fnref n="2" />, Enver Evci<fnref n="1" />,<fnref n="2" />, Arda Guney<fnref n="1" />,<fnref n="2" />, Yildiray Kabak<fnref n="1" />, Gökçe B. Laleci Er-turkmen<fnref n="1" />

**Abstract.** This paper describes how semantic interoperability can be achieved in emergency management domain where different organizations in different domains should communicate through a number of distinct standards to manage crises and disasters effectively. To achieve this goal, a common ontology is defined as lingua franca and standard content models are mapped one by one to the ontology. Then, information represented in one standard is converted to another according to the mappings and exchanged between parties.

**Keywords:** Semantic Interoperability · Semantic Web · Ontology · Emergency Management

## 1 Introduction

Common standard interfaces allow data communication among disparate systems. By complying with a standard interface, each system can exchange data with every other compliant system. Otherwise the interoperability of the systems can be quite challenging, technologically complex, time consuming and expensive. Emergency management is a multi-discipline domain where effective management of crises and disasters requires communication of different organizations in different domains such as government, health, media, and military. Although each of these domains has its own well-established standards, not all emergency responding parties conform to the same set of standards, which creates a crucial interoperability challenge. Furthermore, standards have many optional fields and different versions. Even if only one standard is used by two different systems, interoperability of them can still be problematic due to misinterpretation of optional fields or usage of different versions [1].

Semantic Interoperability has been an active research and development area in various domains such as eHealth and eBusiness. There are several completed and ongoing work in these domains for the semantic interoperability of electronic documents. OASIS Semantic Support for Electronic Business Document Interoperability (SET) TC [2] is one of them and its basic idea is to explicate the semantics of different but overlapping electronic business document standards as ontologies and then provide semantic mediation among these ontologies. OASIS SET TC approach has been proven to be

<footnote n="1">¹SRDC Software Research & Development and Consultancy Corp., Ankara, Turkey</footnote>

<footnote n="2">²Department of Computer Engineering, Middle East Technical University, Ankara, Turkey
mert@srdc.com.tr</footnote>
useful and effective in several studies such as iSURF project, where a Semantic Interoperability Service Utility were developed by following this approach for the exchange of supply chain planning information documents [3].

In order to solve the interoperability problem, in European Commission supported C2-SENSE project [4] which aims to develop a profile based Emergency Interoperability Framework by the use of existing standards and semantically enriched Web services, we take this engineering approach and apply it to the emergency management domain to implement semantic mediation mechanisms to be able to harmonize information conforming to different but overlapping emergency standards. In this regard, in this paper, we present a Semantic Interoperability Suite which enables the information exchange between emergency management domain applications through a central layer instead of one-to-one transformations between several different content models, by developing a common ontology. Common Data Elements (CDEs) that have been elicited within this study underpin the common ontology which can be considered as the semantic dictionary of the interoperating applications.

# 2 Technology Description

## 2.1 Standards

The Emergency Data Exchange Language (EDXL), developed by OASIS International Open Standards Consortium, is a suite of XML-based messaging standards that facilitate emergency information sharing between government entities and the full range of emergency-related organizations [5]. EDXL standardizes messaging formats for communications between these parties. EDXL includes several individual standards, that are Common Alerting Protocol (EDXL-CAP), Distribution Element (EDXL-DE), Hospital AVavailability Exchange (EDXL-HAVE), Resource Messaging (EDXL-RM), Reference Information Model (EDXL-RIM), Situation Reporting (EDXL-SitRep), Tracking Emergency Patients (EDXL-SitRep).

The Common Alerting Protocol [6] is an XML-based data format for exchanging public warnings and emergencies between alerting technologies. CAP allows a warning message to be disseminated simultaneously over many warning systems to many applications.

Distribution Element [7] is used as a container that facilitate the routing of any properly formatted XML emergency message to recipients.

EDXL-HAVE [8] is a document format for exchanging information on status of a hospital, its services, and its resources such as bed capacity, service availability etc.

Resource Messaging [9] defines specific message types supporting the major communication requirements for allocation of resources across the emergency incident lifecycle.

EDXL-SitRep [10] is an XML-based data format for transmitting timely available situation reports, incident or event information, and operational picture.

In much the same way that HTML and HTTP standards enable the exchange of any type of information on the Web, The Open Geospatial Consortium's (OGC) Sensor Web Enablement Initiative (SWE) [11] is focused on developing standards to enable
the discovery of sensors and corresponding observations, exchange, and processing of
sensor observations, as well as the tasking of sensors and sensor systems.

## 2.2 ISO/IEC 11179, Semantic Metadata Registry and IHE Data Element Exchange

ISO/IEC 11179 is an international standard developed with the aim of providing a metadata-driven data exchange in heterogeneous environments. Combining principles of semantic theory and data modelling, the standard defines the representation of metadata in a metadata registry [12].

In our study, we employ an ISO/IEC 11179 compliant Semantic Metadata Registry (MDR) to maintain metadata of data elements (e.g. location, alert, observation) and communicate with it via the IHE Data Element Exchange (DEX) profile, which we authored [13]. DEX provides a standardized way of querying data element metadata, and allows dynamic mappings between data elements such as EDXL data elements to their OGC equivalents when complemented with extraction specifications (e.g. XPATH, SQL scripts) maintained in Semantic MDR.

# 3 Methodology & Implementation

During the implementation of Semantic Interoperability Suite, first information do-
main has been carefully analysed and following standards corresponding to emergency
management have been identified as relevant [14].

* EDXL-SitRep (Situation Reporting)

* EDXL-RM (Resource Messaging)

* EDXL-HAVE (Hospital Availability Exchange)

* EDXL-TEP (Tracking of Patients)

* EDXL-CAP (Common Alerting Protocol)

* OGC SensorML (Sensor Modeling Language)

* OGC O&M (Observations and Measurements)

The common ontology has been created based on the knowledge that was gained as a result of this analysis. In this regard, first a number of Common Data Elements (CDEs) which can be considered as ontology resources have been defined and stored in Semantic MDR. CDEs are the smallest meaningful data container in a context. They can be regarded as the semantic dictionary of the interoperating application.

**Fig. 1** illustrates an example decomposition of a CDE which refers to birth date in-
formation of a person. As shown in the figure, the concept of the CDE and the repre-
sentation are separate in the metamodel. In the given example, “Person” is the Object
Class and “Date of Birth” is the property together which constitute the concept of “Per-
son.DateOFBirth”. This is the concept of the data element regardless of its representa-
tion. The other main concepts for which CDEs are defined can be listed as address,
location, resource, report, alert, and observation (sensor measurement). After CDEs are
defined, a common ontology in OWL (Web Ontology Language) format is generated by following the OASIS SET TC approach.

<figure><img src="image_2.png" /><figcaption>**Fig. 1.** An example of decomposition of a Common Data Element: Person.DateOfBirth.Date</figcaption></figure>

In the next step, standard content models listed above have been mapped to the common ontology via extraction specifications so that data represented in one standard format can be converted to another. Extraction specifications are for locating relevant data element in the corresponding standard content model. As all current standards are XML based, extraction specifications are defined as XPATH queries in our system. **Table 1** below presents three different extraction specifications of EDXL-SitRep, EDXL-CAP and OGC-O&M standards for "LocationByCoordinates.Latitude" data element.

<table><caption>**Table 1.** Data Element and Extraction Specifications</caption><thead><tr><th colspan="2">Data Element</th></tr></thead><tbody><tr><td>Property</td><td>LocationByCoordinates.Latitude</td></tr><tr><td>Data Type</td><td>characterstring</td></tr><tr><td>Definition</td><td>Measure of the latitude of the coordinate in degrees</td></tr><tr><th colspan="2">Extraction Specification</th></tr><tr><td>EDXL-SitRep</td><td>/element(*,ResourceDetailType)/reportToLocation/ct:EDXLGeo-PoliticalLocation/ct:geoCode/ct:value</td></tr><tr><td>EDXL-CAP</td><td>/cap:alert/cap:info/cap:area/cap:circle</td></tr><tr><td>OGC-O&M</td><td>/om:featureOfInterest/gml:AbstractFeature/gml:bound-edBy/gml:Envelope/gml:coordinates</td></tr></tbody></table>

C2-SENSE Semantic Interoperability Suite enables domain experts to define extraction specifications only once, then the conversion between content models is done au-
tomatically according to these specifications. It is possible to define extraction specifications for any number of standard content models. There is no need to make an update on the system, when specifications for a new content model is going to be added.

Overall architecture of C2-SENSE Semantic Interoperability Suite is illustrated in **Fig. 2**. In Semantic Interoperability Suite, a Semantic MDR Tool is provided to users as a graphical user interface (GUI) to facilitate the definition of CDEs and extraction specifications. Semantic MDR Tool can be considered a web-based metadata management and data modelling tool to create and maintain CDEs collaboratively either based on imported standard content models or from scratch [15]. Given a standard format, it is able to list the data elements included in it; given the data element list, it can also provide mappings of elements to a specified target standard format.

<figure><img src="image_3.png" /><figcaption>**Fig. 2.** Architecture of C2-SENSE Semantic Interoperability Suite</figcaption></figure>

Semantic Mediator is the component in Semantic Interoperability Suite fulfilling the duty of converting data represented in one standard to a data represented in another standard. This functionality is satisfied thanks to Semantic MDR and IHE DEX profile. When the system receives a request of conversion, it fetches common ontology (in other words CDEs) and corresponding extraction specifications from Semantic MDR using DEX profile. If the source and target content models are available in the registry, e.g. EDXL-SitRep as the source and OGC-O&M as the target, conversion is done automatically by Semantic Mediator according to pre-defined extraction specifications. Semantic Mediator is provided to outside world through a RESTful API.
## 4 Example Usage

In C2-SENSE project, an Emergency Domain Interoperability Framework, which Semantic Interoperability Suite is part of, has been developed. This framework has been validated by a realistic flood scenario in Puglia region of Italy. In this section, we present an example usage of Semantic Interoperability Suite in this scenario.

It has been raining in Puglia region for several days and the sensors located near Fortore river measures the water level exceeding the threshold value. Therefore, Regional Functional Center of Puglia is alerted and emergency plan for flood situation is started to be applied. As part of this plan, people living near flood area is evacuated, houses, healthcare services and equipment are provided, some roads are blocked and volunteers are involved to follow the situation on field. Meanwhile, a car accident occurred at the 15th km of “Strada Statale 100”. Immediate intervention of Fire Brigade is required. Therefore, Innova Puglia, who is the technology provider of Civil Protection Service of Puglia Region, alerts Fire Brigade regarding the accident. Fire Brigade system uses the EDXL-CAP as the data format and Innova Puglia system is able to produce message in this format. Hence, the following XML message (for the sake of simplicity, namespaces have been removed in the XML messages) is generated by Innova Puglia and sent to Fire Brigade successfully with no additional effort.

```xml
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<alert xmlns="urn:oasis:names:tc:emergency:cap:1.2">
  <identifier>20161206.2.71.1</identifier>
  <sender>mailaddress@mailaddress.com</sender>
  <sent>2016-12-06T10:45:40+01:00</sent>
  <status>Actual</status>
  <msgType>Alert</msgType>
  <scope>Private</scope>
  <code>CAP-IT-VF:0.1</code>
  <info>
    <language>it-IT</language>
    <category>Transport</category>
    <event>Car accident with rollover</event>
    <urgency>Immediate</urgency>
    <severity>Unknown</severity>
    <certainty>Unknown</certainty>
    <effective>2016-12-06T10:45:40+01:00</effective>
    <senderName>INNOVAPUGLIA</senderName>
    <headline>Road vehicle fuel transport accident</headline>
    <description>Traffic accident caused by the combination of vehicles overturning tractor with registration numbers AA00AA and BB11BB. Dangerous goods: UN number 33, Kemler code 1203.</description>
  </info>
</alert>
```
<instruction>Prompted intervention by the local
fire brigade command</instruction>
<area>
<areaDesc>Strada Statale 100, km 15</areaDesc
esc>
<circle>41.003822,16.913184 0.01</circle>
</area>
</info>
</alert>

After Fire Brigade receives the alert message, it needs to inform corresponding local authorities about the situation, and this message should be sent in EDXL-SitRep format. However, Fire Brigade system is only able to produce and retrieve messages in EDXL-CAP format. A solution to this problem could be updating the Fire Brigade system so that it can support exchanging documents in EDXL-SitRep format as well. However, this requires a lot of work and is impossible to do during the emergency situation. Instead of this, Fire Brigade uses the Semantic Interoperability Suite of C2-SENSE system to convert the EDXL-CAP message presented above to EDXL-SitRep message automatically. The result of this operation is the following XML.
```xml
</personName>
</personDetails>
<timeValue>2016-12-06T10:45:40+01:00</timeValue>
</authorizedBy>
<reportPurpose>Alert</reportPurpose>
<reportNumber>1</reportNumber>
<reportVersion>Final</reportVersion>
<forTimePeriod>
<fromDateTime>2016-12-06T10:45:40+01:00</fromDateTime>
<toDateTime>2016-12-06T10:45:40+01:00</toDateTime>
</forTimePeriod>
<reportTitle>Road vehicle fuel transport accident</reportTitle>
<incidentID>T20161206.2.71.1</incidentID>
<originatingMessageID>CAP-IT-VF:0.1</originatingMessageID>
<urgency>Immediate</urgency>
<reportConfidence>NoConfidence</reportConfidence>
<severity>Unknown</severity>
<actionPlan>Transport</actionPlan>
<report xsi:type="SituationInformationType">
<primaryIncidentInformation>
<incidentName>Strada Statale 100, km 15</incidentName>
</geographicSize>
<size>1</size>
</geographicSize>
<incidentLocation>
<EDXLGeoPoliticalLocation>
<geoCode>
<valueListURI>circle</valueListURI>
<value>41.003822,16.913184 0.01</value>
</geoCode>
</EDXLGeoPoliticalLocation>
</incidentLocation>
</primaryIncidentInformation>
<extension>
<parameter>
<nameURI>description</nameURI>
<value>Traffic accident caused by the combination of vehicles overturning tractor with registration numbers AA00AA and BB11BB. Dangerous goods: UN number 33, Kemler code 1203.</value>
</parameter>
</</parameter>
```
```xml
</extension>
<extension>
  <parameter>
    <nameURI>instruction</nameURI>
    <value>Prompted intervention by the local fire brigade command</value>
  </parameter>
</extension>
<extension>
  <parameter>
    <nameURI>event</nameURI>
    <value>Car accident with rollover</value>
  </parameter>
</extension>
<extension>
  <parameter>
    <nameURI>status</nameURI>
    <value>Actual</value>
  </parameter>
</extension>
<extension>
  <parameter>
    <nameURI>scope</nameURI>
    <value>Private</value>
  </parameter>
</extension>
<extension>
  <parameter>
    <nameURI>certainty</nameURI>
    <value>Unknown</value>
  </parameter>
</extension>
</report>
</sitRep>
```

In technical point of view, for instance, in CAP message, latitude and longitude information is provided in `"/cap:alert/cap:info/cap:area/cap:circle"` element (see **Table 1**). In order to present this information in SitRep message, Semantic Mediator of Semantic Interoperability Suite performs following actions:

1. Retrieve CDEs and extraction specifications from Semantic MDR.

2. Find the corresponding Common Data Element for the XPATH `"/cap:alert/cap:info/cap:area/cap:circle"`, that is `LocationByCoordinates.Latitude characterstring`
3. Find the corresponding XPATH definition of SitRep for this Common Data Element, that is "/element(*,ResourceDetailType)/reportToLocation/ct:EDXLGeoPolitical-Location/ct:geoCode/ct:value"

4. Place the information.

# 5 Conclusion

In order to manage crises effectively, interoperability of different systems using dis-
persed standards is crucial. One way to provide interoperability among these systems
is to update the existing software so that one system can generate messages in all the
desired formats. It is obvious that this requires a lot of work and should be done for
every single system. In this regard, C2-SENSE Semantic Interoperability Suite is a
powerful mechanism since it enables organizations to make such conversions between
emergency domain standards automatically without making any updates on their own
systems.

Currently, C2-SENSE Semantic Interoperability Suite is able to make conversion
among EDXL-SitRep, EDXL-RM, EDXL-HAVE, EDXL-CAP, OGC SensorML and
O&M standards. Feasibility and usability of the system is currently being tested in a
realistic flood scenario in Puglia Region of Italy within the scope of C2-SENSE Project.

# 6 Acknowledgements

The work presented in this paper is achieved in the scope of C2-SENSE project [4]
supported by the European Community's Seventh Framework Programme (FP7/2007-
2013) under grant agreement number 607729.

# 7 References

1. Chen, D., & Daclin, N. (2006, March). Framework for enterprise interoperability. In *Proc. of IFAC Workshop E12N* (pp. 77-88).

2. OASIS Semantic Support for Electronic Business Document Interoperability (SET) Technical Committee. (n.d.). Retrieved January 16, 2017, https://www.oasis-open.org/committees/set/charter.php

3. Kabak, Y., Dogac, A., Ocalan, C., Cimen, S., & Laleci, G. B. (2009, October). iSURF Semantic Interoperability Service Utility for Collaborative Planning, Forecasting and Replenishment. In the *Proc. of the eChallenges 2009 Conference*.

4. C2-SENSE Project - Interoperability Profiles for Command/Control Systems and Sensor Systems in Emergency Management. Retrieved January 16, 2017. http://c2-sense.eu/

5. Emergency Data Exchange Language (EDXL). Retrieved January 16, 2017. https://en.wikipedia.org/wiki/EDXL

6. EDXL Common Alerting Protocol (EDXL-CAP) Specification. Retrieved January 16, 2017. http://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.html

7. EDXL Distribution Element (EDXL-DE) Specification. Retrieved January 16, 2017. http://docs.oasis-open.org/emergency/edxl-de/v1.0/EDXL-DE_Spec_v1.0.pdf
8. EDXL Hospital AVavailability Exchange (EDXL-HAVE) Specification. Retrieved January 16, 2017. http://docs.oasis-open.org/emergency/edx1-have/os/emergency_edxl_have-1.0-spec-os.pdf

9. EDXL Resource Messaging (EDXL-RM) Specification. Retrieved January 16, 2017. http://docs.oasis-open.org/emergency/edx1-rm/v1.0/os/EDXL-RM-v1.0-OS.pdf

10. EDXL Situation Reporting (EDXL-SitRep) Specification. Retrieved January 16, 2017. https://docs.oasis-open.org/emergency/edx1-sitrep/v1.0/cs01/edx1-sitrep-v1.0-cs01.html

11. OGC Sensor Web Enablement (SWE). Retrieved January 16, 2017. http://www.opengeo-spatial.org/ogc/markets-technologies/swe

12. ISO/IEC 11179-3, Information technology – Metadata registries (MDR) – Registry meta-model and basic attributes. Retrieved January 16, 2017, http://metadata-standards.org

13. IHE Quality, Research and Public Health Technical Framework Supplement Data Element Exchange (DEX). Retrieved January 16, 2017, http://ihe.net

14. Božić, B., Genççek, M., Duro, R., Kabak, Y., & Schimak, G. (2015, March). Requirements Engineering for Semantic Sensors in Crisis and Disaster Management. In *International Symposium on Environmental Software Systems* (pp. 397-406). Springer International Publishing.

15. Semantic MDR Tool. Retrieved January 16, 2017, http://www.srdc.com.tr/semantic-mdr/