XML Telemetric & Command Exchange Format Avatar
  1. OMG Specification

XML Telemetric & Command Exchange Format — Closed Issues

  • Acronym: XTCE
  • Issues Count: 27
  • Description: Issues resolved by a task force and approved by Board
Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Key Issue Reported Fixed Disposition Status
XTCE-33 Merge the XTCE shemas into a single schema XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-29 There needs to be an ability to define an expected rate on containers XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-26 StringDataType needs a char width Summary XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-30 Use schema keyrefs to guarantee references are valid XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-25 ‘SizeRange’ in StringDataType is ambiguous XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-28 Unique MetaCommand argument names should be enforced XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-27 Ability needed to define a relative time offset within TimeAssociation XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-32 Remove Altova XML spy diagrams from non normative section. XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-24 Missing ‘label’ in RangeEnumeration Summary XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-31 Make UnitSet optional XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-20 ‘shortDescription’ size restriction in the NameType is too short XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-23 ‘minViolations’ is misspelled XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-21 Parameters that are in multiple sub-systems Summary XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-16 Remove DwellSet replace with indirect parameterRef Summary XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-14 Have all FrameTypes inherit from a single BaseFrameType XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-22 Signed/Unsigned attribute for IntegerDataType Summary XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-19 Specification too complex? XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-18 Add array types as one of the fundamental types in XTCE XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-17 Add time encoding Summary XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-15 Change BusAttribute to DataEncoding, have Float, Integer, Enumerated... XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-9 BaseDataType/Any XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-12 Drop obsolete FormatType. XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-13 Have all Algorithm Types inherit from a single BaseAlgorithmType XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-11 Remove obsolete and unreferenced FixedFrameSync Element. XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-10 Make capitalization of Elements and Attributes consistent XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-7 Reed Solomon Encoding and Decoding has no algorithm in the text XTCE 1.0b1 XTCE 1.0 Resolved closed
XTCE-8 BaseDataType/Enumerated has no holder for allowed name/value pairs XTCE 1.0b1 XTCE 1.0 Resolved closed

Issues Descriptions

Merge the XTCE shemas into a single schema

  • Key: XTCE-33
  • Legacy Issue Number: 8061
  • Status: closed  
  • Source: Braxton Technologies, LLC ( Gerry Simon)
  • Summary:

    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

  • Reported: XTCE 1.0b1 — Fri, 31 Dec 2004 05:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

There needs to be an ability to define an expected rate on containers

  • Key: XTCE-29
  • Legacy Issue Number: 8056
  • Status: closed  
  • Source: Braxton Technologies, LLC ( Gerry Simon)
  • 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

  • Reported: XTCE 1.0b1 — Fri, 31 Dec 2004 05:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

StringDataType needs a char width Summary

  • Key: XTCE-26
  • Legacy Issue Number: 8053
  • Status: closed  
  • Source: Braxton Technologies, LLC ( Gerry Simon)
  • Summary:

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

  • Reported: XTCE 1.0b1 — Fri, 31 Dec 2004 05:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

Use schema keyrefs to guarantee references are valid

  • Key: XTCE-30
  • Legacy Issue Number: 8058
  • Status: closed  
  • Source: Braxton Technologies, LLC ( Gerry Simon)
  • Summary:

    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

  • Reported: XTCE 1.0b1 — Fri, 31 Dec 2004 05:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

‘SizeRange’ in StringDataType is ambiguous

  • Key: XTCE-25
  • Legacy Issue Number: 8052
  • Status: closed  
  • Source: Braxton Technologies, LLC ( Gerry Simon)
  • Summary:

    ‘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”.

  • Reported: XTCE 1.0b1 — Fri, 31 Dec 2004 05:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

Unique MetaCommand argument names should be enforced

  • Key: XTCE-28
  • Legacy Issue Number: 8055
  • Status: closed  
  • Source: Braxton Technologies, LLC ( Gerry Simon)
  • Summary:

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

  • Reported: XTCE 1.0b1 — Fri, 31 Dec 2004 05:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

Ability needed to define a relative time offset within TimeAssociation

  • Key: XTCE-27
  • Legacy Issue Number: 8054
  • Status: closed  
  • Source: Braxton Technologies, LLC ( Gerry Simon)
  • Summary:

    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.

  • Reported: XTCE 1.0b1 — Fri, 31 Dec 2004 05:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

Remove Altova XML spy diagrams from non normative section.

  • Key: XTCE-32
  • Legacy Issue Number: 8060
  • Status: closed  
  • Source: Braxton Technologies, LLC ( Gerry Simon)
  • Summary:

    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

  • Reported: XTCE 1.0b1 — Fri, 31 Dec 2004 05:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

Missing ‘label’ in RangeEnumeration Summary

  • Key: XTCE-24
  • Legacy Issue Number: 8051
  • Status: closed  
  • Source: Braxton Technologies, LLC ( Gerry Simon)
  • Summary:

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

  • Reported: XTCE 1.0b1 — Fri, 31 Dec 2004 05:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

Make UnitSet optional

  • Key: XTCE-31
  • Legacy Issue Number: 8059
  • Status: closed  
  • Source: Braxton Technologies, LLC ( Gerry Simon)
  • Summary:

    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.

  • Reported: XTCE 1.0b1 — Fri, 31 Dec 2004 05:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

