search

AMSP-04 / NETN-ORG

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

Redundancy: Echelon covered by SymbolIdentifier #2

Closed bergtwvd closed 4 years ago

bergtwvd commented 5 years ago

Is this not covered by the code for the Symbol Identifier? In that case, it is redundant information.

LennartOlsson commented 5 years ago

This is how it is done in MSDL.

bergtwvd commented 5 years ago

The question is what is best? (rather than how MSDL does it)

LennartOlsson commented 5 years ago

The data type EchelonEnum32 at Unit.Echelon is a little more specified than the value at position 12 in the Symbol Identifier.

A Federate/Application that publish the ORBAT information in a Federation Execution must first load an ORBAT during the Federation Initialization and then save the ORBAT between Federation Executions, I do not know any better than using the SISO standard MSDL (SISO-STD-007-2008) for this. MSDL is used by many Federates/Applications in this community.

With this follows some constraints, definitions of attributes on object classes, definitions of data types, etc.

An ORBAT Federate/Application should also be able to edit an ORBAT and merging saved ORBATs.

bergtwvd commented 5 years ago

Question: is this added by you (for good reasons), or part of MSDL?

See also related question at https://github.com/MSG134/NETN_FOM/issues/6