Issue 7906: GNS FTF issue --conformance clause
Issue 7960: functionality duplicated
Issue 7961: MoveTimeAccuracy attribute from the GNS_QoS interface to GNS.
Issue 7962: Add flexibility to Optional GNS_QoS interface
Issue 7963: It is unclear as to what the GNS_QoS NavSource attribute should be used for
Issue 7906: GNS FTF issue --conformance clause (gns-ftf)
Click here for this issue's archive.
Source: Hewlett-Packard (Dr. Jishnu Mukerji, jishnu(at)hp.com)
Nature: Uncategorized Issue
Severity:
Summary:
In the conformance clause, for each conformance point provide cross reference to normative clauses that must be implemented in order to satisfy the conformance point
The functionality provided by the FOM and TFOM attributes are duplicated by the DeltaLat, DeltaLong, and DeltaAltitude. FOM and TFOM are of GPS origin and may not be well suited to future GNS systems. Recommend Delete all FOM and TFOM references.
Currently TimeAccuracy is included as an optional QoS interface attribute. It is important that this accuracy data be syncronized with its respective data. Recommend that the TimeAccuracy attribute be moved from the GNS_QoS interface to GNS.
The Optional GNS_QoS interface has a SourceType ennumerated list to describe the permitted values for the NavSource attribute. To add flexibility to this interface, it is recommended that the source type "OTHER" be added as the first entry in the list.
It is unclear as to what the GNS_QoS NavSource attribute should be used for. Additional description for each of the elements would also provide value to the specification. It is recommended these two areas be expanded to clarify their purpose and usage.