<!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>Using Semantic Web Technologies to Develop Intrinsically Resilient Energy Control Systems</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Frederick Sheldon and Daniel Fetzer</string-name>
          <email>fetzerdt@ornl.gov</email>
          <email>sheldonft@ornl.gov</email>
          <email>{sheldonft, fetzerdt}@ornl.gov</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jiangbo Dang and Dong Wei</string-name>
          <email>dong.w@siemens.com</email>
          <email>jiangbo.dang@siemens.com</email>
          <email>{jiangbo.dang, dong.w}@siemens.com</email>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Thomas Morris</string-name>
          <email>morris@ece.msstate.edu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jingshan Huang</string-name>
          <email>huang@southalabama.edu</email>
          <xref ref-type="aff" rid="aff5">5</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>David Manz</string-name>
          <email>david.manz@pnnl.gov</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jonathan Kirsch and Stuart Goose</string-name>
          <email>jonathan.kirsch@siemens.com</email>
          <email>stuart.goose@siemens.com</email>
          <email>{jonathan.kirsch, stuart.goose}@siemens.com</email>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Mississippi State University</institution>
          ,
          <addr-line>Mississippi State, MS 39762</addr-line>
          ,
          <country country="US">U.S.A.</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Oak Ridge National Laboratory</institution>
          ,
          <addr-line>Oak Ridge, TN 37831</addr-line>
          ,
          <country country="US">U.S.A.</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Pacific Northwest National Laboratory</institution>
          ,
          <addr-line>Richland, WA 99354</addr-line>
          ,
          <country country="US">U.S.A.</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Siemens Corporation, Corporate Research and Technology</institution>
          ,
          <addr-line>Berkeley, CA 94704</addr-line>
          ,
          <country country="US">U.S.A.</country>
        </aff>
        <aff id="aff4">
          <label>4</label>
          <institution>Siemens Corporation, Corporate Research and Technology</institution>
          ,
          <addr-line>Princeton, NJ 08540</addr-line>
          ,
          <country country="US">U.S.A.</country>
        </aff>
        <aff id="aff5">
          <label>5</label>
          <institution>University of South Alabama</institution>
          ,
          <addr-line>Mobile, AL 36688</addr-line>
          ,
          <country country="US">U.S.A.</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>-To preserve critical energy control functions while under attack, it is necessary to perform comprehensive analysis on root causes and impacts of cyber intrusions without sacrificing the availability of energy delivery. We propose to design an intrinsically resilient energy control system where we extensively utilize Semantic Web technologies, which play critical roles in knowledge representation and acquisition. While our ultimate goal is to ensure availability/resiliency of energy delivery functions and the capability to assess root causes and impacts of cyber intrusions, the focus of this paper is to demonstrate a proof of concept of how Semantic Web technologies can significantly contribute to resilient energy control systems. Index Terms-cybersecurity, energy control system, ontology, knowledge base, semantic annotation, data integration.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>I. INTRODUCTION</title>
      <p>Our energy infrastructure depends on energy delivery
systems comprised of complex and geographically dispersed
network architectures with vast numbers of interconnected
components. These systems provide critical functions to
provide information and automated control over a large,
complex network of processes that collectively ensure reliable
and safe production and distribution of energy. The energy
utilities are modernizing these vast networks with millions of
smart meters, high speed sensors, advanced control systems,
and a supporting communications infrastructure. This
additional complexity brings benefits, but also increases the
risks of cyber attacks that could potentially disrupt our energy
delivery. These systems must maintain high availability and
reliability even when under attack. After a security incident has
been detected, the incident response team needs the ability to
investigate and determine the root cause, attack methods,
consequences, affected assets, impacted stakeholders, and other
information in order to inform an effective response. The
response team needs this information in the short term in order
to contain or eradicate the attack, recover compromised
equipment, and restore normal operation. The team also needs
This manuscript has been authored by contractors of the U.S. Government (USG) under
contract DE-AC05-00OR22725. Accordingly, the USG retains a nonexclusive,
royaltyfree license to publish or reproduce the published form of this contribution, or allow
others to do so, for USG purposes.
to determine counter-measures to prevent recurrence and
possibly collect evidence to legally prosecute the offenders.
This analysis and response must be done without interrupting
the availability of the energy delivery systems.</p>
      <p>To address the aforementioned challenges, this paper
presents the design and architecture of InTRECS, an
InTrinsically Resilient Energy Control System. The ultimate
goal of InTRECS is to provide tools and technologies to ensure
the availability/resiliency of energy delivery functions, along
with the capability to assess root causes and impacts of cyber
intrusions. To meet these goals, InTRECS extensively applies
Semantic Web technologies, including cybersecurity domain
ontologies, a comprehensive knowledge base, and semantic
data annotation &amp; integration techniques. Semantic Web
technologies are built upon ontologies, which are formal,
declarative knowledge models and have been shown to play
critical roles in knowledge representation and acquisition.</p>
      <p>In this paper, we argue that applying Semantic Web
technologies in InTRECS affords several benefits compared to
typical approaches that utilize relational databases:
 While relational databases focus on syntactic
representation of data and lack the ability to explicitly
encode semantics, Semantic Web technologies support
rich semantic encoding, which is critical in automated
knowledge acquisition.
 Powerful tools exist for capturing and managing
