1. OMG Mailing List
  2. XTCE Revision Task Force

Open Issues

  • Issues not resolved
  • Name: xtce-rtf
  • Issues Count: 220

Issues Summary

Key Issue Reported Fixed Disposition Status
XTCE12-448 AbsoluteTimeParameterType Epoch is not always at midnight XTCE 1.1 open
XTCE12-454 LongDescriptionType as a complexType is unnecessary XTCE 1.1 open
XTCE12-397 MetaCommandStep argument assignment XTCE 1.1 open
XTCE12-95 InputOutputTriggerAlgorithmType@triggerContainer is a NameType, should it be a NameReference? XTCE 1.1 open
XTCE12-93 InputOutputAlgorithm@thread optional boolean, should have default of false XTCE 1.1 open
XTCE12-124 MathOperator needs to be cleaned up XTCE 1.1 open
XTCE12-80 IndirectParameterEntry should have segment varient? XTCE 1.1 open
XTCE12-85 CustomAlgorithm should be "typed" reference to AlgorithmSet XTCE 1.1 open
XTCE12-82 Should RestrictionCriteria should be assignment not operators for Commanding? XTCE 1.1 open
XTCE12-61 The XTCE element MetaCommand has a child element called VerifierSet XTCE 1.1 open
XTCE12-47 Elevate annotation specifying time string formats to an attributes XTCE 1.1 open
XTCE12-67 Adding structure to Parameters XTCE 1.1 open
XTCE12-27 Fix annotation issues throughout schema XTCE 1.1 open
XTCE12-456 ValidRange element duplicated with ValidRangeSet in ArgumentTypeSet XTCE 1.1 open
XTCE12-439 Error in unique keys fix in XTCE12-346 XTCE 1.1 open
XTCE12-431 Alternate approach to xs:positiveInteger and xs:nonNegativeInteger XTCE 1.1 open
XTCE12-441 Mistake in previous resolution for addition of XInclude support XTCE 1.1 open
XTCE12-381 The ToString element used in Integer and Float types overlaps with Enumerated types XTCE 1.1 open
XTCE12-113 Autogenerator issue with schema type derivation XTCE 1.1 open
XTCE12-60 element ParameterInstanceRefOperand in the MathOperationType XTCE 1.1 open
XTCE12-395 Use of raw value for calibrator context selection XTCE 1.1 open
XTCE12-110 StringDataType UTF-8/CharacterWidth Issue XTCE 1.1 open
XTCE12-107 Generalize array type, add attribute for ROW or COL order XTCE 1.1 open
XTCE12-111 Unify metacommand/commandContainer and commandContainerSet/commandcontainer schema types XTCE 1.1 open
XTCE12-106 Explain interaction of dynamic value and segments, array lastEntryForThisArray XTCE 1.1 open
XTCE12-92 Derive ArgumentTypes by extension XTCE 1.1 open
XTCE12-87 FloatEncoding float formats -- MIL1750a, IEEE, bit size issues XTCE 1.1 open
XTCE12-88 FixedValueEntry@sizeInBits should be required XTCE 1.1 open
XTCE12-114 Align ArgumentType and ParameterType construction XTCE 1.1 open
XTCE12-72 inside/outside alarms not supported XTCE 1.1 open
XTCE12-66 Member of an AggregateParameterType or AggregateArgumentType can't be an ArrayParameterType or ArrayArgumentType XTCE 1.1 open
XTCE12-84 AlgorithmSet missing algorithms XTCE 1.1 open
XTCE12-62 At the Parameter element, initial values for Array or Aggregates may not be set. XTCE 1.1 open
XTCE12-133 Move array sizing to Parameter and Argument from container area XTCE 1.1 open
XTCE12-22 Repeat arguments XTCE 1.1 open
XTCE12-38 Expand features to include common industry encodings in StreamsSet XTCE 1.1 open
XTCE12-23 Fill argument XTCE 1.1 open
XTCE12-20 Variable length strings need optional maximum length designator XTCE 1.1 open
XTCE12-449 Cleanup Container EntryList element by deprecating IndirectParameterRefEntry XTCE 1.1 open
XTCE12-119 AlarmType produces problem in JaxB XTCE 1.1 open
XTCE12-54 Need support for mask alarm XTCE 1.1 open
XTCE12-50 Off Alarms XTCE 1.1 open
XTCE12-55 Re-architect XTCE alarm model XTCE 1.1 open
XTCE12-53 Combination Alarm XTCE 1.1 open
XTCE12-34 Only single instance of Alarm Condition/Range XTCE 1.1 open
XTCE12-29 Add normal alarm condition or alarm ranges XTCE 1.1 open
XTCE12-76 ChangeAlarmRates confusing and ambiguous XTCE 1.1 open
XTCE12-91 toString/NumberFormat needs default settings XTCE 1.1 open
XTCE12-41 Provide way to categorize all elements with @name into one or more groups XTCE 1.1 open
XTCE12-12 Improve CRCType Polynomial element XTCE 1.1 open
XTCE12-75 ErroCorrectDetect -- Parity XTCE 1.1 open
XTCE12-400 ByteOrderList in XTCE 1.1 needs to be improved XTCE 1.1 open
XTCE12-59 Alarm count to enter alarm (minViolations), needs corresponding count to leave the alarm state XTCE 1.1 open
XTCE12-15 Remove whitespace in selector xpath attribute XTCE 1.1 open
XTCE12-71 In EnumerationAlarm, enumerationValue should called enumerationLabel XTCE 1.1 open
XTCE12-74 remove extraneous keys or uniq XTCE 1.1 open
XTCE12-49 Expand telemetry parameter data source attribute XTCE 1.1 open
XTCE12-52 Digital Alarms XTCE 1.1 open
XTCE12-51 Change alarm XTCE 1.1 open
XTCE12-45 Add raw units to ParameterType XTCE 1.1 open
XTCE12-48 Add ArgumentTypeSet to MetaCommand XTCE 1.1 open
XTCE12-31 Database of single SpaceSystem cannot designate a parameter to be within multiple systems XTCE 1.1 open
XTCE12-32 Add additional math operators to mathoperations XTCE 1.1 open
XTCE12-28 Error detection algorithm does not support XOR XTCE 1.1 open
XTCE12-24 Add to or change way crc is specified XTCE 1.1 open
XTCE12-421 Provide specific type consequence level XTCE 1.1 open
XTCE12-434 XTCE12-11 fix for name references did not work correctly XTCE 1.1 open
XTCE12-96 *Container@abstract should have default of false XTCE 1.1 open
XTCE12-416 Member location within AggregateDataType XTCE 1.0 open
XTCE12-68 Need a ParameterProperty for "observability" or "change only threshold" XTCE 1.1 open
XTCE12-86 Time/Encoding@scale,@offset terminology vs DynamicValue/LinearAdjust XTCE 1.1 open
XTCE12-58 Bit extract feature needed in telemetry parameter XTCE 1.1 open
XTCE12-33 Add ranges to enumeration list XTCE 1.1 open
XTCE12-56 Enum Alarm List should be optional XTCE 1.1 open
XTCE12-10 Add xinclude to support ximport XTCE 1.1 open
XTCE12-39 Add event message support XTCE 1.1 open
XTCE12-78 Clean up semantics of "OO-Include Condition" XTCE 1.1 open
XTCE12-7 toString/NumberFormat needs default settings XTCE 1.0 open
XTCE12-14 Type inheritance missing from Absolute and Relative time data types XTCE 1.1 open
XTCE12-103 size in bits of float encoding XTCE 1.1 open
XTCE12-26 Add support for arbitary floating point XTCE 1.1 open
XTCE12-17 Valid sizeInBits values for encoding="MILSTD_1750A" XTCE 1.1 open
XTCE12-94 MessageSet has unneeded attribute XTCE 1.1 open
XTCE12-108 Add name attribute to context alarms or calibrators XTCE 1.1 open
XTCE12-121 PercentComplete in Verifiers needs clean up XTCE 1.1 open
XTCE12-77 exponent attribute in Term element in PolynomialCalibrator should be non-negative integer XTCE 1.1 open
XTCE12-25 Range support in enumerated parameter type XTCE 1.1 open
XTCE12-19 StringAlarmList is required but it should be optional XTCE 1.1 open
XTCE12-16 Change NameType regex from zero or more to one or more characters XTCE 1.1 open
XTCE12-11 Add regex to enforced syntax of NameReferences XTCE 1.1 open
XTCE12-97 DefaultSignicance element can have no content at all XTCE 1.1 open
XTCE12-100 SplinePoint attribute order should be ignored (typo) XTCE 1.1 open
XTCE12-112 Move ValidRangeAppliesToCalibrated Attribute XTCE 1.1 open
XTCE12-57 SplineCalibrator order attribute too restrictive XTCE 1.1 open
XTCE12-8 Enumeration element could use an @shortDescription XTCE 1.1 open
XTCE12-13 Possible unused attribute in RepeatEntry XTCE 1.1 open
XTCE12-18 Improve FloatRangeType and IntegerRangeType XTCE 1.1 open
XTCE12-73 ByteOrderList is invalid for Containers XTCE 1.1 open
XTCE12-116 Add forward/reverse calibrator metadata XTCE 1.1 open
XTCE12-118 TimeAssociation schema type is incorrect XTCE 1.1 open
XTCE12-105 Use of the include conditions XTCE 1.1 open
XTCE12-109 Key bugs XTCE 1.1 open
XTCE12-115 Change UnitSet to simple String; change name XTCE 1.1 open
XTCE12-99 Remove old comments XTCE 1.1 open
XTCE12-101 relative path in the parameterRef XTCE 1.1 open
XTCE12-102 packet identification XTCE 1.1 open
XTCE12-104 Add explanatory annotation that MetaCommand/CommandContainer is semantically similar to a Java Private Inner Class XTCE 1.1 open
XTCE12-98 Expand NameReference semantics XTCE 1.1 open
XTCE12-81 Condition has two elements with the same name, causes problems for some autogenerators XTCE 1.1 open
XTCE12-83 Add OCL specific Algorithm to XTCE XTCE 1.1 open
XTCE12-90 *Type/@initialValue need clarifications XTCE 1.1 open
XTCE12-69 EnumeratedParameterType does not support multiple context alarms XTCE 1.1 open
XTCE12-70 EnumeratedParameterType does not support multiple context alarms XTCE 1.1 open
XTCE12-79 RelativeTimeType nomenclature conflicts with RelativeTimeParameterType XTCE 1.1 open
XTCE12-43 Add gap entry to container entry list XTCE 1.1 open
XTCE12-42 Add named width spacer to Container entry list XTCE 1.1 open
XTCE12-46 Add variable to containers XTCE 1.1 open
XTCE12-44 Add title to parameter XTCE 1.1 open
XTCE12-21 Add argument and fixed value entries to CommandContainerSet/CommandContainer XTCE 1.1 open
XTCE12-30 AlarmRanges cannot be defined based on raw values XTCE 1.1 open
XTCE12-37 Add APID table list XTCE 1.1 open
XTCE12-40 Add switch entry to container entry list XTCE 1.1 open
XTCE12-136 Create RangeEnumeration Type XTCE 1.1 open
XTCE12-139 Clear Up Calibrated/Uncalibrated Values in Schema XTCE 1.1 open
XTCE12-134 Move Alarms outside of Type Area XTCE 1.1 open
XTCE12-135 Fix ArgumentTypes child element or attributes that use the term Parameter, to Argument XTCE 1.1 open
XTCE12-129 Message/IncludeCondition/BaseContainer similarity XTCE 1.1 open
XTCE12-130 ContextAlarm not set to Inf Elements in EnumerationType XTCE 1.1 open
XTCE12-131 Label Missing in IntegerType/RangeEnumeration area XTCE 1.1 open
XTCE12-132 Add ability to compare counters in IncludeCondition XTCE 1.1 open
XTCE12-126 Put Alarms in Arguments; leaves Alarms in Command Parameters XTCE 1.1 open
XTCE12-127 ErrorDetectCorrect does not support Checksum XTCE 1.1 open
XTCE12-128 Checkwindow not tied to context XTCE 1.1 open
XTCE12-123 Change UnitSet to optional XTCE 1.1 open
XTCE12-125 Clean up Annotation Related to Verifiers XTCE 1.1 open
XTCE12-122 Clarify ContainerRef check in Verification area XTCE 1.1 open
XTCE12-120 AbsoluteTime should have Alarms XTCE 1.1 open
XTCE12-117 Message/ContainRef should read ContainerRef XTCE 1.1 open
XTCE12-65 XTCE 1.1 open
XTCE12-89 attribute twosCompliment should be twosComplement XTCE 1.1 open
XTCE12-36 Fix spelling of one/twosCompliment in IntegerDataEncoding XTCE 1.1 open
XTCE12-64 AggregateParameterType or AggregateArgumentType Member attribute 'typeRef' is vague XTCE 1.1 open
XTCE12-63 No short description or long description at the Member element of AggregateParameterType or AggregateArgumentType XTCE 1.1 open
XTCE12-9 MetaCommandSet is incorrectly set to required XTCE 1.1 open
XTCE12-35 Change all elements to top level schema types XTCE 1.1 open
XTCE12-162 MS-003 Meaning not clear. XTCE 1.0 open
XTCE12-188 HVM-004 Data Encoding definitions XTCE 1.0 open
XTCE12-158 Should use type[FixedFrameSyncStrategyType] in type [FixedFrameStreamType] XTCE 1.0 open
XTCE12-160 V-003 Schema file identification XTCE 1.0 open
XTCE12-161 DC-013 Parameter encoding information XTCE 1.0 open
XTCE12-159 MS-001 Missing page numbering XTCE 1.0 open
XTCE12-155 MM-001 What missions need XTCE 1.0 open
XTCE12-156 MP-001 Terminology XTCE 1.0 open
XTCE12-154 TH-001 Some Typos XTCE 1.0 open
XTCE12-157 MK-005 Should use type[ContextCalibratorType] in … XTCE 1.0 open
XTCE12-150 OnBoard Software XTCE 1.0 open
XTCE12-152 CalibratorType XTCE 1.0 open
XTCE12-151 Section: 7 XTCE 1.0 open
XTCE12-153 MK-002 Type of element[MessageRef] is undefined XTCE 1.0 open
XTCE12-146 6 - Add ToString to Boolean or remove Boolean in favor of Enumerated Types XTCE 1.0 open
XTCE12-145 - Add separate CalibratorSet to XTCE XTCE 1.0 open
XTCE12-147 1 - Support ability to describe redundant or complimentary data XTCE 1.0 open
XTCE12-148 OnBoard Memory XTCE 1.0 open
XTCE12-149 CommandContainerType XTCE 1.0 open
XTCE12-141 8 - Add activity field to Alarms to indicate what the alarm will trigger XTCE 1.0 open
XTCE12-144 5 - Align XTCE and CCSDS Navigation Schemas (types) XTCE 1.0 open
XTCE12-143 4 - Separate XTCE Schema into constituent parts XTCE 1.0 open
XTCE12-142 3 - Use UML Instance diagrams for XTCE document example XTCE 1.0 open
XTCE12-137 Some sections/pages refer to the old (1.0) xsd version XTCE 1.1 open
XTCE12-138 9 - Add filtering of value threshold to maintain telemetry at certain rates XTCE 1.0 open
XTCE12-140 7 - Use UUIDs instead of current XTCE Referencing mechanism XTCE 1.0 open
XTCE12-173 DC-027 Line 3 XTCE 1.0 open
XTCE12-174 DC-032 Line 3 XTCE 1.0 open
XTCE12-178 DC-034 Line 10 XTCE 1.0 open
XTCE12-175 DC-018 Line 10 XTCE 1.0 open
XTCE12-177 DC-029 Line 1 XTCE 1.0 open
XTCE12-180 DC-011 Figure text. XTCE 1.0 open
XTCE12-182 DC-005 Figure XTCE 1.0 open
XTCE12-184 DC-025 Encoding information XTCE 1.0 open
XTCE12-183 DC-026 Encoding area XTCE 1.0 open
XTCE12-190 DC-017 Assembly / dissembly information. XTCE 1.0 open
XTCE12-191 DC-028 ArgumentList XTCE 1.0 open
XTCE12-195 "Parameter Processing" box XTCE 1.0 open
XTCE12-198 "Foreword", line 2. XTCE 1.0 open
XTCE12-166 DC-033 Line 6 XTCE 1.0 open
XTCE12-168 DC-024 Line 6 XTCE 1.0 open
XTCE12-167 DC-030 Line 5 XTCE 1.0 open
XTCE12-169 DC-016 Line 4. XTCE 1.0 open
XTCE12-171 DC-020 Line 4 XTCE 1.0 open
XTCE12-170 DC-008 Line 4 XTCE 1.0 open
XTCE12-176 DC-010 Line 1 XTCE 1.0 open
XTCE12-186 DC-021 Assembly / dissembly of streams XTCE 1.0 open
XTCE12-200 DC-004 "Philosophy", line 2 XTCE 1.0 open
XTCE12-164 DC-012 Line 5 XTCE 1.0 open
XTCE12-181 DC-015 Figure label. XTCE 1.0 open
XTCE12-163 MP-004 Logarithmic calibrations XTCE 1.0 open
XTCE12-179 MS-006 Footing of Figure 1 is missing. XTCE 1.0 open
XTCE12-185 MP-007 Dynamic telemetry check types XTCE 1.0 open
XTCE12-189 MS-009 De-calibration of cmd parameters? XTCE 1.0 open
XTCE12-172 DC-023 Line 3. XTCE 1.0 open
XTCE12-165 DC-009 Line 6 XTCE 1.0 open
XTCE12-187 MK-007 Don't need element[ChangePerSecondAlarmConditions] XTCE 1.0 open
XTCE12-192 MK-010 All ParameterType and ArgumentType should have alarm element XTCE 1.0 open
XTCE12-208 lack of Union construct (MER + ASIST) XTCE 1.0b1 open
XTCE12-209 XTCE issue: dimensionList in arrayParameterRef should be optional XTCE 1.0b1 open
XTCE12-210 inability to describe sets of limits (alarms) and conversions (polynomials) XTCE 1.0b1 open
XTCE12-211 repeat of arguments issue XTCE 1.0b1 open
XTCE12-212 XTCE issue - add shortDescription to EntryList entries XTCE 1.0b1 open
XTCE12-193 AO-006 Additional examples (2) XTCE 1.0 open
XTCE12-194 MK-003 A mistake of type[ContainerSegmentRefEntryType]'s annotation XTCE 1.0 open
XTCE12-199 MK-001 A mistake of attribute[messageRef]'s annotation XTCE 1.0 open
XTCE12-196 "Foreword", 2nd last line XTCE 1.0 open
XTCE12-197 Contents" XTCE 1.0 open
XTCE12-202 "Command Processing" box XTCE 1.0 open
XTCE12-201 Spec too complex? XTCE 1.0 open
XTCE12-203 USE CCSDS examples how to use the standard XTCE 1.0 open
XTCE12-206 too much leeway how to use the standard XTCE 1.0 open
XTCE12-204 Propose that XCTE ( at this point ) will be limited to exchange data XTCE 1.0 open
XTCE12-205 Xpath: XTCE 1.0b1 open
XTCE12-207 command side unable to describe "packed commands" XTCE 1.0b1 open

