1. OMG Mailing List
  2. XTCE US Government Satellite Conformance Profile 1.0 (XUSP) Revision Task Force

Open Issues

  • Issues not resolved
  • Name: xusp-rtf
  • Issues Count: 21

Issues Summary

Key Issue Reported Fixed Disposition Status
XUSP11-41 XUSP should allow alarm severity of Distress XUSP 1.0 open
XUSP11-40 XUSP should not prevent use of Critical alarm severity as it is recommended by XTCE XUSP 1.0 open
XUSP11-42 XUSP should allow nesting of SpaceSystems inside SpaceSystems XUSP 1.0 open
XUSP11-38 Small edits for XTCE 1.2 or misc grammar and dates XUSP 1.0 open
XUSP11-36 name, label and other similar fields should be greater than 64 chars max XUSP 1.0 open
XUSP11-34 SCID should be a Parameter, not an AncillaryData value XUSP 1.0 open
XUSP11-14 Possible typo: omission of "of" XTCE 1.2 open
XUSP11-22 StringDataEncoding/Variable should be disallowed XUSP 1.0 open
XUSP11-6 XUSP 1.1 should not include AlarmMultiRanges XUSP 1.0 open
XUSP11-11 ParameterToSet/Derviation is set to abstract and should not be XUSP 1.0 open
XUSP11-21 ParameterToSet/Derviation is set to abstract and should not be XUSP 1.0 open
XUSP11-15 Possible typo of word "difference" instead of "different" XTCE 1.2 open
XUSP11-16 Enhance support for VCID to not depend on AncillaryData XUSP 1.0 open
XUSP11-13 xpath syntax errors XUSP 1.0 open
XUSP11-10 Errors in rules XUSP 1.0 open
XUSP11-7 XUSP 1.1 should not include rangeForm="inside" XUSP 1.0 open
XUSP11-5 Eliminate extraneous whitespace in XUSP CSV file XUSP 1.0 open
XUSP11-4 The label attribute of a ValueEnumerationType should be limited in length XUSP 1.0 open
XUSP11-12 The following schema-type have a funny character encodings in annotation, create problems XUSP 1.0 open
XUSP11-8 Remove excess whitespace from published 1.0 spec XUSP 1.0 open
XUSP11-1 XUSP does not correspond to current (1.2) revision of XTCE Specification XUSP 1.0 open

Issues Descriptions


XUSP should not prevent use of Critical alarm severity as it is recommended by XTCE

  • Key: XUSP11-40
  • Status: open  
  • Source: Kratos RT Logic, Inc. ( Mr. Justin Boss)
  • Summary:

    XTCE mentions:

    Typical implementations color the "normal" level as green, "warning" level as yellow, and "critical" level as red.

    As such, XUSP should allow the use of critical.

  • Reported: XUSP 1.0 — Thu, 7 Dec 2023 21:32 GMT
  • Updated: Thu, 7 Dec 2023 21:52 GMT

XUSP should allow nesting of SpaceSystems inside SpaceSystems

  • Key: XUSP11-42
  • Status: open  
  • Source: Kratos RT Logic, Inc. ( Mr. Justin Boss)
  • Summary:

    Nesting should be allowed.

    Need to determine if nesting should be limited/constrained to prevent unlimited nesting.

  • Reported: XUSP 1.0 — Thu, 7 Dec 2023 21:48 GMT
  • Updated: Thu, 7 Dec 2023 21:48 GMT

Small edits for XTCE 1.2 or misc grammar and dates

  • Key: XUSP11-38
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    This captures small edits throughout the spec document including changing XTCE 1.1 to XTCE 1.2, dates or small grammar edits.

  • Reported: XUSP 1.0 — Thu, 22 Jun 2023 13:34 GMT
  • Updated: Thu, 22 Jun 2023 13:34 GMT

name, label and other similar fields should be greater than 64 chars max

  • Key: XUSP11-36
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    64 char limited names seemed reasonable however many years ago and in general this is true, nonetheless in our various GSFC conversion efforts we have consistently found a few parameter names that are longer. Usually this is in reference to a "flattening" process from a long complex type style definition to a single long dotted and array subscripted name. The result in a few cases of an overall database is greater than 64.
    Most systems also seem to provide a way to make a shorter global "alias" so while holding these long named items in some internal table.

  • Reported: XUSP 1.0 — Wed, 21 Jun 2023 20:14 GMT
  • Updated: Wed, 21 Jun 2023 20:14 GMT

