Joint Doctrine Ontology: Difference between revisions
From NCOR Wiki
Jump to navigationJump to search
m (→Publication) |
|||
| (23 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
<u> Joint Doctrine Ontology Project</u> | <u> Joint Doctrine Ontology Project</u> | ||
== Background of this project == | |||
This project is carried out under two Rome Air Force Research Laboratory (AFRL) initiatives [http://defensesystems.com/articles/2014/09/15/air-force-mama-network-mapping-analysis.aspx MAMA]" and "Living Plan".The project is directed by [http://ontology.buffalo.edu/smith Barry Smith]. | |||
== Publication == | |||
Peter Morosoff, Ron Rudnicki, Jason Bryant, Robert Farrell, Barry Smith, “[http://ncor.buffalo.edu/2015/STIDS-JDO.pdf Joint Doctrine Ontology: A Benchmark for Military Information Systems Interoperability]”, Semantic Technology for Intelligence, Defense and Security (STIDS), CEUR, 2015 | |||
== Goal == | == Goal == | ||
The goal of this project is to create a formal representation of the content of (selected parts of) Doctrine. | |||
== Examples of potential uses == | |||
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 | |||
4. to facilitate communication | |||
:- for example between intelligence analysts and the warfighters who are users of intelligence data | |||
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. | |||
== Work plan == | |||
The project will begin with a small number of modules focusing on: | The project will begin with a small number of modules focusing on: | ||
| Line 21: | Line 42: | ||
:3. Civil Operations (JP 3-57) | :3. Civil Operations (JP 3-57) | ||
:4. Space Operations (JP 3-14) | :4. Space Operations (JP 3-14) | ||
:5. Air Mobility Operations (JP 3-17) | |||
:TBD: Operational Environment | :TBD: Operational Environment | ||
:TBD: Transport (4-01) | :TBD: Transport (4-01) | ||
:TBD: Sustainment | |||
Initially we are focusing on | Initially we are focusing on | ||
:A. review of existing definitions to identify | :A. review of existing definitions to identify taxonomic relations. | ||
:B. exploring the role of Joint Doctrine and more specific doctrinal publications (for example the relation between the Joint Dictionary (JP 1-02) and the [http://armypubs.army.mil/doctrine/DR_pubs/dr_a/pdf/adrp1_02.pdf Army Doctrine Reference Publication 1-02], or between Joint Planning and Airforce Planning ([http://static.e-publishing.af.mil/production/1/af_cv/publication/afdd3-0/afdd3-0.pdf]) | :B. exploring the role of Joint Doctrine and more specific doctrinal publications (for example the relation between the Joint Dictionary (JP 1-02) and the [http://armypubs.army.mil/doctrine/DR_pubs/dr_a/pdf/adrp1_02.pdf Army Doctrine Reference Publication 1-02], or between Joint Planning and Airforce Planning ([http://static.e-publishing.af.mil/production/1/af_cv/publication/afdd3-0/afdd3-0.pdf]) | ||
| Line 35: | Line 59: | ||
:The role of ontology fragments to be reused in different areas of doctrine, for example pertaining to [https://rdl.train.army.mil/catalog-ws/view/100.ATSC/6A489D10-160C-4301-90D5-377E5FE38156-1311167781441/3-24.2/chap1.htm PMESII-PT] | :The role of ontology fragments to be reused in different areas of doctrine, for example pertaining to [https://rdl.train.army.mil/catalog-ws/view/100.ATSC/6A489D10-160C-4301-90D5-377E5FE38156-1311167781441/3-24.2/chap1.htm PMESII-PT] | ||
== Information on Joint Doctrine == | |||
[http://www.dtic.mil/doctrine/ Joint Electonic Library] | |||
[[Joint Doctrine Hierarchy]] | [[Joint Doctrine Hierarchy]] | ||
| Line 45: | Line 69: | ||
[http://fas.org/man/doctrine.htm DoctrineLink] | [http://fas.org/man/doctrine.htm DoctrineLink] | ||
[http://www.dtic.mil/ | [http://www.dtic.mil/doctrine/new_pubs/cjcsi5705_01d.pdf CJCSI 5705.01D (10 November 2010)] Standardization of Military and Associated Terminology, especially Enclosure C | ||
[http://www.dtic.mil/doctrine/training/ujtl_tasks.htm Universal Joint Task List (UJTL)] | [http://www.dtic.mil/doctrine/training/ujtl_tasks.htm Universal Joint Task List (UJTL)] | ||
| Line 53: | Line 77: | ||
[http://www.jcs.mil/portals/36/Documents/102710173839_Joint_Concept_for_Logistics_v1_FINAL_with_CJCS_Sig.pdf Joint Concept for Logistics] | [http://www.jcs.mil/portals/36/Documents/102710173839_Joint_Concept_for_Logistics_v1_FINAL_with_CJCS_Sig.pdf Joint Concept for Logistics] | ||
[http://www.carlisle.army.mil/library/bibs/joint07.pdf Jointness: A Selected Bibliography] | |||
== Related efforts == | |||
[https://pdfs.semanticscholar.org/a1e6/e43cb0dd427a4689a7875ee63470597c3737.pdf Data Science for Joint Doctrine] | |||
[http://www.isi.edu/isd/JFACC/loom-jfacc-final-report.pdf JFACC Ontology] | [http://www.isi.edu/isd/JFACC/loom-jfacc-final-report.pdf JFACC Ontology] | ||
| Line 70: | Line 97: | ||
[http://www.disa.mil/About/Our-Work/JIE Joint Information Environment (JIE)] | [http://www.disa.mil/About/Our-Work/JIE Joint Information Environment (JIE)] | ||
DoD Architecture Framework (DoDAF) | [http://dodcio.defense.gov/Library/DoDArchitectureFramework/dodaf20_ontology1.aspx DoD Architecture Framework] (DoDAF) | ||
Data Services Environnent (DSE) | [http://www.dtic.mil/whs/directives/corres/pdf/832002p.pdf Data Services Environnent (DSE)]: DoDI 8320.02, “Sharing Data, Information, and Information Technology (IT) Services in the Department of Defense.” | ||
== Global Force Management (GFM) == | == Global Force Management (GFM) == | ||
| Line 87: | Line 114: | ||
== Planning == | == Planning == | ||
[http://www.imse.iastate.edu/dorneich/files/2013/02/2010_KSCO_ITA_Planning.pdf Making Plans Alive] | |||
[http://works.bepress.com/cgi/viewcontent.cgi?article=1016&context=michael_dorneich Improving Coalition Planning by Making Plans Alive] | |||
[https://www.usnwc.edu/getattachment/7f55b167-54e8-4104-814b-c888d5d53113/NWC-2061D-GEF-JSCP-APEX-Dec-2013-CHG-1.aspx APEX and GFM] | [https://www.usnwc.edu/getattachment/7f55b167-54e8-4104-814b-c888d5d53113/NWC-2061D-GEF-JSCP-APEX-Dec-2013-CHG-1.aspx APEX and GFM] | ||
| Line 103: | Line 134: | ||
[http://www.isi.edu/~blythe/papers/pdf/planet-ws00.pdf PLANET: A Shareable and Reusable Ontology for Representing Plans] | [http://www.isi.edu/~blythe/papers/pdf/planet-ws00.pdf PLANET: A Shareable and Reusable Ontology for Representing Plans] | ||
[[Shadow Planning]] | |||
[http://www.slideshare.net/ahmad1957/an-ontological-formalization-of-the-planning-task-presentation An Ontological Formalization of the Planning Task] | |||
Latest revision as of 23:21, 1 July 2018
Joint Doctrine Ontology Project
Background of this project
This project is carried out under two Rome Air Force Research Laboratory (AFRL) initiatives MAMA" and "Living Plan".The project is directed by Barry Smith.
Publication
Peter Morosoff, Ron Rudnicki, Jason Bryant, Robert Farrell, Barry Smith, “Joint Doctrine Ontology: A Benchmark for Military Information Systems Interoperability”, Semantic Technology for Intelligence, Defense and Security (STIDS), CEUR, 2015
Goal
The goal of this project is to create a formal representation of the content of (selected parts of) Doctrine.
Examples of potential uses
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
4. to facilitate communication
- - for example between intelligence analysts and the warfighters who are users of intelligence data
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.
Work plan
The project will begin with a small number of modules focusing on:
- 1. Capstone (Task, Function and Mission) (JP 1)
- 2. Planning (JP 5-0)
- 3. Civil Operations (JP 3-57)
- 4. Space Operations (JP 3-14)
- 5. Air Mobility Operations (JP 3-17)
- TBD: Operational Environment
- TBD: Transport (4-01)
- TBD: Sustainment
Initially we are focusing on
- A. review of existing definitions to identify taxonomic relations.
- B. exploring the role of Joint Doctrine and more specific doctrinal publications (for example the relation between the Joint Dictionary (JP 1-02) and the Army Doctrine Reference Publication 1-02, or between Joint Planning and Airforce Planning ([1])
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
Information on Joint Doctrine
DoD Dictionary of Military Terms
CJCSI 5705.01D (10 November 2010) Standardization of Military and Associated Terminology, especially Enclosure C
Universal Joint Task List (UJTL)
Joint Doctrine Development Process
Jointness: A Selected Bibliography
Related efforts
Data Science for Joint Doctrine
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.”
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
Improving Coalition Planning by Making Plans Alive
The Downfall of Adaptive Planning
Thomas Cleary, Military Decision Making Process: Part 1, Part 2, Part 3
Introduction to Plans and Orders
A Computational Framework for Living Plan Specification, Execution and Evaluation
PLANET: A Shareable and Reusable Ontology for Representing Plans