Issues Descriptions

AbsoluteTimeParameterType Epoch is not always at midnight

  • Key: XTCE12-448
  • Status: open  
  • Source: Boeing ( David Overeem)
  • Summary:

    The Epoch element in the time types does not allow an XTCE user to specify an Epoch date that is not anchored at midnight. At present it is a union of xs:date and xs:string with a restriction on 1 value, which is TAI.

  • Reported: XTCE 1.1 — Thu, 25 May 2017 13:23 GMT
  • Updated: Sat, 17 Jun 2017 00:10 GMT

LongDescriptionType as a complexType is unnecessary

  • Key: XTCE12-454
  • Status: open  
  • Source: Boeing ( David Overeem)
  • Summary:

    In the schema refactoring for 1.2, the LongDescription element content got converted to a complexType containing just a string. This should be a simpleType.

  • Reported: XTCE 1.1 — Thu, 1 Jun 2017 17:51 GMT
  • Updated: Sat, 17 Jun 2017 00:10 GMT

MetaCommandStep argument assignment

  • Key: XTCE12-397
  • Status: open  
  • Source: Northrop Grumman ( Joseph Vlietstra)
  • Summary:

    MetaCommandStep argument values are assigned using <ArgumentList> / <Argument> elements. Using these elements creates two issues in the XTCE model:

    1. Two different element definitions for <ArgumentList> / <Argument>
      1. <MetaCommandStep> / <ArgumentList> / <Argument>
      2. <MetaCommand> / <ArgumentList> / <Argument>
    2. Two XML implementations of the ArgumentAssignment concept:
      1. <MetaCommandStep> / <ArgumentList> / <Argument>
      2. <BaseMetaCommand> / <ArgumentAssignmentList> / <ArgumentAssignment>

    Recommend replacing the argument assignment elements in <MetaCommandStep> with the elements used for <BaseMetaCommand>.
    This would provide a more unified and descriptive definition.

  • Reported: XTCE 1.1 — Tue, 6 Dec 2016 18:00 GMT
  • Updated: Sun, 11 Jun 2017 00:19 GMT

InputOutputTriggerAlgorithmType@triggerContainer is a NameType, should it be a NameReference?

  • Key: XTCE12-95
  • Legacy Issue Number: 14494
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    InputOutputTriggerAlgorithmType@triggerContainer is a NameType, should it be a NameReference?

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sun, 11 Jun 2017 00:19 GMT

InputOutputAlgorithm@thread optional boolean, should have default of false

  • Key: XTCE12-93
  • Legacy Issue Number: 14495
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    InputOutputAlgorithm@thread optional boolean, should have default of false

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sun, 11 Jun 2017 00:19 GMT

MathOperator needs to be cleaned up

  • Key: XTCE12-124
  • Legacy Issue Number: 14467
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:38:51 BST
    MathOperators "^" should either be removed or expanded to include all bitwise
    operators, add or remove operators in math operators.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sun, 11 Jun 2017 00:19 GMT

IndirectParameterEntry should have segment varient?

  • Key: XTCE12-80
  • Legacy Issue Number: 14511
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2008-05-29 19:08:30 BST
    Should IndirectParameterEntry have a segment option?

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sun, 11 Jun 2017 00:19 GMT

CustomAlgorithm should be "typed" reference to AlgorithmSet

  • Key: XTCE12-85
  • Legacy Issue Number: 14505
  • Status: open  
  • Source: NASA ( 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: Sun, 11 Jun 2017 00:19 GMT

Should RestrictionCriteria should be assignment not operators for Commanding?

  • Key: XTCE12-82
  • Legacy Issue Number: 14506
  • Status: open  
  • Source: NASA ( 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: Sun, 11 Jun 2017 00:19 GMT

The XTCE element MetaCommand has a child element called VerifierSet

  • Key: XTCE12-61
  • Legacy Issue Number: 17421
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    The XTCE element MetaCommand has a child element called VerifierSet. Each of the Verifiers in the set are derived by schema-type extension except for the FailedVerifier. This produces an inconsistency when using a tool like JAXB which maps the schema types to classes

  • Reported: XTCE 1.1 — Mon, 11 Jun 2012 04:00 GMT
  • Updated: Sun, 11 Jun 2017 00:19 GMT

Elevate annotation specifying time string formats to an attributes

  • Key: XTCE12-47
  • Legacy Issue Number: 19376
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    The annotation below would be better served as an optional attribute with the specified format as the default. From a telemetry stantpd this would be interpreted as optional display info, and from an argument standpt the user input string format. "Used to contain an absolute time. Contains an absolute (to a known epoch) time. Use the [ISO 8601] extended format CCYY-MM-DDThh:mm:ss where "CC" represents the century, "YY" the year, "MM" the month and "DD" the day, preceded by an optional leading "-" sign to indicate a negative number. If the sign is omitted, "+" is assumed. The letter "T" is the date/time separator and "hh", "mm", "ss" represent hour, minute and second respectively. Additional digits can be used to increase the precision of fractional seconds if desired i.e. the format ss.ss... with any number of digits after the decimal point is supported. "

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Sun, 11 Jun 2017 00:19 GMT

Adding structure to Parameters

  • Key: XTCE12-67
  • Legacy Issue Number: 16721
  • Status: open  
  • Source: Harris ( Christopher Zonca)
  • Summary:

    Currently, it's possible to group ParameterTypes together through the AggregateParameterType. We would like to be able to add similar structure to individually declared Parameters. In other words, we would like a way to group Parameters together in a potentially nested, structured format.

  • Reported: XTCE 1.1 — Tue, 22 Nov 2011 05:00 GMT
  • Updated: Sun, 11 Jun 2017 00:19 GMT

Fix annotation issues throughout schema

  • Key: XTCE12-27
  • Legacy Issue Number: 19398
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Address all annotation issues. Kratos/ISI.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Sun, 11 Jun 2017 00:19 GMT

ValidRange element duplicated with ValidRangeSet in ArgumentTypeSet

  • Key: XTCE12-456
  • Status: open  
  • Source: Boeing ( David Overeem)
  • Summary:

    There appears to be a duplication mistake in the CommandMetaData ArgumentTypeSet. Two of the Argument Types (Integer and Float) have both a ValidRange element and a ValidRangeSet/ValidRange element.

    It is probably not necessary to have both. The single ValidRange should be fine. To define multiple ValidRanges introduces an opportunity for mismatch. If uncalibrated and calibrated ValidRange values exist, they should be converted to one or the other.

  • Reported: XTCE 1.1 — Sat, 3 Jun 2017 17:27 GMT
  • Updated: Sat, 3 Jun 2017 17:27 GMT

Error in unique keys fix in XTCE12-346

  • Key: XTCE12-439
  • Status: open  
  • Source: Boeing ( David Overeem)
  • Summary:

    The revision task force made an error in the resolution of issue XTCE12-15 recorded in subtask XTCE12-346. This error calls out a unique key for the element xtce:CommandMetaData/xtce:ContainerSet attribute @name. This should be xtce:CommandContainerSet.

  • Reported: XTCE 1.1 — Sun, 16 Apr 2017 16:04 GMT
  • Updated: Fri, 2 Jun 2017 00:01 GMT

Alternate approach to xs:positiveInteger and xs:nonNegativeInteger

  • Key: XTCE12-431
  • Status: open  
  • Source: Boeing ( David Overeem)
  • Summary:

    The XTCE Schema uses two XSD types that cause issues for code generators. The xs:positiveInteger and xs:nonNegativeInter end up with things like the "BigInteger" class in the generated code mapping, although the ranging capability is lost. This is not convenient for implementations.

  • Reported: XTCE 1.1 — Thu, 23 Mar 2017 17:20 GMT
  • Updated: Fri, 2 Jun 2017 00:01 GMT

Mistake in previous resolution for addition of XInclude support

  • Key: XTCE12-441
  • Status: open  
  • Source: Boeing ( David Overeem)
  • Summary:

    An issue was created as XTCE12-10 regarding the lack of support for the XML Xinclude facility. A proposal passed under XTCE12-308 to add the import and and nillable attribute. This resolution missed the attribute definition needed to enable the location of the XInclude support.

  • Reported: XTCE 1.1 — Sat, 29 Apr 2017 14:33 GMT
  • Updated: Fri, 2 Jun 2017 00:01 GMT

The ToString element used in Integer and Float types overlaps with Enumerated types

  • Key: XTCE12-381
  • Status: open  
  • Source: Boeing ( David Overeem)
  • Summary:

    Inside of the ToString element, there are possibilities for making number to string mappings that confuse with the Enumerated Parameter/Argument types. These should be removed and the ToString element simplified to satisfy a tighter purpose.

  • Reported: XTCE 1.1 — Sat, 15 Oct 2016 16:16 GMT
  • Updated: Fri, 2 Jun 2017 00:01 GMT

Autogenerator issue with schema type derivation

  • Key: XTCE12-113
  • Legacy Issue Number: 14475
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:51:07 BST
    XMLSpy autogenerator issue, may be true for others. In some cases elements are
    not themselves extensions creating a schema type but are complex types. In
    those cases the class name does not end up matching the element but the
    included type. This is particularly noticeable in several parameterTypes –
    array, aggregate and absoluteTime, and in ALL the argumentTypes. It would be
    better from a code mapping standpt to address this in the schema – yes, just
    so the autogenerator "looks right".

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 2 Jun 2017 00:01 GMT

element ParameterInstanceRefOperand in the MathOperationType

  • Key: XTCE12-60
  • Legacy Issue Number: 17422
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    element ParameterInstanceRefOperand in the MathOperationType has the flag but the "this" parameter doesn't say what the intent is in annotation or give the option of specifying whether it would be the raw or cooked (engineering converted) value.

    So the XTCE 1.2 annotation could say "Use the calibrated value of this parameter in the calculation. If the raw value for this parameter is desired, use the ParameterInstanceRefOperand to spell it out."

    Which I think covers it... although it would be nice to have the attribute.

  • Reported: XTCE 1.1 — Mon, 11 Jun 2012 04:00 GMT
  • Updated: Fri, 2 Jun 2017 00:01 GMT

Use of raw value for calibrator context selection

  • Key: XTCE12-395
  • Status: open  
  • Source: Northrop Grumman ( Joseph Vlietstra)
  • Summary:

    Should be able to select between calibrators by referencing raw value.

    Current ContextCalibrator mechanism doesn't really solve the problem. Access to raw value requires a parameter instance ref with useCalibratedValue=false. Implementing this approach requires a separate parameter type for each parameter that switches based on raw value. It also creates a somewhat circular relationship in the sense that the behavior of the parameter type (calibrator) depends on the parameter instance.

  • Reported: XTCE 1.1 — Mon, 5 Dec 2016 22:37 GMT
  • Updated: Fri, 2 Jun 2017 00:01 GMT

StringDataType UTF-8/CharacterWidth Issue

  • Key: XTCE12-110
  • Legacy Issue Number: 14478
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:56:02 BST
    UTF-8 and UTF-16 are actually multi-byte formats. The character width field
    just says "8" or "16" somewhat implying bit width per character which doesn't
    really match UTF-8/16. We should match them up.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 2 Jun 2017 00:01 GMT

Generalize array type, add attribute for ROW or COL order

  • Key: XTCE12-107
  • Legacy Issue Number: 14481
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 22:00:56 BST
    ROW major order seems to be the poorly described default in XTCE, COL major is
    a less popular but unheard ordering of array cells in memory. These are well
    documented and understood constructs and conversion between them should be easy
    for any implementer. By providing an attribute to select the ordering we'll
    support everything but custom orderings. Wikipedia has an excellent entry on
    the topic.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 2 Jun 2017 00:01 GMT

Unify metacommand/commandContainer and commandContainerSet/commandcontainer schema types

  • Key: XTCE12-111
  • Legacy Issue Number: 14474
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:49:52 BST
    These are implemented slightly differently in the schema and this has
    implications for the programmer & API. It would be easier from the programmer
    standpt if they were same underlying schema types.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 2 Jun 2017 00:01 GMT

Explain interaction of dynamic value and segments, array lastEntryForThisArray

  • Key: XTCE12-106
  • Legacy Issue Number: 14482
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 22:01:57 BST
    It's not really documented how a parameter whose size is determined dynamically
    should react with segment entries which are fixed. Should the user be warned
    when they don't match? In addition arrays can be split across its dimensions
    by using the attribute lastEntryForThisArray, how does this interact with
    segments or in combination with dynamic values in parameter lengths? An array
    in a container, referenced as a containerSegment should be considered as well.
    This needs to documented.
    Comment 1 Kevin Rice 2008-05-21 22:46:12 BST
    If you have a parameterRefEntry of dynamic length and parameterSegment next of
    a fixed lenght – BUT you really need to adjust the segment based on the
    dynamic lenght. This seems either impossible or difficult to do in XTCE at
    this time.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 2 Jun 2017 00:01 GMT

Derive ArgumentTypes by extension

  • Key: XTCE12-92
  • Legacy Issue Number: 14498
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2008-03-20 19:14:51 GMT
    *ArgumentType – should be derived by extension from each *DataType (with no
    additional extending info), autogenerators will then generate classes whose
    class-names match the *ArgumentType names, instead of using the *DataType
    names.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 2 Jun 2017 00:01 GMT

FloatEncoding float formats -- MIL1750a, IEEE, bit size issues

  • Key: XTCE12-87
  • Legacy Issue Number: 14503
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2008-05-01 21:22:02 BST
    XTCE allows one to select in an attribute eithe MIL-1750A or IEEE-754 formats
    and the bitsizes 32, 64, or 128.

    This leaves out bitsize 48 for MIL-1750a – a bug.

    It also allows for combinations which are likely not legal: MIL 64, or MIL
    128.

    DEC floating point encoding must also be accounted for.

    MILSTD-1750A 16 bit integer should probably have a comment that it is not float, rather it is just signMagnitude integer encoding.

    Finally it misses IEEE extended double of 80 bits ...

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 2 Jun 2017 00:01 GMT

FixedValueEntry@sizeInBits should be required

  • Key: XTCE12-88
  • Legacy Issue Number: 14500
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    FixedValueEntry@sizeInBits should be required

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 2 Jun 2017 00:01 GMT

Align ArgumentType and ParameterType construction

  • Key: XTCE12-114
  • Legacy Issue Number: 14476
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:52:34 BST
    In the schema, the parameter/arguments do not share a common root class until
    NameDescriptionType. All the types except for Time/Array & aggregate are
    BaseDataTypes. The Time types are BaseTimeDataTypes and array/aggregate just
    have nameDescription as the root. It would be better if they shared a common
    "lower down" class/type that would be more indicative of what these really are
    instead in nameDescription which is shared by many schema types in XTCE. It
    effects the code – instead having say List<CommonBaseDataType> in Java. One
    gets List<NameDescriptionType> – which works but isn't as type safe - it's too
    generic.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 2 Jun 2017 00:01 GMT

inside/outside alarms not supported

  • Key: XTCE12-72
  • Legacy Issue Number: 14513
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2008-05-30 19:32:10 BST
    most organization use some outside alarms, not available now

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 2 Jun 2017 00:01 GMT

Member of an AggregateParameterType or AggregateArgumentType can't be an ArrayParameterType or ArrayArgumentType

  • Key: XTCE12-66
  • Legacy Issue Number: 17418
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    3) A Member of an AggregateParameterType or AggregateArgumentType cannot be an ArrayParameterType or ArrayArgumentType

    Possible answers:

    3) This one typically comes up when source material has adopted the C syntax for specifying strings as char arrays and its being used in a 'struct'. In XTCE do not map char arrays that are strings to an 8-bit StringParameterType and then an ArrayParameterType that refers to it. Instead calculate the length from the char array and make a StringParameterType that long to hold it and refer to that in the Member element. To date even though this works (largely), it does not produce a happy face for the folks that have the original syntax. The alternative is a complete re-working of XTCE's array description

  • Reported: XTCE 1.1 — Mon, 11 Jun 2012 04:00 GMT
  • Updated: Fri, 2 Jun 2017 00:01 GMT

