<!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>COA modelling with probabilistic ontologies</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Henrique C. Marques, José M. P. de Oliveira</string-name>
          <email>[hmarques, parente]@ita.br</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Paulo Cesar G. da Costa</string-name>
          <email>pcosta@c4i.gmu.edu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>C4I Center - George Mason University</institution>
          ,
          <addr-line>Fairfax</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Instituto Tecnológico de Aeronáutica</institution>
          ,
          <addr-line>São José dos Campos</addr-line>
          ,
          <country country="BR">BRAZIL</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>-Planning during complex endeavors is a daunting task in many aspects. An important one is the representation of shared intent, which is an open research topic focused on expressing a common picture among different planning systems with distinct languages, and sometimes disparate problem solving methodologies. The common approach is to use a translator between the order/request message and the planning system, which doesn't convey all the elements that are necessary to support the planning task. The present research proposes to address this issue by the use of a semantic layer as an interface among different planning systems, which not only improves interoperability but also provides support for pruning the search space before the information is sent to the planning system. The layer is based on a probabilistic ontology, which provides shared intent description as well as formalization of the operational domain and of the planning problem, including a principled representation of the involved uncertainty. The proposed scheme supports previous analysis of the search space in order to send to the planning system a concise set of tasks that will contribute to reach the desired end state.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>I. INTRODUCTION</title>
      <p>Complex endeavors are challenging the Command and
Control (C2) community with respect to both planning automation
and shared intent representation. Both topics are important in
order to reach a shared goal during an operation. Because of
the collaborative aspect of a joint planning we need to observe
the interoperability models in order to provide the level of data
representation to be utilised in the planning description.</p>
      <p>
        On the basis of the Organizational Interoperability Maturity
