Information Meeting on Joint Doctrine Ontology
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
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]