AlgorithmSet missing algorithms

  • Key: XTCE12-84
  • Legacy Issue Number: 14504
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2008-05-28 21:33:03 BST
    Various XTCE schema types for algorithms are not reflected in AlgorithmSet:
    SimpleAlgorith, InputAlgorithm and InputOutputAlgorithm

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 2 Jun 2017 00:01 GMT

At the Parameter element, initial values for Array or Aggregates may not be set.

  • Key: XTCE12-62
  • Legacy Issue Number: 17419
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    At the Parameter element, initial values for Array or Aggregates may not be set. (It actually says this in the annotation.)

    Possible answers:

    4) Since Parameter's @initialValue is a string, I don't see why comma delimited and {} initializers can't be used similar to C, C++, Java, etc... these things should be pretty easy to parse. Of course some extra checking will be needed to make sure the list of items fits into the data type and perhaps there's some sticky cases to be considered which would all need to written up and documented which is probably why the annotation says its not supported in the first place.

  • Reported: XTCE 1.1 — Mon, 11 Jun 2012 04:00 GMT
  • Updated: Fri, 2 Jun 2017 00:01 GMT

Move array sizing to Parameter and Argument from container area

  • Key: XTCE12-133
  • Legacy Issue Number: 14455
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:05:42 BST
    Change where Array sizes are set from Container area to Parameter or Argument
    area. It may make more sense to put the array sizing in the parameter or
    argument area instead of in container where it is now. Currently in XTCE their
    size is set in the Container.
    C-S/CNES
    Ludovic Faure

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 2 Jun 2017 00:01 GMT

Repeat arguments

  • Key: XTCE12-22
  • Legacy Issue Number: 19404
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Repeat arguments group all other arguments (except more repeats) in a specified range - the range may allow the item to be optional, repeated a fixed number of time or repeated within the range. It's challenging to see how this is supported within current XTCE syntax. The suggestion is to add a repeat argument to the argument list in XTCE. Reported by JPL.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Fri, 2 Jun 2017 00:01 GMT

