It is not totally clear how an implementer uses (invokes, implements) a PIM method within the DDS/IDL PSM.

The latest reference for GraphQL is
GraphQL Foundation (https://graphql.org/foundation/),
online at https://spec.graphql.org/October2021/

In v1.1 of TEX in the DDS-IDL PSM all the packages are mapped into the org::omg::tex namespace. TEX was adopted by the DTC at the 2023 Q3 meeting and should be expected to be published/issued ahead of TDAI v1.0.
TDAI current targets v1.0 which does not have this enclosing namespace.
It would make sense to target v1.1 and also to use an equivalent enclosing namespace for consistency.
This issue relates to an AB review comment.

Figure 10.33 PlanExecutionInformation Service Mapping (Component diagram) is in the PlanExecutionRecommendation (10.5) section, but relates to PlanExecutionInformation (10.4) section

Some diagrams no or little meaningful content have been generated into the specification. This add no value and the specification would be clearer without them.
Consider:

• Figure 10.40 TacticalPictureInformation (just a note)
• Figure 10.43 TacticalPictureRecommendations (empty package diagram)

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

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

Use tdai rather than tda to be consistent with nomenclature.

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.

E.g. for a timeout

@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.

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

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