From: Tim_Ellison@oti.com (Tim Ellison OTT) To: esedlar@us.oracle.com (Eric Sedlar), jamsden@us.ibm.com (jamsden) Cc: ietf-dav-versioning@w3.org (ietf-dav-versioning) Message-ID: <1999Dec08.110205.1250.1410702@otismtp.ott.oti.com> Date: Wed, 08 Dec 1999 11:02:26 -0500 Subject: Re: Baselines vs. labels <eric> >I don't see much utility for baselines if you can never >change the revision of a particular file in a baseline. </eric> It gives reproducibility/versioning at a macro level. <eric> <snip ... "performance benefits" ... "baseline configuration" ... > >If you want to prevent baseline configurations from being >changed, use access control. </eric> That doesn't give you version control, which is the objective. <eric> >Is the reason you consider labels less "reliable" than configurations due to >the assumption that you are protecting them with access control on a bunch of >different resources rather than access control on a single resource? > >Also, can an administrator rename baselines? </eric> My understanding was that administrators could not rename baselines (any more than they can rename revisions). <eric/><snip ... example >