XTCE12 — DefaultSignicance element can have no content at all

Description Kevin Rice 2008-03-20 19:07:03 GMT
It has three attributes none of which are required and there are no defaults
for them – result: an empty DefaultSignificance can be set with NO
information. Probably true for ContextSignificance as well. At least one
attribute should be required to avoid this.

Propose to require @consequenceLevel in Significance elements

It appears that a Significance element doesn't have any actionable meaning without at least @consequenceLevel. As a result, propose to make this attribute required in the schema.

<complexType name="SignificanceType">
<annotation>
<documentation>Describe a reason (significance) of potential consequence of a MetaCommand for this or another space system. See ConcernLevelsType.</documentation>
</annotation>
<attribute name="spaceSystemAtRisk" type="xtce:NameReferenceType">
<annotation>
<documentation xml:lang="en">If none is supplied, then the current SpaceSystem is assumed to be the one at risk by the issuance of this command</documentation>
</annotation>
</attribute>
<attribute name="reasonForWarning" type="string"/>
<attribute name="consequenceLevel" type="xtce:ConcernLevelsType" use="required" default="normal"/>
</complexType>

The use="required" default="normal" for the attribute consequenceLevel is the addition to this type.