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


From: Yaron Goland <yarong@Exchange.Microsoft.com>
Date: Thu, 10 Feb 2000 23:47:07 -0800
Message-ID: <7DE119D3D0E15543874F7561EECBDBED0261A165@BEG.platinum.corp.microsoft.com>
To: "'w3c-dist-auth@w3.org'" <w3c-dist-auth@w3.org>
The last two sentences of the last paragraph of section 5 reads:

It creates a new binding between the new redirect reference resource and 
the last path segment of the Request-URI.  The new binding is added to 
its parent collection, identified by the Request-URI minus its trailing 
slash (if present) and final segment.

As discussed in Yaron.Redirect.NoWebDAV#1, we should make it possible to
implement redirect resources and understand the redirect resource draft
without having to resort to any draft but RFC 2616. The use above of the
term binding requires a familiarity not only with RFC 2616, but RFC 2518 as
well as the bind draft. Since the language given above just repeats the
standard behavior for any new resource created inside of a WebDAV compliant
namespace and as it is likely to confuse a reader only familiar with RFC
2616, I move that this paragraph be stricken from the spec.
Received on Friday, 11 February 2000 02:47:25 UTC

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