- From: Jim Davis <jdavis@parc.xerox.com>
- Date: Mon, 14 Sep 1998 19:41:32 PDT
- To: WebDAV WG <w3c-dist-auth@w3.org>
At 06:59 PM 9/14/98 PDT, Jim Whitehead wrote: >What I read from this rough consensus on the list is people would like the >language to read that a parent of a resource does not have to be a >WebDAV-collection. However, if the parent of a WebDAV resource is itself >WebDAV compatible, then it has to be a WebDAV collection. > >A couple of questions: > >1) Should there be a policy for whether the parent of a resource must exist? >So, if http://foo/bar/blah exists, and is DAV-compliant, must resource >http://foo/bar/ exist? >.. my answer is that we shouldn't require a DAV-compliant resource to have >a parent resource. Fine with me. (Don't care much either way.) > I think we should require all collections below a DAV-compliant >resource to also be DAV-compliant. So, while it's OK to not be >DAV-compliant looking up a hierarchy tree, looking down the tree from a >DAV-compliant location should always be DAV-compliant. Strongly agree.
Received on Monday, 14 September 1998 22:41:21 UTC