<!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>ROC: An Ontology for Country Responses towards COVID-19</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>l Al Qun</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>lph S</string-name>
          <email>ralph.schaefermeier@fokus.fraunhofer.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Silvio P</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Fraunhofer FOKUS</institution>
          ,
          <addr-line>Kaiserin-Augusta-Allee 31, 10589 Berlin</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The ROC ontology for country responses to COVID-19 provides a model for collecting, linking and sharing data on the COVID-19 pandemic. It follows semantic standardization (W3C standards RDF, OWL, SPARQL) for the representation of concepts and creation of vocabularies. ROC focuses on country measures and enables the integration of data from heterogeneous data sources. The proposed ontology is intended to facilitate statistical analysis to study and evaluate the e ectiveness and side e ects of government responses to COVID-19 in di erent countries. The ontology contains data collected by OxCGRT from publicly available information. This data has been compiled from information provided by ECDC for most countries, as well as from various repositories used to collect data on COVID-19.</p>
      </abstract>
      <kwd-group>
        <kwd>Ontology Engineering</kwd>
        <kwd>Semantic Web Technologies</kwd>
        <kwd>Covid19 Ontology</kwd>
        <kwd>Novel Coronavirus Ontology</kwd>
        <kwd>Covid-19 Responses</kwd>
        <kwd>Pandemic Country Responses</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Almost all countries are a ected by the (second wave) COVID-19 pandemic.
Many organisations have setup systems and projects to collect and publish global
data on the impact of the virus allowing to monitor the pandemic. Most countries
have implemented responsive measures as reaction to COVID-19. The impact
of the pandemic and policies implemented di er widely among countries.
Meanwhile data on the infection spread and government responses during the rst
phase of the pandemic (March to July 2020) is available to enable research on
the e ects of individual policies.</p>
      <p>Policy makers face tough decisions on how to deal with the pandemic, since
responses considered most e ective have also signi cant negative impacts on
economy and social life. This is strongly re ected in the measures implemented
by the countries. The policies implemented and the reactions of society vary
greatly among countries and cities. While many people support their government
strategy, others reject measures included. Empirical studies need to be conducted
to support decision-makers and information campaigns. Which responses have
proven to be e ective in containing COVID-19 and what are their e ects on the
economy and society? are questions that apply to individual countries as well as
to cultural, political and geographical regions.</p>
      <p>To enable empirical research, global data on infections, recoveries, death rates
and policies implemented in various countries and regions is published via
various sources. The challenge for data scientists and epidemiologists is that these
data sources do not share common standards or methodologies for reporting
their data. The reported data is in uenced by time zones/holidays, di erent
political and/or economic incentives, variation in counting methods1, discovered
/ undiscovered numbers, etc. In addition, in many cases country's reports
differ depending on the reporting institute. For example, the numbers of infected
people in Germany di ers between Johns Hopkins Coronavirus Resource
Center2 (USA) and Robert Koch institute3 (GER). Unfortunately, this di erence is
not comprehensible. To study this valuable information and perform statistical
analysis on it, a common standard for harmonizing and reporting the data is
required.</p>
      <p>
        Many researchers are taking up this challenge, and the rst solutions to this
