Re: DAV:revisions property for a workspace resource

From: Geoffrey M. Clemm (geoffrey.clemm@rational.com)
Date: Thu, Apr 13 2000

  • Next message: Geoffrey M. Clemm: "working resource DAV:merge-state property?"

    Date: Thu, 13 Apr 2000 11:35:57 -0400 (EDT)
    Message-Id: <200004131535.LAA13915@tantalum.atria.com>
    From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
    To: ietf-dav-versioning@w3.org
    Subject: Re: DAV:revisions property for a workspace resource
    
    
       From: jamsden@us.ibm.com
    
       Maybe a workspace should just be a collection? Note that if we do
       this, and have workspace revisions play the role of
       configurations/baselines, then you wouldn't be able to have
       configurations/workspace without versioned collections unless the
       server did special cases for workspaces.
    
    I guess we could do that if we *really* wanted to confuse people (:-).
    
       It really does seem that a
       workspace is a container of references to revisions and working
       resources. This sure sounds like members of a collection, not
       properties of a resource.
    
    A collection gives a binding name (a URL segment) to members of a
    single set.  A workspace has two sets of objects, one of which it
    contains (working resources) and one of which it just refers to
    (revisions), and it does not associate a binding name with members of
    either of these sets.  Doesn't sound like a good fit to me.
    
    Cheers,
    Geoff