‘shortDescription’ size restriction in the NameType is too short

  • Key: XTCE-20
  • Legacy Issue Number: 8047
  • Status: closed  
  • Source: Braxton Technologies, LLC ( Gerry Simon)
  • Summary:

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

  • Reported: XTCE 1.0b1 — Fri, 31 Dec 2004 05:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

‘minViolations’ is misspelled

  • Key: XTCE-23
  • Legacy Issue Number: 8050
  • Status: closed  
  • Source: Braxton Technologies, LLC ( Gerry Simon)
  • Summary:

    ‘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.

  • Reported: XTCE 1.0b1 — Fri, 31 Dec 2004 05:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

Parameters that are in multiple sub-systems Summary

  • Key: XTCE-21
  • Legacy Issue Number: 8048
  • Status: closed  
  • Source: Braxton Technologies, LLC ( Gerry Simon)
  • Summary:

    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

  • Reported: XTCE 1.0b1 — Fri, 31 Dec 2004 05:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

Remove DwellSet replace with indirect parameterRef Summary

  • Key: XTCE-16
  • Legacy Issue Number: 8043
  • Status: closed  
  • Source: Braxton Technologies, LLC ( Gerry Simon)
  • Summary:

    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

  • Reported: XTCE 1.0b1 — Fri, 31 Dec 2004 05:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

Have all FrameTypes inherit from a single BaseFrameType

  • Key: XTCE-14
  • Legacy Issue Number: 6062
  • Status: closed  
  • Source: Braxton Technologies, LLC ( Gerry Simon)
  • Summary:

    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

  • Reported: XTCE 1.0b1 — Mon, 25 Aug 2003 04:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

Signed/Unsigned attribute for IntegerDataType Summary

  • Key: XTCE-22
  • Legacy Issue Number: 8049
  • Status: closed  
  • Source: Braxton Technologies, LLC ( Gerry Simon)
  • Summary:

    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.

  • Reported: XTCE 1.0b1 — Fri, 31 Dec 2004 05:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

Specification too complex?

  • Key: XTCE-19
  • Legacy Issue Number: 8046
  • Status: closed  
  • Source: Braxton Technologies, LLC ( Gerry Simon)
  • Summary:

    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.

  • Reported: XTCE 1.0b1 — Fri, 31 Dec 2004 05:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

Add array types as one of the fundamental types in XTCE

  • Key: XTCE-18
  • Legacy Issue Number: 8045
  • Status: closed  
  • Source: NASA ( Kevin Rice)
  • Summary:

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

  • Reported: XTCE 1.0b1 — Fri, 31 Dec 2004 05:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

Add time encoding Summary

  • Key: XTCE-17
  • Legacy Issue Number: 8044
  • Status: closed  
  • Source: Braxton Technologies, LLC ( Gerry Simon)
  • Summary:

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

  • Reported: XTCE 1.0b1 — Fri, 31 Dec 2004 05:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

Change BusAttribute to DataEncoding, have Float, Integer, Enumerated...

  • Key: XTCE-15
  • Legacy Issue Number: 6063
  • Status: closed  
  • Source: NASA ( Kevin Rice)
  • Summary:

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

  • Reported: XTCE 1.0b1 — Mon, 25 Aug 2003 04:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

BaseDataType/Any

  • Key: XTCE-9
  • Legacy Issue Number: 6057
  • Status: closed  
  • Source: University of Maryland ( Ed Shaya)
  • Summary:

    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

  • Reported: XTCE 1.0b1 — Tue, 12 Aug 2003 04:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

Drop obsolete FormatType.

  • Key: XTCE-12
  • Legacy Issue Number: 6060
  • Status: closed  
  • Source: Braxton Technologies, LLC ( Gerry Simon)
  • Summary:

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

  • Reported: XTCE 1.0b1 — Mon, 25 Aug 2003 04:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

Have all Algorithm Types inherit from a single BaseAlgorithmType

  • Key: XTCE-13
  • Legacy Issue Number: 6061
  • Status: closed  
  • Source: Braxton Technologies, LLC ( Gerry Simon)
  • Summary:

    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.

  • Reported: XTCE 1.0b1 — Mon, 25 Aug 2003 04:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

Remove obsolete and unreferenced FixedFrameSync Element.

  • Key: XTCE-11
  • Legacy Issue Number: 6059
  • Status: closed  
  • Source: Braxton Technologies, LLC ( Gerry Simon)
  • Summary:

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

  • Reported: XTCE 1.0b1 — Mon, 25 Aug 2003 04:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

Make capitalization of Elements and Attributes consistent

  • Key: XTCE-10
  • Legacy Issue Number: 6058
  • Status: closed  
  • Source: Braxton Technologies, LLC ( Gerry Simon)
  • Summary:

    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.

  • Reported: XTCE 1.0b1 — Mon, 25 Aug 2003 04:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

Reed Solomon Encoding and Decoding has no algorithm in the text

  • Key: XTCE-7
  • Legacy Issue Number: 6055
  • Status: closed  
  • Source: Raytheon Corp. ( Ed Shaya)
  • Summary:

    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.

  • Reported: XTCE 1.0b1 — Tue, 12 Aug 2003 04:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT

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

  • Key: XTCE-8
  • Legacy Issue Number: 6056
  • Status: closed  
  • Source: University of Maryland ( Ed Shaya)
  • Summary:

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

  • Reported: XTCE 1.0b1 — Tue, 12 Aug 2003 04:00 GMT
  • Disposition: Resolved — XTCE 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:59 GMT