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

RE: bind draft issues

From: Clemm, Geoff <gclemm@rational.com>
Date: Mon, 3 Mar 2003 15:47:32 -0500
Message-ID: <E4F2D33B98DF7E4880884B9F0E6FDEE25ED6CA@SUS-MA1IT01>
To: WebDAV <w3c-dist-auth@w3.org>

I do not understand what you mean by a URL having a
property.  A URL is just a string.  It has no properties,
no state, nothing other than a sequence of characters.
A URL is mapped by a server to a resource, and that 
resource has state.

A lock can "protect" a URL mapping, but that does not
give a URL a WebDAV property.

So at least as far as bindings are concerned, I feel
that 2518 does fully specify the behavior of the
properties defined by 2518.

Cheers,
Geoff



-----Original Message-----
From: Brian Korver [mailto:briank@xythos.com]
Sent: Monday, March 03, 2003 2:12 PM
To: WebDAV
Subject: Re: bind draft issues



On Saturday, March 1, 2003, at 06:27  AM, Clemm, Geoff wrote:
>
>    From: Brian Korver [mailto:briank@xythos.com]
>
>    URL Properties
>
>    The behavior of other URL properties (in addition to
>    locks) should be fully specified, for instance the
>    display-name property.
>
> I'm not aware of the binding protocol causing any change
> to the behavior of the properties defined by 2518.  Also
> note that a resource has properties, not a URL.

Geoff,

URLs have properties to.  Think about how DAV:lockdiscovery
works in the face of COPY/MOVE, or DAV:displayname for that
matter.

Regarding this issue, I was not suggesting that the problem
is that the binding protocol changed the behavior of properties,
just that the behavior needs to be fully specified.  Do
you feel that 2518 does fully specify the behavior of
URL properties?

-brian
briank@xythos.com
Received on Monday, 3 March 2003 15:48:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:02 GMT