SCID should be a Parameter, not an AncillaryData value

  • Key: XUSP11-34
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    The SCID should be a Parameter.

  • Reported: XUSP 1.0 — Wed, 21 Jun 2023 20:08 GMT
  • Updated: Wed, 21 Jun 2023 20:08 GMT

Possible typo: omission of "of"

  • Key: XUSP11-14
  • Status: open  
  • Source: CACI ( Zebulun Barnett)
  • Summary:

    Missing the word, "of" between "instances" and "this" in "...Interlocks apply instead to any Commands that may follow instances this MetaCommand."

  • Reported: XTCE 1.2 — Thu, 3 Sep 2020 20:27 GMT
  • Updated: Wed, 21 Jun 2023 19:41 GMT

StringDataEncoding/Variable should be disallowed

  • Key: XUSP11-22
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    Purely variable strings are not supported.

  • Reported: XUSP 1.0 — Mon, 5 Dec 2022 20:56 GMT
  • Updated: Mon, 5 Dec 2022 20:57 GMT

XUSP 1.1 should not include AlarmMultiRanges

  • Key: XUSP11-6
  • Status: open  
  • Source: Northrop Grumman ( Mr. Joseph Vlietstra)
  • Summary:

    AlarmMultiRanges feature was added in XTCE 1.2. This feature should not be included in the XUSP 1.1 update since is too complex for the target alarm model.

  • Reported: XUSP 1.0 — Wed, 25 Mar 2020 19:26 GMT
  • Updated: Mon, 5 Dec 2022 20:55 GMT

ParameterToSet/Derviation is set to abstract and should not be

  • Key: XUSP11-11
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    ParameterToSet/Derivation is a MathOperationType which is abstract. Which means you can make an instance of it.

    A simple fix is to make a DerivationType extending MathOperationType.

  • Reported: XUSP 1.0 — Fri, 15 May 2020 17:33 GMT
  • Updated: Wed, 21 Sep 2022 21:01 GMT

ParameterToSet/Derviation is set to abstract and should not be

  • Key: XUSP11-21
  • Status: open  
  • Source: Kratos RT Logic, Inc. ( Mr. Justin Boss)
  • Summary:

    ParameterToSet/Derivation is a MathOperationType which is abstract. Which means you can make an instance of it.

    A simple fix is to make a DerivationType extending MathOperationType.

  • Reported: XUSP 1.0 — Wed, 21 Sep 2022 21:00 GMT
  • Updated: Wed, 21 Sep 2022 21:01 GMT

Possible typo of word "difference" instead of "different"

  • Key: XUSP11-15
  • Status: open  
  • Source: CACI ( Zebulun Barnett)
  • Summary:

    "There are eight different verifiers each associated with *difference* states in command processing"

  • Reported: XTCE 1.2 — Thu, 3 Sep 2020 20:31 GMT
  • Updated: Wed, 21 Sep 2022 20:59 GMT

Enhance support for VCID to not depend on AncillaryData

  • Key: XUSP11-16
  • Status: open  
  • Source: Kratos RT Logic, Inc. ( Mr. Justin Boss)
  • Summary:

    Since the VCID is telemetered and is a standard CCSDS construct, suggest that supporting VCID be promoted to being supported first-class instead of via the AncillaryData construct.

    Also, SCID and other transfer frame constructs should be similarly supported.

  • Reported: XUSP 1.0 — Mon, 21 Jun 2021 13:53 GMT
  • Updated: Wed, 21 Sep 2022 20:56 GMT

xpath syntax errors

  • Key: XUSP11-13
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    The following lines have xpath syntax errors and don't "compile" using Java XPath.

    Bad #1 rule – @line 830 --> count(//@/@lastEntryForThisArrayInstance)=0
    Bad #2 rule – @line 897 --> count(//xtce:CommandMetaData/*/xtce:DefaultAlarm
    Bad #3 rule – @line 898 --> count(//xtce:CommandMetaData/*/xtce:ContextAlarmList
    Bad #4 rule – @line 939 --> count(//xtce:CommandMetaData/*/xtce:DefaultAlarm
    Bad #5 rule – @line 1019 --> count(//xtce:CommandMetaData/*/xtce:DefaultAlarm
    Bad #6 rule – @line 1020 --> count(//xtce:CommandMetaData/*/xtce:ContextAlarmList
    Bad #7 rule – @line 1044 --> count(//xtce:CommandMetaData/*/xtce:DefaultAlarm
    Bad #8 rule – @line 1150 --> count(//xtce:CommandMetaData/*/xtce:DefaultAlarm
    Bad #9 rule – @line 1151 --> count(//xtce:CommandMetaData/*/xtce:ContextAlarmList
    Bad #10 rule – @line 1201 --> count(//xtce:CommandMetaData/*/xtce:DefaultAlarm
    Bad #11 rule – @line 1202 --> count(//xtce:CommandMetaData/*/xtce:ContextAlarmList
    Bad #12 rule – @line 1764 --> count(//@/@lastEntryForThisArrayInstance)=0
    Bad #13 rule – @line 1805 --> count(//@/@lastEntryForThisArrayInstance)=0
    Bad #14 rule – @line 2003 --> count(//@/@lastEntryForThisArrayInstance)=0

  • Reported: XUSP 1.0 — Wed, 16 Sep 2020 16:55 GMT
  • Updated: Wed, 21 Sep 2022 20:55 GMT

