Information Meeting on Joint Doctrine Ontology: Difference between revisions

From NCOR Wiki
Jump to navigationJump to search
 
(45 intermediate revisions by the same user not shown)
Line 1: Line 1:
Venue: MACE (Multi-Agency Collaboration Environment), [https://www.google.com/maps/dir/IAD,+Dulles,+VA/3076+Centreville+Rd,+Herndon,+VA+20171/@38.9423036,-77.4717987,13z/data=!3m1!4b1!4m13!4m12!1m5!1m1!1s0x89b64740174eb057:0x8e01cb201080601d!2m2!1d-77.4565388!2d38.9531162!1m5!1m1!1s0x89b64656a0a33ca9:0xd18aa1814fff93df!2m2!1d-77.41971!2d38.923061 3076 Centreville Road, Herndon, VA 20171]
Venue: MACE (Multi-Agency Collaboration Environment), [https://www.google.com/maps/dir/IAD,+Dulles,+VA/3076+Centreville+Rd,+Herndon,+VA+20171/@38.9423036,-77.4717987,13z/data=!3m1!4b1!4m13!4m12!1m5!1m1!1s0x89b64740174eb057:0x8e01cb201080601d!2m2!1d-77.4565388!2d38.9531162!1m5!1m1!1s0x89b64656a0a33ca9:0xd18aa1814fff93df!2m2!1d-77.41971!2d38.923061 Suite 114, 3076 Centreville Road, Herndon, VA 20171]


Date: September 16-17, 2015
Date: September 16-17, 2015


Nearest hotel: [http://www3.hilton.com/en/hotels/virginia/hilton-washington-dulles-airport-IADAHHF/index.html, Hilton Washington Dulles Airport]
For further information please write to Barry Smith <phismith@buffalo.edu>
 
Registration: $50 flat fee to cover costs


----
----


== Background ==
== '''Background''' ==


The goal of the Joint Doctrine Ontology Project is to create a formal and computer-readable representation of the content of the major doctrinal publications using as starting point the definitions in the [http://www.dtic.mil/doctrine/dod_dictionary/ DoD Dictionary] (JP 1-02).  
The goal of the Joint Doctrine Ontology (JDO) project is to create a formal and computer-readable representation of the content of the major doctrinal publications, using as starting point the definitions in the [http://www.dtic.mil/doctrine/dod_dictionary/ DoD Dictionary] (JP 1-02).


'''Examples of potential benefits to doctrine authors:'''  
== '''Examples of Potential Benefits of the JDO''' ==


1. to doctrine authors:
:- enabling the creation of flexible visualizations of how different parts of doctrine interact, or of doctrinal content relevant to particular types of operations or capabilities
:- enabling the creation of flexible visualizations of how different parts of doctrine interact, or of doctrinal content relevant to particular types of operations or capabilities
:- allowing a tracing of dependences between definitions that can help to ensure that changes in definitions cascade appropriately through all dependent definitions when revisions are made
:- allowing a tracing of dependences between definitions that can help to ensure that changes in definitions cascade appropriately through all dependent definitions when revisions are made


'''Examples of potential benefits to doctrine users:'''
2. to doctrine users:
 
:- enabling more effective discovery of doctrinal knowledge in forms useful for computational reasoning
:- enabling more effective discovery of doctrinal knowledge in forms useful for computational reasoning
:- providing for each term in the DoD Dictionary its own web page, serving as a repository of usage and of revision history, and  as entry points for cross-references to other authoritative sources
:- providing for each term in the DoD Dictionary its own web page, serving as a repository of usage and of revision history,  
 
'''New uses for the content of doctrine potentially enabled'''


3. in the form of new uses for the content of doctrine
:- allowing the DoD Dictionary to serve as entry point for web-based searches across multiple repositories of authoritative data
:- facilitating greater coordination of training and operations particularly as these involve IT systems working alongside human beings
:- facilitating greater coordination of training and operations particularly as these involve IT systems working alongside human beings
:- increasing automation of processes such as plan specification, ops assessment, BlueForce Status, and [http://www.tradoc.army.mil/tpubs/regs/TR71-4.pdf scenario development]
:- increasing automation of processes such as plan specification, ops assessment, BlueForce Status, and scenario development
:- allowing new sorts of assessment processes, for example based on measures of adherence to doctrine, processes which may in turn give rise to new ways of computationally identifying areas where changes in doctrine may be needed
:- allowing new sorts of assessment processes, for example based on measures of adherence to doctrine, processes which may in turn give rise to new ways of computationally identifying areas where changes in doctrine may be needed


Most importantly, the Joint Doctrine Ontology will provide a new source of ground truth for ontologists across DoD and IC that will help to identify gaps and errors in existing military ontologies. It will thereby support consistent agile ontology development of a sort that will counteract current tendencies towards silo-formation and failure of interoperation.
The Joint Doctrine Ontology will enable doctrine to serve as a new source of ground truth for ontologists across DoD and IC that will help to identify gaps and errors in existing military ontologies. It will thereby support consistent agile ontology development of a sort that will counteract current tendencies towards silo-formation and failure of interoperation.
 
----
 
== '''Schedule: Wednesday, September 16''' ==
 
8:30 Coffee available


The project is directed by Barry Smith of the [http://ncor.us National Center for Ontological Research]. A first sample is [http://ncor.buffalo.edu/Joint-Doctrine-Ontology/JP1-is_a-hierarchy.pdf here]. Work on the ontology is being carried out as part of two Rome Air Force Research Laboratory (AFRL) projects "Mission Assurance through Mission Awareness (MAMA)" and "Living Plan". The goal of MAMA is to enhance cyber-situational awareness by the automated assessment of mission execution through the analysis of network traffic flows. MAMA has two facets, relating to Air Mobility Command and Air Force Space Command. The goal of the Living Plan initiative is to transform Air Force planning and operations assessment from a disjointed static approach based on paper documents into a unified dynamic and computational approach.
9:00 Barry Smith (NCOR): Introduction to the meeting: Addressing DoD information and coordination needs


----
9:15 Jason R. Bryant (AFRL): Introduction to the MAMA Project
 
9:30 Grizelda Loy-Kroft (AFRL): Agile and Secure Information Capabilities to Enhance Decision-Making for Cradle-to-Cradle System Life Cycle Management


== Provisional Agenda ==
9:45 Brian Campbell (Securboration): MAMA applied to Air Mobility Command 


'''September 16'''
10:15 Break


8:30 Coffee available
10:30 William Tagliaferri (CUBRC): MAMA applied to the Space Mission


9:00 Start
11:00 Erik Thomsen (Charles River Analytics): Ontological Support for Living Plan Specification, Execution and Evaluation


*Barry Smith (NCOR): Introduction to the meeting: Addressing DoD information and coordination needs
11:30 Ron Rudnicki (CUBRC): Common Core Ontologies (IARPA, I2WD, JIDO, ONR, AFRL, ARL)


*Col William Mandrick (Institute for Military Support to Governance / Joint Special Operations University): War Fighter Ontology
12:00 Lunch


*Lee Krause (Securboration): MAMA applied to Air Mobility Command 
13:00 Lt Col James McArthur (USMC / Joint Staff J-7): Joint Doctrine Support for AFRL


*William Tagliaferri (CUBRC): MAMA applied to the Space Mission
13:05 Col William Mandrick, PhD (Institute for Military Support to Governance / Joint Special Operations University): War Fighter Ontology


*Ron Rudnicki (CUBRC): Common Core Ontologies (IARPA, I2WD, JIDO, ONR, AFRL, ARL)
13:30 Barry Smith (NCOR), Alex Cox (CUBRC): Joint Doctrine Ontology: Strategy, Benefits, Applications


12:00 - 13:00 Lunch
14:00 Review of the Dictionary Writing Guide, Enclosure of [http://www.dtic.mil/doctrine/new_pubs/cjcsi5705_01d.pdf CJCSI 5705-01D]


*Barry Smith (NCOR): Joint Doctrine Ontology: Strategy, Benefits, Applications
14:30 Presentation of initial draft modules
::[http://ncor.buffalo.edu/JDO/JP1 JP1 Capstone Ontology]
::[http://ncor.buffalo.edu/JDO/JP3-0 JP 3-0 (Operations) Ontology] 
::[http://ncor.buffalo.edu/JDO/JP3-14 JP 3-14 (Space Operations) Ontology]


*Initial draft modules:
15:00 Break
::JP1 Capstone (Mission) Ontology (Barry Smith)
::JP 3-0 (Operations) Ontology (Barry Smith)
:::JP 3-14 (Space Operations) Ontology (Alex Cox, CUBRC)
:::JP 3-57 (Civil-Military Operations) Ontology (Col William Mandrick, JSOU and Fort Bragg)
::JP 5-0 (Plan) Ontology (Barry Smith)


*Feedback from Joint Doctrine Staff
15:15 Feedback and General Discussion, introduced by Lt Col William D Betts (USAF / Joint Staff J-7, DoD Terminologist)


*Discussion
17:00 Close


*18:00 Dinner
18:00 Dinner


September 17
== '''Schedule: Thursday September 17''' ==


8:30 Coffee available
8:30 Coffee available


9:00 Start
The goal of Day 2 is to address technical details of the work described on Day 1
*Erik Thomsen (CRA) Living Plan  
 
*Space Mission Data and Space Ontology (CUBRC, AFRL Rome)
9:00 Robert J. Farrell (AFRL): The Living Plan in a Distributed Contested Environment [http://ncor.buffalo.edu/2015/JDO-MACE/Farrell.pptx Slides]
*Transcom Mission Data and Transport Ontology (Securboration)
 
9:45 Alexander Cox (CUBRC): Space Mission Data and Space Ontology  
 
10:45 Break
 
11:00 Michelle Sabin (Securboration), David Monk (C5T), Janet Girton (C5T), and Alan Belasco (Securboration): USTRANSCOM Mission Data and Transport Ontology [http://ncor.buffalo.edu/2015/JDO-MACE/RAP.pptx Slides 1] [http://ncor.buffalo.edu/2015/JDO-MACE/SES.pptx Slides 2]


12:00 Lunch
12:00 Lunch


13:00 - 15:30 [Closed Session]
13:00 - 15:30 [Closed Session]

Latest revision as of 00:10, 15 October 2015

Venue: MACE (Multi-Agency Collaboration Environment), Suite 114, 3076 Centreville Road, Herndon, VA 20171

Date: September 16-17, 2015

For further information please write to Barry Smith <phismith@buffalo.edu>


Background

The goal of the Joint Doctrine Ontology (JDO) project is to create a formal and computer-readable representation of the content of the major doctrinal publications, using as starting point the definitions in the DoD Dictionary (JP 1-02).

Examples of Potential Benefits of the JDO

1. to doctrine authors:

- enabling the creation of flexible visualizations of how different parts of doctrine interact, or of doctrinal content relevant to particular types of operations or capabilities
- allowing a tracing of dependences between definitions that can help to ensure that changes in definitions cascade appropriately through all dependent definitions when revisions are made

2. to doctrine users:

- enabling more effective discovery of doctrinal knowledge in forms useful for computational reasoning
- providing for each term in the DoD Dictionary its own web page, serving as a repository of usage and of revision history,

3. in the form of new uses for the content of doctrine

- allowing the DoD Dictionary to serve as entry point for web-based searches across multiple repositories of authoritative data
- facilitating greater coordination of training and operations particularly as these involve IT systems working alongside human beings
- increasing automation of processes such as plan specification, ops assessment, BlueForce Status, and scenario development
- allowing new sorts of assessment processes, for example based on measures of adherence to doctrine, processes which may in turn give rise to new ways of computationally identifying areas where changes in doctrine may be needed

The Joint Doctrine Ontology will enable doctrine to serve as a new source of ground truth for ontologists across DoD and IC that will help to identify gaps and errors in existing military ontologies. It will thereby support consistent agile ontology development of a sort that will counteract current tendencies towards silo-formation and failure of interoperation.


Schedule: Wednesday, September 16

8:30 Coffee available

9:00 Barry Smith (NCOR): Introduction to the meeting: Addressing DoD information and coordination needs

9:15 Jason R. Bryant (AFRL): Introduction to the MAMA Project

9:30 Grizelda Loy-Kroft (AFRL): Agile and Secure Information Capabilities to Enhance Decision-Making for Cradle-to-Cradle System Life Cycle Management

9:45 Brian Campbell (Securboration): MAMA applied to Air Mobility Command

10:15 Break

10:30 William Tagliaferri (CUBRC): MAMA applied to the Space Mission

11:00 Erik Thomsen (Charles River Analytics): Ontological Support for Living Plan Specification, Execution and Evaluation

11:30 Ron Rudnicki (CUBRC): Common Core Ontologies (IARPA, I2WD, JIDO, ONR, AFRL, ARL)

12:00 Lunch

13:00 Lt Col James McArthur (USMC / Joint Staff J-7): Joint Doctrine Support for AFRL

13:05 Col William Mandrick, PhD (Institute for Military Support to Governance / Joint Special Operations University): War Fighter Ontology

13:30 Barry Smith (NCOR), Alex Cox (CUBRC): Joint Doctrine Ontology: Strategy, Benefits, Applications

14:00 Review of the Dictionary Writing Guide, Enclosure of CJCSI 5705-01D

14:30 Presentation of initial draft modules

JP1 Capstone Ontology
JP 3-0 (Operations) Ontology
JP 3-14 (Space Operations) Ontology

15:00 Break

15:15 Feedback and General Discussion, introduced by Lt Col William D Betts (USAF / Joint Staff J-7, DoD Terminologist)

17:00 Close

18:00 Dinner

Schedule: Thursday September 17

8:30 Coffee available

The goal of Day 2 is to address technical details of the work described on Day 1

9:00 Robert J. Farrell (AFRL): The Living Plan in a Distributed Contested Environment Slides

9:45 Alexander Cox (CUBRC): Space Mission Data and Space Ontology

10:45 Break

11:00 Michelle Sabin (Securboration), David Monk (C5T), Janet Girton (C5T), and Alan Belasco (Securboration): USTRANSCOM Mission Data and Transport Ontology Slides 1 Slides 2

12:00 Lunch

13:00 - 15:30 [Closed Session]