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

List of areas in the specification where properties are empty/not set

From: Peter Raymond <Peter.Raymond@merant.com>
Date: Thu, 9 Aug 2001 12:56:35 +0100
Message-ID: <20CF1CE11441D411919C0008C7C5A13B025E39B7@stalmail.eu.merant.com>
To: ietf-dav-versioning@w3.org

I raised in an earlier e-mail that the specification still talked about
being empty or not set instead of being removed.  In one of the deltav
sessions I
was asked to scour the spec and find all affected areas.
I think the list is:

Section 3.9 in the additional postconditions (DAV:auto-checkout) for PUT,
the spec 
says "the DAV:checked-in property MUST be empty". I propose it should
instead read
"the DAV:checked-in property MUST be removed".

Section 4.4 in the additional postconditions (DAV:cancel-checked-out) for
the spec says "and the DAV:checked-out property no longer is set".  I
propose it
should read "and the DAV:checked-out property is removed".

Section 11.2 the description of the MERGE method says "a version-controlled
with a non-empty DAV:merge-set". I propose it should read "a
resource with a DAV:merge-set property".

Section 11.6 in the additional preconditions (DAV:merge-must-be-complete)
the spec says "The DAV:merge-set and DAV:auto-merge-set of the checked-out
MUST be empty".  I propose it should read "The checked-out resource MUST not
have the 
DAV:merge-set or DAV:auto-merge-set properties".

Somewhere in the spec perhaps we should state that when a property is
removed from a 
resource it is no longer returned by PROPFIND or in any <DAV:prop> response
any method.

Peter Raymond - MERANT
Technical Architect (ADM)
Tel: +44 (0)1727 813362
Fax: +44 (0)1727 869804
WWW: http://www.merant.com
Received on Thursday, 9 August 2001 07:57:16 UTC

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