Target Lists

[clblais]

C2SIM Problem Report / Change Request Submitter Name (s): Curtis Blais for Geir Sletten and Ole Martin Mevassvik Contact email address: Geir.Sletten@ffi.no, Ole-Martin.Mevassvik@ffi.no Submitter Organization(s): FFI Date of Submission: 23 May 2022 Type (Problem Report or Change Request): Problem Report Product: Core Ontology Problem/Change Description: From: Evaluation of C2SIM for use in Army Course of Action simulation, 22 February 2022, p 6

There is no direct way of grouping candidate targets in C2SIM as target lists, except for creating an overlay (target is not a class concept in C2SIM).

[dr-cgf-home]

Actually, an overlay seems like a fine class to express a set of references to objects, if that's what a target list is. However, is it always the case that a target is a known entity, vs. an abstract construct created by the sensing agent(s) to refer to fused sensor data? I.e. perhaps due to jamming it doesn't really exist, or perhaps there are two entities causing the sensor reading. At any rate, it seems likely that specific structured C2 messages in the world (e.g. TDL, or internal SWAP messages maybe), or specific report formats, will not be matched by C2SIM classes. I think that maybe specific structured messages should be describe in extensions that can be added to C2SIM.

[MagdalenaDechand]

Overlay class (AbstractObject) vs. Entity (Concrete)

Entity is defined as any individually identified object. Each entity will be defined as PhysicalEntity then. If additionally an entity can perform a task, it will be seen as ActorEntity. A target would be a PhysicalEntity in case it is concrete. We could specify a role class such as "AffectedEntity" or "TargetEntity" as opposed to "ActorEntity". Any subclass of ActorEntity (e.g. CollectiveEntity for target grouping) is potentially subclass of AffectedEntity, because e.g. a CollectiveEntity is not per se defined by its acting role.

This taxonomy would align with the notion of task. An attack task is described with "hasAffectedEntity min 0 UUIDBase" restriction to define a target. "hasAffectedEntity" would work as object property restriction even better and could point to a new AffectedEntity class

[MagdalenaDechand]

Overlay is defined by having the restriction "hasEntityReference min 1 UUIDBase". "hasEntityReference" (The reference is to an instance of an Entity) contradicts the definition of AbstractObject and does not fit.

However, any other AbstractObject could be used as Target (e.g. CommunicationNetwork).