ontological knowledge, including an abundance of
reasoning tools readily supplied for ontological models,
making it much more convenient to query, manipulate, and
reason over available data sets. As a result,
semanticsbased queries, instead of SQL queries, are made possible.
 Advances in an energy delivery system (EDS) require
changes to be made regularly regarding underlying data
models. In addition, more often than not, it is preferable to
represent data at different levels and/or with different
abstractions. There are no straightforward methods for
performing such updates if relational models are adopted.
 Semantic Web technologies better enable EDS researchers
to append additional data into repositories in a more
flexible and efficient manner. The formal semantics
encoded in ontologies makes it possible to reuse data in
unplanned and unforeseen ways, especially when data
users are not data producers, which is now very common.</p>
      <p>While our ultimate goal is to ensure availability/resiliency
of energy delivery functions and the capability to assess root
causes and impacts of cyber intrusions, the focus of this paper
is to demonstrate a proof of concept of how Semantic Web
technologies can significantly contribute to resilient energy
control systems. The rest of the paper is organized as follows.
Section II gives a brief review on related research in ontologies
and semantic annotation &amp; integration, respectively. Section III
describes the overall architecture of InTRECS, followed by
methodology details for developing domain ontologies &amp;
knowledge base and performing data annotation &amp; integration.
Section IV demonstrates our preliminary experimental results.
Finally, Section V concludes with future research directions.</p>
    </sec>
    <sec id="sec-2">
      <title>II. RELATED WORK</title>
      <sec id="sec-2-1">
        <title>A. Ontologies in Energy Delivery Control and Cybersecurity</title>
        <p>
          Energy delivery control systems comprise complex network
architectures that may contain hundreds of specialized cyber
components and may extend across wide geographical regions.
Cyber attack investigation involves examining large volumes
of data from heterogeneous sources. Researchers are facing the
challenge of how to maintain the integrity of data derived from
diverse sources across distributed geographic areas ([
          <xref ref-type="bibr" rid="ref1 ref2 ref3 ref4 ref5 ref6 ref7">1-7</xref>
          ]).
These research efforts have resulted in various ad-hoc
proprietary formats for storing and analyzing data and
maintaining respective metadata. Different parties are likely to
adopt different formats according to specific needs. Therefore,
the seamless communication among different parties, along
with the knowledge sharing and reuse that follow, become a
non-trivial problem. Turnitsa and Tolk [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ] discussed in depth
multi-resolution, multi-scope, and multi-structure challenges
during data exchange between different models.
        </p>
        <p>
          Semantic Web technologies that are based on domain
ontologies can render tremendous help. Ontologies are
declarative knowledge models, defining essential
characteristics and relationships for specific domains of interest.
As a semantic foundation, ontologies greatly help domain
experts to formally define domain knowledge in terms of data
semantics (intended meanings) rather than data syntax (forms
in which data are represented). Reasons for developing
ontologies include, but not limited to: (i) to share domain
information among people and software; (ii) to enable reuse of
domain knowledge; (iii) to analyze domain knowledge and
make it more explicit; and (iv) to separate domain knowledge
from its implementation. There exist some domain ontologies
in cybersecurity and related areas, e.g., Intrusion Detection
System Ontology [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ], Network Security Ontology [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ], Process
Control Ontology [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ], INSPIRE Ontology [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ], and GE SADL
Host Defense Ontology [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]. These ontologies provide metadata
and standard terminologies in respective domains.
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>B. Semantic Data Annotation &amp; Integration</title>
        <p>
          Semantic data annotation &amp; integration can bring critical
impacts and benefits to data analysis and management.
Semantic annotation (tagging) systems can be divided into
manual, semi-automatic, and automatic ones [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]. In manual
tagging systems (Sema-Link [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ] for example), users employ
controlled vocabularies from some ontology to tag documents.
Such a manual process is time-consuming and requires deep
domain expertise, in addition to the inconsistency issue.
Semiautomatic tagging systems improve manual tagging systems
by automatically parsing documents and recommending
potential tags. Human annotators only need to select tags from
candidates suggested by the system. Automatic semantic
tagging systems offer further improvement by parsing and
tagging documents with ontological concepts and instances in
a fully automatic way. Zemanta [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ] is such an example. By
suggesting contents from various sources, such as Wikipedia,
YouTube Flickr, and Facebook, Zemanta disambiguates terms
and maps them to the Common Tag Ontology [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]. Dang et al.
have developed one of the largest comprehensive,
domainindependent ontological knowledge base, UNIpedia+ [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ],
which covers around 11 million named English entities. Based
on UNIpedia+, they further developed an automatic tagging
system [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ] to produce semantically linked tags for given data.
The information system architecture in the Los Angeles Smart
Grid project [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ] enabled analytical tools and algorithms to
forecast energy load and identify load curtailment response
through semantically meaningful data.
        </p>
      </sec>
      <sec id="sec-2-3">
        <title>A. InTRECS Overall Architecture</title>
        <p>Figure 1 illustrates the overall architecture of InTRECS,
which is decomposed into six subsystems.</p>
        <p> Intrusion-Tolerant SCADA (InTRADA)</p>
        <p>
          We will develop a survivable SCADA system based
on intrusion-tolerant replication [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ]. InTRADA will
be capable of guaranteeing correct operations and
excellent performance even when part of the system
has been compromised and is under the control of an
intelligent attacker.
 Cybersecurity Ontologies and Knowledge Base for
        </p>
      </sec>
      <sec id="sec-2-4">
        <title>Energy Delivery Systems (CoEDS)</title>
        <p>CoEDS knowledge base (KB) contains domain
