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

My third issue

From: merlin <merlin@baltimore.ie>
Date: Thu, 12 Dec 2002 13:38:40 +0000
To: www-xkms@w3.org
Message-Id: <20021212133840.C1C2443C61@yog-sothoth.ie.baltimore.com>


I meant to send this issue earlier, but:

In X-BULK we had a StatusRequest / StatusResult message
set that allowed a server to query the state of an outstanding
batch without grabbing the entire result. Now that we have
compound in XKMS, do we want StatusRequest/StatusResult messages?

I would envision something like HTTP HEAD - it returns detail
to the level of ResultAbstractType; i.e., ResultMajor/Minor.
This would allow a workflowy-type system to easily find the
status of a request. When requesting the status of a batch,
the same level of detail is returned for each individual req
in the batch.

        <element name="StatusRequest" type="xkms:StatusRequestType"/>
        <complexType name="StatusRequestType">
                        <extension base="xkms:RequestAbstractType">
                                <attribute name="ResponseId" type="anyURI" use="optional"/>

        <element name="StatusResult" type="xkms:StatusResultType"/>
        <complexType name="StatusResultType">
                        <extension base="xkms:ResultAbstractType"/>

        <!-- Status of a compound request -->
        <complexType name="CompoundStatusResultType">
                        <extension base="xkms:StatusResultType">
                                <sequence minOccurs="0" maxOccurs="unbounded">
                                        <element ref="xkms:StatusResult"/>

We do have PendingNotification which in some sense could provide
the same level of reporting; however, it is not well defined where
StatusRequest is simple and standard.

Received on Thursday, 12 December 2002 08:39:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:31:40 UTC