W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > July to September 2001

Postconditions with no XML elements defined?

From: Peter Raymond <Peter.Raymond@merant.com>
Date: Mon, 9 Jul 2001 16:38:57 +0100
Message-ID: <20CF1CE11441D411919C0008C7C5A13B2CA654@stalmail.eu.merant.com>
To: ietf-dav-versioning@w3.org
Hi,

In section 1.6 of the specification it states:

In order to allow better client handling of 403 and 409 responses, a
distinct XML element 
type is associated with each method precondition and postcondition of a
request.

But several Postconditions in the specification do not have any XML elements
defined.

Section 8.5, 8.6, 8.7, 8.8, and 9.6 for example.  Do we need to change 1.6
to say that some
preconditions and postconditions have distinct XML elements?

Also regarding the 403/409 responses it was not clear from the spec when to
send 403
and when to send 409.  The text in section 1.6 reads:

If a method precondition for a request is not satisfied, or if a method
postcondition for a 
request cannot be achieved, the response status of the request MUST be 403
(Forbidden) 
or 409 (Conflict).

Does this mean a 403 should be sent for a failed precondition and a 409
should be sent
for a postcondition failure.  Or does it mean the server implementer can
return either code
in either situation.  This is not clear from reading the spec.

Regards,
--
Peter Raymond - MERANT
Technical Architect (ADM)
Tel: +44 (0)1727 813362
Fax: +44 (0)1727 869804
mailto:Peter.Raymond@merant.com
WWW: http://www.merant.com
Received on Monday, 9 July 2001 11:39:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:42 GMT