XTCE12 — Missed DynamicValue in the PercentCompleteType from the proposal

The latest draft of the 1.2 schema included a change of the primitive type for the FixedValue element but did not include the DynamicValue element that was proposed.

Propose to merge in the DynamicValue to PercentCompleteType

The proposed schema also includes a DynamicValue element. In order to incorporate this, the PercentCompleteType should be updated to replace this existing definition:

<complexType name="PercentCompleteType">
<annotation>
<documentation>Describe a percentage complete that is fixed from 0 to 100, or as value from a parameter. See ExecutionVerifierType.</documentation>
</annotation>
<choice>
<element name="FixedValue">
<annotation>
<documentation>0 to 100 percent</documentation>
</annotation>
<simpleType>
<restriction base="double">
<minInclusive value="0.0"/>
<maxInclusive value="100.0"/>
</restriction>
</simpleType>
</element>
</choice>
</complexType>

With a new definition of:

<complexType name="PercentCompleteType">
<annotation>
<documentation xml:lang="en">Describe a percentage complete that is fixed from 0 to 100, or as value from a parameter. See ExecutionVerifierType.</documentation>
</annotation>
<choice>
<element name="FixedValue">
<annotation>
<documentation xml:lang="en">0 to 100 percent</documentation>
</annotation>
<simpleType>
<restriction base="double">
<minInclusive value="0.0"/>
<maxInclusive value="100.0"/>
</restriction>
</simpleType>
</element>
<element name="DynamicValue" type="xtce:DynamicValueType">
<annotation>
<documentation xml:lang="en">Uses a parameter instance to obtain the value. The parameter value may be optionally adjusted by a Linear function or use a series of boolean expressions to lookup the value. Anything more complex and a DynamicValue with a CustomAlgorithm may be used.</documentation>
</annotation>
</element>
</choice>
</complexType>