Stable URL's for working resources?

From: Clemm, Geoff (gclemm@Rational.Com)
Date: Thu, Apr 06 2000

  • Next message: Clemm, Geoff: "RE: Stable Href's of collections"

    Message-ID: <65B141FB11CCD211825700A0C9D609BC025FA321@chef.lex.rational.com>
    From: "Clemm, Geoff" <gclemm@Rational.Com>
    To: "DeltaV (E-mail)" <ietf-dav-versioning@w3.org>
    Date: Thu, 6 Apr 2000 00:33:43 -0400 
    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