ontologies, a resource description framework (RDF)
repository, a SPARQL RDF query engine, and an
inference engine. The KB will provide end users
with a unified and consistent data layer for analyzing
data at the semantic level.
 Semantic Data Integration and Processing (SeDIEP)
Our focus is to develop an automatic semantic data
annotation &amp; integration engine for tagging data
sources based on the metadata defined in CoEDS
ontologies. An event-processing engine will handle
dynamic events and generate security alerts.
 Root Cause and Impact Analysis (RoCIA)</p>
        <p>RoCIA provides the basis to detect cyber incidents
and investigate the root cause, attack methods,
consequences, affected assets, impacted stakeholders,
attackers’ identity, and other metrics to inform an
effective response. RoCIA will leverage the Cyber
Security Econometrics System (CSES) and the
inference and query engines provided within CoEDS
KB to assist EDS stakeholders in evaluating
cybersecurity investments and to provide an
economic impact assessment of on-going cyber
intrusions.
 Dashboard Analytics and Situation Awareness
(DaSA)
Dashboard analytics includes a user graphical user
interface (GUI) to support interactions between end
users and InTRECS. Situational awareness will be
performed for end users. We will also support
reasoning through the inference engine in CoEDS.
 Test and Evaluation (TnE)</p>
        <p>Implemented modules will automatically configure
the test suite environment to the appropriate start
state for the test case. A portal will provide the
information and documentation and will execute the
test case. We will also develop a test suite in an
enduser setting, including a set of denial of service
(DOS), reconnaissance, and network packet integrity
exploits targeting SCADA, remote terminal unit
(RTU), and network architecture vulnerabilities.</p>
        <p>InTRECS will be constantly active to intrinsically
provide resiliency, i.e., correct operations and excellent
performance. At the same time, a DaSA GUI will guide end
users to generate queries out of data derived from diverse
sources. Query results, e.g., the root cause, extent, and
impacts of the cyber intrusion, can then be provided back to
end users. InTRECS will also push security alerts up to end
users. Both query results and alerts are regarded as semantic
decision support to end users because they extensively utilize
Semantic Web technologies, namely, domain ontologies,
RDF triples resulting from semantic annotation, and
inferences &amp; analysis performed at the semantic level.</p>
      </sec>
      <sec id="sec-2-5">
        <title>B. CoEDS Domain Ontologies and Knowledge Base</title>
        <p>There are four components in CoEDS KB: (i) CoEDS
domain ontologies, (ii) an RDF repository, (iii) a SPARQL
RDF query engine, and (iv) an inference engine. Through
automatic data integration and logic reasoning, CoEDS KB
will be able to provide a unified and consistent data layer for
analyzing data at the semantic level. It will thus assist end
users to effectively obtain real-time decision support, so that
they can (i) obtain health status updates of SCADA replicas,
(ii) analyze and better understand the root cause, extent, and
impacts of an attack, (iii) acquire situational awareness, and
(iv) recommend courses of action.</p>
      </sec>
      <sec id="sec-2-6">
        <title>1) Interaction between CoEDS and other InTRECS</title>
        <p>subsystems: CoEDS KB actively exchanges information
with other subsystems of InTRECS on a regular basis.
 InTRADA receives system health and status
information from CoEDS KB, and incorporates such
knowledge to enhance its fault-detection algorithms.
This will enable InTRADA to more rapidly
reconfigure itself in the event of a cyber attack by
helping it distinguish between performance faults
caused by a malicious application and by more
benign issues such as transitory network problems.
InTRADA sends to CoEDS KB status updates
regarding the health of the replicas, hence providing
data for future cyber attack analysis.
 SeDIEP obtains the data semantics, i.e., ontological
metadata, from CoEDS KB and utilizes such
metadata during the automatic semantic annotation.
Annotated data, including cybersecurity
econometrics, dynamic events, etc., are stored back
into CoEDS KB to construct and continuously
update the central data repository in the KB.
 CoEDS KB provides RoCIA with topology data as
well as the data semantics essential for performing
root cause and impact analysis. RoCIA supplies
CoEDS KB with root cause and impact analysis data,
including attack signatures, attack locations, exploits,
consequences, countermeasures, model parameters,
network components, security requirements, threats,
vulnerabilities, and stakeholders.
 CoEDS KB furnishes DaSA with dynamic events
and electric grid components and topology data, both
of which are in an annotated form. DaSA sends back
situational awareness data to CoEDS KB. In addition,
the KB also provides the Correlation Layers for
Information Query and Exploration (CLIQUE) and
Traffic Circle, two visual analytics tools in DaSA,
with interoperability for behavior model-based
anomaly detection.</p>
        <p>2) Motivation for developing CoEDS ontologies: Among
existing ontologies in cybersecurity and related areas
(mentioned in Section II), there is not a single one that is
comprehensive enough to cover a complete set of concepts
and relationships for the purpose of this research. In
particular, with regard to the fields of SCADA status, root
cause analysis, situational awareness, electric grid
components and topology, cybersecurity econometrics, cost
benefit analysis, and complex event processing, all
aforementioned existing ontologies are missing some
necessary concepts within these critical fields. Even in the
case that a specific concept of our interest is contained in
some existing ontology, more often than not, the semantics
defined in such an ontology need to be extended and
customized before this concept can be utilized within
InTRECS system. In brief, Energy Control Systems (ECS)
end users lack a comprehensive, customized conceptual
model, which prevents the energy sector from leveraging
enhanced knowledge acquisition processes brought by
Semantic Web technologies. Such a situation motivates us
to develop CoEDS domain ontologies.</p>
        <p>
          3) Ontology development principles: We have observed
