W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > October to December 2000

Re: comments on deltav-10.5 from Yaron Goland, Act One

From: Geoffrey M. Clemm <geoffrey.clemm@rational.com>
Date: Thu, 21 Dec 2000 10:23:21 -0500 (EST)
Message-Id: <200012211523.KAA07016@tantalum.atria.com>
To: ietf-dav-versioning@w3.org

Here is the response from the working group to Yaron's comments.
These changes appear in the current (10-11) working draft.

   ------- Act I --------------

   (I.1) Get rid of DAV:must-support attribute, and instead define tokens
	 for use in an If header.


   (I.2) Add an intermediate node above any list of property names in a
	 report request or response, so that the report can be extended
	 with additional XML markup.

Done.  (I think I caught them all).

   (I.3) Add an "unknown" value for checkin-date.

The working group felt a "null" value was appropriate for this,
rather than defining an "unknown" value.

   (I.4) Require that the 403/409 response body token appear as the top
	 level element "unless explicitly negotiated otherwise", so that
	 clients get predictable behavior, but later specs can allow
	 clients to request other behavior.


   (I.5) Need to define the precondition for when cannot place a resource
	 at this place. (one per resource type).


   (I.6) Have an example show additional elements in request body being
	 ignored by the request.

This will be reflected in the "scenarios" document, since this is just
one of many interesting examples that are worth describing.

   (I.7) Add a response body to VERSION-CONTROL, so that can indicate
	 it is a no-op or not.  <DAV:already-under-control/>


   (I.8) Whenever a statement of the form "the xxx specified in the yyy
	 element" refers to an element in the request body, it should
	 explicitly say "the xxx specified in the yyy element in the
	 request body".

Done wherever there was a chance of ambiguity.

   (I.9) Indicate which live properties are controlled by a lock.

Done (in particular, every versioning live property is controlled by
a write lock).

Received on Thursday, 21 December 2000 10:24:07 UTC

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