Next message: Clemm, Geoff: "MKRESOURCE vs. MKACTIVITY and MKWORKSPACE"
To: ietf-dav-versioning@w3.org
Message-ID: <OF73B61ED9.C4AF5D6B-ON852568B9.00501383@ott.oti.com>
From: "Tim Ellison/OTT/OTI" <Tim_Ellison@oti.com>
Date: Thu, 6 Apr 2000 10:38:00 -0400
Subject: Re: Stable URL's for working resources?
I feel like I'm being awkward today...
Working resources are first class resources, they have an identity, and
thereby a Stable URL.
I vote that we keep it.
Regards,
Tim
p.s. Although the resource is mutable, that means its contents/members
change -- the working resource itself (i.e., the 'thing' that is in a
checked-out state) is persistent and uniquely identifiable.
"Clemm, Geoff"
<gclemm@rational.com> To: "DeltaV (E-mail)" <ietf-dav-versioning@w3.org>
Sent by: cc:
ietf-dav-versioning-requ Subject: Stable URL's for working resources?
est@w3.org
06-04-00 12:33 AM
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