seven practices suggested by Smith et al. [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ]: the ontology
should (i) be freely available; (ii) be expressed using a
standard language or syntax; (iii) provide tracking and
documentation for successive versions; (iv) be orthogonal to
existing ontologies; (v) include natural language
specifications of all concepts; (vi) be developed
collaboratively; and (vii) be used by multiple researchers. In
particular, we propose a decomposition methodology as the
strategy for coming up with orthogonal ontologies. Our
methodology is similar to those used in the database
normalization theory, third normal form (3NF) for example.
We first began with concepts from possibly many
subdomains in one large set, followed by the identification of
dependencies or overlaps among these concepts, and we
finally proceeded to decompose all concepts based on their
identified dependencies. Our preliminary design is to
develop seven sub-ontologies in CoEDS: SCADA status,
root cause &amp; impact, situational awareness, grid component
&amp; topology, cybersecurity econometrics, cost benefit, and
complex event processing. Consequently, we achieved the
orthogonality feature, i.e., the non-overlapping feature, for
CoEDS domain ontologies.
        </p>
      </sec>
      <sec id="sec-2-7">
        <title>4) Knowledge-driven ontology development procedure:</title>
        <p>
          The ontology development was not from scratch. Instead, to
(i) take advantage of the knowledge already contained in
existing ontologies and (ii) reduce the possibility of
redundant efforts, we have reused, extended, and
customized a set of well-established concepts from existing
domain ontologies. In addition, popular upper ontologies,
e.g., the Basic Formal Ontology (BFO), was imported into
our ontologies. The ontology development was driven by
domain knowledge and decomposed into five stages, as
suggested by Uschold and Gruninger [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ]: (i) specification
of content; (ii) informal documentation of concept
definitions (by domain experts); (iii) logic-based
formalization of concepts and relationships between
concepts; (iv) implementation of the ontology in a computer
language; and (v) evaluation of the ontology, including the
internal consistency and the ability to answer logical
queries. As illustrated in Figure 2, these five stages are
essentially ongoing and iterative because end users’ needs
will change as their understanding of the domain evolves. In
this iterative, knowledge-driven approach, both ontology
engineers and domain experts have been involved, working
together to capture domain knowledge, develop a
conceptualization, and implement the conceptual model.
The ontology construction process has taken place over a
number of iterations, involving a series of interviews,
evaluation strategies, and refinements. Standard
revisioncontrol procedures have been utilized.
        </p>
      </sec>
      <sec id="sec-2-8">
        <title>5) Ontology format and development tool: There are</title>
        <p>
          different formats and languages for describing ontologies,
all of which are popular and based on different logics: Web
Ontology Language (OWL) [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ], Open Biological and
Biomedical Ontologies (OBO) [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ], Knowledge Interchange
Format (KIF) [
          <xref ref-type="bibr" rid="ref21">21</xref>
          ], and Open Knowledge Base Connectivity
(OKBC) [
          <xref ref-type="bibr" rid="ref22">22</xref>
          ]. We have chosen the OWL format
recommended by the World Wide Web Consortium (W3C).
OWL is designed for use by applications that need to
process the content of information instead of just presenting
information to humans. As a result, OWL facilitates greater
machine interpretability of Web contents. We have chosen
Protégé, an open-source ontology editor developed by
Stanford [
          <xref ref-type="bibr" rid="ref23">23</xref>
          ], as our development tool over other available
tools such as CmapTools and OntoEdit.
        </p>
      </sec>
      <sec id="sec-2-9">
        <title>6) CoEDS KB components – RDF Repository, Query</title>
        <p>
          Engine, and Inference Engine: Based on the formal
knowledge defined in CoEDS ontologies, heterogeneous
data sources can be annotated and integrated into a central
repository. Note that data sources to be integrated include
structured, semi-structured, or unstructured data, the
interoperability thus becomes an obstacle during knowledge
discovery. We adopt RDF, a model for data interchange
recommended by the W3C, to handle such a challenge. RDF
specifically supports the evolution of schemas over time
without requiring all the data consumers to be changed. The
generic structure of RDF allows structured, semi-structured,
and unstructured data to be mixed, exposed, and shared
across different applications, thus helping to handle the data
interoperability challenge. Following automatic semantic
data annotation (see Section III.C), RDF triples will be
indexed and accumulated into a central repository. SPARQL
Protocol and RDF Query Language (SPARQL) [
          <xref ref-type="bibr" rid="ref24">24</xref>
          ] is a
query language recommended by W3C to retrieve and
manipulate RDF data. End users of InTRECS system will be
guided by a GUI to automatically generate RDF queries
across semantically integrated sources. These queries will
then be executed by a SPARQL-based query engine.
        </p>
        <p>The RDF data repository and query answering are not
