Next message: Geoffrey M. Clemm: "Versioning TeleConf Agenda, 9/22/00 (Friday) 11am-noon/EST"
Message-ID: <3906C56A7BD1F54593344C05BD1374B10D9E85@SUS-MA1IT01>
From: "Clemm, Geoff" <gclemm@rational.com>
To: ietf-dav-versioning@w3.org
Date: Wed, 20 Sep 2000 16:39:20 -0400
Subject: RE: Comments on 08.1
Well, I was going to allow it on a working resource, so that you
could store it in a version, and then use it to initialize the
DAV:auto-version property of a new version selector that initially
selects that version.
I'll admit that this is a pretty obscure case, but since it is
simpler to just allow it on a working resource, it seemed reasonable
to do so, rather than requiring that a working resource not have
a DAV:auto-version property.
Cheers,
Geoff
-----Original Message-----
From: Boris Bokowski/OTT/OTI [mailto:Boris_Bokowski@oti.com]
Sent: Wednesday, September 20, 2000 4:24 PM
To: ietf-dav-versioning@w3.org
Subject: Re: Comments on 08.1
Good point. But then section 5.4 should be changed; in its current form it
says that a working resource has all the properties of a checked out
version selector (which would include DAV:auto-version).
> 5.3.4 DAV:auto-version
> This property only makes sense for a checked in version selector.
>
> If a user can modify this property, you probably don't want it
> disappearing (and needing to be re-set) when you checkout the version
> selector, so having it on the checked-out version selector is probably
> best.