Errors in rules

  • Key: XUSP11-10
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    Several of the rules appear to have syntax errors, such as:

    count(//xtce:CommandMetaData/*/xtce:DefaultAlarm

  • Reported: XUSP 1.0 — Thu, 16 Apr 2020 17:53 GMT
  • Updated: Wed, 21 Sep 2022 20:47 GMT

XUSP 1.1 should not include rangeForm="inside"

  • Key: XUSP11-7
  • Status: open  
  • Source: Northrop Grumman ( Mr. Joseph Vlietstra)
  • Summary:

    rangeForm attribute was added in XTCE 1.2. This attribute allows severity level between alarm ranges to be reversed (that is, rangeForm="inside" causes the more severe alarm ranges to inside of less severe alarm ranges). The rangeForm="inside" option not be included in the XUSP 1.1 update since is too complex for the target alarm model.

  • Reported: XUSP 1.0 — Wed, 25 Mar 2020 19:33 GMT
  • Updated: Wed, 21 Sep 2022 20:45 GMT

Eliminate extraneous whitespace in XUSP CSV file

  • Key: XUSP11-5
  • Status: open  
  • Source: Northrop Grumman ( Mr. Joseph Vlietstra)
  • Summary:

    The XUSProfileRules.csv file contains extraneous spaces between commas. The spacing between commas is inconsistent it's mostly “, ,” but frequently “,,”. These spaces cause non-empty entries when the CSV file is imported into Excel.

  • Reported: XUSP 1.0 — Wed, 25 Mar 2020 19:12 GMT
  • Updated: Wed, 21 Sep 2022 20:40 GMT

The label attribute of a ValueEnumerationType should be limited in length

  • Key: XUSP11-4
  • Status: open  
  • Source: Peraton ( Brad Kizzort)
  • Summary:

    Most names and fields in XUSP have added limits to the string length. There is no limit on the label size. I recommend that it match the mnemonic length of 64 characters.

  • Reported: XUSP 1.0 — Wed, 25 Mar 2020 19:06 GMT
  • Updated: Wed, 21 Sep 2022 20:39 GMT

The following schema-type have a funny character encodings in annotation, create problems

  • Key: XUSP11-12
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    The following 4 schema-types have funny character encodings for quotes or similar in a few lines of annotation, probably from Word editing.

    BinaryArgumentType
    BinaryDataType
    BinaryParametertype
    ServiceRefType

    The errors are around "" items like "dangling reference" and some of the path related items.

    approx. lines 20, 22, 26 and 58 per each file.

    This makes some things complain – maybe compilers, Javadoc other tools.

    The quick fix is to simply edit the schema and fix them, then motor on your way.

  • Reported: XUSP 1.0 — Fri, 26 Jun 2020 19:18 GMT
  • Updated: Wed, 22 Jun 2022 20:09 GMT

Remove excess whitespace from published 1.0 spec

  • Key: XUSP11-8
  • Status: open  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    The published specification has extra whitespace in some of the columns. These should be removed before proceeding on updating the rules further.

  • Reported: XUSP 1.0 — Thu, 16 Apr 2020 13:51 GMT
  • Updated: Sat, 2 May 2020 00:40 GMT
  • Attachments:

XUSP does not correspond to current (1.2) revision of XTCE Specification

  • Key: XUSP11-1
  • Status: open  
  • Source: Peraton ( Brad Kizzort)
  • Summary:

    The XTCE 1.2 specification was approved by the DTC. The XUSP profile, which is based on XTCE, should be updated to use the Elements and Attributes of the XTCE 1.2 schema.

  • Reported: XUSP 1.0 — Mon, 25 Jun 2018 16:39 GMT
  • Updated: Thu, 6 Feb 2020 14:24 GMT