enough for an effective and comprehensive knowledge
acquisition. Suppose that some facts do not exist in any
original data sources, they will thus not be stored in the RDF
repository. But such information may be critical to end
users. To obtain the ability to acquire previously implicit
knowledge, we will incorporate an inference engine (a.k.a.
logic reasoner). Compared with traditional relational
database techniques, inference engines provide a more
expressive method for querying and reasoning over
available data sets. Thus, ontology-based (a.k.a.
semanticsbased) queries, instead of traditional SQL queries, are
possible. Ontology-based queries improve traditional
keyword-based queries in several ways. (i) Both
synonymous terms (those having same meaning) and
polysemous terms (those having different meanings) can be
included to obtain more results that are relevant to the user
query. (ii) Semantic relationships among terms often reveal
extra clues hidden in disparate data sources. Such
relationships can be explicitly discovered to further improve
the quality of query answering. Consequently, we will be
able to acquire hidden knowledge and information that was
originally implicit and unclear, yet critical, to end users.
With a logic reasoner, CoEDS repository will work as a
comprehensive knowledge base.</p>
      </sec>
      <sec id="sec-2-10">
        <title>7) Sesame framework for RDF repository, SPARQL</title>
        <p>
          RDF query engine, and inference engine: We have
preliminarily chosen Sesame framework [
          <xref ref-type="bibr" rid="ref25">25</xref>
          ] to store and
manage the RDF repository. Sesame is an open-source Java
framework for the storage and querying of RDF data. The
framework is fully extensible and configurable with respect
to storage mechanisms, inferencers, RDF file formats, query
result formats, and query languages. In addition, Sesame
offers a JBDC-like user API, streamlined system APIs, and
a RESTful HTTP interface supporting the SPARQL
protocol for RDF. Moreover, Sesame contains a built-in
inference engine, and various reasoning tasks, e.g.,
subsumption and contradiction reasoning, can be performed.
        </p>
      </sec>
      <sec id="sec-2-11">
        <title>C. Semantic Data Annotation and Event Processing</title>
        <p>According to the formal domain knowledge, including a
global metadata model, defined in CoEDS, heterogeneous
data sources can be annotated and seamlessly integrated into
a central RDF data repository, which will serve as a unified
and consistent data layer for data analytics applications.</p>
        <p>Semantic TagPrint</p>
        <p>Concepts
Properties</p>
        <p>CoEDS Ontologies</p>
        <p>Fig. 3. Semantic data annotation and event processing (SeDIEP).
1) System overview: Semantic data annotation and event
processing (SeDIEP) subsystem manages various data
sources and automatically annotates and integrates data at
semantic level. As shown in Figure 3, there are three major
components in the subsystem: (i) Semantic TagPrint, (ii)
Semantic Knowledge Management Tool (SKMT), and (iii)
Event Engine. Semantic TagPrint is an automatic semantic
tagging engine that annotates structured data and free text
using ontological entities from CoEDS ontologies. SKMT
manages heterogeneous data sources for semantic
annotation and integration. Event engine feeds the semantic
tagging engine with dynamic events. It also generates alerts
with the support from CoEDS through modified RDF
queries and the semantic reasoning.</p>
        <p>Heterogeneous data sources will be annotated and
seamlessly integrated into a central RDF data repository
based on CoEDS ontologies. This data repository will serve
as a unified and consistent data layer for further analyzing
data at the semantic level. Our core technologies can
substantially reduce design-to-execution time for application
domains of data integration, visualization, and analysis.</p>
        <p>SKMT
(Semantic Knowledge Management Tool)</p>
        <p>Data bases</p>
        <p>Query Interface
Indexing Manager</p>
        <p>Repository</p>
        <p>Manager
Knowledge
Sources</p>
        <p>Content
Named
Entity
Detection</p>
        <p>Semantic</p>
        <p>Annotation
Ontology
Mapping</p>
        <p>Concept
Weighting</p>
        <p>Event Engine
Event Stream
Event Processing</p>
        <p>Alerts</p>
        <p>CoEDS
Knowledge</p>
        <p>Base
(RDF Store)
• Meaningful data. Our system will annotate terms in text
with their corresponding concepts in CoEDS ontologies
by finding their meanings and analyzing their context.
• Scalability. Indexed data are stored and managed in a
repository. Collected and initially processed data can be
incrementally analyzed and indexed.
• Easy integration. Various data sources can be seamlessly
integrated along with their semantic indexes.</p>
      </sec>
      <sec id="sec-2-12">
        <title>2) Deep annotation and integration: Data sources to be</title>
        <p>integrated contain structured, semi-structured, or
unstructured data. As discussed in the previous section, we
adopt RDF to handle the data interoperability challenge.
Semantic data annotation is the process of tagging source
files with metadata predefined in ontologies such as names,
entities, attributes, definitions, and descriptions. Herein, we
use terms of “semantic annotation” and “semantic tagging”
interchangeably. The annotation provides extra information
contained in metadata to existing pieces of data. Metadata
are usually from a set of ontological entities (including
concepts and instances of concepts) predefined in
ontologies. For unstructured data such as free text, we will
use a tagging engine to align them with ontological entities
and generate semantic annotations. For structured data
including database data, the annotation will take two
successive steps: (i) first we will annotate data source
schemas by aligning their metadata with ontological entities;
(ii) according to annotated schemas we will then transform
original data instances into RDF triples. We refer to such
annotation as “deep” annotation – this term was coined by
Goble, C. in the Semantic Web Workshop of WWW 02. It is
necessary to annotate more than just data source schemas
because there are situations where the opposite “shallow”
annotation (i.e., annotation on schemas alone) cannot
provide users with the desired knowledge. Following
semantic data annotation, RDF triples will be indexed and
accumulated into a central repository.</p>
        <p>3) Unified view over original data sources and
