XTCE12 — Derived Issue: Update string alarm definition types

This new issue is derived from existing issues because it is not possible to attach more than 1 resolution to an issue.

Update alarm type for string alarm definitions

This is the second resolution for the alarm definition issues. The overall resolution is broken up into several smaller resolutions for ease of review.

In the complexType "StringAlarmLevelType", first replace the documentation element in the annotations with the following update.

<documentation xml:lang="en">Describe a string alarm condition based on matching a regular expression. The level and regular expression are described. The specific implementation of the regular expression syntax is not specified in the schema at this time. See StringAlarmListType.</documentation>

Next, in the complexType "StringAlarmListType", add a new annotation element and documentation where it did not exist previously. The type definition with the annotation/documentation elements added is below.

<complexType name="StringAlarmListType">
<annotation>
<documentation xml:lang="en">Describe an ordered collection of string alarms, where duplicates are valid. Evaluate the alarms in list order. The first to evaluate to true takes precedence. See StringAlarmLevelType.</documentation>
</annotation>
<sequence>
<element name="StringAlarm" type="xtce:StringAlarmLevelType" maxOccurs="unbounded"/>
</sequence>
</complexType>

Next, replace the existing definition complexType for "StringAlarmType" with the following definition.

<complexType name="StringAlarmType">
<annotation>
<documentation xml:lang="en">Describe alarms specific to the string data type, extends the basic AlarmType, while adding a StringAlarmList and defaultAlarmLevel attribute. The string alarm list is evaluated in list order. See ConcernsLevelsType and StringAlarmListType.</documentation>
</annotation>
<complexContent>
<extension base="xtce:AlarmType">
<sequence>
<element name="StringAlarmList" type="xtce:StringAlarmListType" minOccurs="0"/>
</sequence>
<attribute name="defaultAlarmLevel" type="xtce:ConcernLevelsType" default="normal"/>
</extension>
</complexContent>
</complexType>

In the complexType "StringContextAlarmType", add a new annotation/documentation element as shown in the complexType below. The type already exists, just the annotation is needed.

<complexType name="StringContextAlarmType">
<annotation>
<documentation xml:lang="en">Describe a context that when true the alarm may be evaluated. See ContextMatchType and StringAlarmType.</documentation>
</annotation>
<complexContent>
<extension base="xtce:StringAlarmType">
<sequence>
<element name="ContextMatch" type="xtce:ContextMatchType"/>
</sequence>
</extension>
</complexContent>
</complexType>

In similar fashion to the above, add a new annotation/documentation element to the complexType "StringContextAlarmListType" as described below. The type already exists, but the annotation does not.

<complexType name="StringContextAlarmListType">
<annotation>
<documentation xml:lang="en">An ordered collection of numeric alarms associated with a context. Process the contexts in list order. See StringContextAlarmType.</documentation>
</annotation>
<sequence>
<element name="ContextAlarm" type="xtce:StringContextAlarmType" maxOccurs="unbounded"/>
</sequence>
</complexType>