XML Telemetric & Command Exchange Format Avatar
  1. OMG Specification

XML Telemetric & Command Exchange Format — Open Issues

  • Acronym: XTCE
  • Issues Count: 18
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Summary

Key Issue Reported Fixed Disposition Status
XTCE14-15 Move Alarms outside of Type Area XTCE 1.1 open
XTCE14-14 Message/IncludeCondition/BaseContainer similarity XTCE 1.1 open
XTCE14-10 Expand NameReference semantics XTCE 1.1 open
XTCE14-9 CustomAlgorithm should be "typed" reference to AlgorithmSet XTCE 1.1 open
XTCE14-8 Should RestrictionCriteria should be assignment not operators for Commanding? XTCE 1.1 open
XTCE14-7 Re-architect XTCE alarm model XTCE 1.1 open
XTCE14-6 Need support for mask alarm XTCE 1.1 open
XTCE14-4 Add variable to containers XTCE 1.1 open
XTCE14-3 Provide way to categorize all elements with @name into one or more groups XTCE 1.1 open
XTCE14-2 Add switch entry to container entry list XTCE 1.1 open
XTCE14-1 Expand features to include common industry encodings in StreamsSet XTCE 1.1 open
XTCE14-13 Checkwindow not tied to context XTCE 1.1 open
XTCE14-11 Add forward/reverse calibrator metadata XTCE 1.1 open
XTCE14-20 Cleanup Container EntryList element by deprecating IndirectParameterRefEntry XTCE 1.1 open
XTCE14-19 Add event message support XTCE 1.1 open
XTCE14-18 List and List> clean up needed XTCE 1.1 open
XTCE14-12 AbsoluteTime should have Alarms XTCE 1.1 open
XTCE14-5 Add ArgumentTypeSet to MetaCommand XTCE 1.1 open

Issues Descriptions

Move Alarms outside of Type Area

  • Key: XTCE14-15
  • Legacy Issue Number: 14454
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:04:10 BST
    Move Alarms outside of Type area. Alarms may change a lot and it may be easier
    to have them set in the Parameter area, further alarms and calibrators, as well
    as the time types reference Parameters directly which seems inconsistent with
    them being in types.

    C-S/CNES
    Ludovic Faure
  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Tue, 10 Jun 2025 23:06 GMT

Message/IncludeCondition/BaseContainer similarity

  • Key: XTCE14-14
  • Legacy Issue Number: 14460
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:11:43 BST
    Message, IncludeCondition and BaseContainer do similar things and should be
    unified
    Comment 1 Kevin Rice 2007-10-22 21:21:03 BST
    Message, IncludeCondition and BaseContainer do similar things and should be
    unified
  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Tue, 10 Jun 2025 23:06 GMT

Expand NameReference semantics

  • Key: XTCE14-10
  • Legacy Issue Number: 14489
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    Description Kevin Rice 2008-03-04 22:57:09 GMT
    Expand NameReference concept to allow specifying items in precise locations
    such as TelemetryMetaData, CommandMetaData, etc...
  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Tue, 10 Jun 2025 23:06 GMT

CustomAlgorithm should be "typed" reference to AlgorithmSet

  • Key: XTCE14-9
  • Legacy Issue Number: 14505
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    Description Kevin Rice 2008-05-28 21:35:39 BST
    CustomAlgorithm which appears in many places in the schema should be a
    namereference to AlgorithmSet. To enforce the proper semantics the Ref should
    "name" which algorithm type it referes to such as "InputAlgorithmRef" or
    "InputOutputAlgorithmRef", etc...
  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Tue, 10 Jun 2025 23:05 GMT

Should RestrictionCriteria should be assignment not operators for Commanding?

  • Key: XTCE14-8
  • Legacy Issue Number: 14506
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    Description Kevin Rice 2008-05-28 21:39:55 BST
    RestrictionCriteria seems incorrect for commands. the value checked are
    inserted to form the command, operators seem a little strange, maybe only '=='
    makes sense, etc...
  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Tue, 10 Jun 2025 23:05 GMT

Re-architect XTCE alarm model

  • Key: XTCE14-7
  • Legacy Issue Number: 19369
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    XTCE alarms are associated with data types and come in a default and context set form. A variety of alarm types are associated with each data type, some specific to it (such enum alarms). However this is too restrictive to meet the needs of many of organizations. Specifically the following is requested: allow set of alarms without a required context by data type. Original reporter is JPL.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Tue, 10 Jun 2025 23:05 GMT

Need support for mask alarm

  • Key: XTCE14-6
  • Legacy Issue Number: 19371
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    A mask alarm applies to numerics and enums – although usage in floats is discouraged. It defines 16-states which map 1 to 1 with values (say 1-16), it's a 16-bit mask – each bit is either a care or don't care. If set to 1, it's a care bit. If the value associated with that bit appears, it is in alarm. If the mask bit is set to 0, it's a don't care bit – and the value associated with it will not trip an alarm. When used with enums it's almost like an enum alarm list,except the states can go "past" the range of values given in the enum list itself. For example, suppose an enum had the values of OPEN=1, SHUT=2. The mask could be 0xfffffffc - as one and two are allowed and valid. And any other value would be in alarm. Because there's only two enum values and each of these is green but any other value is read, it is hard to completely simulate this alarm with the enum alarm list. It's possible to use a condition perhaps in this one example but the current syntax requires the enum alarm list. Further transferring this information through to another party will be hard in that case. Reported by JPL.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Tue, 10 Jun 2025 23:04 GMT