costefficient analysis: All semantic tags will be generated from a
global metadata model, i.e., CoEDS ontologies, our tool
thus provides a unified view over original data sources at the
semantic level. As discussed before, our RDF query and
reasoning engines will provide users with more meaningful
and relevant information from semantically annotated and
integrated data sources. In addition, semantic relationships
among tags provide us with additional clues and will further
improve the quality of retrieved results. Given a set of
candidate results to be returned to users, we will calculate
the semantic similarity between each result and the user
query using semantic features such as (i) hypernym, which
defines the superClassOf relationship and (ii) holonym,
which defines the partOf relationship. We will then rank
these results by their respective semantic similarities.
Consequently, users can be presented with more relevant
query results.</p>
      </sec>
      <sec id="sec-2-13">
        <title>4) Semantic event processing: Dynamic events will be</title>
        <p>fed to our Semantic Tag Print, which will annotate these
events with semantic tags. Then events are represented as
RDF triples, accompanied with event attributes such as
timestamps and probabilities. With the support from
CoEDS, SeDIEP will transform these tagged events into
SPARQL queries. We will perform event filtering,
correlation, and aggregation or abstraction using semantic
matching, rules, and similarity evaluations. Moreover, we
will detect event patterns on event streams with temporal
semantic rules. As a result, high-risk vulnerabilities and
threats can be predicted, and security alerts will then be
automatically generated and rendered to users when facing
potential cyber intrusions.</p>
        <p>5) Core Components in SeDIEP: Figure 3 shows three
major components in SeDIEP to semantically integrate
various data sources and event streams.</p>
        <p>a) Component one: Semantic TagPrint is an automatic
semantic tagging engine that annotates structured data and
free text using ontological entities. Three modules were
designed for this component.</p>
        <p>
           Named Entity Detection: This module extracts
named entities, noun phrases in general, from the
input text. We adopt Stanford Parser [
          <xref ref-type="bibr" rid="ref26">26</xref>
          ] to detect
and tokenize sentences, and assign Part-of-Speech
(PoS) tags to tokens. Entity names will be extracted
based on PoS tags.
 Ontology Mapping: This module maps extracted
entity names to CoEDS concepts and instances with
two steps: Phrase mapping and Sense mapping.
Phrase mapping will match the noun phrase of an
entity name to a predefined concept or instance.
Sense mapping will utilize a linear-time lexical
chain algorithm to disambiguate terms that have
several senses defined in ontologies.
 Ontology Weighting: This module utilizes statistical
and ontological features of concepts to weigh
semantic tags. We then annotate the input text using
the semantics with higher weights.
        </p>
        <p>b) Component two: SKMT collects original text and
sends annotation results to Repository Manager, whose main
role is to manage RDF repository (store) and to
communicate with Query Interface. These components
altogether provide a unified view over original data sources
at the semantic level. Users will be guided by a GUI to
automatically generate RDF queries across semantically
integrated data sources. These queries will then be executed
by a SPARQL-based RDF query engine. As discussed
earlier in this subsection, we can calculate the semantic
similarity between each candidate query result and the user
query using semantic features such as hypernym and
holonym. These query results can then be ranked by their
respective semantic similarities. Consequently, we are able
to render users more accurate and desired query results.</p>
      </sec>
      <sec id="sec-2-14">
        <title>c) Component three: Event Engine annotates dynamic</title>
        <p>events and stores them as RDF triples. It will then generate
SPARQL queries and perform event filtering, correlation,
and aggregation or abstraction with the semantics defined in
CoEDS ontologies.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>IV. PRELIMINARY EXPERIMENTAL RESULTS</title>
      <p>In this ongoing research, we have developed a
preliminary version of CoEDS domain ontologies and
knowledge base to demonstrate a proof of concept of how
Semantic Web technologies can significantly contribute to
resilient energy control systems. We also exported instances
into an RDF data repository within the Sesame framework.</p>
      <sec id="sec-3-1">
        <title>A. CoEDS Ontologies</title>
        <p>As discussed earlier in Section III.B, we have developed
seven sub-ontologies in CoEDS: SCADA Status Ontology,</p>
      </sec>
      <sec id="sec-3-2">
        <title>Root Cause &amp; Impact Ontology, Situational Awareness</title>
      </sec>
      <sec id="sec-3-3">
        <title>Ontology, Grid Component &amp; Topology Ontology,</title>
      </sec>
      <sec id="sec-3-4">
        <title>Cybersecurity Econometrics Ontology, Cost Benefit</title>
      </sec>
      <sec id="sec-3-5">
        <title>Ontology, and Complex Event Processing Ontology. The</title>
        <p>purpose of such a decomposition strategy is to achieve the
orthogonality feature, i.e., the non-overlapping feature
among different CoEDS sub-ontologies. After individual
sub-ontologies were developed, we then imported them into
CoEDS. If future modifications are needed for any
subontology, the changed schema information will be
automatically integrated into CoEDS ontologies. Figure 4
demonstrates a screen shot from Protégé GUI, which exhibits
a portion of CoEDS concepts. Note that the well-defined,
general-purpose structure from the Basic Formal Ontology
(BFO), a popular upper ontology across different disciplines
and research areas, was preserved in the ontology schema.
Statistic information for all seven sub-ontologies is
summarized in Table I. In total, CoEDS ontologies contain
269 concepts, 232 object properties, and 110 data properties.</p>
      </sec>
      <sec id="sec-3-6">
        <title>B. CoEDS Knowledge Base</title>
        <p>The current CoEDS KB contains a total of 1,223 facts
