${taskforce.name} Avatar
  1. OMG Task Force

Tactical Decision Aids Interface (TDAI) 1.0 FTF2 — Closed Issues

  • Key: TDAI
  • Issues Count: 18
Open Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Key Issue Reported Fixed Disposition Status
TDAI-12 Support recommendation of threat priority TDAI 1.0b1 TDAI 1.0 Resolved closed
TDAI-22 PlanExecutionInformation Service Mapping Component diagram in wrong section TDAI 1.0b1 TDAI 1.0 Resolved closed
TDAI-35 GraphQL Normative Reference is out of date TDAI 1.0a1 TDAI 1.0 Resolved closed
TDAI-33 TEX v1.1 uses org.omg.tex namespace in DDS-IDL PSM TDAI 1.0a1 TDAI 1.0 Resolved closed
TDAI-37 DDS PSM Topic types for PIM Method unclear TDAI 1.0a1 TDAI 1.0 Resolved closed
TDAI-29 Superfluous Diagrams in the Specification Document TDAI 1.0b1 TDAI 1.0 Resolved closed
TDAI-10 Change prefix of predefined errors to tdai TDAI 1.0b1 TDAI 1.0 Resolved closed
TDAI-13 Clarify relationship of EntityRef to TEX standard TDAI 1.0b1 TDAI 1.0 Resolved closed
TDAI-11 system_track_type does not contain identity or classification OARIS 2.0b2 TDAI 1.0 Closed; Out Of Scope closed
TDAI-7 Key Annotation Casing in DDS IDL TDAI 1.0b1 TDAI 1.0 Resolved closed
TDAI-2 GraphQL PSM refers to 'struct' TDAI 1.0b1 TDAI 1.0 Resolved closed
TDAI-8 Need to be able undo or unset recommendations TDAI 1.0b1 TDAI 1.0 Resolved closed
TDAI-5 Need to be able to refer to another entity when recommending status TDAI 1.0b1 TDAI 1.0 Resolved closed
TDAI-9 Add standard internal error reason value TDAI 1.0b1 TDAI 1.0 Resolved closed
TDAI-1 DDS referred to in GraphQL PSM TDAI 1.0a1 TDAI 1.0 Resolved closed
TDAI-6 Nested Key Annotation in DDS IDL TDAI 1.0a1 TDAI 1.0 Resolved closed
TDAI-4 Method to recommend a reference entity with a status TDAI 1.0b1 TDAI 1.0 Duplicate or Merged closed
TDAI-3 Method to change multiple identity attributes at once required TDAI 1.0b1 TDAI 1.0 Resolved closed

Issues Descriptions

Support recommendation of threat priority


PlanExecutionInformation Service Mapping Component diagram in wrong section

  • Key: TDAI-22
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

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

  • Reported: TDAI 1.0b1 — Mon, 23 Oct 2023 13:52 GMT
  • Disposition: Resolved — TDAI 1.0
  • Disposition Summary:

    Move PlanExecutionInformation Service Mapping diagram

    Move the PlanExecutionInformation Service Mapping (Component diagram) - Figure 10.33 - from section 10.5 to section 10.4

  • Updated: Mon, 25 Mar 2024 14:23 GMT


TEX v1.1 uses org.omg.tex namespace in DDS-IDL PSM

  • Key: TDAI-33
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    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.

  • Reported: TDAI 1.0a1 — Wed, 22 Nov 2023 15:45 GMT
  • Disposition: Resolved — TDAI 1.0
  • Disposition Summary:

    Target TEX v1.1 and use an enclosing namespace

    TDAI v1.0 should target TEX v1.1 (i.e. be the normative reference).

    Each of the IDL files for the DDS PSM should have an enclosing namespace of org::omg::tdai

    The DDS IDL files should reference identifiers using the relevant enclosing namespace - org::omg::tex (for top-level packages defined by TEX) or org::omg::tdai (for top-level packages defined by TDAI).

  • Updated: Mon, 25 Mar 2024 14:23 GMT

DDS PSM Topic types for PIM Method unclear

  • Key: TDAI-37
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

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

  • Reported: TDAI 1.0a1 — Mon, 27 Nov 2023 16:53 GMT
  • Disposition: Resolved — TDAI 1.0
  • Disposition Summary:

    Add Comments to Topic Type Definition to emphasise their role

    Add comments to each generated topic type from a method signature (as per section 12.1) to state that it is intended as a DDS Topic type, maps to the original PIM method and is used through publication to invoke or subscription to implement.

    For each topic type insert (prepend) at the head of the comment block
    "This is the DDS Topic type for invoking and implementing the {@Operation} method on the {@Interface} interface.
    To invoke the operation publish a DDS Sample of this type; to implement it subscribe for samples."

  • Updated: Mon, 25 Mar 2024 14:23 GMT

