Issue 8056: There needs to be an ability to define an expected rate on containers (xtce-ftf) Source: Integral Systems (Mr. Charles Gerry Simon, gsimon@integ.com) Nature: Revision Severity: Significant Summary: This rate will be used to generate an alarm if certain telemetry containers do not arrive at the anticipated rate. This rate could also be used by simulators (for generating telemetry) or as guides for generating forward link containers Resolution: Revised Text: Resolution: A 'RateInContainer' sequence was added to 'ContainerType'. This change will not require changes to existing XML documents. Revised Text: <sequence> <annotation> <documentation>RateInStream is used to: a) generate alarms when the Container is updated too frequently or too infrequently, b) provide some 'guidelines' for generating forward link containers, c) provide some guidelines for spacecraft simulators to generate telemetry containers. If necessary, these rates may be defined on a per stream basis.</documentation> <appinfo source="The software should check that any Stream names referenced in the RateInStreamSet actually exist."/> </annotation> <element name="DefaultRateInStream" type="xtce:RateInStreamType" minOccurs="0"/> <element name="RateInStreamSet" minOccurs="0"> <complexType> <sequence> <element name="RateInStream" maxOccurs="unbounded"> <complexType> <complexContent> <extension base="xtce:RateInStreamType"> <attribute name="streamRef" type="xtce:NameReferenceType" use="required"/> </extension> </complexContent> </complexType> </element> </sequence> </complexType> </element> </sequence> Actions taken: December 31, 2004: received issue August 2, 2005: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 31 Dec 2004 19:27:37 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Gerry Simon Company: Lockheed Martin mailFrom: gerry.simon@schriever.af.mil Notification: No Specification: XTCE Section: schema FormalNumber: dtc/03-05-07 Version: 1 RevisionDate: 03/29/2003 Page: all Nature: Revision Severity: Significant HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) Description There needs to be an ability to define an expected rate on containers Summary: This rate will be used to generate an alarm if certain telemetry containers do not arrive at the anticipated rate. This rate could also be used by simulators (for generating telemetry) or as guides for generating forward link containers