Re: Baselines vs. labels
Tim Ellison OTT (Tim_Ellison@oti.com)
Mon, 06 Dec 1999 10:32:27 -0500
From: Tim_Ellison@oti.com (Tim Ellison OTT)
To: esedlar@us.oracle.com (Eric Sedlar),
Message-ID: <1999Dec06.103145.1250.1407439@otismtp.ott.oti.com>
Date: Mon, 06 Dec 1999 10:32:27 -0500
Subject: RE: Baselines vs. labels
Sure, I'll give it a shot ...
A baseline is a 'deep revision' of a collection, that is to say that it
captures not only the versioned resource identifier for each binding, but
also the revision that the binding selected in that workspace. The entire
'snapshot' of the collection is a baseline. Baselines are immutable.
If you applied label recursively you could write your client code in such a
way as to identify all the revisions reachable from the collection in the
same way, however, there woud be no single resource that represented that
'snapshot' (i.e. the labels would not be connected in any sense), other
resources would be free to have the same label even if they were not part of
your snapshot, and, perhaps most importantly, labels can move after you have
taken the snapshot and thereby change the make-up of the set of revisions.
Regards,
Tim
----------
>From: Eric Sedlar
>To: ietf-dav-versioning
>Subject: Baselines vs. labels
>Date: Saturday, December 04, 1999 3:48PM
>
><<File Attachment: HEADER.TXT>>
>Can someone give a bit of rationale for when you use baselines and when
>you use a label applied recursively to all the elements of a
>collection? Is a baseline just a specialized case of a label?
>
>
>