(a.k.a. axioms in Protégé). Details can be found in Table II.</p>
      </sec>
      <sec id="sec-3-7">
        <title>C. Sesame Framework to Manage Data Repository</title>
        <p>Within the Sesame framework we exported all
ontological instances into an RDF data repository for future
storage and management. Figure 5 is a screen shot from
Sesame GUI, where the seven sub-ontologies and the overall
CoEDS ontologies were clearly demonstrated. Being an
open-source Java framework, Sesame framework can be
readily extended and configured for the storage and querying
of RDF data. Moreover, a JBDC-like user API, streamlined
system APIs, and a RESTful HTTP interface are offered in
Sesame as well.</p>
        <p>To preserve critical energy control functions while under
attack, it is necessary to perform comprehensive analysis on
the root cause, extent, and impacts of cyber intrusions
without sacrificing the availability of energy delivery. We
proposed to develop InTRECS, an intrinsically resilient
energy control system, to address these challenges. Semantic
Web technologies, which play critical roles in knowledge
representation and acquisition, have been extensively
adopted in our system. The focus of this ongoing research is
to demonstrate a proof of concept of how Semantic Web
technologies can significantly contribute to resilient energy
control systems. We justified the research motivation,
described our methodology in detail, and exhibited
preliminary experimental results. Future research directions
include, but are not limited to, (i) continue CoEDS ontology
development towards delivering a highly stable and more
usable version; (ii) incorporate query and inference engines
into the knowledge base for end users to better analyze root
causes and impacts of cyber intrusions; and (iii) implement
SeDIEP subsystem.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>ACKNOWLEDGMENT</title>
      <p>This research was partially supported through the U.S.
