XTCE13 — Reconsider if Specific Color Names Should be Referenced

Given that alarm consequence/significance labels are concepts and colors are implementations, should the XTCE schema refer to the colors by name? Perhaps it should refer to implementation of suggest AstroUX as a reference?

Remove implementation specific color names from the schema

It is not good practice to dictate implementation in the XTCE schema. We will remove the reference to specific color names for displays by updating the documentation and throwing a hat tip our to AstroUX for generally managing a standard for this.

Existing ConcernLevelsType:

<simpleType name="ConcernLevelsType">
<annotation>
<documentation xml:lang="en">Defines six levels: Normal, Watch, Warning, Distress, Critical and Severe. Typical implementations color the "normal" level as green, "warning" level as yellow, and "critical" level as red. These level definitions are used throughout the alarm definitions. Some systems provide a greater fidelity with the additional levels provided here. The "normal" level is not typically needed because "normal" should be construed as none of the concern levels evaluating to true. For cases where definiing "normal" is needed, refer to the specific alarm definition types.</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>

New 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>