Closed lofstrandbjorn closed 4 years ago
This also means using the GeodeticPoint defined in NETN-BASE instead of the GDC type defined in NETN-ORG.
I suggest to create a single attribute for Symbol Text Amplifications. These are the text that appears beside the graphical symbol. Different amplifiers are used for Units and Equipment items so I suggest 2 fixed record datatypes.
I suggest to create a single attribute for Disposition (an MSDL term) for FormationPosition, Location, Direction and Speed. These are attributes that may be updated more frequently than the Text amplifiers. So I suggest a fixed record that can be used both for the Disposition of Unit and EquipmentItem.
I propose that some of the JC3IEDM attributes such as UnitSize, ArmCategory, etc. currently defined in Unit should be removed. These are not represented in MSDL and can if required be derived from Symbol information.
I propose to move the Name attribute from ORG_Root and define it on each subclass with explicit semantics for the different uses.
I propose to use the NETN-BASE datatype UUID instead of UuidArrayOfHLAbyte16 (just a name change).
I suggest we set up a telecon to discuss these changes.
I suggest to only support GDC for Units and Equipment items in the federation. If the MSDL uses other formats these should be converted to GDC in the federation.