Expand features to include common industry encodings in StreamsSet

  • Key: XTCE12-38
  • Legacy Issue Number: 19386
  • Status: open  
  • Source: NASA ( 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: Fri, 2 Jun 2017 00:01 GMT

Fill argument

  • Key: XTCE12-23
  • Legacy Issue Number: 19403
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Fill arguments have a name and optional value, they are supplied by the system however. The closest match in XTCE is fixed value entry. However there's no way to associate a name with it or enforce the order in relation to other arguments, and if the container is not being specified this approach will not work either. Reported by JPL.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Fri, 2 Jun 2017 00:01 GMT

Variable length strings need optional maximum length designator

  • Key: XTCE12-20
  • Legacy Issue Number: 19407
  • Status: open  
  • Source: NASA ( James Rice)
  • Summary:

    way to specify the maximum length for variable length strings is missing. A related issue is for pascal-style strings is the bit/byte order of the preceding length is missing. (that makes this another issue but I am tired of adding issues to this thing!) Note: this is actually an old issue which somehow never made it into the issues list here that I can fine. I believe the original issue was relayed to me by EADS 5+ yrs ago. I thought they intended to put it in.

  • Reported: XTCE 1.1 — Mon, 5 May 2014 04:00 GMT
  • Updated: Fri, 2 Jun 2017 00:01 GMT

Cleanup Container EntryList element by deprecating IndirectParameterRefEntry

  • Key: XTCE12-449
  • Status: open  
  • Source: Boeing ( 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, 1 Jun 2017 14:32 GMT

AlarmType produces problem in JaxB

  • Key: XTCE12-119
  • Legacy Issue Number: 14465
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:36:19 BST
    AlarmType is abstract in the XTCE schema and this presents problems for some
    code generators such as JAXB. AlarmType is set to abstract and the code
    generated by JAXB means the class cannot be directly instantiated. This would
    present problems for some Alarms for certain parameter types that are of type
    AlarmType directly. There may be several ways to fix this in the schema and
    those should be analyzed.
    CNES
    Ludovic Faure

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Wed, 24 May 2017 23:38 GMT

Need support for mask alarm

  • Key: XTCE12-54
  • Legacy Issue Number: 19371
  • Status: open  
  • Source: NASA ( 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: Sat, 29 Apr 2017 17:59 GMT

Off Alarms

  • Key: XTCE12-50
  • Legacy Issue Number: 19375
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    An off alarm disables a previously defined alarm. It will turn off ALL previously defined alarms at a certain level
    (RED or YELLOW) associated with the specified telemetry parameter. If the alarms themselves can be addressed, it can be configured to turn off individual alarms. Reported by JPL.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Sat, 29 Apr 2017 17:59 GMT

Re-architect XTCE alarm model

  • Key: XTCE12-55
  • Legacy Issue Number: 19369
  • Status: open  
  • Source: NASA ( 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: Sat, 29 Apr 2017 17:59 GMT

Combination Alarm

  • Key: XTCE12-53
  • Legacy Issue Number: 19374
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    A combination alarm allows conditions to be checked on multiple telemetry channels, and the resulting alarm conditions set on multiple telemetry channels. The source channels (which trigger the alarm) and the target channels (which show the alarm) do not have to be the same. One alarm level applies to all of the source alarms included in the combination set. Reported by JPL.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Sat, 29 Apr 2017 17:50 GMT

Only single instance of Alarm Condition/Range

  • Key: XTCE12-34
  • Legacy Issue Number: 19393
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Add a new alarm type (we know what this means). Kratos/ISI.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Sat, 29 Apr 2017 17:41 GMT

Add normal alarm condition or alarm ranges

  • Key: XTCE12-29
  • Legacy Issue Number: 19392
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Add a new alarm type to capture sequential ranges to permit a "barber pole" like definition. Reported by Kratos/ISI.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Sat, 29 Apr 2017 17:41 GMT

ChangeAlarmRates confusing and ambiguous

  • Key: XTCE12-76
  • Legacy Issue Number: 14512
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2008-05-29 19:09:28 BST
    ChangeAlarmRates is confusing and ambigous due the fact the attribute setting
    of which there are four are all optional but only certain combinations are
    valid. Valid combos are: Change Per Sample, absolute change, whereas Change
    Per Second may be absolute change or percentage change. Also absolute change
    implies absolute value yet ranges allows for assymetric specification of +/-

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sat, 29 Apr 2017 17:39 GMT

toString/NumberFormat needs default settings

  • Key: XTCE12-91
  • Legacy Issue Number: 14496
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2008-03-20 19:13:40 GMT
    toString/NumberFormat - element is required if toString is in use. Almost all
    attributes are optional but defaults should be

    provided for "most common" likely format...

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sat, 29 Apr 2017 00:10 GMT

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

  • Key: XTCE12-41
  • Legacy Issue Number: 19381
  • Status: open  
  • Source: NASA ( 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, 18 Apr 2017 14:50 GMT

Improve CRCType Polynomial element

  • Key: XTCE12-12
  • Legacy Issue Number: 19436
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    The annotation states that the coefficients of the CRC poly can only be 1 or 0, and the exponent can only be integers. However the schema types for these two attribute are double. Enforcing the annotation through changes to the syntax of its polynomial would be easy to accomplish. A new type for CRC polynomials would need to be created, and the attribute types changes to match the desired behavior.

  • Reported: XTCE 1.1 — Wed, 28 May 2014 04:00 GMT
  • Updated: Sun, 16 Apr 2017 00:19 GMT

ErroCorrectDetect -- Parity

  • Key: XTCE12-75
  • Legacy Issue Number: 14515
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2009-03-18 22:16:51 GMT
    Doesn't really have enough info to identify parity bit location, and various
    other aspects to completely describe it.

    CRC may be problematic as well

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sun, 16 Apr 2017 00:19 GMT

ByteOrderList in XTCE 1.1 needs to be improved

  • Key: XTCE12-400
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    ByteOrderList is an element that describes the byte order of encoded packet info – mnemonics. Each mnemonic may have a different byte order. ByteOrderList is currently optional. The problems with it are:
    1) Not specifying it means the item is most significant byte first. But many adopters of XTCE fail to realize this initially at least producing many bad XTCE files.
    2) When specifying it, each "significance" is given a numerical value. The exact mechanism or meaning of this is not explained in the annotation. Results are a lack of commonality by XTCE file authors.
    3) There are 2 popular byte orders which cover many cases: "big" and "little" endian (or most/least significant byte first). Explicitly specifying these produces a lot of XML but a clearer XTCE file.
    Suggested fix: make the item required or provide an explicit default setting. This possibly means moving it to an attribute. Make the defaults the common settings, provide a bail out for the less common byte orders. Improve the annotation.

  • Reported: XTCE 1.1 — Fri, 16 Dec 2016 19:10 GMT
  • Updated: Sun, 16 Apr 2017 00:19 GMT

Alarm count to enter alarm (minViolations), needs corresponding count to leave the alarm state

  • Key: XTCE12-59
  • Legacy Issue Number: 19368
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    In the current schema minViolation gives the count to go into alarm... But there is not attribute for leaving alarm. Note JPL is the original reporter.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Sun, 16 Apr 2017 00:19 GMT

Remove whitespace in selector xpath attribute

  • Key: XTCE12-15
  • Legacy Issue Number: 19437
  • Status: open  
  • Source: Northrop Grumman ( Joseph Vlietstra)
  • Summary:

    XTCE schema contains several <key> elements to ensure unique "name" attributes across various namespaces. Namespaces searched are specified by the "xpath" attribute in the <selector> element.

    Several XTCE xpath attributes contain spaces to improve readability of the xpath expression. Although whitespace is allowed by paragraph 3.7 of the xpath specification, there is a bit of ambiguity since it's not in the formal BNF grammar. This means some schema processors (e.g., Eclipse modeling framework) may reject the xpath expression.

    Recommend removing the space around the union (|) operator in the xpath expressions.

  • Reported: XTCE 1.1 — Wed, 28 May 2014 04:00 GMT
  • Updated: Sun, 16 Apr 2017 00:19 GMT

In EnumerationAlarm, enumerationValue should called enumerationLabel

  • Key: XTCE12-71
  • Legacy Issue Number: 14518
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2009-09-10 23:02:26 BST
    Although the data type is a string and it will accept labels, because it has
    the term "value" in the name, causes confusion.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sun, 16 Apr 2017 00:19 GMT

remove extraneous keys or uniq

  • Key: XTCE12-74
  • Legacy Issue Number: 14514
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2008-05-30 19:35:01 BST
    at least on old key is in the schema at the container area, remove any old ones

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sun, 16 Apr 2017 00:19 GMT

Expand telemetry parameter data source attribute

  • Key: XTCE12-49
  • Legacy Issue Number: 19378
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    The XTCE options:
    telemetered, derived, constant, local

    The JPL options:
    flight, derived, bit_extract, simulation

    The suggestion is expand the list in XTCE to include "Segmented" or something of that nature to match the ParameterSegmentRefEntry.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Sun, 16 Apr 2017 00:19 GMT

Digital Alarms

  • Key: XTCE12-52
  • Legacy Issue Number: 19372
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Digital alarms are a mask (typically 16 bits) that have value and don't care bits. For example a mask might be defined as:

    X11X 10X0 0111 X111

    The X positions are don't care, but the 0,1 are values which if they appear in telemetry of interest put it into alarm.

    It isn't clear that this representable in XTCE.

    Original report is JPL.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Sun, 16 Apr 2017 00:19 GMT

Change alarm

  • Key: XTCE12-51
  • Legacy Issue Number: 19373
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Change alarm define any change in value from a numeric, enum or string as in alarm. Float usage is often discouraged. XTCE has no specific syntax to support this. Reported by JPL.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Sun, 16 Apr 2017 00:19 GMT

Add raw units to ParameterType

  • Key: XTCE12-45
  • Legacy Issue Number: 19379
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    A specific syntactic element to capture raw units if it needed, possibly in addition to engineering units is not provided. There is a unit set in XTCE but was not intended to be used in this manner. Reported by JPL.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Sun, 16 Apr 2017 00:19 GMT

Add ArgumentTypeSet to MetaCommand

  • Key: XTCE12-48
  • Legacy Issue Number: 19377
  • Status: open  
  • Source: NASA ( 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: Sun, 16 Apr 2017 00:19 GMT

Database of single SpaceSystem cannot designate a parameter to be within multiple systems

  • Key: XTCE12-31
  • Legacy Issue Number: 19395
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Database of single SpaceSystem cannot designate a parameter to be within multiple systems. Add some way to categorize elements with @name.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Sun, 16 Apr 2017 00:19 GMT

Add additional math operators to mathoperations

  • Key: XTCE12-32
  • Legacy Issue Number: 19394
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Add additional operators to the math operations element. Kratos/ISI.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Sun, 16 Apr 2017 00:19 GMT

Error detection algorithm does not support XOR

  • Key: XTCE12-28
  • Legacy Issue Number: 19397
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Add XOR support in error detection algorithm. Kratos/ISI.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Sun, 16 Apr 2017 00:19 GMT

Add to or change way crc is specified

  • Key: XTCE12-24
  • Legacy Issue Number: 19400
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Add to or change the way the crc is specified in the schema. Kratos/ISI

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Sun, 16 Apr 2017 00:19 GMT

Provide specific type consequence level

  • Key: XTCE12-421
  • Status: open  
  • Source: Northrop Grumman ( Joseph Vlietstra)
  • Summary:

    XTCE v1.1 provided an anonymous type for the consequence level of a command. In proposed v1.2, consequence level type and AlarmLevels are merged into ConcernLevelsType. Besides being backwards-incompatible, this merges two different concepts.

  • Reported: XTCE 1.1 — Thu, 26 Jan 2017 18:13 GMT
  • Updated: Thu, 6 Apr 2017 00:55 GMT

XTCE12-11 fix for name references did not work correctly

  • Key: XTCE12-434
  • Status: open  
  • Source: Boeing ( David Overeem)
  • Summary:

    The resolution for XTCE12-11 turned out to have an error. The Comments section outlines the error in that issue.

  • Reported: XTCE 1.1 — Thu, 23 Mar 2017 17:59 GMT
  • Updated: Thu, 6 Apr 2017 00:55 GMT

*Container@abstract should have default of false

  • Key: XTCE12-96
  • Legacy Issue Number: 14491
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2008-03-20 19:05:29 GMT
    metaCommand@abstract has a default value of false, but *container@abstract does
    not.

    It should.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Thu, 6 Apr 2017 00:55 GMT

Member location within AggregateDataType

  • Key: XTCE12-416
  • Status: open  
  • Source: Northrop Grumman ( Joseph Vlietstra)
  • Summary:

    AggregateDataType assumes each member immediately follows the previous member in the telemetry stream (no gaps). If there are unused bits in the stream, a dummy parameter must defined to account for the unused bits.

  • Reported: XTCE 1.0 — Tue, 10 Jan 2017 21:45 GMT
  • Updated: Thu, 6 Apr 2017 00:55 GMT

Need a ParameterProperty for "observability" or "change only threshold"

  • Key: XTCE12-68
  • Legacy Issue Number: 16722
  • Status: open  
  • Source: Boeing ( David Overeem)
  • Summary:

    It does not appear possible for the satellite factory to pass a minimum "observability" for parameters using XTCE. It is possible I am mistaken here and a clarification would be sufficient. This type of property is used when determining if a parameter has changed and damps out potential jitter in the measurements.

  • Reported: XTCE 1.1 — Wed, 23 Nov 2011 05:00 GMT
  • Updated: Thu, 6 Apr 2017 00:55 GMT

Time/Encoding@scale,@offset terminology vs DynamicValue/LinearAdjust

  • Key: XTCE12-86
  • Legacy Issue Number: 14502
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2008-05-01 21:19:28 BST
    These two items use a y=mx+b style adjuster to change the value given. The
    terminology should be aligned.

    One implements it using attributes the other a seperate element, possible these
    should be aligned as well.

    FINALLY the default SLOPE (i.e. 'm') is 0 in one which is wrong – adding an
    empty LinearAdjust will result in a ZERO-ing of the retrieve dynamic value – a
    mistake.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Thu, 6 Apr 2017 00:55 GMT

Bit extract feature needed in telemetry parameter

  • Key: XTCE12-58
  • Legacy Issue Number: 19367
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Specific syntax associating bits from one or more parent parameters to create a new parameter in the Parameter element is needed. Currently XTCE supports this concept at the container (ParameterSegmentEntryRef) level, and in theory by using an algorithm. However containers associated with some parameters may not always be defined in XTCE, and algorithmic descriptions are difficult to exchange. Note original reporter is JPL.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Thu, 6 Apr 2017 00:55 GMT

Add ranges to enumeration list

  • Key: XTCE12-33
  • Legacy Issue Number: 19391
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Add option to map a range of value to a label, instead of just one value as is current in XTCE. Reported by Kratos/ISI.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Thu, 6 Apr 2017 00:55 GMT

Enum Alarm List should be optional

  • Key: XTCE12-56
  • Legacy Issue Number: 19370
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    The enum alarm list is required in the syntax. But other alarms types are available for enums, and it is possible that one may require one of them but not have need to define an explicit enum alarm list. The syntax prevents this from occurring. Perhaps the enum list element should be optional.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Thu, 6 Apr 2017 00:55 GMT

Add xinclude to support ximport

  • Key: XTCE12-10
  • Legacy Issue Number: 19632
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    To support xinclude, the following should added to the root schema element: <import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/03/xml.xsd"/>

  • Reported: XTCE 1.1 — Mon, 6 Oct 2014 04:00 GMT
  • Updated: Fri, 31 Mar 2017 16:05 GMT

Add event message support

  • Key: XTCE12-39
  • Legacy Issue Number: 19388
  • Status: open  
  • Source: NASA ( 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: Fri, 31 Mar 2017 15:39 GMT

Clean up semantics of "OO-Include Condition"

  • Key: XTCE12-78
  • Legacy Issue Number: 14509
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2008-05-28 21:45:18 BST
    In EntryList, a containerRef that's to an abstract container has special
    meaning. perhaps it warrants it own entry to clear up the semantics.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Tue, 21 Mar 2017 15:53 GMT

toString/NumberFormat needs default settings

  • Key: XTCE12-7
  • Legacy Issue Number: 14497
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2008-03-20 19:13:40 GMT
    toString/NumberFormat - element is required if toString is in use. Almost all
    attributes are optional but defaults should be

    provided for "most common" likely format...

  • Reported: XTCE 1.0 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 13 Jan 2017 00:40 GMT

Type inheritance missing from Absolute and Relative time data types

  • Key: XTCE12-14
  • Legacy Issue Number: 19633
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Absolute and Relative time should have a "baseType" similar to the other scalar data types. This is probably an oversight.

  • Reported: XTCE 1.1 — Mon, 6 Oct 2014 04:00 GMT
  • Updated: Fri, 13 Jan 2017 00:40 GMT

size in bits of float encoding

  • Key: XTCE12-103
  • Legacy Issue Number: 14488
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Ludovic FAURE 2007-12-12 07:02:01 GMT
    XTCE schema seems to allow only three size in bits for float encoding: 32, 64
    and 128. Some existing missions at CNES, uses float parameters encoded on 48
    bits and then this size is not correct against XTCE.
    Comment 1 Kevin Rice 2008-05-01 21:41:23 BST
    This the same at 667 – 48 bits is for 1750a, and some combos are probably not
    legal given the attribute values for setting this, further IEEE 80 bit
    extended format is not supported either.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sat, 24 Dec 2016 00:18 GMT
  • Attachments:

Add support for arbitary floating point

  • Key: XTCE12-26
  • Legacy Issue Number: 19399
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Add support for arbitrary floating point formats within FLoatDataEncoding.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Sat, 24 Dec 2016 00:18 GMT

Valid sizeInBits values for encoding="MILSTD_1750A"

  • Key: XTCE12-17
  • Legacy Issue Number: 19415
  • Status: open  
  • Source: Jacobs Technology, Inc. ( Robert Goodwin)
  • Summary:

    The XTCE schema currently defines the following three legal values for sizeInBits in the FloatDataEncodingType complex type: 32, 64, 128. These legal values are correct if the encoding attribute is “IEEE754_1985”; but for encoding=”MILSTD_1750A”, the legal values should be 32 (single precision) and 48 (extended precision). Reference sections 4.1.5 and 4.1.6 of the MIL-STD-1750A specification (http://www.xgc.com/manuals/m1750-ada/m1750/book1.html). Need to add XTCE support for sizeInBits=48 when encoding=”MILSTD_1750A”.

  • Reported: XTCE 1.1 — Tue, 13 May 2014 04:00 GMT
  • Updated: Sat, 24 Dec 2016 00:18 GMT

MessageSet has unneeded attribute

  • Key: XTCE12-94
  • Legacy Issue Number: 14493
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2008-03-20 19:09:35 GMT
    MessageSet has an unrequired name. This is not part of the NameReference
    annotation and is inconsistent. I don't think this is used at all and should be
    removed.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 23 Dec 2016 00:51 GMT

Add name attribute to context alarms or calibrators

  • Key: XTCE12-108
  • Legacy Issue Number: 14480
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:59:47 BST
    An optional name should be associated with context alarms and calibrators in
    type. This would particularly be useful to type inheritance, because same
    'named' contexts could be overloaded.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 23 Dec 2016 00:51 GMT

PercentComplete in Verifiers needs clean up

  • Key: XTCE12-121
  • Legacy Issue Number: 14470
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:42:34 BST
    Clarify the way percentComplete is specified. Value should be constrained from
    0 to 100.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 23 Dec 2016 00:51 GMT

exponent attribute in Term element in PolynomialCalibrator should be non-negative integer

  • Key: XTCE12-77
  • Legacy Issue Number: 14516
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2009-06-04 18:07:59 BST
    Strictly speaking polynomials only have exponents in their terms which are
    non-negative whole numbers. the current construction specifies it as a double,
    which is too broad...

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 23 Dec 2016 00:51 GMT

Range support in enumerated parameter type

  • Key: XTCE12-25
  • Legacy Issue Number: 19401
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Add range support in enum list. Reported by ESA.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Fri, 23 Dec 2016 00:51 GMT

StringAlarmList is required but it should be optional

  • Key: XTCE12-19
  • Legacy Issue Number: 19411
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    This is similar to issue 19370. StringParameterTypes can have several types of alarms but the StringAlarmList is required. Thus if you have a string alarm condition but nothing to go into the string alarm list, you have to make one up. For example if you are comparing the current string value to a past one in some manner, there is not necessarily a string alarm to go with it. The solution is to make the string alarm list optional.

  • Reported: XTCE 1.1 — Mon, 12 May 2014 04:00 GMT
  • Updated: Fri, 23 Dec 2016 00:51 GMT

Change NameType regex from zero or more to one or more characters

  • Key: XTCE12-16
  • Legacy Issue Number: 19442
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    NameType's regex currently allows a name to be empty, and it should not allow this...

  • Reported: XTCE 1.1 — Mon, 2 Jun 2014 04:00 GMT
  • Updated: Thu, 27 Oct 2016 00:25 GMT

Add regex to enforced syntax of NameReferences

  • Key: XTCE12-11
  • Legacy Issue Number: 19446
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    NameReferences which are "text pointers" in XTCE are currently an open string type, even though the form is "path-like" (e.g. sat/power/battery[0].voltage). There are a variety of forms of it and different types (regular namereferences and parameter instance refs). The syntax of these could be enforced with a regular expression. Below is an example that can used as basis for in the spec.

    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
    <xs:element name="test">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="path" maxOccurs="unbounded">
    <xs:simpleType>
    <xs:restriction base="xs:string">
    <xs:pattern value="/?(([a-zA-Z0-9_\-]|\.|\.\.)/)([a-zA-Z0-9_\-]([[0-9]])?)([\.][a-zA-Z0-9_\-]([[0-9]+])?)"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:element>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:schema>

    — EXAMPLES

    <test xsi:noNamespaceSchemaLocation="path.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <path>foo</path>
    <path>foo[9].bar[0].baz[0]</path>
    <path>foo[0999]</path>
    <path>/foo/bar</path>
    <path>/foo/bar/baz</path>
    <path>/oo/bar/baz.bif</path>
    <path>/foo/bar[99].bif</path>
    <path>foo/bar[99].bif</path>
    <path>../././bar[99].bif</path>
    </test>

  • Reported: XTCE 1.1 — Wed, 4 Jun 2014 04:00 GMT
  • Updated: Mon, 24 Oct 2016 03:20 GMT

DefaultSignicance element can have no content at all

  • Key: XTCE12-97
  • Legacy Issue Number: 14492
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2008-03-20 19:07:03 GMT
    It has three attributes none of which are required and there are no defaults
    for them – result: an empty DefaultSignificance can be set with NO
    information. Probably true for ContextSignificance as well. At least one
    attribute should be required to avoid this.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sat, 22 Oct 2016 00:26 GMT

SplinePoint attribute order should be ignored (typo)

  • Key: XTCE12-100
  • Legacy Issue Number: 14487
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-11-12 20:29:42 GMT
    The SplinePoint element has an attribute called 'order' which seems to be a
    hold over from an earlier version of this construct. It should be ignored.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sat, 22 Oct 2016 00:26 GMT

Move ValidRangeAppliesToCalibrated Attribute

  • Key: XTCE12-112
  • Legacy Issue Number: 14477
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:53:45 BST
    ValidRangeAppliesToCalibrated should be moved to ValidRange element. Right now
    this attribute is in the main element for the datatype but should probably be
    moved to a specific element to which it refers.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sat, 22 Oct 2016 00:26 GMT

SplineCalibrator order attribute too restrictive

  • Key: XTCE12-57
  • Legacy Issue Number: 18537
  • Status: open  
  • Source: Boeing ( David Overeem)
  • Summary:

    As previously discussed, the @order attribute of the <SplineCalibrator> relates to the fit funtion that is used for interpolation and extrapolation.

    Interpolation is implied when the @order attribute is used. Extrapolation has an explicit attribute.

    Setting the order to zero effectively creates a "step" function, as the fit function is limited to zeroth order behavior. First order behavior creates a linear function, otherwise called a "point to point". Second order would be a quadratic, etc.

    The schema allows only positive integers for the @order attribute. This should be non-negative integer.

  • Reported: XTCE 1.1 — Fri, 8 Mar 2013 05:00 GMT
  • Updated: Sat, 22 Oct 2016 00:26 GMT

Enumeration element could use an @shortDescription

  • Key: XTCE12-8
  • Legacy Issue Number: 18540
  • Status: open  
  • Source: Boeing ( David Overeem)
  • Summary:

    It would be convenient to add a shortDescription attribute to the Enumeration element for enumerated types.

  • Reported: XTCE 1.1 — Sun, 10 Mar 2013 05:00 GMT
  • Updated: Sat, 22 Oct 2016 00:26 GMT

Possible unused attribute in RepeatEntry

  • Key: XTCE12-13
  • Legacy Issue Number: 19443
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    The RepeatEntry has a count element (required) and an offset element (optional). The offset element has four choices: offsetSizeInBits (attribute), FixedValue, DynamicValue, DiscreteLookupList (elements).

    The first item there seems a sore thumb... further you can easily say two conflicting things with it.

    The offsetSizeInBits is probably an vestige from an earlier version of the schema and can be removed.

  • Reported: XTCE 1.1 — Mon, 2 Jun 2014 04:00 GMT
  • Updated: Sat, 22 Oct 2016 00:26 GMT

Improve FloatRangeType and IntegerRangeType

  • Key: XTCE12-18
  • Legacy Issue Number: 19435
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    IntegerRangeType and FloatRangeType define ranges with attributes. The integer version has two, min/max which are inclusive and the float has four which are both inclusive and exclusive. The float version is particularly “bad” because its four attributes can all be set, or some combination of them, forcing the implementer to quality check that just two are set.

    Another approach would be to provide two attributes: min/max for the value ­ and then a third attribute called “rangeType” or some such to indicate the kind of comparison to be performed: open, closed, open-closed, closed-open indicating whether the values are inclusive or exclusive – one, the other, or both.

  • Reported: XTCE 1.1 — Wed, 28 May 2014 04:00 GMT
  • Updated: Mon, 17 Oct 2016 21:34 GMT

ByteOrderList is invalid for Containers

  • Key: XTCE12-73
  • Legacy Issue Number: 14517
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2009-09-10 22:59:58 BST
    ByteOrderList is not valid for container and is part of the BinaryEncoding
    element.

    Ignore or remove from future version.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sat, 15 Oct 2016 19:27 GMT

Add forward/reverse calibrator metadata

  • Key: XTCE12-116
  • Legacy Issue Number: 14473
  • Status: open  
  • Source: NASA ( 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: Sat, 8 Oct 2016 00:25 GMT

TimeAssociation schema type is incorrect

  • Key: XTCE12-118
  • Legacy Issue Number: 14463
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:33:28 BST
    Parameter/TimeAssociation@offset – current date type should be decimal for
    holding offset. Change the Date to offsetTimeInMillisec, and make it a decimal
    type. It is possible to work around this by storing the milliseconds as a YEAR
    date but its awkward:
    0001-01-01+00:00
    0002-01-01+00:00
    9999-01-01+00:00, 10000-01-01+00:00

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sat, 8 Oct 2016 00:25 GMT

Use of the include conditions

  • Key: XTCE12-105
  • Legacy Issue Number: 14484
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Ludovic FAURE 2007-10-31 17:22:31 GMT
    The CNES recommendations suggest a way to define packets descriptions without
    using inheritance. Actually, we define a unique generical packet (non-abstract
    container) that contains the definition of all the packets for a given mission.
    It is possible by using optional container and parameter entries, thanks to the
    element IncludeCondition.
    This approach is equivalent to the inheritance approach (a XSLT translator has
    been developped) and is simpliest to handle at the software level. What about
    write this approach in the magenta book as OK approach?

  • Reported: XTCE 1.1 — Tue, 6 Oct 2009 04:00 GMT
  • Updated: Sat, 8 Oct 2016 00:25 GMT

Key bugs

  • Key: XTCE12-109
  • Legacy Issue Number: 14479
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:58:41 BST
    Keys for the ContainerSet check should read CommandContainerSet on the
    commandMetaData portion and there is no key at all for ArgumentTypeSet. These
    can be added with little effort although it seems many parsers ignore the keys.
    Comment 1 Kevin Rice 2008-03-03 21:15:40 GMT
    Most of the keys in fact are incorrect in the Xpath designations. For example
    the parameterNameKey should read:

    "xtce:TelemetryMetaData/xtce:ParameterSet/|xtce:CommandMetaData/xtce:ParameterSet/"

    Most if not all the other keys have the same issue related to incorrectly
    specifying the "xtce:" namespace and thus do nothing.

    Further, they are all at the top of the schema and instead could be positioned
    at each element of interest, this would help with the error message generated.

    Finally, instead of using key, the "unique" tag could be used instead as this
    is exactly what the keys are checking for, uniqueness.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sat, 8 Oct 2016 00:25 GMT

Change UnitSet to simple String; change name

  • Key: XTCE12-115
  • Legacy Issue Number: 14472
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:46:32 BST
    UnitSet should just be a simple string, rename it to "Unit" and add the
    attributes 'name' and 'description'. However the element should have content
    like:

    <Unit name="metersPerSecond" description="meters per second">m/s</Unit>
    Comment 1 Kevin Rice 2008-03-04 22:29:39 GMT
    Unit is actually a type "Any" which is clearly not what was intended either...
    Comment 2 Kevin Rice 2008-04-18 14:54:47 BST
    Unit is not a Type ANY – its set to MIXED but has not child elements. In
    XMLSpy '08 in grid mode it seems to initially accept mixed concept. However
    going to text will fail – not validate.

    The out of the box Java parser does not validate it either if there is mixed
    content.

    Suggest setting the mixed content attribute to FALSE to be – well absolutely
    correct.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sat, 8 Oct 2016 00:25 GMT

Remove old comments

  • Key: XTCE12-99
  • Legacy Issue Number: 14490
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2008-03-20 19:03:47 GMT
    Two old comments are in the schema and should be removed. They are:

    Remove this comment: <!-- removed for CASTOR: default="PT0S" --> line 1028

    Remove this comment: <!-- default="00" (does not work with CASTOR 0.9.5.3) -->
    line 2257

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sat, 8 Oct 2016 00:25 GMT

relative path in the parameterRef

  • Key: XTCE12-101
  • Legacy Issue Number: 14486
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Ludovic FAURE 2007-10-31 17:38:22 GMT
    In the first example of the chapter 2.3.3.1, the refernce to the parameter used
    the relative path: "PrimaryHeader.apid". The relative path for the space system
    tree uses '/' to separate space systems, why not use '/' to separate container
    from other container or parameter? By this way we will get an homogeneous way
    to define paths in XTCE.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sat, 8 Oct 2016 00:25 GMT

packet identification

  • Key: XTCE12-102
  • Legacy Issue Number: 14485
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Ludovic FAURE 2007-10-31 17:31:13 GMT
    In the chapter 2.3.4.4, it is written that a packet is identified as a
    non-abstract container that has a base container (or a message as well). I
    think a packet can be a non-abstract container without base container. For
    example, if the description contains only one container that defines a packet.
    There is no base container whereas this is a packet.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sat, 8 Oct 2016 00:25 GMT

Add explanatory annotation that MetaCommand/CommandContainer is semantically similar to a Java Private Inner Class

  • Key: XTCE12-104
  • Legacy Issue Number: 14483
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 22:03:01 BST
    MetaCommand/CommandContainer should have the same semantics as Java private
    Inner classes. Update annotation to reflect this.

  • Reported: XTCE 1.1 — Tue, 6 Oct 2009 04:00 GMT
  • Updated: Sat, 8 Oct 2016 00:25 GMT

Expand NameReference semantics

  • Key: XTCE12-98
  • Legacy Issue Number: 14489
  • Status: open  
  • Source: NASA ( 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: Sat, 8 Oct 2016 00:25 GMT

Condition has two elements with the same name, causes problems for some autogenerators

  • Key: XTCE12-81
  • Legacy Issue Number: 14508
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2008-05-28 21:43:30 BST
    Some autogenerators have problems with this – name change.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sat, 8 Oct 2016 00:25 GMT

Add OCL specific Algorithm to XTCE

  • Key: XTCE12-83
  • Legacy Issue Number: 14507
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2008-05-28 21:41:50 BST
    OCL is an OMG standard that adds a constraint language to UML or any model.
    It's related to RestrictionCriteria. Would a specific XTCE Algorithm for OCL
    be useful?

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sat, 8 Oct 2016 00:25 GMT

*Type/@initialValue need clarifications

  • Key: XTCE12-90
  • Legacy Issue Number: 14499
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2008-03-20 19:37:07 GMT
    *Type/@initialValue - intialValue for the various types need to be more fully
    spelled out. StringType give no provision for UTF-8/UTF-16. FloatType is a
    double although encoding may generate 32-bit quantity... BinaryType may clip
    actual storage size. Enumeration doesn't specify whether to use label or
    value... Boolean: possibly either '0' | '1' or 'oneStringValue' |
    'zeroStringValue'.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sat, 8 Oct 2016 00:25 GMT

EnumeratedParameterType does not support multiple context alarms

  • Key: XTCE12-69
  • Legacy Issue Number: 15874
  • Status: open  
  • Source: Harris ( Christopher Zonca)
  • Summary:

    The EnumeratedParameterType element currently does not support multiple context alarms, unlike the other ParameterType elements.

    This is probably because, on line 743 of the schema, the ContextAlarm element is not setting the maxOccurs attribute to "unbounded". Without this attribute, only one instance of the ContextAlarm element is allowed.

  • Reported: XTCE 1.1 — Mon, 29 Nov 2010 05:00 GMT
  • Updated: Sat, 8 Oct 2016 00:25 GMT

EnumeratedParameterType does not support multiple context alarms

  • Key: XTCE12-70
  • Legacy Issue Number: 15858
  • Status: open  
  • Source: Harris ( Christopher Zonca)
  • Summary:

    The EnumeratedParameterType element currently does not support multiple context alarms, unlike the other ParameterType elements.

    This is probably because, on line 743 of the schema, the ContextAlarm element is not setting the maxOccurs attribute to "unbounded". Without this attribute, only one instance of the ContextAlarm element is allowed.

  • Reported: XTCE 1.1 — Mon, 29 Nov 2010 05:00 GMT
  • Updated: Sat, 8 Oct 2016 00:25 GMT

RelativeTimeType nomenclature conflicts with RelativeTimeParameterType

  • Key: XTCE12-79
  • Legacy Issue Number: 14510
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2008-05-29 19:07:02 BST
    Confusing, suggest name change

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Sat, 8 Oct 2016 00:25 GMT

Add gap entry to container entry list

  • Key: XTCE12-43
  • Legacy Issue Number: 19384
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    A gap entry is an addressing mechanism to move the address pointer relative or absolutely as specified in the gap entry. This is an alternate approach to XTCE's location in container element. Reported by JPL.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Sat, 8 Oct 2016 00:25 GMT

Add named width spacer to Container entry list

  • Key: XTCE12-42
  • Legacy Issue Number: 19383
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    named width spacer entry is an alternative way to do addressing as provided by the location in container element in XTCE. Reported by JPL.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Sat, 8 Oct 2016 00:25 GMT

Add variable to containers

  • Key: XTCE12-46
  • Legacy Issue Number: 19382
  • Status: open  
  • Source: NASA ( 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: Sat, 8 Oct 2016 00:25 GMT

Add title to parameter

  • Key: XTCE12-44
  • Legacy Issue Number: 19380
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    A specific syntactic item for a title associated with telemetry parameters is not available in XTCE. Reported by JPL

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Sat, 8 Oct 2016 00:25 GMT

Add argument and fixed value entries to CommandContainerSet/CommandContainer

  • Key: XTCE12-21
  • Legacy Issue Number: 19402
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    The CommandContainerSet/CommandContainer is missing arguments related entries which make it impossible to describes some ESA packet definitions.

    Reported by ESA.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Sat, 8 Oct 2016 00:25 GMT

AlarmRanges cannot be defined based on raw values

  • Key: XTCE12-30
  • Legacy Issue Number: 19396
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Add raw value support in alarm ranges.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Sat, 8 Oct 2016 00:25 GMT

Add APID table list

  • Key: XTCE12-37
  • Legacy Issue Number: 19387
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Add an apid table list to XTCE so that packets defined in containers can be easily associated with their apid.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Sat, 8 Oct 2016 00:25 GMT

Add switch entry to container entry list

  • Key: XTCE12-40
  • Legacy Issue Number: 19385
  • Status: open  
  • Source: NASA ( 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: Sat, 8 Oct 2016 00:25 GMT

Create RangeEnumeration Type

  • Key: XTCE12-136
  • Legacy Issue Number: 14451
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 20:58:07 BST
    XTCE does not support RangeEnumeration directly. A RangeEnumeration maps a
    label to a range of values. Currently XTCE only has the simpler Enumeration
    Type - one label, one value. The IntegerType/ToString/rangeEnumeration could be
    used [note: label is missing]. But this is not strictly speaking a
    "RangeEnumerationTypes". (From Chris Simms/NASA-MSFC)

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 30 Sep 2016 00:48 GMT

Clear Up Calibrated/Uncalibrated Values in Schema

  • Key: XTCE12-139
  • Legacy Issue Number: 14450
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 20:56:01 BST
    XTCE has several locations within it where values need to be supplied, in many
    cases they may be calibrated or uncalibrated values and an associated attribute
    is supplied which determines whether the value should be treated as such.
    However in some cases, no attribute is supplied and the default is to treat the
    value as calibrated. The problem is that this is inconsistent and may not
    cover the common industry use cases, especially as related to alarms (limits).
    This bug report lists all the areas that use such a value in XTCE where an
    attribute is not supplied along with it to set whether the value should be
    calibrated or not. These areas need to be considered and an attribute supplied
    if appropriate.
    The following list may not be exhaustive (although it needs to be) and some may
    make more sense than others in terms of supplying calibrated or uncalibrated
    values; that needs to be determined (through use cases) and schema changes
    applied consistently to all these areas in the next revision.
    ParameterSet/parameter@initialValue
    Verifiers/ParameterValueChange/Change@value
    StringParameterType/SizeRangeInCharacters@min,max
    StringParameterType/

    {Default|Context}Alarm/StringAlarmList/StringAlarm@patternMatch
    EnumerationType/EnumerationList/Enumeration@value
    EnumerationType/{Default|Context}

    Alarm/EnumerationAlarmList/EnumerationAlarm@enumerationValue

    • (attributes is a string, is it the enum value, or is it label?)
      IntegerParameterType/toString/RangeEnumeration
      IntegerParameterType/StaticRangeAlarm
      IntegerParameterType/ChangeAlarms
      FloatParameterType/StaticRangeAlarm
      FloatParameterType/ChangeAlarms
      RelativeTimeType/ChangePerSecondAlarms
      ArgumentList/Argument@initialValue
      ParameterToSetList/../NewValue
  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 30 Sep 2016 00:48 GMT

Move Alarms outside of Type Area

  • Key: XTCE12-134
  • Legacy Issue Number: 14454
  • Status: open  
  • Source: NASA ( 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: Fri, 30 Sep 2016 00:48 GMT

Fix ArgumentTypes child element or attributes that use the term Parameter, to Argument

  • Key: XTCE12-135
  • Legacy Issue Number: 14453
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:02:49 BST
    Argument elements need to have their attributes or child elements set to
    ARGUMENTxxx. Many of the major elements associated with ArgumentTypes seem to
    have child or attributes that say "parameterXXX" instead of "argumentXXX".
    C-S/CNES
    Ludovic Faure

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 30 Sep 2016 00:48 GMT

Message/IncludeCondition/BaseContainer similarity

  • Key: XTCE12-129
  • Legacy Issue Number: 14460
  • Status: open  
  • Source: NASA ( 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: Fri, 30 Sep 2016 00:48 GMT

ContextAlarm not set to Inf Elements in EnumerationType

  • Key: XTCE12-130
  • Legacy Issue Number: 14457
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:08:06 BST
    Contextalarmlist/contextalarm in the enumarationType is not set to inf
    elements; missing INF in schema element

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 30 Sep 2016 00:48 GMT

Label Missing in IntegerType/RangeEnumeration area

  • Key: XTCE12-131
  • Legacy Issue Number: 14456
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:06:59 BST
    Label missing in RangeEnumeration element in ToString in IntegerType

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 30 Sep 2016 00:48 GMT

Add ability to compare counters in IncludeCondition

  • Key: XTCE12-132
  • Legacy Issue Number: 14452
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:00:29 BST
    IncludeCondition doesn't directly allow for certain types of comparisons except
    through CustomAlgorithm - counter based sampling particular. This need is
    related to supercomming or supersampling based on counts.
    (NASA-MSFC, Chris Simms)
    Comment 1 Kevin Rice 2008-05-21 21:40:25 BST
    Need to get more information -KR
    Comment 2 Kevin Rice 2008-05-21 21:51:11 BST
    You could use MathOperator in AlgorithmSet to derive something from another
    parameter and then use Condition (BooleanExpression) or Comparison in
    IncludeCondition to compare to the final result, such as a mod of a counter

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 30 Sep 2016 00:48 GMT

Put Alarms in Arguments; leaves Alarms in Command Parameters

  • Key: XTCE12-126
  • Legacy Issue Number: 14461
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:17:55 BST
    Command Argument should have alarms; I have found one user that claims alarms
    on USER INPUT arguments. Therefore I believe we should generalize the schema
    to having them both in parameters and arguments. In the end I believe we'll be
    making arguments and parameters look exactly the same even if the nomenclature
    stays separate.
    Comment 1 Kevin Rice 2007-10-22 21:20:06 BST
    Command Argument should have alarms; I have found one user that claims alarms
    on USER INPUT arguments. Therefore I believe we should generalize the schema
    to having them both in parameters and arguments. In the end I believe we'll be
    making arguments and parameters look exactly the same even if the nomenclature
    stays separate.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 30 Sep 2016 00:48 GMT

ErrorDetectCorrect does not support Checksum

  • Key: XTCE12-127
  • Legacy Issue Number: 14459
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:10:29 BST
    ErrorDetectCorrect doesn't support Checksum, especially on command side

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 30 Sep 2016 00:48 GMT

Checkwindow not tied to context

  • Key: XTCE12-128
  • Legacy Issue Number: 14458
  • Status: open  
  • Source: NASA ( 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: Fri, 30 Sep 2016 00:48 GMT

Change UnitSet to optional

  • Key: XTCE12-123
  • Legacy Issue Number: 14471
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:43:57 BST
    Making UnitSet required wastes instance file space, make UnitSet optional.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 30 Sep 2016 00:48 GMT

Clean up Annotation Related to Verifiers

  • Key: XTCE12-125
  • Legacy Issue Number: 14469
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:41:16 BST
    Update annotation related to verifiers parameterValueChange. It's supposed to
    mean the Delta change (you could just do a comparison check for a specific
    value). So if the current value is 10 and you're looking for a ValueChange of
    2, then you'd need a new value that's greater than 12 for the Verifier to trip.
    The annotation should be clearer.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 30 Sep 2016 00:48 GMT

Clarify ContainerRef check in Verification area

  • Key: XTCE12-122
  • Legacy Issue Number: 14468
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:40:01 BST
    Clarification needed for ContainerRef check. Clean up the annotation – it
    says: "When verification is a new instance the referenced Container". This
    doesn't make any sense.

    It just means the verification is reached when you receive that container. An
    example might be sending a command to download memory then receiving a packet
    with the memory download.

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 30 Sep 2016 00:48 GMT

AbsoluteTime should have Alarms

  • Key: XTCE12-120
  • Legacy Issue Number: 14466
  • Status: open  
  • Source: NASA ( 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: Fri, 30 Sep 2016 00:48 GMT

Message/ContainRef should read ContainerRef

  • Key: XTCE12-117
  • Legacy Issue Number: 14462
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2007-10-22 21:31:25 BST
    It's a typo

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 30 Sep 2016 00:48 GMT

  • Key: XTCE12-65
  • Legacy Issue Number: 17405
  • Status: open  
  • Source: Boeing ( David Overeem)
  • Summary:

    Clarify the reference point of absolute and relative bit positions in the container, when SequenceContainers are contained by other Containers. This clarification should be added to the annotations in the schema

  • Reported: XTCE 1.1 — Tue, 5 Jun 2012 04:00 GMT
  • Updated: Fri, 30 Sep 2016 00:48 GMT

attribute twosCompliment should be twosComplement

  • Key: XTCE12-89
  • Legacy Issue Number: 14501
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Description Kevin Rice 2008-03-27 22:13:54 GMT
    spelling typo

  • Reported: XTCE 1.1 — Thu, 17 Sep 2009 04:00 GMT
  • Updated: Fri, 30 Sep 2016 00:48 GMT

Fix spelling of one/twosCompliment in IntegerDataEncoding

  • Key: XTCE12-36
  • Legacy Issue Number: 19390
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    It should be complement, not compliment. Reported by Kratos/ISI.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Fri, 30 Sep 2016 00:48 GMT

AggregateParameterType or AggregateArgumentType Member attribute 'typeRef' is vague

  • Key: XTCE12-64
  • Legacy Issue Number: 17417
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    AggregateParameterType or AggregateArgumentType Member attribute 'typeRef' is vague in that it does not specify whether one is referring to a ParameterType or ArgumentType.

    It's safe to assume that the AggregateParameterType member should only refer to ParameterTypes and AggregateArgumentType members should only refer to ArgumentType. Alternatively again, the schema types could be split along the parameter and argument lines... and differentiated explicitly

  • Reported: XTCE 1.1 — Mon, 11 Jun 2012 04:00 GMT
  • Updated: Fri, 30 Sep 2016 00:48 GMT

No short description or long description at the Member element of AggregateParameterType or AggregateArgumentType

  • Key: XTCE12-63
  • Legacy Issue Number: 17416
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    There's no short description or long description at the Member element of AggregateParameterType or AggregateArgumentType

    Possible answers:

    1) Use the short/long descriptions of the referred to types. Alternatively we'd have to re-construct the schema type add descriptive info

  • Reported: XTCE 1.1 — Mon, 11 Jun 2012 04:00 GMT
  • Updated: Fri, 30 Sep 2016 00:48 GMT

MetaCommandSet is incorrectly set to required

  • Key: XTCE12-9
  • Legacy Issue Number: 19634
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    The MetaCommandSet is incorrectly set to required and should be optional, like all the other "top-level" elements in XTCE.

  • Reported: XTCE 1.1 — Mon, 6 Oct 2014 04:00 GMT
  • Updated: Fri, 30 Sep 2016 00:48 GMT

Change all elements to top level schema types

  • Key: XTCE12-35
  • Legacy Issue Number: 19389
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    By making all the elements top level schema types, the class mapping is cleaner.

  • Reported: XTCE 1.1 — Wed, 30 Apr 2014 04:00 GMT
  • Updated: Fri, 19 Feb 2016 05:15 GMT
  • Attachments:

MS-003 Meaning not clear.

  • Key: XTCE12-162
  • Legacy Issue Number: 9064
  • Status: open  
  • Source: Anonymous
  • Summary:

    Source: Michael Staub michael.staub@dlr.de
    Description : Reword: "The space industry is fragmented between Packet telemetry

    and
    commanding and Time Division Multiplexing (TDM) telemetry and commanding."
    Resolution:
    Title: MS-001 Missing page numbering
    Source: Michael Staub michael.staub@dlr.de
    Description : Add page numbering to document.

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

HVM-004 Data Encoding definitions

  • Key: XTCE12-188
  • Legacy Issue Number: 9038
  • Status: open  
  • Source: es ( Hans van der Meij)
  • Summary:

    Source: Hans.van.der.Meij Hans.van.der.Meij@es
    Description : In a number of places in the schema it is possible to define similar/equal properties
    of a parameter type.

    E.g. for an IntegerParameterType definition, the sizeInBits and the signed-ness
    can be be defined as attributes, and it is possible to define this type of information
    in the IntegerDataEncoding child.

    Please clarify which is the preferred way to specify this type of information and
    what is provided by XTCE to avoid ambiguities and inconsistencies.

    In any case, it is recommended to either update the specification to take out the
    flagged redundancies or to update the text to clearly define the intended use.
    Resolution: The document will be edited to clarify the differences between the two proprieties.
    The Integer parameter type describes how to handle the parameter in the ground
    software, while the Encoding integer type describes how the parameter is encoded
    in either the TM or TC.

  • Reported: XTCE 1.0 — Tue, 11 Oct 2005 04:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

Should use type[FixedFrameSyncStrategyType] in type [FixedFrameStreamType]

  • Key: XTCE12-158
  • Legacy Issue Number: 9069
  • Status: open  
  • Source: Anonymous
  • Summary:

    Source: Makoto Kawai kawai.makoto@jaxa.jp
    Description : Currently, the definition of element[SyncStrategy] in type

    [FixedFrameStreamType]
    is described by complexContent. To make the structure more simple, I
    recommend to use type[FixedFrameSyncStrategyType] in
    type[FixedFrameStreamType].

    From: "<element name="SyncStrategy"> ... </element>" To: "<element
    Resolution: Agree (with discussion). Suggest instead simply deleting
    FixedFrameSyncStrategyType (since it is would be used at most once).

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

V-003 Schema file identification

  • Key: XTCE12-160
  • Legacy Issue Number: 9067
  • Status: open  
  • Source: Anonymous
  • Summary:

    Source: Gert Villemos gev@terma.com
    Description : The schema file should be clearly identifiable, i.e. the XTCE

    document version
    referenced and/or the schema file version number changed.
    Resolution: Add version number to document

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

DC-013 Parameter encoding information

  • Key: XTCE12-161
  • Legacy Issue Number: 9066
  • Status: open  
  • Source: Anonymous
  • Summary:

    ource: D.Campbell dave.campbell@scisys
    Description : Lines 5-7. What is the information which states how encoding should

    be
    performed? The text mentions the "Encoding area" - where / what is this? What
    constraints are there / what documents specify how the encoding is to be
    performed? Should this information be included in this standards document?
    Different agencies may misinterpret how to use the encoding information unless its
    use is also standardised in some document.
    Resolution: Add clarifications to the text

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

MS-001 Missing page numbering

  • Key: XTCE12-159
  • Legacy Issue Number: 9065
  • Status: open  
  • Source: Anonymous
  • Summary:

    Source: Michael Staub michael.staub@dlr.de
    Description : Add page numbering to document.

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

MM-001 What missions need

  • Key: XTCE12-155
  • Legacy Issue Number: 9073
  • Status: open  
  • Source: Anonymous
  • Summary:

    Source: Mario Merri Mario.Merri@esa.int
    Description : In an ideal world, the Project Manager of a new space mission would

    like to have a
    simple life and put a single requirement to the Spacecraft Prime Contractor that
    reads something like: "It shall be possible to export the operational database into
    XTCE (ref. .)".

    To have project managers buying in XTCE, we should be able to demonstrate the
    goodness of the requirement above and explain that the Prime Contractor will have
    to produce a simple tool to translate from their internal DB format into XTCE.
    Therefore, the questions are:

    a) are the XTCE specifications enough to unambiguosly develop the software tool
    that translates into XTCE?

    b) Where should a new mission start from? (missions tend to re-use what has
    been done by other mission before. In the absece of a predecessor is there any
    help that we coulf provide to missions?)

    Clarification and possibly real-mission examples should be provided to clarify the
    above.
    Resolution: Update introductory section and consider development of associated

    tools (e.g.
    validator).

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

MP-001 Terminology

  • Key: XTCE12-156
  • Legacy Issue Number: 9071
  • Status: open  
  • Source: Anonymous
  • Summary:

    ource: M. Pecchioli mauro.pecchioli@esa.i
    Description : There are many specific (and non-obvious) terms used in this

    standard. They
    should be introduced and explained clearly in Section 4. Unfortunately, in the
    current version of the standard, only the obvious terms (telemetering and
    command) are defined. In the state where it is, the standard cannot be really
    understood and thus reviewed without a very significant effort.
    Resolution: CLARIFICATION Add additional terms

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

TH-001 Some Typos

  • Key: XTCE12-154
  • Legacy Issue Number: 9070
  • Status: open  
  • Source: Anonymous
  • Summary:

    Source: Thomas Huang txh@mipl.jpl.nasa.gov
    Description : There are a few minor cosmetic errors
    In the Green Book - Page 15 - <TAG>data<\TAG> should be <TAG>data</TAG> -
    Page 22 - missing '/' before SpaceSystemV1.0.xsd in xsi:schemaLocation - Page
    36 - same problem as in Page 22.

    In the Red Book - Page 13 references 'Appendix A'. I think it should be 'Annex A'.

    • Page 24 - sub-heading 6.1.3.2.6 used twice (for Interlock and Verifiers) - Page

    25

    • perhaps a page and/or section break before '6.2 The Schema'. - Page 70 -
      perhaps a page/or section break before 'Annex B'.
  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

MK-005 Should use type[ContextCalibratorType] in …

  • Key: XTCE12-157
  • Legacy Issue Number: 9068
  • Status: open  
  • Source: Anonymous
  • Summary:

    Description : Currently, element[ContextCalibrator] in element

    [ContextCalibratorList] in
    type[IntegerDataEncodingType], [FloatDataEncodingType] and
    [StringDataEncodingType] are defined by complexContent. To make the structure
    more simple, I recommend to use type[ContextCalibratorType] in
    type[IntegerDataEncodingType], [FloatDataEncodingType] and
    [StringDataEncodingType].

    From: "<element name="ContextCalibrator" maxOccurs="unbounded"> ...
    </element>" To: "<element name="ContextCalibrator"
    type="xtce:ContextCalibratorType" maxOccurs="unbounded"/>"
    Resolution: Good input. Fix schema and associated documentation.

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

OnBoard Software

  • Key: XTCE12-150
  • Legacy Issue Number: 9222
  • Status: open  
  • Source: Anonymous
  • Summary:

    The are no OBSW space element, specific additional information such as OBSW version,
    memory that is read, write, unreadable, protected, constant, variable, start address, etc.

    This may be out of scope of XTCE, but another very common database exchange on modern
    missions. OBSW memory map and execution information, which should ideally be included as a very specific space system element. And is the OBSW version that is valid for the database release.

  • Reported: XTCE 1.0 — Thu, 1 Dec 2005 05:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

CalibratorType

  • Key: XTCE12-152
  • Legacy Issue Number: 9204
  • Status: open  
  • Source: Anonymous
  • Summary:

    SCOS 2K uses another type of calibrators that is not supported by XTCE. XTCE should provide a way to support a kind of logarithmic (or custom) calibrator. The calibration is defined by the following equation: Y = 1/

    {A0 + A1 ln(x) + A2 ln2(x) + A3 ln3(x) + A4 ln4(x)}

    . Ln is the natural log (base e), and Ai are coefficients stored for the calibrations. Of course such a
    calibrator will need, as others, a short description and a name. If this thought as not generic
    enough, then XTCE should give a way to describe non standard calibrators. For example, coefficient, base, exponent in a term sum used as a calibrator.

  • Reported: XTCE 1.0 — Thu, 1 Dec 2005 05:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

Section: 7

  • Key: XTCE12-151
  • Legacy Issue Number: 9083
  • Status: open  
  • Source: Anonymous
  • Summary:

    CNES remarks and recommendations for the XTCE norm CNES (French Space Agency) has led a study to determine if and how the XTCE standard can be used in the context of the Myriade project. (Myriade is a microsatellites family, initiated by Demeter, Parasol …). Some files produced by the actual Myriade data base (called BDMS)for the CCC Control Center have been translated in XTCE. Here are the results of this study : About Telemetry : We have chosen the decommutation plan which is one of the most representative file among those who are exported from the system data base. In this file we have chosen a significant TM packet (called ECU) with a structure containing a discriminating element (part of the telemetry depends on the value of a parameter called a "selector"). The complexity is to separate the data from the processes in the BDMS to define the best implementation with theXTCE norm. We see that the data in the XTCE file must be processed in order to obtain the expected file (addition of ground calculated parameters, renaming of some parameters, calculation of the offset, ...). For the XTCE norm itself, we can notice that there are two ways to define conditional structure. We think that, at least, a way to use XTCE must be recommended in order to obtain a homogenous implementation in different projects. About Telecommands We encountered some difficulties in trying to implement the example of TC with the XTCE norm. We found a lot of similarities in the definitions of types included in the TelemetryMetaDataType and the CommandMetaDataType elements. In some cases, these similarities present slight differences, which are obviously not enough justified with sufficient explanations (ie the definition of the CommandContainer is different coming from CommandMetaData/MetaCommandSet/MetaCommand or coming from CommandMetaData/CommandContainerSet), and therefore resulted in some confusions. The structure of nested types is not easy to assimilate. Some information seem to be redundant inside a type. It would be useful to have more explanations of this case. At first, the information provided by the TC example and the elements defined in the XTCE norm didn’t fit. We finally carried out a way to proceed, nevertheless, there is no evidence that our solution is the best one. The point that is not resolved is how to implement the variable argument. Conclusion of the study Within the framework of this study, the scope of TM/TC implemented with XTCE clearly appeared as limited. We focused our study on a subset of one TM packet, and also on one specific TC. As a result, the first step can be consider positive. However, in the absence of a more exhaustive study which encompass more possibilities of XTCE, the overall feasibility is still pending. The most important problem of the norm is that it is very complex, and difficult to learn, even for engineers experimented in XML, and data base schemas. Its complexity comes from its genericity. We think that there are too many ways to define a TM packet with this norm to be sure that every project will define its telemetry using the same philosophy. In the SpaceSystem schema which describes the norm, the <Annotation> sections are very succinct and sometimes not sufficient. So, in order to help users to understand the schema, the chapter 6 (The Specification) of the XTCE norm should contains more in-depth explanations. Moreover, the standard is far from being user friendly due to excessive offered possibilities in terms of implementation. We did not find any example corresponding to our needs. The available documentation is surely not designed for an easy learning. Of course, a tutorial is to be issued. A solution to reduce the learning effort could be to define a smaller kernel of the norm, with some possible extensions for some specific use. One important lack of the norm seems to be that it does not enable a user to define its own tags and attributes in order to complete the description. This could be the solution to avoid changing the norm each time a particular need appears in a project. Another important remark we have to make is about the state of XTCE. The norm has changed a lot between the OMG version of 2004 and the referenced CCSDS red book. It seems not to be still defintly defined. This fact is very important because if we want to use the norm in an operational context, with have to be sure that there will not have big changes before starting the development of tools based upon the norm. Tools are mandatory to use this norm because it is quite impossible to create a full XTCE file with a simple XML editor. When the norm will be approved, the XML-oriented database can be the next step in the XTCE deployment. It could be interesting to have a generic code that enables the updates of a database by reading a XTCE file and enables the extractions from a database to produce some XTCE files. Xavier Passot CNES DCT/SB/CC With Erwann Poupart (CNES DCT/PS) and Frederic Berriri (CS/SI)

  • Reported: XTCE 1.0 — Wed, 19 Oct 2005 04:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

MK-002 Type of element[MessageRef] is undefined

  • Key: XTCE12-153
  • Legacy Issue Number: 9072
  • Status: open  
  • Source: Anonymous
  • Summary:

    ource: Makoto Kawai kawai.makoto@jaxa.jp
    Description : Type of element[MessageRef] in element[MessageRefSet] in type

    [ServiceType] is
    undefined.

    To change as below.

    From: "
    <element name="MessageRef" maxOccurs="unbounded"/>"

    To: "
    <element name="MessageRef" type="xtce:MessageRefType"
    maxOccurs="unbounded"/>"

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

6 - Add ToString to Boolean or remove Boolean in favor of Enumerated Types

  • Key: XTCE12-146
  • Legacy Issue Number: 10174
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    6 - Add ToString to Boolean or remove Boolean in favor of Enumerated Types (ESA-007)

    Defer (no agreement on approach)

  • Reported: XTCE 1.0 — Fri, 1 Sep 2006 04:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

- Add separate CalibratorSet to XTCE

  • Key: XTCE12-145
  • Legacy Issue Number: 10170
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    2 - Add separate CalibratorSet to XTCE as many legacy system hold calibrators in tables (ESA-006)

    Defer (breaks current XTCE model, complexity)

  • Reported: XTCE 1.0 — Fri, 1 Sep 2006 04:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

1 - Support ability to describe redundant or complimentary data

  • Key: XTCE12-147
  • Legacy Issue Number: 10169
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    1 - Support ability to describe redundant or complimentary data (ESA-001)

    Defer (complexity)

  • Reported: XTCE 1.0 — Fri, 1 Sep 2006 04:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

OnBoard Memory

  • Key: XTCE12-148
  • Legacy Issue Number: 9221
  • Status: open  
  • Source: Anonymous
  • Summary:

    There are no specific descriptions of onboard memory possible, i.e. block size, addressing technique, etc as per tables 12, 13 of the ECSS. This I would expect at the space-system
    description level?

    Onboard memory is a very specific type of space system element, for which a lot of specific data is always needed, and it would be worth making specific entry types appropriate to onboard memory system elements. This to include Memory ID, Accessibility (read,write), smallest addressable unit, addressing technique, block length, subblock symbolic name, subblock offset, subblock length, etc

  • Reported: XTCE 1.0 — Thu, 1 Dec 2005 05:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

CommandContainerType

  • Key: XTCE12-149
  • Legacy Issue Number: 9206
  • Status: open  
  • Source: Anonymous
  • Summary:

    A fixed value cannot be added to a container created in the ContainerSet but only to a
    container created in the MetaCommand object. In SCOS 2K, fixed values would be added in
    the Meta Command and this cannot be done. Add the Fixed Area support to container defined with the MetaCommand would help

  • Reported: XTCE 1.0 — Thu, 1 Dec 2005 05:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

8 - Add activity field to Alarms to indicate what the alarm will trigger

  • Key: XTCE12-141
  • Legacy Issue Number: 10176
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    8 - Add activity field to Alarms to indicate what the alarm will trigger (ESA-015)

    Defer (further discussion needed)

  • Reported: XTCE 1.0 — Fri, 1 Sep 2006 04:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

5 - Align XTCE and CCSDS Navigation Schemas (types)

  • Key: XTCE12-144
  • Legacy Issue Number: 10173
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    5 - Align XTCE and CCSDS Navigation Schemas (types) (JPL-029)

    Defer (possible future work area)

  • Reported: XTCE 1.0 — Fri, 1 Sep 2006 04:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

4 - Separate XTCE Schema into constituent parts

  • Key: XTCE12-143
  • Legacy Issue Number: 10172
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    4 - Separate XTCE Schema into constituent parts (JPL-016,022,026,030)

    Defer (possible future work area

  • Reported: XTCE 1.0 — Fri, 1 Sep 2006 04:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

3 - Use UML Instance diagrams for XTCE document example

  • Key: XTCE12-142
  • Legacy Issue Number: 10171
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    3 - Use UML Instance diagrams for XTCE document example (ESA-038)

    Defer (more appropriate for XTCE CCSDS Green/Magenta Books, future work area)

  • Reported: XTCE 1.0 — Fri, 1 Sep 2006 04:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

Some sections/pages refer to the old (1.0) xsd version

  • Key: XTCE12-137
  • Legacy Issue Number: 12803
  • Status: open  
  • Source: NLR ( Leo Timmermans)
  • Summary:

    Some sections/pages refer to the old (1.0) xsd version: 1 - page v: Version 1.1: The source documents for this specification include: Formal version 1.0: formal/2005-08-01 Associated Schema files: formal/2005-08-02 (xsd) 2 - page 19: The XTCE normative specification is contained entirely as a W3C XML Schema. This schema is available as a standalone document at http://www.omg.org/space/xtce/SpaceSystem1.0.xsd [=> This link is incorrect ]

  • Reported: XTCE 1.1 — Wed, 3 Sep 2008 04:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

9 - Add filtering of value threshold to maintain telemetry at certain rates

  • Key: XTCE12-138
  • Legacy Issue Number: 10177
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    9 - Add filtering of value threshold to maintain telemetry at certain rates (ESA-048)

    Defer (additional discussion, future work area)

  • Reported: XTCE 1.0 — Fri, 1 Sep 2006 04:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

7 - Use UUIDs instead of current XTCE Referencing mechanism

  • Key: XTCE12-140
  • Legacy Issue Number: 10175
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    7 - Use UUIDs instead of current XTCE Referencing mechanism (ESA-005)

    Defer (complexity, no agreement on approach, further consideration needed)

  • Reported: XTCE 1.0 — Fri, 1 Sep 2006 04:00 GMT
  • Updated: Fri, 15 Jan 2016 05:04 GMT

DC-027 Line 3

  • Key: XTCE12-173
  • Legacy Issue Number: 9053
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : From: "a TransmissionContraintList"
    To: "a TransmissionConstraintList"
    Resolution: Fix text

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:21 GMT

DC-032 Line 3

  • Key: XTCE12-174
  • Legacy Issue Number: 9052
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : From: "overidden"
    To: "overridden"
    Resolution: Fix text

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:21 GMT

DC-034 Line 10

  • Key: XTCE12-178
  • Legacy Issue Number: 9051
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    ource: D.Campbell dave.campbell@scisys
    Description : From: "the UML refenceces"
    To: "the UML references"
    Resolution: Fix Schema annotation and text

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:21 GMT

DC-018 Line 10

  • Key: XTCE12-175
  • Legacy Issue Number: 9050
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : Is this a typo?
    From: "minorFrame 20"
    To: "minorFrame 8"
    Resolution: Fix text 6.2.2.3

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:21 GMT

DC-029 Line 1

  • Key: XTCE12-177
  • Legacy Issue Number: 9048
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : From: "user access our confirmations"
    To: "user access confirmation"
    Resolution: Fix text - actually should read "user access or confirmations"

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:21 GMT

DC-011 Figure text.

  • Key: XTCE12-180
  • Legacy Issue Number: 9046
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : "CommandMetaDataType" lists its attributes, but the attributes in
    "TelemetryMetaDataType" are missing.
    Resolution: Correct UML figure

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:21 GMT

DC-005 Figure

  • Key: XTCE12-182
  • Legacy Issue Number: 9044
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : No label or Figure number
    Resolution: Fix text

  • Reported: XTCE 1.0 — Tue, 11 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:21 GMT

DC-025 Encoding information

  • Key: XTCE12-184
  • Legacy Issue Number: 9043
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : Lines 6-7. Same query as for DC-013, DC-017, DC-021. An argument may "include
    information about how the value is encoded for transmission", but there’s nothing
    in the document to define how this information should be used. So where is that
    defined? "All of the encoding information is in the Encoding area." What is this,
    where is it defined, and why is it not included in the list of terms?
    Resolution: Text should be updated for clarification

  • Reported: XTCE 1.0 — Tue, 11 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:21 GMT

DC-026 Encoding area

  • Key: XTCE12-183
  • Legacy Issue Number: 9042
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : Lines 8. "All of the encoding information is in the Encoding area." What is this,
    where is it defined, and why is it not included in the list of terms?
    Resolution: Fix text

  • Reported: XTCE 1.0 — Tue, 11 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:21 GMT

DC-017 Assembly / dissembly information.

  • Key: XTCE12-190
  • Legacy Issue Number: 9036
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : Lines 2-3. Same query as for DC-013. How is this information used to assemble an
    uplink / disassemble a downlink? And where are these methods of assembly /
    disassembly defined? More information in this document or inclusion of a reference
    to the relevant document would be useful.
    Resolution: The XTCE powerpoint tutorial contains the best explanatory information on XTCE.
    Text should be updated to add clarity to the assembly/disassembly mechanisms.

  • Reported: XTCE 1.0 — Tue, 11 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:21 GMT

DC-028 ArgumentList

  • Key: XTCE12-191
  • Legacy Issue Number: 9035
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : This should explain how MetaCommand arguments are used compared to
    Command arguments and how they relate to each other, if at all.
    Resolution: Clarify text

  • Reported: XTCE 1.0 — Tue, 11 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:21 GMT

"Parameter Processing" box

  • Key: XTCE12-195
  • Legacy Issue Number: 9029
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : Should "deramdomization" be de-randomisation" with an 'n' and an 's'?
    Resolution: Not sure about the 's'

  • Reported: XTCE 1.0 — Tue, 11 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:21 GMT

"Foreword", line 2.

  • Key: XTCE12-198
  • Legacy Issue Number: 9028
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : From: "in all phases of the a spacecraft"
    To: "in all phases of the spacecraft"
    Resolution: Fx

  • Reported: XTCE 1.0 — Tue, 11 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:21 GMT

DC-033 Line 6

  • Key: XTCE12-166
  • Legacy Issue Number: 9062
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : From: "Element and Type names begin with a capitol letter."
    To: "Element and Type names begin with a capital letter."
    Resolution: Fix text and associated schema annotation

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:21 GMT

DC-024 Line 6

  • Key: XTCE12-168
  • Legacy Issue Number: 9060
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : From: "Most Arguments, are"
    To: "Most Arguments are"
    Resolution: Fx text

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:21 GMT

DC-030 Line 5

  • Key: XTCE12-167
  • Legacy Issue Number: 9058
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : From: "is is possible"
    To: "it is possible"
    Resolution: Fix

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:21 GMT

DC-016 Line 4.

  • Key: XTCE12-169
  • Legacy Issue Number: 9057
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : From: "a Parameter it is not the value itself."
    To: "a Parameter is not the value itself."
    Resolution: Fix text

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:21 GMT

DC-020 Line 4

  • Key: XTCE12-171
  • Legacy Issue Number: 9056
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : From: "The collection of messages to search thru"
    To: "The collection of messages to search through"
    Resolution: Fx text

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:21 GMT

DC-008 Line 4

  • Key: XTCE12-170
  • Legacy Issue Number: 9055
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : From: "RF hardware and other many other assets"
    To: "RF hardware and many other assets"
    Resolution: Fix text

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:21 GMT

DC-010 Line 1

  • Key: XTCE12-176
  • Legacy Issue Number: 9049
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : From: "the organization of the data may be organized hierarchical structure"
    To: "the data may have a hierarchical structure"
    Resolution: Fix text

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:21 GMT

DC-021 Assembly / dissembly of streams

  • Key: XTCE12-186
  • Legacy Issue Number: 9037
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : Lines 2-4. Same query as for DC-013 and DC-017. The types listed do NOT
    contain "the knowledge for how to assemble, disassemble and process spacecraft
    uplink and downlink streams" - they may hold the constraint or type information
    required by the assembly / disassembly methods, but they do not define the
    knowledge of how to do this. There needs to be another document which does
    Resolution: Propose revised text 6.1.2.5

  • Reported: XTCE 1.0 — Tue, 11 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:21 GMT

DC-004 "Philosophy", line 2

  • Key: XTCE12-200
  • Legacy Issue Number: 9030
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : From: "While, the basic"
    To: "While the basic"

  • Reported: XTCE 1.0 — Tue, 11 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:21 GMT

DC-012 Line 5

  • Key: XTCE12-164
  • Legacy Issue Number: 9059
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : From: "Most Parameters, are"
    To: "Most Parameters are"
    Resolution: Fix text

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:21 GMT

DC-015 Figure label.

  • Key: XTCE12-181
  • Legacy Issue Number: 9045
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : From: "Figure 3 ParameteTypeSet"
    To: "Figure 3 ParameterTypeSet"

  • Reported: XTCE 1.0 — Tue, 11 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:20 GMT

MP-004 Logarithmic calibrations

  • Key: XTCE12-163
  • Legacy Issue Number: 9063
  • Status: open  
  • Source: Anonymous
  • Summary:

    ource: M. Pecchioli mauro.pecchioli@esa.i
    Description : It seems that logarithmic calibrations are not supported by the

    standard. I think
    this should be added.

    -----Added after meeting with clarification by MP of 18Apr05:

    What we support in S2K is the following:

    In the case of parameters associated to a logarithmmic calibration, the engineering
    value ‘Y’ corresponding to the raw value ‘X’ of a parameter is calculated using

    the
    following formula:
    Y = 1 / [A0 + A1*ln(X) + A2*ln2(X) + A3*ln3(X) + A4*ln4(X)]
    Resolution: Question: Would a polynomial approximation be close enough? What

    forms of
    logarithmic calibration are required: natural, base 10 other. What direction of
    conversions are required?

    Discussion: what is ln2 (a base 2 log or the second natural log?)

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:15 GMT

MS-006 Footing of Figure 1 is missing.

  • Key: XTCE12-179
  • Legacy Issue Number: 9047
  • Status: open  
  • Source: Anonymous
  • Summary:

    Footing of Figure 1 is missing.
    Source: Michael Staub michael.staub@dlr.de
    Description :
    Resolution: Add footing

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:14 GMT

MP-007 Dynamic telemetry check types

  • Key: XTCE12-185
  • Legacy Issue Number: 9041
  • Status: open  
  • Source: Anonymous
  • Summary:

    Source: M. Pecchioli mauro.pecchioli@esa.i
    Description : It seems that only alarms based on static definition of the allowed value ranges are
    supported. Spacecraft control systems also require the support of checks against
    a dynamic reference, either maintained based on commanding activities (this is
    known as Status Consistency Checks in SCOS-2000) or maintained using
    telemetry data (this is known as Delta checks in SCOS-2000). Provision for this
    type of checks (against a 'moving' reference) shall also be made in XTCE.
    Resolution: XTCE does support a form of Delta Range checks called "ChangePerSecond".
    Question to RID author: "is this what you are looking for, or are you looking for
    something else?" Status consistancy checks should be added to the schema. It
    is believed that XTCE does support the RID authors's requirements for Delta
    checks.

    Add clarification for Delta checks.

  • Reported: XTCE 1.0 — Tue, 11 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:14 GMT

MS-009 De-calibration of cmd parameters?

  • Key: XTCE12-189
  • Legacy Issue Number: 9039
  • Status: open  
  • Source: Anonymous
  • Summary:

    Source: Michael Staub michael.staub@dlr.de
    Description : Is command parameter processing intentionally left out? On the other hand, TM
    calibration is mentioned. The same is valid for command packetization.
    Resolution: but for command arguments
    Title: GV-007 Dependencies or aggregation
    Source: Gert Villemos gev@terma.com
    Description : The UML diagrams seems to use dependencies (arrow) instead of aggregation (line
    with diamond). From the context, aggregation is meant. It is not clear whether the
    UML diagrams are intended only to illustrate the definition or actually be formal
    Resolution: Notation was decided by the tool that was used to do reverse engineering (from
    XML Schema to UML). It is agreed that the suggested representation is more
    correct.

    ACTION GV-007-01: Gert Villemos to provide updated UML diagrams for XTCE.
    Due 30May05

  • Reported: XTCE 1.0 — Tue, 11 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:14 GMT

DC-023 Line 3.

  • Key: XTCE12-172
  • Legacy Issue Number: 9054
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : "MessageSet" is not shown in Figure 1 or Figure 7.
    Resolution: Figure 7 does not show a MessageSet because it is not part of
    CommandMetaData (whether it should be is another discussion).

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:13 GMT

DC-009 Line 6

  • Key: XTCE12-165
  • Legacy Issue Number: 9061
  • Status: open  
  • Source: scisys ( Dave Campbell)
  • Summary:

    Source: D.Campbell dave.campbell@scisys
    Description : From: "markup documentation,"
    To: "markup documentation)"
    Resolution: Fix text

  • Reported: XTCE 1.0 — Wed, 12 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:12 GMT

MK-007 Don't need element[ChangePerSecondAlarmConditions]

  • Key: XTCE12-187
  • Legacy Issue Number: 9040
  • Status: open  
  • Source: jaxa.jp ( Makoto Kawai)
  • Summary:

    MK-007 Don't need element[ChangePerSecondAlarmConditions] intype[NumericAlarmConditionType]
    Source: Makoto Kawai kawai.makoto@jaxa.jp
    Description : Currently, element[ChangePerSecondAlarmConditions] is defined in
    element[ConditionalAlarm] in type[NumericAlarmConditionType], but Change rate
    evaluation cannot apply to Conditions. To change as below.

    From:
    "<element name="ConditionalAlarm"> <annotation>
    <documentation>…</documentation> </annotation>
    <complexType>
    <sequence>
    <element name="StaticAlarmConditions"
    type="xtce:AlarmConditionsType" minOccurs="0"/>
    <element name="ChangePerSecondAlarmConditions"
    type="xtce:AlarmConditionsType" minOccurs="0"/>
    </sequence>
    </complexType>
    </element>"

    To: "
    <element name="ConditionalAlarm"> <annotation>
    <documentation>…</documentation> </annotation>
    <complexType>
    <sequence>
    <element name="StaticAlarmConditions"
    type="xtce:AlarmConditionsType" minOccurs="0"/>
    </sequence>
    </complexType>
    </element>"
    Resolution: To be even clearer, we should change "StaticAlarmConditions" to simply
    "AlarmConditions". Fix schema and supporting documentation

  • Reported: XTCE 1.0 — Tue, 11 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:08 GMT

MK-010 All ParameterType and ArgumentType should have alarm element

  • Key: XTCE12-192
  • Legacy Issue Number: 9034
  • Status: open  
  • Source: jaxa.jp ( Makoto Kawai)
  • Summary:

    Source: Makoto Kawai kawai.makoto@jaxa.jp
    Description : Alarm element is just defined in Integer and Float type in ParameterType,
    ArgumentType in type[ParameterTypeSetType] and element[ArgumentTypeSet],
    but all ParameterType and ArgumentType (especially, enumerated type) are to
    have alarm element.
    Resolution: Agree, but implementation of Alarm for non-numeric types needs to be discussed

  • Reported: XTCE 1.0 — Tue, 11 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 07:02 GMT

lack of Union construct (MER + ASIST)

  • Key: XTCE12-208
  • Legacy Issue Number: 8909
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    MER supports a Union construct because their abstract data types live past decomm. ASIST also supports the same idea – that an abstract data type onboard the spacecraft MAY live past decomm. Although it is possible to let multiple parameters overlap, in a sense allowing for a Union in XTCE. The issue arises that validating software cannot differentiate this with a bug in a container specification. A union tag or element of some sort is needed.

  • Reported: XTCE 1.0b1 — Tue, 21 Jun 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 06:58 GMT

XTCE issue: dimensionList in arrayParameterRef should be optional

  • Key: XTCE12-209
  • Legacy Issue Number: 8704
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Specifying array dimension sizes in arrayParameterRef should be optional. In telemetry arrays often include an on the fly 'count' in the data packet. Therefore this may come in conflict with the fixed sizes in the dimension list.

    The other option is to clearly state in the annotation that the dimensionList is mearly an hint to the run-time software and more more processing will need to be done to ascertain the true size.

    Finally, a further option would be to have the dimensionList optionally look up the dimension size using a InstanceRef to another parameter in the data stream...

  • Reported: XTCE 1.0b1 — Tue, 26 Apr 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 06:58 GMT

inability to describe sets of limits (alarms) and conversions (polynomials)

  • Key: XTCE12-210
  • Legacy Issue Number: 8908
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    inability to describe sets of limits (alarms) and conversions (polynomials) and then select a set per parameter depending on mission phase (JWST)

    JWST hold conversion and limits in a seperate file that are grouped. Certains "sets" can be used for different mission phases such as test, on-orbit and so on, or for any reason deemed appropriate. XTCE allows one to specify at MOST one of each of these per parameterType

  • Reported: XTCE 1.0b1 — Tue, 21 Jun 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 06:57 GMT

repeat of arguments issue

  • Key: XTCE12-211
  • Legacy Issue Number: 8886
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    The following command makes use of a repeat block of arguments:

    ack_packets ( num_acks, ack_block )

    Ack_block consists of three arguments: pkt_start, pkt_end and pkt_time

    This would be a perfectly valid command:

    ack_block[0].pkt_start = 1
    ack_block[0].pkt_end = 1
    ack_block[0].pkt_time = 00:00:00

    ack_packets ( 1, ack_block )


    This is not capturable in XTCE because there is no mechanism for having REPEATS of ARGUMENTS.

    There are workarounds but there are less than ideal, they are:

    – use an array, this is problematic because the types of each sub-field may be different (see above, pkt_time is a TIME type)
    – treat them as parameters... which they are not...

  • Reported: XTCE 1.0b1 — Tue, 28 Jun 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 06:57 GMT

XTCE issue - add shortDescription to EntryList entries

  • Key: XTCE12-212
  • Legacy Issue Number: 8703
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Items in entryList should each have their own optional shortDescription attribute for documentation at each entry of the container itself.

  • Reported: XTCE 1.0b1 — Tue, 26 Apr 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 06:57 GMT

AO-006 Additional examples (2)

  • Key: XTCE12-193
  • Legacy Issue Number: 9033
  • Status: open  
  • Source: Anonymous
  • Summary:

    Source: Amalaye Oyake amalaye.oyake@jpl.na
    Description : Future examples should demonstrate onboard EH&A and Event Reporting (EVR)
    translation to an XTCE compliant XML document. Telemetry contains EH&A and
    EVR information. This information can be translated into an XTCE compliant
    document when downlink is complete.
    Resolution: It is generally agreed that a CCSDS green book (or equivalent) should be written for
    XTCE, however, no timelime has been established.

  • Reported: XTCE 1.0 — Tue, 11 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 06:56 GMT

MK-003 A mistake of type[ContainerSegmentRefEntryType]'s annotation

  • Key: XTCE12-194
  • Legacy Issue Number: 9032
  • Status: open  
  • Source: Anonymous
  • Summary:

    Source: Makoto Kawai kawai.makoto@jaxa.jp
    Description : The annotation of type[ContainerSegmentRefEntryType] is to be changed as
    below.

    From: "An Entry ... order=0" To: "An Entry ... portion of a container. It is assumed

  • Reported: XTCE 1.0 — Tue, 11 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 06:56 GMT

MK-001 A mistake of attribute[messageRef]'s annotation

  • Key: XTCE12-199
  • Legacy Issue Number: 9031
  • Status: open  
  • Source: Anonymous
  • Summary:

    Source: Makoto Kawai kawai.makoto@jaxa.jp
    Description : The annotation of attribute[messageRef] in type[MessageRefType] is to be
    changed as below.

    From: "name of container"
    To: "name of message"

  • Reported: XTCE 1.0 — Tue, 11 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 06:56 GMT

"Foreword", 2nd last line

  • Key: XTCE12-196
  • Legacy Issue Number: 9027
  • Status: open  
  • Source: Anonymous
  • Summary:

    Description : From: "support of all phases of the satellite"
    To: "support all phases of the satellite"

  • Reported: XTCE 1.0 — Tue, 11 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 06:56 GMT

Contents"

  • Key: XTCE12-197
  • Legacy Issue Number: 9026
  • Status: open  
  • Source: Anonymous
  • Summary:

    Contents listing is incomplete - "Foreword", "Introduction" and section "1 Scope"
    are all missing

  • Reported: XTCE 1.0 — Tue, 11 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 06:56 GMT

"Command Processing" box

  • Key: XTCE12-202
  • Legacy Issue Number: 9025
  • Status: open  
  • Source: Anonymous
  • Summary:

    Should "deramdomization" be de-randomisation" with an 'n' and an 's'?

  • Reported: XTCE 1.0 — Tue, 11 Oct 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 06:56 GMT

Spec too complex?

  • Key: XTCE12-201
  • Legacy Issue Number: 8962
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Too complex, ( I have some examples from the ASIST meeting ).

  • Reported: XTCE 1.0 — Fri, 5 Aug 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 06:56 GMT

USE CCSDS examples how to use the standard

  • Key: XTCE12-203
  • Legacy Issue Number: 8961
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    USE CCSDS examples how to use the standard ( we can provide data set with tlm & commnad)

  • Reported: XTCE 1.0 — Fri, 5 Aug 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 06:56 GMT

too much leeway how to use the standard

  • Key: XTCE12-206
  • Legacy Issue Number: 8960
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Ambiguity - The is too much leeway how to use the standard, and things are left for interpretation. The standard allows / calls for users to add thier own items when they are missing. Need to tighten the standard so things will be done consistently

  • Reported: XTCE 1.0 — Fri, 5 Aug 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 06:56 GMT

Propose that XCTE ( at this point ) will be limited to exchange data

  • Key: XTCE12-204
  • Legacy Issue Number: 8959
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    Propose that XCTE ( at this point ) will be limited to exchange and not to all mission data

  • Reported: XTCE 1.0 — Fri, 5 Aug 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 06:56 GMT

Xpath:

  • Key: XTCE12-205
  • Legacy Issue Number: 8927
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    – Xpath: xpath is the XML answer to unix-style paths but includes MATCHING, the ability really to get some chunk of any XML document using an Xpath expression. We should consider Xpath as the format for Refs... but there needs to be a technical debate.

    "... A reference to a Parameter. Uses Unix ‘like’ naming across the
    > SpaceSystem Tree (e.g., SimpleSat/Bus/EPDS/BatteryOne/Voltage). To
    > reference an individual member of an array use the zero based bracket
    > notation commonly used in languages like C, C++, and Java."

  • Reported: XTCE 1.0b1 — Wed, 6 Jul 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 06:56 GMT

command side unable to describe "packed commands"

  • Key: XTCE12-207
  • Legacy Issue Number: 8907
  • Status: open  
  • Source: NASA ( Kevin Rice)
  • Summary:

    command side unable to describe "packed commands" where multiple commands are packed into a single packet (MER)

    It isn't clear metacommand which itself represents a command in XTCE can package more than one command. Essentially this is multiple commands stuffed in a single packet

  • Reported: XTCE 1.0b1 — Tue, 21 Jun 2005 04:00 GMT
  • Updated: Fri, 27 Nov 2015 06:56 GMT