XTCE13 — Simplify/align alarm severities across OMG specifications

To align with other specifications within the OMG and AstroUXDS guidance, deprecate the watch and severe alarm severity levels.

Deprecated Down to 4 Alarm Concern Levels

This resolution follows up with the June 2024 technical meeting agreements. The number of concern levels will decrease to 4 in a later XTCE specification, but at present we retain backwards compatibility. We express our intentions in the annotation for the end users.

Note that the deprecated is introduced inside the enumerations as Ithe author has observed that to be done in other contexts.

Previous ConcernLevelsType:

<simpleType name="ConcernLevelsType">
<annotation>
<documentation xml:lang="en">Defines six levels: Normal, Watch, Warning, Distress, Critical and Severe, in that order of concern from least to most. These level definitions are used throughout the alarm definitions. An implementation should interpret these as best to match their uniqueness and provide documentation on how this standard maps to their implementation. Not all are likely to be provided, with some either ignored, promoted or demoted to others, or warned on input. There exist some reasonable usage recommendations in the user community.</documentation>
</annotation>
<restriction base="string">
<enumeration value="normal"/>
<enumeration value="watch"/>
<enumeration value="warning"/>
<enumeration value="distress"/>
<enumeration value="critical"/>
<enumeration value="severe"/>
</restriction>
</simpleType>

Proposed ConcernLevelsType:

<simpleType name="ConcernLevelsType">
<annotation>
<documentation xml:lang="en">Defines six levels: Normal, Watch, Warning, Distress, Critical and Severe, in that order of concern from least to most. These level definitions are used throughout the alarm definitions. An implementation should interpret these as best to match their uniqueness and provide documentation on how this standard maps to their implementation. Not all are likely to be provided, with some either ignored, promoted or demoted to others, or warned on input. There exist some reasonable usage recommendations in the user community.</documentation>
</annotation>
<restriction base="string">
<enumeration value="normal">
<annotation>
<documentation xml:lang="en">The case of "normal" or "no concern level" is generally the default. This value can be useful when describing an exception or disabling when the more typical case is a non-normal concern level.</documentation>
</annotation>
</enumeration>
<enumeration value="watch">
<annotation>
<documentation xml:lang="en">DEPRECATED: The lowest level of concern. Systems that support only 3 or 4 concern levels have been observed to promote "watch" to "warning" during data processing, if this enumeration is not explicitly supported. This value may not exist in future versions of this specification.</documentation>
</annotation>
</enumeration>
<enumeration value="warning">
<annotation>
<documentation xml:lang="en">A level of concern to be interpreted by the user as less than the highest possible concern. This is intended by the specification to be quite vague. The project operational concept will explicitly define how these are to be used.</documentation>
</annotation>
</enumeration>
<enumeration value="distress">
<annotation>
<documentation xml:lang="en">A level of concern to be interpreted by the user as greater than the least concern but not yet rising to the highest possible concern. This is intended by the specification to be quite vague. The project operational concept will explicitly define how these are to be used.</documentation>
</annotation>
</enumeration>
<enumeration value="critical">
<annotation>
<documentation xml:lang="en">A level of concern to be interpreted by the user as the highest possible concern. This is intended by the specification to be quite vague. The project operational concept will explicitly define how these are to be used.</documentation>
</annotation>
</enumeration>
<enumeration value="severe">
<annotation>
<documentation xml:lang="en">DEPRECATED: The highest level of concern. Systems that support only 3 or 4 concern levels have been observed to demote "severe" to "critical" during data processing, if this enumeration is not explicitly supported. This value may not exist in future versions of this specification.</documentation>
</annotation>
</enumeration>
</restriction>
</simpleType>