Next message: Geoffrey M. Clemm: "Re: DAV:revisions property for a workspace resource"
From: jamsden@us.ibm.com
To: ietf-dav-versioning@w3.org
Message-ID: <852568C0.004CE090.00@d54mta03.raleigh.ibm.com>
Date: Thu, 13 Apr 2000 09:59:39 -0400
Subject: Re: DAV:revisions property for a workspace resource
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. 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.
|------------------------+------------------------>
|                        |   "Clemm, Geoff"       |
|                        |   <gclemm@rational.com>|
|                        |   Sent by:             |
|                        |   ietf-dav-versioning-r|
|                        |   equest@w3.org        |
|                        |                        |
|                        |   04/12/2000 12:54 PM  |
|                        |                        |
|------------------------+------------------------>
  >------------------------|
  |                        |
  |           To:          |
  |   "DeltaV (E-mail)"    |
  |   <ietf-dav-versioning@|
  |   w3.org>              |
  |           cc:          |
  |           Subject:     |
  |   DAV:revisions        |
  |   property for a       |
  |   workspace resource   |
  >------------------------|
Jim Amsden requested that the list of revisions in a workspace
be available as a property.  I pushed back a bit by saying that
this would make label-based workspace implementations hard, since
such a workspace implementation would not know what has been labeled.
Jim responded by saying that normally the labeled revisions would
be those in a fixed number of collections, and so such an implementation
would be able to find the revisions if it remembered the list of
relevant collections.
That makes sense to me, so I propose that we do as Jim suggests, and
make the list of revisions in a workspace available as a property.
In particular, I propose that we use the DAV:revisions property,
which contains a list of stable URL's to the relevant revisions
(like the versioned resource DAV:revisions property, and the activity
DAV:revisions property).
Any objections?
Cheers,
Geoff