Spec users have not understood that EntityRef values correspond to Entities received over the TEX interface

It is possible to recommend a status, but unclear how to quantify that status.

These attributes are important for enabling a sensor to processing specific to the actual category of object that it is tracking.

DDS X-Types requires attributes at each level of a nested key type to have the @key annotation.

Use tdai rather than tda to be consistent with nomenclature.

E.g. for a timeout

Tactical Decision Aids may have a revised opinion about previous decisions. This may mean lower confidence in a previous recommendation rather than an alternative recommendation (which would override). There needs to be a mechanism to unset, or recommend that the system reverts to the previous state.

@key should be lower case (not title case @Key)

When making a recommendation of status for an entity, for some concepts it is important to be able to do this by reference to some other entity. E.g. when saying that an entity is a threat to identify the entity that is threatened.

Some decision aids have a need to qualify a status recommendation with a reference entity - e.g. that an entity is a threat to another entity in particular.

TDAI provides methods to change standard identity, classification and activity individually. Some decision aids will want to recommend changes to more than one of these at once as a coherent set.

The GraphQL in describing the extensible enumeration mapping copies the DDS text and hence refers to the IDL: type system. It should refer to the GraphQL type system.

In the GraphQL Data Model PSM section the text refers to DDS rather than GraphQL