MSDL Brief to CBML

1
MSDL Brief to CBML
2
MSDL use case within OneSAF

• MSDL provides the Military Scenario portion of a
  scenario in XML data interchange format (DIF).
• A C2 planner (MSDE) produces MSDL and archives
  the scenario in the MSR.
• The MCT imports MSDL and instantiates the
  Military portion of the scenario in an OOS
  specific format (SSDL).

3
MSDL use case within OneSAF

• The Military Scenario (not MSDL) is then updated
  by
• Data received through the C4I adapter
• Role player activity
• SAF actions and the corresponding effects to the
  battlefield
• The OneSAF AAR then imports the MSDL scenario to
  compare against the actual results in AAR
  products.

4
Use cases applied to OOS that involve Military
Scenario data

• C2 planner provides Military Data that is loaded
  into OneSAF via the MSDL format.
• The OneSAF intent has been that C2 applications
  adopt the MSDL format.
• C2 formats will need to be and translated to MSDL
  for application in OOS.
• The OneSAF C4I Adapter sends/receives messages
  to/from operational devices.

5
MSDL Successes The Enabling Concepts

• MSDL describes the Mission domain of a military
  scenario.
• MSDL does not describe the means for achieving a
  missions objectives.
• The means is considered application/situation/in
  stance specific.
• MSDL is required to be independent of the means
  (specific OOS composition) that will satisfy the
  Military Scenario.

6
MSDL Successes The Enabling Concepts

• MSDL has borrowed from philosophy and science to
  support overlapping but differing ontologies.
• Abstraction is used only when necessary.
• Coordinate/projection system
• Enumeration Standard
• BML Language (tasks/missions/actions)
• The problem with abstraction is keeping the
  information explicit across ontologies.

7
MSDL Challenges

• OneSAF is challenged with identifying a DIF based
  mechanism for controlling the ontological
  overlaps within MSDL.
• Provide a context-sensitive implementation of the
  language
• Enumerations (MIDB, LIN, DIS, BSO)
• Coordinates (GCC, GDC, MGRS, UTM)
• Tasks/Missions, AUTL, UJTL, OTB
• Why TBD, currently uses the MSDB set
• Implementations are considering Visitor Design
  Pattern approach to the problem

8
MSDL Challenges

• For enumerated types that overlap with 2525B, the
  types start with 2525B and extend from there to
  provide the needed precision.
• Unit Roles (operational role)
• Unit Types (specific functional role)
• Entity Types (specific platform/weapon/munition
  type)

9
Ontological Overlaps
Army
USAF
Navy
USMC
OOS
DIS
OTB
WarSIM