At least one FOM attribute appears in the FOM that is not present in the SISO MSDL schema (SISO-STD-007-2008). In UnitModelType there is no element EntityType. This appears to be manually edited/added in the schema used for V18, and added as attribute to the FOM Unit class.
Are there more edits/additions to the official schema and that ended up in the ORBAT FOM?
If the design decision is to use the MSDL schema, we should stick to the SISO schema as is.
The ORBAT federate should get the additional information such as the entity type for a unit from another source then the MSDL fille. And should not save it back to an MSDL file either.
A traceability table should be created between MSDL schema and FOM attributes, with the reason why an attribute has been added, or a schema element not modelled.
At least one FOM attribute appears in the FOM that is not present in the SISO MSDL schema (SISO-STD-007-2008). In
UnitModelType
there is no elementEntityType
. This appears to be manually edited/added in the schema used for V18, and added as attribute to the FOM Unit class.Are there more edits/additions to the official schema and that ended up in the ORBAT FOM?
If the design decision is to use the MSDL schema, we should stick to the SISO schema as is. The
ORBAT federate
should get the additional information such as the entity type for a unit from another source then the MSDL fille. And should not save it back to an MSDL file either.A traceability table should be created between MSDL schema and FOM attributes, with the reason why an attribute has been added, or a schema element not modelled.