Next message: Geoffrey M. Clemm: "Re: Stable URL's for working resources?"
From: jamsden@us.ibm.com
To: ietf-dav-versioning@w3.org
Message-ID: <852568B9.00710061.00@d54mta03.raleigh.ibm.com>
Date: Thu, 6 Apr 2000 16:34:15 -0400
Subject: Re: Stable URL's for working resources?
I'm OK with this, but workspaces should not be concerned with
implementations that store resources locally in the client file system.
This is purely a client issue for optimizing access, supporting file-based
access to resources, and supporting disconnected work.
|------------------------+------------------------>
| | "Clemm, Geoff" |
| | <gclemm@rational.com>|
| | Sent by: |
| | ietf-dav-versioning-r|
| | equest@w3.org |
| | |
| | 04/06/2000 12:33 AM |
| | |
|------------------------+------------------------>
>------------------------|
| |
| To: |
| "DeltaV (E-mail)" |
| <ietf-dav-versioning@|
| w3.org> |
| cc: |
| Subject: |
| Stable URL's for |
| working resources? |
>------------------------|
I'd like to remove the requirement that a workspace resource provide stable
URL's for its working resources.
The problem is that many/most implementations don't store the working
resources in a repository, but rather in a simple file system tree. So
although
it is reasonable to expect an implementation to maintain stable URL's for
the versioning metadata such as revisions and activities, it is not as
reasonable
to expect it to maintain them for working resources. Since the whole
point of a working resource is for it to be mutable, requiring it to be
identifiable
via an immutable URL is not what one would expect in any case.
The only change that this requires to the protocol is to change the
definition
of the DAV:working-resources property of a workspace resource to no longer
require that the href's contain "stable URL's".
Comments?
Cheers,
Geoff