Department of Energy (DOE) Higher Education Research
Experiences (HERE) program for Faculty at the Oak Ridge
National Laboratory, Oak Ridge, Tennessee, sponsored by
the U.S. Department of Homeland Security (DHS).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>J.</given-names>
            <surname>Undercoffer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Joshi</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Pinkston</surname>
          </string-name>
          , “
          <article-title>Modeling Computer Attacks: An Ontology for Intrusion Detection</article-title>
          ,
          <source>” RAID</source>
          <year>2003</year>
          , LNCS 2820, pp.
          <fpage>113</fpage>
          -
          <lpage>135</lpage>
          ,
          <year>2003</year>
          , Springer-Verlag Berlin Heidleberg,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>A.</given-names>
            <surname>Simmonds</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Sandilands</surname>
          </string-name>
          , and L. Ekert, “
          <article-title>An Ontology for Network Security Attacks,”</article-title>
          <source>Proc. the 2nd Asian Applied Computing Conference (AACC-04)</source>
          ,
          <source>LNCS 3285</source>
          , pp.
          <fpage>317</fpage>
          -
          <lpage>323</lpage>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>W.</given-names>
            <surname>Wang</surname>
          </string-name>
          and
          <string-name>
            <given-names>T.</given-names>
            <surname>Daniels</surname>
          </string-name>
          , “
          <article-title>A Graph Based Approach toward Network Forensic Analysis</article-title>
          ,
          <source>” ACM Transactions on Information and Systems Security</source>
          , Vol.
          <volume>12</volume>
          , No. 1,
          <string-name>
            <surname>Article</surname>
            <given-names>4</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pub</surname>
          </string-name>
          . Date: Oct.
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>J.</given-names>
            <surname>Hieb</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Graham</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Guan</surname>
          </string-name>
          , “
          <article-title>An Ontology for Identifying Cyber Intrusion Induced Faults in Process Control Systems,” Critical Infrastructure Protection III</article-title>
          ,
          <source>IFIP AICT 311</source>
          , pp.
          <fpage>125</fpage>
          -
          <lpage>138</lpage>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>G.</given-names>
            <surname>Isaza</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Castillo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Lopez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Casillo</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Lopez</surname>
          </string-name>
          , “
          <article-title>Intrusion Correlation Using Ontologies and Multi-agent Systems,”</article-title>
          <source>Proc. 4th International Conference on Information Security and Assurance (ISA-10)</source>
          , pp.
          <fpage>355</fpage>
          -
          <lpage>361</lpage>
          , Miyazaki, Japan, June 23-25,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>M.</given-names>
            <surname>Choras</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Kozik</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Flizikowski</surname>
          </string-name>
          , and W. Holubowicz, “
          <article-title>Ontology Applied in Decision Support System for Critical Infrastructures Protection,” IEA/AIE2010</article-title>
          , LNAI, pp.
          <fpage>671</fpage>
          -
          <lpage>680</lpage>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>B.</given-names>
            <surname>Barnett</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Crapo</surname>
          </string-name>
          , and
          <string-name>
            <surname>P. O'Neil</surname>
          </string-name>
          , “
          <article-title>Experiences in Using Semantic Reasoners to Evaluate Security of Cyber Physical Systems</article-title>
          ,”
          <source>General Electric Internal Report GridSec</source>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>C.</given-names>
            <surname>Turnitsa</surname>
          </string-name>
          and
          <string-name>
            <given-names>A.</given-names>
            <surname>Tolk</surname>
          </string-name>
          , “
          <article-title>Knowledge Representation and the Dimensions of a Multi-Model Relationship,”</article-title>
          <source>Proc. the 40th Conference on Winter Simulation (WSC-08)</source>
          , pp.
          <fpage>1148</fpage>
          -
          <lpage>56</lpage>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>L.</given-names>
            <surname>Reeve</surname>
          </string-name>
          and H. Han, “
          <article-title>Semantic Annotation for Semantic Social Networks Using Community Resources,” AIS SIGSEMIS Bulletin</article-title>
          , vol.
          <volume>2</volume>
          , pp.
          <fpage>52</fpage>
          -
          <lpage>56</lpage>
          ,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>S.</given-names>
            <surname>Wiesener</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Kowarschick</surname>
          </string-name>
          , and
          <string-name>
            <given-names>R.</given-names>
            <surname>Bayer</surname>
          </string-name>
          , “
          <article-title>SemaLink: An Approach for Semantic Browsing through Large Distributed Document Spaces,”</article-title>
          <source>Proc. the 3rd International Forum on Research and Technology Advances in Digital Libraries</source>
          , p.
          <fpage>86</fpage>
          ,
          <year>1996</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <surname>Zemanta</surname>
          </string-name>
          . http://www.zemanta.com/.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>Common</given-names>
            <surname>Tag</surname>
          </string-name>
          . http://www.commontag.org/.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>K.</given-names>
            <surname>Murat</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Dang</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Uskudarli</surname>
          </string-name>
          , “
          <article-title>UNIpedia: A Unified Ontological Knowledge Platform for Semantic Content Tagging</article-title>
          and Search,
          <source>” Proc. the 4th IEEE International Conference on Semantic Computing</source>
          , Pittsburg, PA, USA,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>K.</given-names>
            <surname>Murat</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Dang</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Uskudarli</surname>
          </string-name>
          , “Semantic TagPrint: Indexing Content at Semantic Level,
          <source>” Proc. the 4th IEEE International Conference on Semantic Computing</source>
          , Pittsburg, PA, USA,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Simmhan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Q.</given-names>
            <surname>Zhou</surname>
          </string-name>
          , and
          <string-name>
            <given-names>V.K.</given-names>
            <surname>Prasanna</surname>
          </string-name>
          ,“
          <article-title>Semantic Information Integration for Smart Grid Applications</article-title>
          ,” Chapter 19,
          <string-name>
            <surname>Green</surname>
            <given-names>IT</given-names>
          </string-name>
          : Technologies and Applications, pp.
          <fpage>361</fpage>
          -
          <lpage>80</lpage>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>J.</given-names>
            <surname>Kirsch</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Goose</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Amir</surname>
          </string-name>
          , and
          <string-name>
            <given-names>P.</given-names>
            <surname>Skare</surname>
          </string-name>
          , “
          <string-name>
            <surname>Toward Survivable</surname>
            <given-names>SCADA</given-names>
          </string-name>
          ,
          <source>” Proc. the Annual Cyber Security and Information Intelligence Research Workshop (CSIIRW-11)</source>
          , Oak Ridge,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>B.</given-names>
            <surname>Smith</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Ashburner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Rosse</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Bard</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Bug</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Ceusters</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Goldberg</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Eilbeck</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Ireland</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Mungall</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Leontis</surname>
          </string-name>
          , P. RoccaSerra,
          <string-name>
            <given-names>A.</given-names>
            <surname>Ruttenberg</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Sansone</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Scheuermann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Shah</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Whetzel</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Lewis</surname>
          </string-name>
          , “
          <article-title>The OBO foundry: coordinated evolution of Ontologies to support biomedical data integration</article-title>
          ,” Nature Biotechnology,
          <volume>25</volume>
          (
          <issue>11</issue>
          ):
          <fpage>1251</fpage>
          -
          <lpage>1255</lpage>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>M.</given-names>
            <surname>Uschold</surname>
          </string-name>
          and
          <string-name>
            <given-names>M.</given-names>
            <surname>Gruninger</surname>
          </string-name>
          , “Ontologies: principles, methods, and applications,” Knowledge Engineering Review,
          <volume>11</volume>
          (
          <issue>2</issue>
          ):
          <fpage>93</fpage>
          -
          <lpage>155</lpage>
          ,
          <year>1996</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>[19] OWL. http://www.w3.org/2004/OWL/.</mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>[20] OBO. http://www.obofoundry.org/.</mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <surname>KIF</surname>
          </string-name>
          <article-title>(Knowledge Interchange Format)</article-title>
          . http://logic.stanford.edu/kif/.
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>[22] OKBC. http://www.ai.sri.com/okbc/.</mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <string-name>
            <surname>Protégé</surname>
          </string-name>
          . http://protege.stanford.edu/.
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>[24] SPARQL. http://www.w3.org/TR/rdf-sparql-query/.</mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          [25]
          <string-name>
            <surname>Sesame</surname>
          </string-name>
          . http://www.openrdf.org/doc/sesame/.
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          [26]
          <string-name>
            <given-names>D.</given-names>
            <surname>Klein</surname>
          </string-name>
          and
          <string-name>
            <given-names>C.D.</given-names>
            <surname>Manning</surname>
          </string-name>
          , “Accurate Unlexicalized Parsing,
          <source>” Proc. the 41st Meeting of the Association for Computational Linguistics</source>
          , pp.
          <fpage>423</fpage>
          -
          <lpage>430</lpage>
          ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>