Model for C2 (OIMM) [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], the Levels of Conceptual
Interoperability Model (LCIM) [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], and the Levels of Information
Systems Interoperability (LISI) [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], at least a collaborative
level, from an organizational perspective, and a distributed
level, from a system perspective, have to be achieved in order
to be able to execute a joint planning process [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. From
a data perspective, the semantic (LCIM) interoperability is
needed to provide a collaborative (OIMM) - distributed (LISI)
level in the highest capability. The semantic interactive level
(LCIM Level 3) means that data is shared through the use
of a common reference model and content of the information
exchange requests is unambiguously defined (see Figure 1).
      </p>
      <p>
        Our present research aims to establishing a knowledge
representation for improved planning automation that relies on
Modeling and Simulation (M&amp;S) interoperability frameworks
as its foundational approach. The current major efforts in M&amp;S
interoperability are the SISO Coalition-Battle Management
Language (C-BML) and the SISO Military Scenario Definition
Language (MSDL) [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. They provide restricted semantic
interoperability (mostly relying on the eXtensible Markup
Language - XML format) which allows Command and Control
systems and simulations to interoperate. One of the reasons
behind the restricted semantics is that simulations need less
information to generate behavior than what is needed to C2
planning. Since both standards aim to support interoperability
among systems and simulations based on the structured XML
metadata, their representational demands are comfortably
restricted to the smaller information set than what is needed
for a C2 planning system. Therefore, Command and Control
planning systems cannot take full advantage of the available
information until a more expressive approach is used to
formaly represent it [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
      </p>
      <p>
        The main problem faced by a military planning system is to
generate an adequate, feasible, acceptable, and complete plan
that is also opportune [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. In order to support planning
automation it is a good practice to represent knowledge in a way
that allows for pruning the search space. As a consequence,
algorithms ideally have to work with the minimum knowledge
that is necessary to produce solutions. This is especially true
for the military domain, in which uncertainty is the norm and
a plan is usually comprised by a large number of possible
tasks whose interaction must reach the desired effects (end
state). Also, each organization involved in the operation may
have its own planning system, possibly applying a different
problem-solving method.
      </p>
      <p>With the development of a more expressive representation
to describe the planning domain and the planning problem, it
is expected that a planner will have access to more efficient
pruning algorithms. This, in turn, will support the
identification of solutions for larger problems, as well as to increase
the ability to leverage most of the information available to the
decision-making process.</p>
      <p>Therefore, developing a knowledge representation model
and an associated interoperability model are essential steps
towards the automation of the planning activity, which is also
a major step towards providing alternative Courses of Action
(COA) that are reliable, efficient, and opportune. The present
research investigates the use of a semantic planning layer,
based on a mid-level task probabilistic ontology description as
a technical solution for the contextualization of the planning
problem. The proposed approach is depicted in Figure 2.</p>
      <p>The proposed semantic layer is being developed to support
the use of different planning systems in COA development
based on a common context description. Section IV describes
the layer in more details.</p>
      <p>Semantics are essential to align planning automation with
a shared intent, while also providing consistency in planning
given the orders and requests issued by different organizations.</p>
      <p>The paper is divided as follows. Section II provides
background on the hierarchical planning process. Section III
conveys a brief description of related research addressing
automation strategies for operational planning. Section IV addresses
the proposed semantic layer, while Section V provides an
overview of COA modeling. Section VI describes the COA
development based on the adopted methodology, and Section
VII concludes this paper with a discussion on the current state
of our work.</p>
    </sec>
    <sec id="sec-2">
      <title>II. PLANNING PROCESS</title>
      <p>
        The overall research in this work is grounded on the
collaborative aspect of joint planning, and aims to support the Joint
Operation Planning Process (JOPP) at the operational level of a
joint operation [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. We chose this process because it involves a
joint planning effort within a hierarchical structure with a well
established doctrine. Figure 3 shows JOPP from the research
development’s point of view. The process was divided into six
steps, each one with its own role and task to be achieved. The
present paper addresses the third step, namely the uncertainty
representation during the process of COA determination. For
the purpose of this work, the representation of command intent
and the description of causal relations will be considered as
given. The remaining steps are beyond the scope of this paper.
      </p>
      <p>The output of the third step, COA determination, is a
representation of a Course of Action with a description of the
Measures of Performance (MOP), Measures of Effectiveness
(MOE), the planning constraints, and the possible states of the
environment.</p>
      <p>
        To produce this output, current decision support systems
rely on frameworks that generate orders that are evaluated
through simulations. The shared intent is developed via a
C2 system GUI that normally generates a set of high level
orders and requests that are saved to an exchange data model
database. M&amp;S frameworks make use of the SISO
CoalitionBattle Management Language (C-BML) [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] message schemata
to deliver the command intent, and rely on the SISO Military
Scenario Definition Language (MSDL) [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ][
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] to describe
the scenario and the operational domain in terms of spatial
situation of allocated resources.
      </p>
      <p>
        The work in [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] defined an interface between the C2
system’s BML output and a standard semantic planning language
as the Planning Domain Definition Language (PDDL) [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
In this scheme, the planning system receives a set of orders
converted from the BML format into a more generic planning
language, which enables the generation of the right context as
a planning problem and a planning domain file.
      </p>
      <p>As a result of the adoption of this scheme, many different
planning systems have their own "translator" from BML to a
PDDL-like language, usually not aggregating any advantage
to the planning process since it does not improve planning
agility. In our proposal, we focus on applying ontologies to
support automated reasoning over the search space as a means
to reduce it before sending the context information to the
planning system.</p>
      <p>In this approach, the planning system receives only the
states, methods and operators that are relevant to the
construction of a plan. Efficiency is sought that such this plan can only
be generated under the defined constraints and preconditions,
and must be in conformance to the desired effect.</p>
    </sec>
    <sec id="sec-3">
      <title>III. RELATED WORK</title>
      <p>
        Due to the large spectrum of existing initiatives related to
interoperability among command and control (C2) systems,
as well as among C2 simulation systems, only those of most
interest to this study’s context are mentioned here. Initiatives
such as the SISO C-BML [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] and MSDL [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] have
established the initial structure to support the interoperability
among C2 and simulation systems, as well as are setting
the standards for addressing the problem of translating the
commander’s intent into a format that is suitable for simulation
and planning systems. The NATO Modeling and Simulation
Group Technical Activity 48 (MSG-048) is evaluating a
series of technologies to promote such interoperability and is
conducting experiments with multinational C2 and simulation
systems since 2006 [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ].
      </p>
      <p>
        Another important aspect is to find methods to analyze
and evaluate COAs based on effects, as described in [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ].
The Effects Based Operations planning significantly increases
the number of alternative plans and the depth of evaluation.
Therefore, appropriate metrics must be devised to support
principled quantification of their relative merits. Generating
plans that are aligned with the commander´s intent is a
key aspect that may be achieved by the use of semantics
during the order generation process. The study conducted in
[
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] presented results in which all planned orders verified
by an ontology-based tool have shown inconsistencies. Such
consideration indicates the necessity to utilize semantics in the
planning phase to minimize the possibility of inconsistencies
with the orders generated at the upper level of the command
structure.
      </p>
      <p>
        In the field of ontology generation for tasking planning, the
study in [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ] presented an ontology engineering process
applicable to such problem. The methodology was straightforward
and made explicit the need for breaking down the problem into
small pieces, a known strategy in decision theory. The study
supports the hypothesis that it is very convenient to manipulate
small ontologies that would be integrated later in the process.
      </p>
      <p>
        Initiatives such as [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ] [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ] describe the use of task
ontologies to support pruning before the planning system receives the
planning problem and domain. However, they are not pointing
to the interoperability in multilateral application frameworks
based on the SISO standards.
      </p>
      <p>
        Gilmour et al. [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ] present a solution using a semantic layer
in multilateral frameworks to generate plans in accordance
with a military ontology. However, the work focus purely in
the semantic interoperability of tasks, and does not address
the interoperability issue among different planning systems.
Thus, in addition to a semantic layer, an ontology extension
to support different planning systems has to be established,
since each system is likely to have its specific language and a
problem-solving method.
      </p>
      <p>
        The work in [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ] is closer to our approach and differs with
respect to the implementation and to the ontology integration.
While the authors developed a series of military ontologies in
OWL language [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ], our focus is on achieving interoperability
with the reuse of existing ontologies. Another difference is our
concern in representing uncertainty in a explicit and principled
way, so our approach does address uncertainty representation
and reasoning through a mid-level task probabilistic ontology.
      </p>
    </sec>
    <sec id="sec-4">
      <title>IV. SEMANTIC PLANNING LAYER</title>
      <p>Different hierarchical levels have to produce a joint
operational plan, so different types of planning systems may be
utilized throughout the operational campaign. The operational
level works with higher level tasks (activities) and is not aware
of the exact unity that will handle the task and achieve its
desired effect, but it does know which effects will interfere
with the desired end-state.</p>
      <p>Effects modeling thus play a key role in determining which
activities have to be executed in order to achieve the desired
effects. It helps improving the tactical level task decomposition
by ensuring that only the tasks with higher probabilities to lead
to the desired goal effect will be planned at the lower level of
the hierarchical chain.</p>
      <p>To develop an approach that might handle the effects-based
modeling we are proposing a Semantic Planning Layer, which
is depicted in Figure 4. As can be seen in the figure, the
Semantic Planning Layer is made of a Task Probabilistic
Ontology, an Activities Reasoning Module, and a Planning
Context Definition Module.</p>
      <p>1) Task Probabilistic Ontology: In order to model the
effects and to translate it into a lower level task decomposition,
it will be necessary to develop a task ontology that can handle
uncertainty. From our perspective, activities are tasks that are
more abstract and need to be broken down into smaller tasks
until reaching a primitive one. It is also necessary to describe
the shared intent in a way that it can be related as desired
effects and activities. This is the main reason of our interest
in generating a BML ontology description.</p>
      <p>Another important description is the domain ontology that
will formalize the planning domain specification and interface
with other domain descriptions. We are aiming to both
describing the hierarchical planning concepts as well as to relate
it with the COA description process. The end result will be a
better description of the way the activities will be structured
in phases and the establishment of a view from the operational
perspective.</p>
      <p>
        The mid-level Task Probabilistic Ontology is composed by
four ontologies: BML Ontology (BML), Application Domain
Ontology (ApplicationDomain), Planning Ontology
(HPlanner), and COA Ontology (COA). It is being developed using
the PR-OWL probabilistic ontology language [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ] and aims to
describe the connection between each ontology as well as the
causal relations between the main concepts considered during
pre-planning reasoning.
      </p>
      <p>The constituent ontologies can be existing ones, which
can come from the literature, gold standards, or a particular
implementation. The basic premise is that an upper/mid-level
ontology describing the core task planning information, and
having principled support for uncertainty representation and
reasoning will be capable to comprehensively convey all the
necessary domain information for planning purposes.</p>
      <p>Figure 5 depicts a partial view of the concepts described in
the mid-level probabilistic ontology. The hierarchical planner
ontology is a specialization of the planning ontology and
can be more detailed if needed by a specific problem-solving
method. In this scheme, mapping concepts among and between
constituent ontologies can be seen as a way of ensuring
interoperability from one problem domain to another (eg.,
from the BML-described commander intent to the Planning
domain).
2) Activities Reasoning: The activities reasoning module
executers four main steps:</p>
      <p>
        Pull BML/MSDL campaign level orders - This step
utilizes an already available BML service and no
development will be made;
Identify the activities to be planned through the
probabilistic task ontology and by the analyst criteria (defined
threshold for each phase (MOE));
Generate Situation Specific Bayesian Networks (SSBN)
[
        <xref ref-type="bibr" rid="ref24">24</xref>
        ] to support the activities inference; and
Export the activities list to be described by the Planning
Context definition module;
      </p>
      <p>After a succession of queries, a list with the selected
activities will be sent to the Planning Context Definition
module. The proposed algorithm is showed below:</p>
      <p>3) Planning Context Definition: The planning context
definition is the process of establishing the problem context to
be submitted to the planning system. It is composed by three
activities:</p>
      <p>Planning Domain definition - After receiving the activities
list the module will identify methods that decompose the
activities and the operators;
Planning Problem definition - The planning problem
consists of the tasks to be decomposed and the initial
state declared on the MSDL message; and</p>
      <p>PDDL files generation.</p>
      <p>After receiving the task list, the module has to describe the
tasks with the constraints, the current state, and the proposed
goal. Such description will then be translated into a
PDDLlike format. Finally, the resulting files will be submitted to
a domain-independent planning system that will address the
planning problem. As depicted in Figure 4, the output are the
two PDDL formatted files describing the Domain Problem and
the Planning Problem.</p>
    </sec>
    <sec id="sec-5">
      <title>V. COA MODELING</title>
      <p>
        Military operations are generally described by phases and
activities at the operational level, which are then translated
into tasks at the tactical level. The development of Courses of
Action follows a decomposition model in the Effects-Based
Operations (EBO) paradigm [
        <xref ref-type="bibr" rid="ref25">25</xref>
        ]. The modeling effort aims
to express a cause-effect relationship from the perspective of
activities that will produce outcomes.
      </p>
      <p>
        Figure 7 shows an example of a phase decomposed into
activities and tasks. The arrangement of both the activities and
the tasks may be serial, parallel or a combination of both. The
task decomposition is a process used in hierarchical planning
systems [
        <xref ref-type="bibr" rid="ref26">26</xref>
        ] [
        <xref ref-type="bibr" rid="ref27">27</xref>
        ]. In our approach, different hierarchical
planning systems can receive shared intents and generate
different plans that adhere to a mid-level ontology, based
on their own problem-solving methods. Hierarchical planning
systems were selected because they build plans by hierarchical
decomposition that correspond to task models of human task
performers. In that way, the generated plans will meet with
human approval [
        <xref ref-type="bibr" rid="ref28">28</xref>
        ].
      </p>
      <p>So, in our modeling we describe the COA in terms of
phases, activities, tasks, and effects. Figure 8 shows the
cumulative effects model we are using to generate queries about the
planned tasks. Before sending activities to the planning effort,
it is possible to identify the ones that are most important to
reach the desired phase’s outcome.</p>
      <p>The process of COA modeling demands a comprehensive
method to develop the different ontologies to be utilized in
the semantic layer. Our approach relies on ontologies for
describing and updating the necessary information to support
a planning cell from a military organization in acquiring and
maintaining a high-level situational awareness. This requires a
formal representation of concepts about time, space, actions,
effects, resources, and uncertainty over a dynamic future.</p>
      <p>
        Traditional ontologies do not have built-in mechanisms for
representing or inferring with uncertainty, requiring extensions
with new classes, subclasses, and properties that support
uncertainty representation and reasoning. The PR-OWL
probabilistic ontology language [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ] and its newest version
PROWL 2 [
        <xref ref-type="bibr" rid="ref29">29</xref>
        ] are written in OWL [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ] and provide a consistent
framework for representing and reasoning in domains with
uncertainty.
      </p>
      <p>
        The mathematical basis for PR-OWL is Multi-Entity
Bayesian Networks - MEBN, which integrates first order logic
with Bayesian probability. MEBN provides adequate formal
support for representing a joint probability distribution over
situations involving unbounded numbers of entities interacting
in complex ways [
        <xref ref-type="bibr" rid="ref24">24</xref>
        ]. This is a major requirement to achieve
principled representation of the multiple, multi-modal sensor
input and their compounded interactions. MEBN represents
domain information as a collection of inter-related entities
and their respective attributes. Knowledge about attributes of
entities and their relationships is represented as a collection of
repeatable patterns, known as MEBN Fragments (MFrags).
      </p>
      <p>A set of MFrags that collectively satisfies first-order logical
constraints ensuring a unique joint probability distribution is
a MEBN Theory (MTheory). As in any Bayesian approach, a
MEBN model includes the a priori knowledge stored in local
probability distributions. The inference process is triggered by
one or more queries, which trigger a reasoner that applies
Bayesian inference to calculate the marginal distributions.</p>
      <p>During a campaign, as new information accrues, this process
is used to calculate the posterior probabilities that represent the
best knowledge possible to support new planned actions given
the information available at the decision time.</p>
    </sec>
    <sec id="sec-6">
      <title>VI. COA DEVELOPMENT</title>
      <p>The COA development starts with the analysis of the
activities to be delineated as tasks to the tactical level. Thus, it is
necessary to have the operational description of the outcomes
in order to reason about the associated likelihoods of reaching
the desired effects.</p>
      <p>In our model we describe the phases, activities, and effects
that will produce the desired end state in a backwards
description of the plan. That is, from the desired effect back to the
task to be executed as seen in Table I.</p>
      <p>The information received from the operational level
establishes the COA description and the Domain description.
The Domain ontology captures all the information regarding
the physical aspects of the operation, and will be utilized
to describe the scenario situation. The Effects, Activities and
Tasks are described as individuals in our COA ontology (see
Figure 9).</p>
      <p>During the ontology construction we can use the modeling
depicted in Figure 8, showing the cumulative effects to support
the phase’s outcome reasoning. This part of the ontology can
be modelled through the probabilistic representation available
in PR-OWL. Basically, we model the causal relations in the
same way a depicted in Figure 8, establishing a joint
probability distribution that will allow reasoning on the available
information regarding the current operation situation.</p>
      <p>Figure 10 shows a MEBN fragment with only the effects
portion of the ontology. The MFrag shows the structure, but
not the individuals in the knowledge base. Resident nodes
(yellow ovals in the figure) are the actual random variables
that form the core subject of the MFrag. Context nodes
(green pentagons in the figure) are boolean random variables
representing conditions that must be satisfied to make the
probability distribution of an MFrag valid. The reasoning
occurs by executing a query to support the analysis during the
tactical COA development. Thus, given a new set of effects to
be reached, one can query the knowledge base for which task
might have the greatest influence on a specific effect.</p>
      <p>Using the data in Table I we can identify the impact from
the Air Superiority phase on the accumulated effect. This takes
into account the change in the quantity of a given task from
a specific activity. We have modeled the knowledge base with
two scenarios:</p>
      <p>One task as the attack in the C2 Comm
(Attack_C2Comm_03Bravo), two tasks as SEAD missions
(SEAD_AAA_01Alfa), and one task as the attack in the
Radar site (Attack_Radar_02Bravo). See Figure 11; and
Two tasks as the attack in the C2 Comm
(Attack_C2Comm_03Bravo), two tasks as SEAD missions
(SEAD_AAA_01Alfa), and one task as the attack in the
Radar site (Attack_Radar_02Bravo). See Figure 12.</p>
      <p>In performing this analysis, one can assess the
impact of another attack mission over the C2
Communications facilities with an expected increasing in the
accumulated effect by 3.18%. This analysis capability
allows for not only to decomposing the activities into tasks
as expected for a planning algorithm, but also to
identify the activities to be decomposed that will support the
expected effect for each phase of the campaign. In the
example, the answered query ?hasAccomplishedPhaseGoal
(Phase1_Air_superiority_COA_02A) has not reached yet the
60% level defined threshold and other activities will be
selected in order to generate the minimum expected outcome
for the desired effect based on the model.</p>
    </sec>
    <sec id="sec-7">
      <title>VII. CONCLUSION AND FUTURE WORK</title>
      <p>The present work involves using a probabilistic ontology
language (PR-OWL) to support task analysis and to provide
a mid-level ontology as part of a layer between the intent
description and the planning system that has to generate a
Course of Action. Our approach aims to establish a knowledge
representation layer to facilitate pruning the search space. It
also verifies the activities that have to be sent to the planner
in order to generate the plan that will contribute to reach the
desired end state of the campaign.</p>
      <p>As future work we have identified the need of improving
the effects model to also show the secondary effects produced
by the primary effects caused by activities. We also intend to
fully implement the semantic layer and to integrate a planning
system that is capable to take advantage of the approach.
Finally, we plan to test and evaluate our results via a simulation
testbed, which is current in development in a shared effort
between the GMU C4I Center and the Brazilian Instituto
Tecnológico de Aeronáutica.</p>
      <p>The SSBN of the first scenario. The cumulative effect is 53.24%.</p>
      <p>The SSBN of the second scenario. The cumulative effect is 56.42%</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>T.</given-names>
            <surname>Clark</surname>
          </string-name>
          . and
          <string-name>
            <given-names>R.</given-names>
            <surname>Jones</surname>
          </string-name>
          , “
          <article-title>Organisational interoperability maturity model for c2,”</article-title>
          <source>in Proceedings of the 1999 Command and Control Research and Technology Symposium</source>
          ., United States Naval War College.
          <source>Newport: ommand and Control Research Program (CCRP)</source>
          ,
          <year>June 1999</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>A.</given-names>
            <surname>Tolk</surname>
          </string-name>
          and
          <string-name>
            <given-names>J. A.</given-names>
            <surname>Muguira</surname>
          </string-name>
          , “
          <article-title>The Levels of Conceptual Interoperability Model (LCIM),”</article-title>
          <source>in Proceedings IEEE Fall Simulation Interoperability Workshop</source>
          . IEEE CS Press,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>D. o. D.</surname>
          </string-name>
          C4ISR Interoperability Working Group, “
          <article-title>Levels of information systems interoperability</article-title>
          ,” C4ISR Architectures Working Group,
          <year>March 1998</year>
          . [Online]. Available: http://www.c3i.osd.mil/org/cio/i3/
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>L. S.</given-names>
            <surname>Winters</surname>
          </string-name>
          ,
          <string-name>
            <surname>M. M. Gorman</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Tolk</surname>
          </string-name>
          , “
          <article-title>Next generation data interoperability: It's all about the metadata</article-title>
          ,” Fall Simulation Interoperability Workshop, Fall Simulation Interoperability Workshop,
          <year>September 2006</year>
          , orlando, FL.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>S. I. S.</given-names>
            <surname>Organization</surname>
          </string-name>
          ,
          <string-name>
            <surname>C-BML- PDG - Coalition-Battle Management</surname>
            <given-names>Language</given-names>
          </string-name>
          ,
          <article-title>Simulation Interoperability Standards Organization (SISO) Std</article-title>
          .,
          <year>April 2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6] --,
          <string-name>
            <surname>SISO-REF-</surname>
          </string-name>
          015
          <article-title>-2006 Military Scenario Definition Language (MSDL), Simulation Interoperability Standards Organization (SISO) Std</article-title>
          .,
          <year>September 2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>A.</given-names>
            <surname>Tolk</surname>
          </string-name>
          and
          <string-name>
            <given-names>C. L.</given-names>
            <surname>Blais</surname>
          </string-name>
          , “Taxonomies, ontologies, and
          <article-title>battle management languages - recomendations for the coalition bml study group</article-title>
          ,” Spring Simulation Interoperability Workshop, Spring Simulation Interoperability Workshop,
          <year>April 2005</year>
          , san Diego.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8] DoD, Joint Operation Planning, joint publication 5 ed., Joint Publication Library, USA, august
          <year>2011</year>
          . [Online]. Available: http://www.dtic.mil/doctrine/new_pubs/jp5_0.pdf
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>J.</given-names>
            <surname>Publication</surname>
          </string-name>
          , Command and Control of Joint Air Operations,
          <year>January 2010</year>
          . [Online]. Available: http://www.dtic.mil/doctrine/new_pubs/jp3_
          <fpage>30</fpage>
          .pdf
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <article-title>(2011, September) Simulation interoperability standards organization</article-title>
          . SISO. [Online]. Available: http://www.sisostds.org/Home.aspx
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>M.</given-names>
            <surname>Nazih</surname>
          </string-name>
          and U. Schade, “
          <article-title>Einsatz der battle management language zur befehligung von einheiten in einem simulationssystem,” FKIE-</article-title>
          <string-name>
            <surname>Bericht</surname>
          </string-name>
          ,
          <source>Tech. Rep. 174</source>
          ,
          <year>2009</year>
          , wachtberg:FGAN.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>D.</given-names>
            <surname>McDermott</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Ghallab</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Howe</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Knoblock</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Ram</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Veloso</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Weld</surname>
          </string-name>
          , and
          <string-name>
            <given-names>D.</given-names>
            <surname>Wilkins</surname>
          </string-name>
          , “
          <article-title>PDDL - the planning domain definition language - version 1.2,” Yale Center for Computational Vision</article-title>
          and Control,
          <source>Tech. Rep</source>
          .,
          <year>October 1998</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>J.</given-names>
            <surname>Pullen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Hike</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Levine</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Tolk</surname>
          </string-name>
          , and
          <string-name>
            <given-names>C.</given-names>
            <surname>Blais</surname>
          </string-name>
          , “
          <article-title>Joint battle management language (jbml) - us contribution to the c-bml pdf and nato msg-048 ta</article-title>
          ,”
          <source>presented at the IEEE European Simulation Interoperability Workshop</source>
          ,
          <year>June 2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>J.</given-names>
            <surname>Pullen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Corner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Cordonnier</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Mennane</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Khimeche</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O. M.</given-names>
            <surname>Mevassvik</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Alstad</surname>
          </string-name>
          ,
          <string-name>
            <given-names>U.</given-names>
            <surname>Schade</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Frey</surname>
          </string-name>
          , N. d. Reus, P. d. Krom,
          <string-name>
            <surname>N.</surname>
          </string-name>
          <article-title>LeGrand, and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Brook</surname>
          </string-name>
          , “
          <article-title>Adding reports to coalition battle management language for nato msg</article-title>
          -
          <volume>048</volume>
          ,” in Joint SISO/SCS European Multiconference, Instambul, Turkey,
          <year>July 2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>C.</given-names>
            <surname>Egan</surname>
          </string-name>
          and
          <string-name>
            <given-names>J.</given-names>
            <surname>Reaper</surname>
          </string-name>
          , “
          <article-title>Course of action scoring and analysis</article-title>
          ,
          <source>” presented at the 12th International Command and Control Research and Technology Symposium, DOD CCRP. Newport</source>
          ,
          <string-name>
            <surname>RI</surname>
          </string-name>
          , USA: CCRP Publications,
          <year>June 2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>D.</given-names>
            <surname>Gilmour</surname>
          </string-name>
          and
          <string-name>
            <given-names>Z. M.</given-names>
            <surname>Zhang</surname>
          </string-name>
          , “
          <article-title>Determining course of action alignment with operational objectives,” presented at the Command and Control Research and Technology Symposium: The state of the art of the practice</article-title>
          ,
          <year>June 2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>A.</given-names>
            <surname>Frantz</surname>
          </string-name>
          and
          <string-name>
            <given-names>M.</given-names>
            <surname>Franco</surname>
          </string-name>
          , “
          <article-title>A semantic web application for the air tasking order,” presented at the 10th</article-title>
          <source>International Command and Control Research and Technology Symposium: The Future of C2</source>
          ,
          <year>June 2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>B.</given-names>
            <surname>Chandrasekaran</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. R.</given-names>
            <surname>Josephson</surname>
          </string-name>
          , and
          <string-name>
            <given-names>V. R.</given-names>
            <surname>Benjamins</surname>
          </string-name>
          , “
          <article-title>Ontology of tasks and methods</article-title>
          ,”
          <year>1998</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>A. F.</given-names>
            <surname>Martins and R. D</surname>
          </string-name>
          . A. Falbo, “
          <article-title>Models for representing task ontologies</article-title>
          .”
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <given-names>D.</given-names>
            <surname>Gilmour</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Krause</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Lehman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>McKeever</surname>
          </string-name>
          , and T. Stirtzinger, “
          <article-title>Scenario generation to support mission planning</article-title>
          ,
          <source>” 2006 Command and Control Research and Technology Symposium</source>
          ,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <surname>I.-C. Hsu</surname>
            ,
            <given-names>Y. K.</given-names>
          </string-name>
          <string-name>
            <surname>Tzeng</surname>
          </string-name>
          , Y. J. Cheng, and D.-C. Huang, “
          <article-title>Semanticbased military scenario generation for mission planning</article-title>
          ,
          <source>” Journal of Convergence Information technology</source>
          , vol.
          <volume>6</volume>
          , no.
          <issue>4</issue>
          , pp.
          <fpage>123</fpage>
          -
          <lpage>134</lpage>
          ,
          <year>April 2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <fpage>W3C</fpage>
          .
          <article-title>(2004, February) Owl web ontology language</article-title>
          .
          <source>W3C Recommendation</source>
          . [Online]. Available: http://www.w3.org/TR/owlfeatures/
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <string-name>
            <surname>P. C. G. da Costa</surname>
          </string-name>
          , “
          <article-title>Bayesian semantics for the semantic web</article-title>
          ,
          <source>” Ph.D. dissertation</source>
          , George Mason University,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [24]
          <string-name>
            <surname>K. B. Laskey.</surname>
          </string-name>
          (
          <year>2007</year>
          ,
          <article-title>December) Mebn: A language for firstorder bayesian knowledge bases</article-title>
          . Online. [Online]. Available: http://ite.gmu.edu/ klaskey/papers/Laskey_MEBN_Logic.pdf
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          [25]
          <string-name>
            <given-names>E. A.</given-names>
            <surname>Smith</surname>
          </string-name>
          ,
          <string-name>
            <surname>Effects Based</surname>
          </string-name>
          <article-title>Operations: Applying Network Centric Warfare in Peace, Crisis and War</article-title>
          , DoD, Ed. CCRP,
          <year>2002</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          [26]
          <string-name>
            <given-names>Q.</given-names>
            <surname>Yang</surname>
          </string-name>
          ,
          <article-title>Intelligent planning: a decomposition and abstraction based approach</article-title>
          . London, UK: Springer-Verlag,
          <year>1997</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          [27]
          <string-name>
            <given-names>M.</given-names>
            <surname>Ghallab</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Nau</surname>
          </string-name>
          , and
          <string-name>
            <given-names>P.</given-names>
            <surname>Traverso</surname>
          </string-name>
          ,
          <source>Automated Planning Theory and Practice</source>
          . Amsterdam: Elsevier/Morgan Kaufmann,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          [28]
          <string-name>
            <given-names>R. P.</given-names>
            <surname>Goldman</surname>
          </string-name>
          , “
          <article-title>Ontologies and planners a statement of interest</article-title>
          ,”
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          [29]
          <string-name>
            <given-names>R.</given-names>
            <surname>Carvalho</surname>
          </string-name>
          , “
          <article-title>Probabilistic ontology: Representation and modeling methodology</article-title>
          ,
          <source>” Ph.D. dissertation</source>
          , George Mason University,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>