Joint Doctrine Ontology: Difference between revisions
mNo edit summary |
mNo edit summary |
||
Line 16: | Line 16: | ||
:2. Planning (JP 5-0) | :2. Planning (JP 5-0) | ||
:3. Civil Operations (JP 3-57) | :3. Civil Operations (JP 3-57) | ||
:4. Space Operations (JP 3-14) | |||
:TBD: Operational Environment | :TBD: Operational Environment | ||
:TBD: Transport (4-01) | |||
Initially we are focusing on | Initially we are focusing on |
Revision as of 23:11, 15 July 2015
Joint Doctrine Ontology Project
The goal of this project is to create a formal representation of the content of (selected parts of) Doctrine that is designed to help
- understand logically how different parts of doctrine interact
- visualize how different parts of doctrine interact
- understand dependences between definitions,
- ensure that changes in definitions cascade appropriately through all dependent definitions
- enabling more efficient web access to and discovery of doctrinal knowledge and definitions of a sort that will facilitate greater coordination of training and operations particular as these involve IT systems working alongside human beings.
The project is directed by Barry Smith, whose work is carried out under two Rome Air Force Research Laboratory (AFRL) projects "MAMA" and "Living Plan". The project has the support of Lt Col James McArthur, Chief, Joint Doctrine Division, J-7, Joint Staff.
The project will begin with a small number of modules focusing on:
- 1. Capstone (JP 1-0)
- 2. Planning (JP 5-0)
- 3. Civil Operations (JP 3-57)
- 4. Space Operations (JP 3-14)
- TBD: Operational Environment
- TBD: Transport (4-01)
Initially we are focusing on
- A. review of existing definitions to identify and fix logical errors.
- B. exploring the role of Joint Doctrine and more specific doctrinal publications (for example the relation between Joint Planning and Airforce Planning ([http://static.e-publishing.af.mil/production/1/af_cv/publication/afdd3-0/afdd3-0.pdf)
Issues to be addressed:
- Relation to existing efforts, especially:
- The role of ontology fragments to be reused in different areas of doctrine, for example pertaining to PMESII-PT
Background Information on Joint Doctrine
DoD Dictionary of Military Terms
Joint Doctrine, Joint Terminology Program, and DoD Instruction (DoDI) 5025. 12: Standardization of Military and Associated Terminology
Universal Joint Task List (UJTL)
Joint Doctrine Development Process
Related Efforts
Acquisition Community Connection
U.S. Army Unified Land Operations, with Army Doctrine Reference Publication (ADRP) 1-02: Operational Terms and Military Symbol
National Information Exchange Model (NIEM)
Joint Information Environment (JIE)
DoD Architecture Framework (DoDAF).
Data Services Environnent (DSE). DoDI 8320.02, “Sharing Data, Information, and Information Technology (IT) Services in the Department of Defense.”
c. Joint Taxonomy effort.
d. Adaptive Planning and Execution (APEX) System
Global Force Management (GFM)
Based on the authoritative guidance in the following issuances:
- DoD Manual (DoDM) 8260.03, Volume 1: The Global Force Management Data Initiative (GFM DI) Implementation: Unique Identification (UID) for GFM
- DoDM 8260.03 Volume 2: Global Force Management Data Initiative (GFM DI) Implementation: The Organizational and Force Structure Construct (OFSC)
Planning
Adaptive Planning and Execution (APRX)
Thomas Cleary, Military Decision Making Process: Part 1, Part 2, Part 3
Introduction to Plans and Orders
Erik Thomsen, William Duncan, Tatanya Malyuta and Barry Smith, “A Computational Framework for Living Plan Specification, Execution and Evaluation”, Proceedings of the Conference on Semantic Technology in Intelligence, Defense and Security (STIDS), George Mason University, Fairfax, VA, November 18-20, 2014.