Next message: Geoffrey M. Clemm: "Re: version-name property"
Date: Fri, 25 Aug 2000 18:04:41 -0400 (EDT)
Message-Id: <200008252204.SAA05256@tantalum.atria.com>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
Subject: Re: are workspaces versionable?
From: "Boris Bokowski/OTT/OTI" <Boris_Bokowski@oti.com>
The third sentence of section 10.6.1 is "When the
baseline selector of a collection is checked out, the resulting working
baseline tracks the target of each version selector that is a member of
the collection." I would like it to keep track of the version selector of
the collection itself as well, so that the information stored in a
baseline is sufficient to reconstruct the collection.
Good point. That was what was intended, but a collection is not
normally considered to be a member of itself, so this needs to be
explicitly stated. I'll make this change.
I'm assuming that
baselines are dependent on versioned collections - is this correct?
No, baselines could be implemented by a server that does not support
versioned collections. It would have to have some other
implementation specific way of remembering what the relative name of
each version in the baseline should be with respect to the baselined
collection (so that the baseline can be used in a SET-TARGET request
to restore the collection to a previous state). The only interoperable
way of discovering those names is to set the target of the baseline
selector (this allows servers to implement baselines efficiently).
Cheers,
Geoff