Versioning TeleConf Agenda, 5/3/99 (Monday) 2-3pmEST
Geoffrey M. Clemm (gclemm@tantalum.atria.com)
Mon, 3 May 1999 10:49:37 -0400
Date: Mon, 3 May 1999 10:49:37 -0400
Message-Id: <9905031449.AA06708@tantalum>
From: "Geoffrey M. Clemm" <gclemm@tantalum.atria.com>
To: ietf-dav-versioning@w3.org
Subject: Versioning TeleConf Agenda, 5/3/99 (Monday) 2-3pmEST
phone: 888 819 8909 pass-code#97985
Agenda:
- Configurations and Snapshots
I believe we are close to finishing this topic (one can always hope :-).
In particular, I believe the following proposal captures the current
thinking on the topic:
* a configuration is a versioned-resource
* a revision of a configuration is called a snapshot
* a snapshot has a DAV:scope property containing a list of URL's.
* the DAV:scope property can be modified in a checked-out configuration
* a snapshot has an associated list of revisions, specified at CHECKIN time
by selecting a revision of each URL in the DAV:scope, and a revision
of each internal member of each versioned-collection revision in the list.
* the revisions associated with a snapshot are selected from the current
workspace.
I believe the major unresolved issue is how to provide a "lightweight"
way of producing new snapshots, for clients that just want to say
"take the predecessor snapshot but use these particular revisions instead".
I believe that an interoperable way of achieving this is to have
such a client checkout the configuration into a "configuration workspace",
enumerate the revisions to be changed (with a PROPATCH to the DAV:rsr),
and then issue the CHECKIN.
Hopefully Chris will be available today to discuss this proposal.
And then just in case we have more time:
- Repositories
This is the resource type that contains a set of versioned-resources,
activities, and configurations. I have proposed that we represent the
resources in the repository as property-collections of the repository.
This I'm sure will be an interesting topic.
Cheers,
Geoff