problem have already been developed. The COviD-19 ontology (CODO) is an
ontology for organizing cases data and patient information and aims to use the
technology of knowledge graphs to analyse the pandemic [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Our work follows the
same approach to ontology design and has a common motivation. Nevertheless,
it focuses on areas not yet covered, government responses to the pandemic, and
therefore this work is equally unique in this eld. The ontology developed in this
paper addresses the following goals:
serve as a reference scheme for use in reporting COVID-19 related data.
provide a common conceptualization and thereby abstract from
heterogeneous structures of existing sources of (static) data and provide a common
linking schema, which is essential for data accessibility.
provide a de ned data structure with a xed semantics for further analysis
or monitoring systems.
o er a supplement of the existing ontologies in order to build a common
global data model.
o er a template to organize data from other pandemics or nationwide events
or measures.
(as a follow-up outcome) enable countries to make coordinated strategic
decisions while avoiding lockdowns and their entailed risks
      </p>
      <p>For the ontology development process, we followed a hybrid approach, which
is driven by available data on the one hand and questions of interest that should
be answerable by the ontology on the other hand. We mainly collected data from
1 cause and place of death -at home or in
hospital2 https://coronavirus.jhu.edu/map.html
3 https://rki.de/DE/Content/InfAZ/N/Neuartiges Coronavirus/Fallzahlen.html
OxCGRT4, ILO5 and ECDC6. ECDC provides data on infection rates, OxCGRT
systematically monitors government actions related to the pandemic and ILO
provides economic indicators focused on the labour market. The modeling of the
data consisted of the following steps: manual review and merging of the data.
Concepts were extracted and linked using logical relationships. To design and
create the ontology, we used Protege and then ingested the data based on the
ROC ontology.</p>
      <p>The remainder of the paper is organized as follows: Section 2 contains a review
on related work. Section 3 describes the development methodology. Section 4
introduces the ROC ontology and its concepts. Section 5 describes the data
ingestion process and querying capabilities. Section 6 concludes the paper with
a short summary and future work.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Related Work</title>
      <p>This section provides an overview on related work investigating ontologies related
to diseases, especially relevant to COVID-19.</p>
      <p>
        The Human Disease Ontology (DO)7 classi es thousands of human diseases
moving to a multi-editor model in web ontology language enabling collaboration
of several working groups, and has recently been extended by DOID8
including COVID-19 concepts [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. The Infectious Disease Ontology (IDO) [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] and the
Ontology of Coronavirus Infectious Disease (CIDO) [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] de ne vocabulary
relating to infectious diseases such as u, malaria, and brucellosis. CIDO additionally
represents comparative analysis of COVID-19 and other diseases wrt. symptoms,
drugs, clinical trials etc.
      </p>
      <p>
        One of the most relevant work is the Ontology for cases and patient
information (CODO)9, which initiated the development of CIDO. It provides a
standards-based and comprehensive open source model for data collection on
the COVID 19 pandemic. The ontology is very well suited for the integration
of data from heterogeneous data sources and thus represents one of the major
inspirations for our work. Furthermore, our methodology follows the procedure
for term de nition described in the work. This is based on the reuse of concepts
from other leading vocabularies and the use of the W3C standards RDF, OWL,
SWRL and SPARQL. The evaluation of CODO was conducted on the basis of
data received from the Indian government [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
      <p>
        Of course, the ontologies (COVIDCRFRAPID)10 of the World Health
Organization (WHO) as data model for the case COVID-19 RAPID, the ontologies
Kg-COVID-1911 for the creation of knowledge graphs including SARS-COV-2
4 https://www.bsg.ox.ac.uk/
5 https://www.ilo.org/global/lang{en/index.htm
6 https://www.ecdc.europa.eu/
7 http://www.disease-ontology.org
8 https://disease-ontology.org/term/DOID:11725/
9 https://github.com/biswanathdutta/CODO
10 https://bioportal.bioontology.org/ontologies/COVIDCRF RAPID
11 https://github.com/Knowledge-Graph-Hub/kg-covid-19
and the ontology Linked-Data COVID-1912 are also relevant. These ontologies
contain conceptualizations (and partially instance data) related to COVID-19
cases and are primarily aimed at software applications such as question &amp;
answering or monitoring dashboards [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. However, to our knowledge, the work
described in this paper is the rst work to take into account government responses
and link them to epidemiolical data, such as case data.
      </p>
      <p>All these works support the containment of the pandemic, but more
importantly, the works build on and complement each other. The focus so far has been
mainly on gathering cases, symptoms and information from infected people, for
example to identify and isolate hot spots. However, one eld has not been
covered so far, namely the eld of countries government responses. It is precisely
this knowledge gap that our work with the ROC ontology aims to ll.</p>
      <p>In the next sections we describe the methodology for the development of
the ROC ontology based on the state-of-the-art principles, its structure and
evaluation.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Methodology</title>
      <p>The artifact created and investigated in this work is an ontology authored using
the Web Ontology Language 2 (OWL 2)13, the semantics of which are based on
description logics.</p>
      <p>The main purpose of the ontology, as pointed out in Section 1, is the
integration of public data on national responses to the COVID-19 pandemic and
to provide a layer of interoperability between di erent and diverse resources as
well as to answer interesting questions from the data. The development of the
ontology was therefore bottom-up data-driven as well as top-down application
driven. A further requirement was the integration of existing ontologies in the
domain of COVID-19 in order to avoid redundancy as well as to leverage
knowledge gained from the integration of existing knowledge (such as the combination
of data about national responses with case data).</p>
      <p>
        A multitude of ontology development methods exist, comprising, but not
limited to METHONTOLOGY [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] and On-To-Knowledge [
        <xref ref-type="bibr" rid="ref11">9</xref>
        ], both of which provide
general ontology development guidelines and principles, Diligent [
        <xref ref-type="bibr" rid="ref13">11</xref>
        ], which
denes an argumentation-based development process as well as agile development
methods, such as RapidOWL [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
      </p>
      <p>The selection of the ontology development method was driven by the
nonfunctional requirements to (a) integrate existing data sources and (b) integrate
existing ontological sources as well as (c) by content-related requirements, which
are formulated in the form of competency questions.</p>
      <p>
        We decided to use the NeOn methodology [
        <xref ref-type="bibr" rid="ref10">8</xref>
        ], since it provides guidelines for
either of the above-mentioned requirement types and allows combining them.
NeOn identi es a set of scenarios and provides an ontology development method
12 https://zenodo.org/record/3765375#.XraWJmgzbIU
13 https://www.w3.org/TR/owl2-overview/
for each scenario. The scenarios applicable to the development of the ROC
ontology are scenario 1 \From speci cation to implementation" (which involves
requirement engineering and is suitable for our non-functional requirement (c)),
scenario 2 \Reusing and re-engineering non-ontological resources" , as we use
external, non-ontological data sources (item (a)) and scenario 3 \Reusing
ontological resources", since we reuse concepts from the CODO ontology and align
concepts derived from the external data sources with existing ones in the CODO
ontology manually (item (b)).
      </p>
      <p>The ontology development process therefore consists of three main
activities, which start in parallel and which are divided into subtasks, some of which
interact (see Figure 1):</p>
      <p>Requirements Analysis Data-driven development</p>
      <p>CODO integration</p>
      <p>T1.1-1.3
Purpose, scope,
language, users</p>
      <p>T1.4-1.7
Requirements /</p>
      <p>CQs</p>
      <p>T1.8
Terminology
extraction</p>
      <p>T2.1
Data gathering</p>
      <p>T2.2
Conceptual
abstraction</p>
      <p>T2.3
Information
exploration</p>
      <p>T2.7-2.8
Formalization,
implementation</p>
      <p>ROC</p>
      <p>T2.4-2.6
Transformation and</p>
      <p>refinement
CODO Alignment</p>
      <p>T3.1-3.3
External statement
selection</p>
      <p>T3.4
External statement
mapping</p>
      <p>T3.5</p>
      <p>Consistency check</p>
      <p>Activities 2 and 3 resulted in the ROC ontology, while activity 3 resulted in
a set of import and mapping axioms (which are also part of the ROC ontology).
4</p>
    </sec>
    <sec id="sec-4">
      <title>The ROC Ontology</title>
      <p>The ontology14 was designed around a set of competency questions, for instance,
one can ask the following:
CQ1 Which countries do establish a certain response?
CQ2 At which incidence level do individual countries establish certain responses
/ response levels?
CQ3 How long do individual countries keep their response measures active?
CQ4 Were countries which established responses at low incidence levels able to
avoid high incidence rates?
CQ5 Is there an e ect of certain responses on infection rates? Can we measure
e ect or delay of e ect?
14 The current version 1.0 of the ROC ontology is publicly available at
http://qurator-csi.de/ontologies/roc</p>
      <p>The ontology consists of 27 OWL classes, 10 object properties, 42 data
properties and 3 annotation properties. Its expressivity is ALE HI(D), i.e., AL with
full existential quali cation, role hierarchy, inverse roles and data types,
making it a member of the OWL 2 DL pro le. The central domain concepts of the
ROC ontology are the indicators as de ned by the Oxford Covid-19 Government
Response Tracker (OxCGRT) mentioned in Section 1.</p>
      <p>The values for each of these indicators is acquired and stored in a data
record. A record is represented in the ROC ontology as an instance of the class
ResponseStatistics, which is a subclass of the CODO class CountryWiseStatistics
(see Figure 2a).</p>
      <p>In alignment with the structure of the data sources, which assign numerical
values to each of these indicators, we modeled these indicators as data properties.
We established a data property hierarchy re ecting the taxonomy of OxCGRT
coding categories (containment and closure (C), economic response (E), health
systems (H), and miscellaneous (M)) (see Figure 2b). Creating common super
properties for each category of response values allows for a Description Logic
reasoner to infer that if any of the response values in a certain category has
a value, then the super data property (representing the whole category) has a
value.
(b) The hierarchy of data
properties representing
the OxCGRT response
(a) A response statistics instance with acquired response values
values
5</p>
      <p>ROC in use
This section describes how the ontology is used to ingest a set of data collected
from multiple sources. It outlines the data transformation process and how to
query the resulting RDF knowledge base (KB) to answer competency questions.</p>
      <sec id="sec-4-1">
        <title>Data ingestion</title>
        <p>
          We manually reviewed and merged data collected from OxCGRT, ILO and
ECDC. We then transformed data coming from those di erent sources into RDF
based on the ROC ontology. The resulting KB serves as an integrated view to
answer queries spreading over all required sources. For data transformation, we
made use of the Karma integration tool [
          <xref ref-type="bibr" rid="ref12">10</xref>
          ]. The tool o ers a user interface
(as depicted in Figure 3) for mapping di erent types of structured data and
publish it in an RDF format. It automatically generates an R2RML15 mapping
model based on users input. The model can be stored and reused on similarly
structured data.
The resulting KB contains 1850 instances with data for Germany, Jordan
and Sweden collected between January and the beginning of November 2020.
We loaded the RDF data into the Virtuoso16 triple store, making it accessible
and queryable through the SPARQL endpoint.
5.2
        </p>
      </sec>
      <sec id="sec-4-2">
        <title>Data querying</title>
        <p>We devised an initial set of queries to answer the competency questions over
the RDF data. As an example, for the question "List the countries and their
respective health responses?" the corresponding query would be the one depicted
in Listing 1.</p>
        <p>PREFIX roc : &lt;http :// qurator - csi . de / ontologies / covid / responses #&gt;
PREFIX codo : &lt;http :// www . isibang . ac . in / ns / codo #&gt;
SELECT ? country AVG (? testing_policy ) AVG (? contact_tracing )
SUM (? investment_healthcare ) SUM (? investment_in_vaccines )
AVG (? facial_coverings )
WHERE {
? country codo : countryWiseStatistics ? stats .</p>
        <p>? stats roc : h2_testing_policy ? testing_policy ;
15 https://www.w3.org/TR/r2rml/
16 https://virtuoso.openlinksw.com/
roc : h3_contact_tracing ? contact_tracing ;
roc : h4_emergency_investment_in_healthcare ? investment_healthcare ;
roc : h5_investment_in_vaccines ? investment_in_vaccines ;
roc : h6_facial_coverings ? facial_coverings .
}
GROUP BY ? country
Listing 1: SPARQL query for question:"List the countries and their respective
health responses?"</p>
        <p>The query results are depicted in Figure 4. We can see for instance that
Germany has a higher testing policy index and the highest emergency investments
in healthcare and vaccines. We can also note that Sweden did not implement
a facial covering policy. Based on the correlation between countries stringency
and actual statistics, the e ectiveness or failure of implemented measures can
be derived, informing government future decisions.
The present work focuses on country responses against COVID-19 and proposes
a novel ontology ROC to enable the integration of data from heterogeneous data
sources and answer interesting questions. This facilitates statistical analysis to
investigate and evaluate the e ectiveness and side e ects of such responses. The
ontology consists of 27 OWL classes, 10 object properties, 42 data properties and
3 annotation properties. The data collected by OxCGRT, ILO and ECDC were
manually reviewed and merged. Then we converted data from these di erent
sources into RDF based on the ROC ontology. The resulting RDF serves as an
integrated view to answer queries that span all required sources. The resulting
KB contains 1850 instances of data for Germany, Jordan and Sweden collected
between January and early November 2020. We uploaded the RDF data to the
Virtuoso Triple Store and made it accessible and queryable through a SPARQL
endpoint.</p>
        <p>
          Given the fact that most experts are not familiar with SPARQL nor with
Semantic Web technologies, we plan to connect our Controlled Natural Language
querying system [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ], o ering a user-friendly interface for querying the KB.
        </p>
        <p>Other factors could in uence the e ectiveness of country responses. These are
either di cult to capture17 or relatively easy to determine18. Consideration of
such factors would lead to the extension of the properties of the concepts/terms
in order to increase the semantic expressiveness of the ontology.</p>
        <p>Lastly, a technical and a goal-based evaluation of the e ectiveness of the
approach is a challenge to be addressed by future work.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Acknowledgements</title>
      <p>The research presented in this article is partially funded by the German Federal
Ministry of Education and Research (BMBF) through the project QURATOR
(Unternehmen Region, Wachstumskern, grant no. 03WKDA1F). http://qurator.ai</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Auer</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Herre</surname>
          </string-name>
          , H.:
          <article-title>RapidOWL | An Agile Knowledge Engineering Methodology</article-title>
          . In: Virbitskaite,
          <string-name>
            <given-names>I.</given-names>
            ,
            <surname>Voronkov</surname>
          </string-name>
          ,
          <string-name>
            <surname>A</surname>
          </string-name>
          . (eds.)
          <source>Perspectives of Systems Informatics</source>
          , vol.
          <volume>4378</volume>
          , pp.
          <volume>424</volume>
          {
          <fpage>430</fpage>
          . Springer Berlin Heidelberg, Berlin, Heidelberg (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Babcock</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cowell</surname>
            ,
            <given-names>L.G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Beverley</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Smith</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>The infectious disease ontology in the age of covid-19</article-title>
          . OSF Preprints (
          <year>2020</year>
          ). https://doi.org/10.31219/osf.io/az6u5
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Dutta</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>DeBellis</surname>
          </string-name>
          , M.:
          <article-title>Codo: An ontology for collection and analysis of covid-19 data</article-title>
          . arXiv preprint arXiv:
          <year>2009</year>
          .
          <volume>01210</volume>
          (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Fernandez</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gomez-Perez</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Juristo</surname>
          </string-name>
          , N.:
          <article-title>METHONTOLOGY: from Ontological Art towards Ontological Engineering</article-title>
          .
          <source>In: Proceedings of the AAAI97 Spring Symposium</source>
          . pp.
          <volume>33</volume>
          {
          <fpage>40</fpage>
          .
          <string-name>
            <surname>Stanford</surname>
          </string-name>
          , USA (Mar
          <year>1997</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>He</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yu</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ong</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wang</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Liu</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hu</surname>
            <given-names>man</given-names>
          </string-name>
          , A.,
          <string-name>
            <surname>Huang</surname>
            ,
            <given-names>H.h.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Beverley</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hur</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yang</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          , et al.:
          <article-title>Cido, a community-based ontology for coronavirus disease knowledge and data integration, sharing, and analysis</article-title>
          .
          <source>Scienti c Data</source>
          <volume>7</volume>
          (
          <issue>1</issue>
          ), 1{
          <issue>5</issue>
          (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Karam</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Streibel</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Karjauv</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Coskun</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Paschke</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Answering controlled natural language questions over RDF clinical data</article-title>
          .
          <source>In: The Semantic Web: ESWC 2020 Satellite Events</source>
          , Heraklion, Crete, Greece, May 31 - June 4,
          <source>2020. Lecture Notes in Computer Science</source>
          , vol.
          <volume>12124</volume>
          , pp.
          <volume>129</volume>
          {
          <fpage>134</fpage>
          . Springer (
          <year>2020</year>
          ). https://doi.org/10.1007/978-3-
          <fpage>030</fpage>
          -62327-2 22
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Kibbe</surname>
            ,
            <given-names>W.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Arze</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Felix</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mitraka</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bolton</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fu</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mungall</surname>
            ,
            <given-names>C.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Binder</surname>
            ,
            <given-names>J.X.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Malone</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vasant</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parkinson</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schriml</surname>
            ,
            <given-names>L.M.</given-names>
          </string-name>
          :
          <article-title>Disease Ontology 2015 update: an expanded and updated database of human diseases for linking biomedical knowledge through disease data</article-title>
          .
          <source>Nucleic Acids Research</source>
          <volume>43</volume>
          (
          <issue>D1</issue>
          ),
          <source>D1071{D1078 (10</source>
          <year>2014</year>
          ). https://doi.org/10.1093/nar/gku1011
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          <article-title>17 such as culture, acceptance of people, discipline, people's perseverance, family structure, types of contacts in society</article-title>
          , etc.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          <article-title>18 such as public events during the pandemic, foreign trade, tourism, weather, country's experience of pandemics, time (how long the reactions will last), government system, structure, infrastructure, relationship between people and government (trust), etc</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          8.
          <string-name>
            <surname>Suarez-Figueroa</surname>
            ,
            <given-names>M.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gomez-Perez</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fernandez-Lopez</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>The NeOn Methodology for Ontology Engineering</article-title>
          . In: Suarez-Figueroa,
          <string-name>
            <given-names>M.C.</given-names>
            ,
            <surname>Gomez-Perez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Motta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            ,
            <surname>Gangemi</surname>
          </string-name>
          ,
          <string-name>
            <surname>A</surname>
          </string-name>
          . (eds.) Ontology Engineering in a Networked World, pp.
          <volume>9</volume>
          {
          <fpage>34</fpage>
          . Springer (
          <year>2012</year>
          ). https://doi.org/10.1007/978-3-
          <fpage>642</fpage>
          -24794-1 2
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          9.
          <string-name>
            <surname>Sure</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Staab</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Studer</surname>
          </string-name>
          , R.:
          <article-title>On-To-Knowledge Methodology (OTKM)</article-title>
          . In: Staab,
          <string-name>
            <given-names>P.D.S.</given-names>
            ,
            <surname>Studer</surname>
          </string-name>
          ,
          <string-name>
            <surname>P.D.R</surname>
          </string-name>
          . (eds.) Handbook on Ontologies, pp.
          <volume>117</volume>
          {
          <fpage>132</fpage>
          .
          <source>International Handbooks on Information Systems</source>
          , Springer Berlin Heidelberg (Jan
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          10.
          <string-name>
            <surname>Taheriyan</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Knoblock</surname>
            ,
            <given-names>C.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Szekely</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ambite</surname>
            ,
            <given-names>J.L.</given-names>
          </string-name>
          :
          <article-title>Learning the semantics of structured data sources</article-title>
          .
          <source>Journal of Web Semantics 37-38</source>
          ,
          <issue>152</issue>
          {
          <fpage>169</fpage>
          (
          <year>2016</year>
          ). https://doi.org/10.1016/j.websem.
          <year>2015</year>
          .
          <volume>12</volume>
          .003
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          11.
          <string-name>
            <surname>Tempich</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Simperl</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Luczak</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Studer</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pinto</surname>
            ,
            <given-names>H.S.:</given-names>
          </string-name>
          <article-title>ArgumentationBased Ontology Engineering</article-title>
          .
          <source>IEEE Intelligent Systems</source>
          <volume>22</volume>
          (
          <issue>6</issue>
          ),
          <volume>52</volume>
          {59 (Nov
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>