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

RE: Postconditions with no XML elements defined?

From: Clemm, Geoff <gclemm@rational.com>
Date: Wed, 11 Jul 2001 14:44:25 -0400
Message-ID: <3906C56A7BD1F54593344C05BD1374B1038E206A@SUS-MA1IT01>
To: ietf-dav-versioning@w3.org
Those postconditions should each have a token defined for them.
I'll give them each one.  Thanks for noticing that!


-----Original Message-----
From: Peter Raymond [mailto:Peter.Raymond@merant.com]
Sent: Monday, July 09, 2001 11:39 AM
To: ietf-dav-versioning@w3.org
Subject: Postconditions with no XML elements defined?

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
But several Postconditions in the specification do not have any XML elements
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
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. 
Peter Raymond - MERANT 
Technical Architect (ADM) 
Tel: +44 (0)1727 813362 
Fax: +44 (0)1727 869804 
WWW: http://www.merant.com 
Received on Wednesday, 11 July 2001 14:37:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:47 UTC