Member names of a configuration
Geoffrey M. Clemm (gclemm@tantalum.atria.com)
Fri, 7 May 1999 12:27:20 -0400
Date: Fri, 7 May 1999 12:27:20 -0400
Message-Id: <9905071627.AA08683@tantalum>
From: "Geoffrey M. Clemm" <gclemm@tantalum.atria.com>
To: ietf-dav-versioning@w3.org
Subject: Member names of a configuration
Just to make sure we're all on the same page, I wanted to make sure
we all understand/agree that in order to allow collection revisions
in a configuration, the internal member names of a configuration
must be the versioned-resource-id, not some user meaningful name
for the revision.
For example, if you have a configuration with the URL:
/repo/configs/C1
that contains revisions of:
/A/
/A/A/
/A/A/test.html
then the configuration collection contains members named something like
VR-23
VR-97
VR-128
and *not* members named things like "A" or "test.html". In particular,
the URL for the revision selected by C1 for /A/ is:
/repo/configs/C1/VR-23
and *not* something like
/repo/configs/C1/A/
So the namespace of the configuration collection does *not* mimic or
simulate the namespace that would appear in a workspace that had
that configuration in its revision selection rule. So although a
configuration collection provides a namespace (which it must, since
all collections give names to their members), it does *not* provide
a user meaningful namespace.
Cheers,
Geoff