search

AMSP-04 / NETN-ORG

NATO Education and Training Network (NETN) Organisation (ORG) Module
Other
1 stars 1 forks source link

Correlation: entityType and SymbolIdentifier #3

Closed bergtwvd closed 4 years ago

bergtwvd commented 5 years ago

Although there is not a 1-1 mapping between these two, these attribute values should match up. The semantics of both attributes should point this out.

LennartOlsson commented 5 years ago

The EntityType specifies the type, e.g. Leopard 2, while the SymbolIdentifier specifies the class, e.g Main Battle Tank and the affiliation of a specific entity.

Yes, semantics can be extended to explain the difference.

bergtwvd commented 5 years ago

Is entitytype part of MSDL, or is this field added by you to enable easier instantiations of entities by a CGF?

There still needs to be an application that derives the entity type from the SIDC. So I guess we now move this mapping from each CGF to the federate that manages the creation of the ORBAT object instances.

Would be good to document a default mapping somewhere. I attached a document on this topic.

SISO-REF-010_TO_MIL-STD-2525.pdf

LennartOlsson commented 5 years ago

The EntityType, Deployment and Holdings was added by MSG-106 as an extension to MSDL.

What stands SIDC for?

bergtwvd commented 5 years ago

SIDC = Symbol Identification Code (see also MIL-STD-2525).

For the additions mentioned above, these should be documented (in AMSP-04) in a ORBAT-FOM to MSDL schema traceability table. See https://github.com/MSG134/NETN_FOM/issues/13.

LennartOlsson commented 5 years ago

MSG-106 also added Extended description of humans and Embarkment status.

These extension are documented in the AMSP-04 in chapter 4.

bergtwvd commented 5 years ago

I see. I never read (and used) those parts.

A few questions pop up:

LennartOlsson commented 5 years ago

Yes, if SISO is willing to do updates of the standard, it would be great.

Not all application will listen to the ORBAT FOM data published in a federation execution, they will create their entities from a file (MSDL). Before exercises, it is also needed to distribute the ORBAT to participants, for that is a common used format needed.

LennartOlsson commented 5 years ago

Semantics updated in the next version.

EntityType: DIS Enumeration, defining the type of the entity, e.g. for the Main Battle Tank type Leopard 2 A5, the value shall be: 1.1.78.1.2.5.0

SymbolIdentifier: msdl:UnitType/SymbolIdentifier, MIL 2525 C symbol code. Required. The symbol code describes the class, e.g. for ARMOR TRACK, HEAVY as a Leopard 2 shall the symbol code be: S*GPUCATH-****, the in second (2:nd) position is to be replaced to specify the affiliation. The affiliation on a unit may change during an federation execution which imply that the 2:nd character will change. Other characters specifies functionallity, e.g. if a submarine is surfaced or bottomed which can be the case during a federation execution.

bergtwvd commented 5 years ago

In my view the MSDL additions should be followed-up with the respective SISO PSG for MSDL. Users will download the MSDL standard from the SISO site. This addition is entirely hidden inside a document, that people cannot get to anyway. before I close this issue, I would like to make sure that a follow will be done....