W3C home > Mailing lists > Public > www-xkms@w3.org > September 2002

Issue 20 - redesign of status

From: Hallam-Baker, Phillip <pbaker@verisign.com>
Date: Wed, 25 Sep 2002 14:08:36 -0700
Message-ID: <2F3EC696EAEED311BB2D009027C3F4F40E6B2473@vhqpostal.verisign.com>
To: www-xkms@w3.org
 
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 -->
Received on Wednesday, 25 September 2002 17:06:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:39:17 GMT