Next message: jamsden@us.ibm.com: "Re: Questions on activities"
Date: Fri, 21 Apr 2000 17:59:18 -0400 (EDT)
Message-Id: <200004212159.RAA26248@tantalum.atria.com>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
Subject: Re: Questions on activities
From: jamsden@us.ibm.com
I don't think the server should be making up activity (or any
resource) names. These belong to the user creating the activity or
resource. WebDAV collections were introduced to provide a mechanism
for managing namespaces. WebDAV versioning should use this
mechanism and not introduce something else.
Any resource that is commonly implemented as a row in a database (as
is often the case for an "activity") is likely to have a server
defined segment in its name. There will be client defined properties
(such as DAV:display-name), but whenever there are a large number of
objects in a single collection (such as rows in a database), it is
common for the server to assign the key, rather than the client.
Having servers define the names for members in very large collections
is in no way incompatible with the WebDAV namespace mechanism.
Cheers,
Geoff