| Key | Issue | Reported | Fixed | Disposition | Status | |
|---|---|---|---|---|---|---|
| C2INAV13-3 | Enumeration value ESTIMATED used twice in the same package | C2INAV 1.2b1 | open | |||
| C2INAV13-2 | Enumeration value ESTIMATED used twice in the same package | C2INAV 1.2b1 | open | |||
| C2INAV13-1 | C2INav Model refers to an old OARIS Common Types package | C2INAV 1.2 | open | |||
| C2INAV12-1 | Use @key instead of @Key | C2INAV 1.0 | C2INAV 1.2 | Resolved | closed | |
| C2INAV11-1 | FTF-1 changes to be applied to GraphQL PSM | C2INAV 1.0a1 | C2INAV 1.1 | Resolved | closed | |
| C2INAV11-3 | Update GraphQL PSM Mapping | C2INAV 1.0 | C2INAV 1.1 | Duplicate or Merged | closed |
Using the value ESTIMATED for both accuracy_derivation_type and navigation_derivation_kind_type causes problems in some programming languages; it is also better practice to be more descriptive.
Using the value ESTIMATED in accuracy_derivation_type and navigation_derivation_kind_type causes problems when mapped to some programming languages; it is also better practice to be more descriptive.
The C2INav Model refers to a package defined by OARIS 1.1.
OARIS 2.0 is about to be published and there are 2.1 RTF & 3.0 FTF in progress.
The IDL shipped with this specification uses @Key but that should be @key, IDL is case sensitive and DDSXTypes/IDL42 define @key, all lower case
Change IDL to use @key
IDL 4.2 & DDS X-Types defines the annotation as @key (lower case).
See section 8.3.2.1 of IDL specification v4.2
Update the relevant PSM files accordingly
Some but by now means all of the Issue Resolution from FTF-1 are applicable to the GraphQL PSM. These should be determined and applied as appropriate.
Generate new GraphQL PSM Schema from the PIM
The 1-1 FTF did not apply PIM changes to the GraphQL PSM. Furthermore the proposed schema mapping was in practice less than optimal for specialization-generalization relationships, leading to a complicated mapping in many GraphQL software language clients.
This proposal uses an improved mapping where there is a base type for common attributes and union for the specialized attributes.
The GraphQL mapping in the specification and defined in the schema files leads to an unnecessarily complicated implementation of the standard and should be simplified
Regenerate GraphQL PSM with updated mapping
The updated mappings from PIM to GraphQL as incorporated into the TDAI beta spec should be used.