Message-ID: <65B141FB11CCD211825700A0C9D609BC0252B768@chef.lex.rational.com> From: "Clemm, Geoff" <gclemm@Rational.Com> To: ietf-dav-versioning@w3.org Date: Sat, 1 Apr 2000 00:35:47 -0500 Subject: RE: WebDAV Versioning Scenarios From: jamsden@us.ibm.com [mailto:jamsden@us.ibm.com] I think we need to describe checkin as keeping the checked in resource in the workspace until the next refresh so they don't disappear. It seems that any technique of refreshing a workspace will have the problem that if the revisions that you select aren't labeled properly or in the right activity or configuration, you might not get the revision you wanted. I don't think this is unique to using a workspace RSR to specify the revisions to select on refresh although it may require an extra step to update the rule before the refresh. I think this is a benefit though. That's a good point. The need for DAV:current-revision and DAV:current-label really resulted from dynamic revision selection, not from having a revision selection rule. We do still have to give core versioning clients a way to specify the "default" revision (i.e. some SET-DEFAULT-REVISION method). Cheers, Geoff