Re: Repository -- do we need it?
Geoffrey M. Clemm (gclemm@tantalum.atria.com)
Mon, 3 May 1999 21:34:30 -0400
Date: Mon, 3 May 1999 21:34:30 -0400
Message-Id: <9905040134.AA06937@tantalum>
From: "Geoffrey M. Clemm" <gclemm@tantalum.atria.com>
To: sv@hunchuen.crystaliz.com
Cc: ietf-dav-versioning@w3.org
In-Reply-To: <00c801be958a$8323a790$d0acddcf@crystaliz.com>
Subject: Re: Repository -- do we need it?
From: "Sankar Virdhagriswaran" <sv@hunchuen.crystaliz.com>
> > - 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.
Just so I am not confused, are repositories and workspaces the same
things or are workspaces what a user's view is and repositories are
where centralized data (of the above kind) kept?
The latter. A workspace provides a "version-selection" mechanism that
maps from versioned-resources to revisions and working-resources. A
repository holds the versioned-resources, activities, configurations,
and workspaces.
And, what are property-collections?
A property collection is just a property whose value is the URL of a
collection, where that URL is specified by the server, not the client.
Cheers,
Geoff