W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 1998

Comments on draft-ietf-webdav-protocol-06.txt

From: Ralph R. Swick <swick@w3.org>
Date: Thu, 12 Feb 1998 03:05:28 -0500
Message-Id: <>
To: w3c-dist-auth@w3.org
7.1: Are there any atomicity guarantees for PROPFIND?  Section 8.3 could be
interpreted as applying only to depthwise operations.  For depth 0 PROPFIND,
a client should have a way to know that, for example, the values of all
the live properties in a reply were valid taken as a whole at some instant.
If such a guarantee is not provided, clients may resort to abusing the lock

7.10: The requirement that a COPY be octet-for-octet identical is overly
restrictive.  This prevents, for example, an intelligent HTML copy that
fixes relative links in the content such that they continue to work from
the location of the copy.

12.12.1:  Is it the intention of this protocol to not allow a server to support
different lock types in different parts of its namespace?


In 2.4 the value of a property is described as being a well-formed XML *document*.
However, it is the response to each method that is the well-formed document;
the value of each returned property (e.g. in PROPFIND) is just well-formed XML.
Received on Thursday, 12 February 1998 03:12:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:13 UTC