Information Meeting on Joint Doctrine Ontology: Difference between revisions
m (→Background) |
m (→Background) |
||
Line 16: | Line 16: | ||
:- enabling the creation of flexible visualizations of how different parts of doctrine interact | :- enabling the creation of flexible visualizations of how different parts of doctrine interact | ||
:- allowing a | :- 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 | ||
It will help '''doctrine users''' for example by | It will help '''doctrine users''' for example by | ||
:- enabling more | :- enabling more effective discovery of doctrinal knowledge in forms useful for computational reasoning | ||
:- providing for each term in the [http://www.dtic.mil/doctrine/dod_dictionary/ DoD Dictionary of Military and Associated Terms] (JP 1-02) a separate | :- providing for each term in the [http://www.dtic.mil/doctrine/dod_dictionary/ DoD Dictionary of Military and Associated Terms] (JP 1-02) a separate web address serving as a repository for cross-references to other authoritative sources, examples of usage, and history of changes in definitions. | ||
More ambitiously, it will '''create new uses for the content of doctrine''' for example by | More ambitiously, it will '''create new uses for the content of doctrine''' for example by |
Revision as of 13:32, 17 August 2015
Venue: MACE (Multi-Agency Collaboration Environment), 3076 Centreville Road, Herndon, VA 20171
Date: September 16-17, 2015
Nearest hotel: Hilton Washington Dulles Airport
Registration: $50 flat fee to cover costs
Background
The goal of the Joint Doctrine Ontology Project is to create a formal representation of the content of the major doctrinal publications. It is designed first of all to enhance the content of doctrine by providing a computerized representation of doctrinal definitions.
This will potentially assist doctrine authors for example by
- - enabling the creation of flexible visualizations of how different parts of doctrine interact
- - 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
It will help doctrine users for example by
- - enabling more effective discovery of doctrinal knowledge in forms useful for computational reasoning
- - providing for each term in the DoD Dictionary of Military and Associated Terms (JP 1-02) a separate web address serving as a repository for cross-references to other authoritative sources, examples of usage, and history of changes in definitions.
More ambitiously, it will create new uses for the content of doctrine for example by
- - facilitating greater coordination of training and operations particular as these involve IT systems working alongside human beings
- - increasing automation of processes such as plan specification and scenario development
- - serving as basis for new sorts of quality assurance by providing the basic for allowing operations to be assessed by software in light of their conformity to and departures from doctrine
- - providing a benchmark for agile ontology development across DoD and IC of a sort that will counteract current tendencies towards silo-formation and failure of interoperation.
The project is directed by Barry Smith of the National Center for Ontological Research. A first sample is 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.
Provisional Agenda
September 16
8:30 Coffee available
9:00 Start
- Barry Smith (NCOR): Introduction to the meeting: Addressing DoD information and coordination needs
- Col William Mandrick (Institute for Military Support to Governance / Joint Special Operations University): War Fighter Ontology
- Lee Krause (Securboration): MAMA applied to Air Mobility Command
- William Tagliaferri (CUBRC): MAMA applied to the Space Mission
- Ron Rudnicki (CUBRC): Common Core Ontologies (IARPA, I2WD, JIDO, ONR, AFRL, ARL)
- Representative from D-TIC (TBD)
12:00 - 13:00 Lunch
- Barry Smith (NCOR): Joint Doctrine Ontology: Strategy, Benefits, Applications
- Initial draft modules:
- 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
- Discussion
- 18:00 Dinner
September 17
8:30 Coffee available
9:00 Start
- Space Mission Data and Space Ontology (CUBRC, AFRL Rome)
- Transcom Mission Data and Transport Ontology (Securboration)
12:00 Lunch
13:00 - 15:30 [Closed Session]