Superfluous Diagrams in the Specification Document

  • Key: TDAI-29
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    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)
  • Reported: TDAI 1.0b1 — Tue, 31 Oct 2023 17:45 GMT
  • Disposition: Resolved — TDAI 1.0
  • Disposition Summary:

    Remove Superfluous Diagrams

    Remove diagrams and captions for 10.40 & 10.43 (original numbering) and renumber remaining figures

  • Updated: Mon, 25 Mar 2024 14:23 GMT

Change prefix of predefined errors to tdai

  • Key: TDAI-10
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    Use tdai rather than tda to be consistent with nomenclature.

  • Reported: TDAI 1.0b1 — Sat, 23 Sep 2023 12:33 GMT
  • Disposition: Resolved — TDAI 1.0
  • Disposition Summary:

    Change response prefex to tdai

    Change prefix for standard response to tdai

  • Updated: Mon, 25 Mar 2024 14:23 GMT

Clarify relationship of EntityRef to TEX standard

  • Key: TDAI-13
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

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

  • Reported: TDAI 1.0b1 — Sat, 23 Sep 2023 16:04 GMT
  • Disposition: Resolved — TDAI 1.0
  • Disposition Summary:

    Clarify relationship to TEX in the overview section

    Extend the opening paragraph to discuss the linkage to the TEX specification and explicitly mention EntityRef.

  • Updated: Mon, 25 Mar 2024 14:23 GMT

system_track_type does not contain identity or classification

  • Key: TDAI-11
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

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

  • Reported: OARIS 2.0b2 — Sat, 23 Sep 2023 12:45 GMT
  • Disposition: Closed; Out Of Scope — TDAI 1.0
  • Disposition Summary:

    Raise issue in OARIS 2.1 RTF

    This is an OARIS Issue, raised in the wrong task force issues list.
    This has been raised as an issue in OARIS 2.1 - see https://issues.omg.org/browse/OARIS21-60

  • Updated: Mon, 25 Mar 2024 14:23 GMT

Key Annotation Casing in DDS IDL


GraphQL PSM refers to 'struct'

  • Key: TDAI-2
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    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.

  • Reported: TDAI 1.0b1 — Fri, 17 Feb 2023 17:27 GMT
  • Disposition: Resolved — TDAI 1.0
  • Disposition Summary:

    Refer to GraphQL Object types

    State that by default PIM classes are mapped to GraphQL object and input object types.
    State that the base type for inheritance is an object type (and input equivalent).
    For Extensible Enumerations they are mapped to object and input object types not structs.

  • Updated: Mon, 25 Mar 2024 14:23 GMT

Need to be able undo or unset recommendations


Need to be able to refer to another entity when recommending status


Add standard internal error reason value

  • Key: TDAI-9
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    E.g. for a timeout

  • Reported: TDAI 1.0b1 — Sat, 23 Sep 2023 12:32 GMT
  • Disposition: Resolved — TDAI 1.0
  • Disposition Summary:

    Add additional standard error conditions

    Add standard error conditions for a timeout and a general internal error. Also state that standard descriptors may be extended for implementation specifics.

  • Updated: Mon, 25 Mar 2024 14:23 GMT

DDS referred to in GraphQL PSM

  • Key: TDAI-1
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

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

  • Reported: TDAI 1.0a1 — Fri, 11 Feb 2022 15:08 GMT
  • Disposition: Resolved — TDAI 1.0
  • Disposition Summary:

    Refer to GraphQL schema rather than DDS PSM IDL

    In the GraphQL PSM sections the code generation should be described as transforming to GraphQL schema

  • Updated: Mon, 25 Mar 2024 14:23 GMT

Nested Key Annotation in DDS IDL


Method to recommend a reference entity with a status

  • Key: TDAI-4
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    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.

  • Reported: TDAI 1.0b1 — Fri, 17 Feb 2023 17:33 GMT
  • Disposition: Duplicate or Merged — TDAI 1.0
  • Disposition Summary:

    This is a duplicate of the next issue

    Looks like this issue was raised twice in error

  • Updated: Mon, 25 Mar 2024 14:23 GMT

Method to change multiple identity attributes at once required

  • Key: TDAI-3
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    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.

  • Reported: TDAI 1.0b1 — Fri, 17 Feb 2023 17:30 GMT
  • Disposition: Resolved — TDAI 1.0
  • Disposition Summary:

    Define a Recommend Categorization operation

    Add a new operation recommendCategorization to the extendedCategorization interface, which allows definition of a superset of the categorization recommendation as a single atomic recommendation. This consists optional classification, identity, activity and a list of status values.

  • Updated: Mon, 25 Mar 2024 14:23 GMT