Issue 14479: Key bugs (xtce-rtf)
Source: NASA (Mr. Kevin Rice, james.k.rice-1(at)nasa.gov)
Nature: Uncategorized Issue
Severity: 
Summary: Description Kevin Rice 2007-10-22 21:58:41 BST 
Keys for the ContainerSet check should read CommandContainerSet on the
commandMetaData portion and there is no key at all for ArgumentTypeSet. These
can be added with little effort although it seems many parsers ignore the keys.
Comment 1 Kevin Rice 2008-03-03 21:15:40 GMT 
Most of the keys in fact are incorrect in the Xpath designations.  For example
the parameterNameKey should read:

"xtce:TelemetryMetaData/xtce:ParameterSet/*|xtce:CommandMetaData/xtce:ParameterSet/*"

Most if not all the other keys have the same issue related to incorrectly
specifying the "xtce:" namespace and thus do nothing.

Further, they are all at the top of the schema and instead could be positioned
at each element of interest, this would help with the error message generated.

Finally, instead of using key, the "unique" tag could be used instead as this
is exactly what the keys are checking for, uniqueness.

Resolution: 
Revised Text: 
Actions taken:
September 17, 2009: received issue
Discussion: 

End of Annotations:=====
s is issue # 14479

Key bugs

Description Kevin Rice 2007-10-22 21:58:41 BST 
Keys for the ContainerSet check should read CommandContainerSet on the
commandMetaData portion and there is no key at all for ArgumentTypeSet. These
can be added with little effort although it seems many parsers ignore the keys.
Comment 1 Kevin Rice 2008-03-03 21:15:40 GMT 
Most of the keys in fact are incorrect in the Xpath designations.  For example
the parameterNameKey should read:

"xtce:TelemetryMetaData/xtce:ParameterSet/*|xtce:CommandMetaData/xtce:ParameterSet/*"

Most if not all the other keys have the same issue related to incorrectly
specifying the "xtce:" namespace and thus do nothing.

Further, they are all at the top of the schema and instead could be positioned
at each element of interest, this would help with the error message generated.

Finally, instead of using key, the "unique" tag could be used instead as this
is exactly what the keys are checking for, uniqueness.