Academic
Publications
Taxonomies, Ontologies, and Battle Management Languages - Recommendations for the Coalition BML Study Group

Taxonomies, Ontologies, and Battle Management Languages - Recommendations for the Coalition BML Study Group,Andreas Tolk,Curtis L. Blais

Taxonomies, Ontologies, and Battle Management Languages - Recommendations for the Coalition BML Study Group   (Citations: 18)
BibTex | RIS | RefWorks Download
Battle Management Language (BML) is defined as an unambiguous language to command and control forces and equipment conducting military operations and to provide for situational awareness and a shared, common operational picture. BML is being designed as a standard representation of a "digitized commander's intent" to be used for real troops, for simulated troops, and for future robotic forces. Three views have been identified as necessary to describe BML: (1) A Doctrine View - BML must be connected to doctrine; (2) A Representation View - BML must model relevant aspects; (3) A Protocol View - BML must specify the underlying protocols for transferring BML. Ongoing research is coping with several questions; for example, if these views are sufficient, how they are interconnected, what implementations and alternatives exist, and many more. Is BML a taxonomy, an ontology, or something else? How is BML related to these terms? Should it replace military ontologies or benefit from them? Can we migrate results from related efforts of the open standards community, such as mapping of ontologies to Platform Independent Models (PIM) or to the Resource Description Framework (RDF)? How will this influence the ongoing evolution of the DoD Architecture Framework (DoDAF) and the Universal Joint Task Lists of the Joint Forces and the Services? This paper references related efforts and tries to create a map showing how they are interrelated, where they are mutually exclusive and where they are supportive. However, the list of related efforts is neither complete nor exclusive. Based on Lessons Learned within national and international applications and collaborations involving BML, tentative recommendations for community discussion will be given. The paper does not present ready to implement solutions. It is written as a discussion paper to be used in the Simulation Interoperability Standards Organization (SISO) study group on Coalition BML and in the NATO M&S Group Exploratory Team ET-16 dealing with the same topic.
Cumulative Annual
Sort by: