Re: Locking a workspace

From: Geoffrey M. Clemm (geoffrey.clemm@rational.com)
Date: Wed, May 31 2000

  • Next message: Geoffrey M. Clemm: "Re: Why do we need working resource ids ?"

    Date: Wed, 31 May 2000 07:15:20 -0400 (EDT)
    Message-Id: <200005311115.HAA25097@tantalum.atria.com>
    From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
    To: ietf-dav-versioning@w3.org
    Subject: Re: Locking a workspace
    
    
       From: jamsden@us.ibm.com
    
       Sounds good to me. We have to define the merge and create baseline
       semantics for a workspace that has working resources and
       unversioned resources. I suggest merge and create baseline fails if
       there are working resources, and unversioned resources are ignored.
    
    That sounds exactly right to me.
    
    Cheers,
    Geoff
    
       From: geoffrey.clemm@rational.com
    
       The proposal is to extend the notion of a workspace
       so that instead of it just being a resource that defines
       a versioned-resource to revision mappings, it is now
       a collection of versioned and unversioned resources that
       defines a versioned-resource to revision mapping for the
       versioned resource members of that collection.
    
       This extension provides a mechanism for a workspace to
       contain unversioned resources that are local to that workspace
       (for derived and temporary resources that are not valid
       outside that workspace).
    
       The collection is not structured around a URL namespace,
       but it does define a (relative) URL namespace for its members.
    
       Cheers,
       Geoff