Issue 14461: Put Alarms in Arguments; leaves Alarms in Command Parameters (xtce-rtf)
Source: NASA (Mr. Kevin Rice, james.k.rice-1(at)nasa.gov)
Nature: Enhancement
Severity: 
Summary: Description Kevin Rice 2007-10-22 21:17:55 BST 
Command Argument should have alarms; I have found one user that claims alarms
on USER INPUT arguments.  Therefore I believe we should generalize the schema
to having them both in parameters and arguments. In the end I believe we'll be
making arguments and parameters look exactly the same even if the nomenclature
stays separate.
Comment 1 Kevin Rice 2007-10-22 21:20:06 BST 
Command Argument should have alarms; I have found one user that claims alarms
on USER INPUT arguments.  Therefore I believe we should generalize the schema
to having them both in parameters and arguments. In the end I believe we'll be
making arguments and parameters look exactly the same even if the nomenclature
stays separate.

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

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

Put Alarms in Arguments; leaves Alarms in Command Parameters

Description Kevin Rice 2007-10-22 21:17:55 BST 
Command Argument should have alarms; I have found one user that claims alarms
on USER INPUT arguments.  Therefore I believe we should generalize the schema
to having them both in parameters and arguments. In the end I believe we'll be
making arguments and parameters look exactly the same even if the nomenclature
stays separate.
Comment 1 Kevin Rice 2007-10-22 21:20:06 BST 
Command Argument should have alarms; I have found one user that claims alarms
on USER INPUT arguments.  Therefore I believe we should generalize the schema
to having them both in parameters and arguments. In the end I believe we'll be
making arguments and parameters look exactly the same even if the nomenclature
stays separate.