Re: WeDAV Versioning Summary - Mutability
Geoffrey M. Clemm (gclemm@tantalum.atria.com)
Fri, 21 May 1999 23:23:08 -0400
Date: Fri, 21 May 1999 23:23:08 -0400
Message-Id: <9905220323.AA05794@tantalum>
From: "Geoffrey M. Clemm" <gclemm@tantalum.atria.com>
To: ietf-dav-versioning@w3.org
In-Reply-To: <3FF8121C9B6DD111812100805F31FC0D0879322B@RED-MSG-59> (message
Subject: Re: WeDAV Versioning Summary - Mutability
In the protocol, the "mutable revision" notion only appears as two
additional values for the DAV:checkin-policy property. These two
values are DAV:mutable (i.e. create the new revision as mutable) and
DAV:replace (i.e. overwrite the predecessor instead of creating a
new revision).
This concept was heavily lobbied by the document management
representative on the design team. Since the document management
world has a good deal of experience with "lightweight versioning",
I'd like to accomodate their requests when it doesn't introduce
excessive complexity. Assuming it continues to just require these
two additional values for a property, I'd vote to keep it in
(btw, our server like most CM servers will just fail any request
to check-in mutable).
Cheers,
Geoff
From: Yaron Goland <yarong@microsoft.com>
I am having trouble reconciling the following two sentences:
"A checked in revision cannot be modified by anyone at any time."
and
"A revision may be checked in as mutable or immutable."
I find the whole issue of mutable to be...strange and out of scope for a
versioning system. I believe we produce real value if the WebDAV versioning
specification can just provide for versioning support, as widely accepted
and implemented, and deal with this "mutable" concept in an add-on
specification.