Task symbol representations in C2SIM

[bruno-g]

C2SIM Problem Report / Change Request Submitter Name: Ole-martin Mevassvik and Geir Sletten Submitter Organization: FFI Date of Submission: 29 March 2022 Type (Problem Report or Change Request): Problem Report Product: C2SIM 1.0.0/1.0.1 + SMX + LOX ontologies (rdf/xml)

Reference: FFI memo "Evaluation of C2SIM for use in Army Course of Action simulation", 22 February 2022, Section 6.3, p14

Problem/Change Description: There are issues regarding task symbol representations. MapGraphic is an Entity, where the actual symbol code can be filled in through EntityType. The subclass TaskGraphic under TacticalGraphic is defined as “Specifies a NATO APP6-C-based tactical graphics symbol for a Task”. The graphics symbols for tasks are designed for interpretation by humans (visual aid) and have not been included in previous C2SIM standards. The standard furthermore does not define or provide the necessary constructs to represent the task symbols. An example is the seize symbol, which includes a circle and a bowed arrow.

[dr-cgf-home]

The APP6 standard defines how to draw the symbols, including task graphics such as seize, with anchor points. Since graphics are physical entities, they have one or more locations, which are the anchor points of the graphic. (In another issue, the problem of specifying the order of the given locations is addressed.) These anchor points do not always define everything necessary for the task, e.g. there is no anchor point for seize to define the radius of the circle. C2SIM at this point will use the standard drawing instructions for representation of the graphic, and leave it to the (simulation) systems to interpret the anchor points appropriately. Note that this requirement for interpretation is much easier than the interpretation of the semantics of "seize" itself.