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

No Data Available

Within a MetaCommand, the uniqueness of argument names can be enforced by the schema language and should be.

No Data Available

The normative XML schema component of the specification is broken into separate W3C schemas. While this is a valid approach by the W3C schema specification, many (most?) of the currently available XML validation tools do not gracefully handle multiple schemas. This change will have no effect on compliant XML documents

No Data Available

Reason: The auto-generated documentation may be generated by anyone and makes the non-normative specification difficult to manage and extraordinarily large. UML diagrams in the document serve the same purpose

No Data Available

Currently an Empty UnitSet is required for all data types even when there are no units. This adds significant extra text to an XML document that validates to the XTCE schema.

No Data Available

If items like Parameters, and MetaCommands, Containers, and Algorithms were given a unique id then references to those objects could be guaranteed to be correct by the XML parsers

No Data Available

BaseDataType/Enumerated has no holder for allowed name/value pairs

No Data Available

Reed Solomon Encoding and Decoding has no algorithm in the text. Suggest providing pseudocode for CCSDS Reed Solomon. Suggest adding that missions may enter their own pseudocode if they wish.

No Data Available

Early reviewers of the specification have consistently complained that the specification is too complex – particularly in the packaging section and that the annotations that accompany the scheme are oftentimes incomplete, contain typos, or vague.

No Data Available

Add array types as one of the fundamental types in XTCE. This addition, once thought to be a ‘nice’ enhancement is now considered essential

No Data Available

Add time encoding Summary: provide a general mechanism to describe parameters and arguments that are encoded for transmission containing absolute and relative time values.

No Data Available

Remove DwellSet replace with indirect parameterRef Summary: DwellSet as currently implimented is not sufficient for all types of telemetry dwell. A Container Entry type where the entry is given indirectly will simplify the schema and provide a more general Dwell telemetry description

No Data Available

Change BusAttribute to DataEncoding, have Float, Integer, Enumerated … inherit from AbstractDataType, and make SpaceSystemType, BaseAlgorithmType, ContainerNameType … all inherit from NameDescriptionType

No Data Available

Ability needed to define a relative time offset within TimeAssociation Summary: The ‘TimeAssociationType’ provides a means for ParameterInstances to be tied to a time value, but this time association also needs to have an optional relative time offset.

No Data Available

The StringDataType needs a character width attribute to be used by the ground software when it is necessary to handle multi-byte characters.

No Data Available

Parameters that are in multiple sub-systems Summary: ITOS frequently has parameters that are considered members of multiple sub-systems, the adopted XTCE format only allows Parameters to be members of a single sub-system

No Data Available

‘shortDescription’ size restriction in the NameType is too short. Summary: 'shortDescription’ size restriction in the NameType is too short

No Data Available

‘SizeRange’ in StringDataType is ambiguous ‘SizeRange’ in StringDataType is ambiguous because it’s unclear if the size is in characters, or bytes, or bits or something else. This Element name violates one of the XTCE conventions “Hints on units (for values with units) are provided in the names of attributes”.

No Data Available

Missing ‘label’ in RangeEnumeration Summary: The label in the ToStringCalibrator for RangeEnumeration is missing

No Data Available

‘minViolations’ is misspelled The attribute ‘minViolations’ in the complex type NumericAlarmContions is spelled minVioatons’. This change will only impact XML documents that use the misspelled ‘minVioatons’ attribute.

No Data Available

Signed/Unsigned attribute for IntegerDataType Summary: The Integer Data Type requires an attribute to indicate whether this Data should be treated as a signed or unsigned integer. Missions may need the extra bit for large data values.

No Data Available

Make capitalization of Elements and Attributes consistent. According to the formatting rules at the top of the schema, all schema attributes should begin with a lower case letter and all Elements should begin with an upper case letter. This rule is mostly, but not always applied.

No Data Available

BaseDataType/Any should be reserved to describe any parameter that can be of any datatype. As it is, it is fixed to be a SourceParameterRef only

No Data Available

Have all FrameTypes inherit from a single BaseFrameType. This will simplify the schema and any auto generated code generated from the schema. Any XML documents compliant with the schema will not change as a result of this schema change

No Data Available

Have all Algorithm Types inherit from a single BaseAlgorithmType. This will simplifiy the schema and will make code auto-generated code from the schema simpler. XML documents compliant with the schema will not change as a result of this schema change.

No Data Available

Drop obsolete FormatType. This Element/Complex type is no longer used and is now orphaned

No Data Available

Remove obsolete and unreferenced FixedFrameSync Element. This element is no longer used and is now orphaned

No Data Available