Issue 20 - redesign of status

 
The issues arround the redesign of status were that we wanted to have a
complete description of the reasons that were valid and invalid so that
things like the status report in Outlook still work OK.

<!-- Status -->
<element name="Status" type="xkms:StatusType"/>
<complexType name="StatusType">
    <sequence>
        <element ref="xkms:ValidReason" minOccurs="0"
maxOccurs="unbounded"/>
        <element ref="xkms:InvalidReason" minOccurs="0"
maxOccurs="unbounded"/>
        <element ref="xkms:IndeterminateReason" minOccurs="0"
maxOccurs="unbounded"/>
    </sequence>
<attribute name="StatusValue" type="xkms:KeyBindingStatus"/>
</complexType>
<simpleType name="KeyBindingStatus">
    <restriction base="QName">
        <enumeration value="xkms:Valid"/>
        <enumeration value="xkms:Invalid"/>
        <enumeration value="xkms:Indeterminate"/>
    </restriction>
</simpleType>
<!-- /Status -->

<!-- Reason -->
<element name="ValidReason" type="QName"/>
<element name="InvalidReason" type="QName"/>
<element name="IndeterminateReason" type="QName"/>
<!-- /Reason -->