XTCE 1.3 RTF Avatar
  1. OMG Issue

XTCE13 — Unecessary Sequence of choice in AlarmType

Open Closed All
  • Key: XTCE13-66
  • Status: closed  
  • Source: NASA ( Mr. James Kevin Rice)
  • Summary:

    Just a typo in the schema construction, should just be optional choice.

    <sequence>
    <choice minOccurs="0">
    <element name="AlarmConditions" type="xtce:AlarmConditionsType">
    <annotation>
    <documentation xml:lang="en">A MatchCriteria may be specified for each of the 5 alarm levels. Each level is optional and the alarm should be the highest level to test true.</documentation>
    </annotation>
    </element>
    <element name="CustomAlarm" type="xtce:CustomAlarmType">
    <annotation>
    <documentation xml:lang="en">An escape for ridiculously complex alarm conditions. Will trigger on changes to the containing Parameter.</documentation>
    </annotation>
    </element>
    </choice>
    </sequence>
  • Reported: XTCE 1.2 — Tue, 1 Oct 2019 18:22 GMT
  • Disposition: Resolved — XTCE 1.3
  • Disposition Summary:

    Correct Schema Construction For AlarmType

    The construction of the AlarmType complexType in the schema has a redundant sequence and choice model. This should be removed. There is no impact to the XTCE XML documents in this case. It appears that this is restoring XTCE v1.2 to XTCE v1.1 schema construction.

    In addition, the choice of 1 of the elements will be made required so that the parent element, which is optional, requires content if it is chosen to be included. Including an empty element does not make technical sense.
  • Updated: Tue, 1 Jul 2025 15:05 GMT