Add variable to containers

  • Key: XTCE14-4
  • Legacy Issue Number: 19382
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    Variables are local values created from bit/sub-bits specified in the entry list of container. They are similar to parameters but exist only within the scope of the container they are defined – they are of type integer. Reported by JPL.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Tue, 10 Jun 2025 23:02 GMT

Provide way to categorize all elements with @name into one or more groups

  • Key: XTCE14-3
  • Legacy Issue Number: 19381
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    Outside of the SpaceSystem and systemName, a general mechanism for categorizing @name elements into one or groups is needed. Reported by JPL.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Tue, 10 Jun 2025 23:02 GMT

Add switch entry to container entry list

  • Key: XTCE14-2
  • Legacy Issue Number: 19385
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    A switch entry is similar to the switch/case statement provided in most programming languages, and would improve upon the include condition currently found in XTCE. Reported by JPL.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Tue, 10 Jun 2025 23:01 GMT

Expand features to include common industry encodings in StreamsSet

  • Key: XTCE14-1
  • Legacy Issue Number: 19386
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    Added specific support for reed-solomon and turbo encoding, among others in the stream set. Reported by JPL.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Tue, 10 Jun 2025 23:01 GMT
  • Attachments:

Checkwindow not tied to context

  • Key: XTCE14-13
  • Legacy Issue Number: 14458
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:09:15 BST
    CheckWindow has no way to vary window size based on context
  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Tue, 10 Jun 2025 20:20 GMT

Add forward/reverse calibrator metadata

  • Key: XTCE14-11
  • Legacy Issue Number: 14473
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:48:47 BST
    Some organizations wish to capture counts to units on the telemetry side & then
    units to counts on command side (often called reverse or inverse calibrators).
    In some cases they may wish to both for various reasons, often in testing
    scenarios to validate their operation calibration. XTCE does not provide an
    easy way to mark a calibrator as either 'reverse' or 'forward'.
  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Tue, 10 Jun 2025 20:12 GMT

Cleanup Container EntryList element by deprecating IndirectParameterRefEntry

  • Key: XTCE14-20
  • Status: open  
  • Source: Boeing ( Mr. David Overeem)
  • Summary:

    The IndirectParameterRefEntry is a clever construct that has the potential to be useful, although I am not aware of anyone who has used it.

    I suggest that we consider removing it because it is a limited case of the more general case solved by the IncludeCondition element. The IncludeCondition can provide this functionality and a lot more. As a result, this element is effort for implementers that doesn't add anything really "new". In addition, it leaves a case where the need is addressed in more than 1 way - which is generally not the best idea.
  • Reported: XTCE 1.1 — Tue, 30 May 2017 23:44 GMT
  • Updated: Thu, 3 Apr 2025 20:13 GMT

Add event message support

  • Key: XTCE14-19
  • Legacy Issue Number: 19388
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    Even message support is need in XTCE. Adding an EventSet to TelemetryMetaData would be an appropriate location.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Thu, 3 Apr 2025 20:13 GMT

List and List> clean up needed
  • Key: XTCE14-18
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    After jaxb runs on the current XTCE 1.2 (after ballot 28) schema. The following methods show weaknesses in the schema type hierarchy (below). It's been shown they schema types can be meaningfully tweaked and these items will map cleanly. It also suggest but is not clear the order of the items in some the lists may not be enforced. for two of the items below this would be bad. this is conjecture however.

    >> ArgumentInputSetType.java: public List<Object> getInputParameterInstanceRefOrInputArgumentInstanceRef() {
    >> InputSetType.java: public List<Object> getInputParameterInstanceRefOrConstant() {
    >> ParameterSetType.java: public List<Object> getParameterOrParameterRef() {
    >>
    >> ArgumentComparisonCheckType.java: public List<JAXBElement<?>> getRest() {
    >> ComparisonCheckType.java: public List<JAXBElement<?>> getRest() {
    >> MathOperationCalibratorType.java: public List<JAXBElement<?>> getValueOperandOrThisParameterOperandOrOperator() {
    >> MetaCommandSetType.java: public List<JAXBElement<?>> getMetaCommandOrMetaCommandRefOrBlockMetaCommand() {
    >>
  • Reported: XTCE 1.1 — Wed, 14 Feb 2018 17:43 GMT
  • Updated: Thu, 3 Apr 2025 20:13 GMT
  • Attachments:

AbsoluteTime should have Alarms

  • Key: XTCE14-12
  • Legacy Issue Number: 14466
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:37:38 BST
    AbsoluteTimeParameterType do not have alarm elements associated with it. In
    the current schema this may be by design – an example of a usage for an
    alarming absolute time could be helpful. JWST claims to alarm on occurrences
    of reverse time which in fact would probably be a packet ordering issue.
  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Thu, 3 Apr 2025 20:13 GMT

Add ArgumentTypeSet to MetaCommand

  • Key: XTCE14-5
  • Legacy Issue Number: 19377
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    Allow for local argument types to be defined in MetaCommand, helps avoid collisions with arguments in other commands of the same name but different properties.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Thu, 3 Apr 2025 20:13 GMT