W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > July to September 2002

RE: VERSION-CONTROL (6.7) vs resurrecting deleted VCRs

From: Clemm, Geoff <gclemm@rational.com>
Date: Wed, 21 Aug 2002 18:49:31 -0400
Message-ID: <3906C56A7BD1F54593344C05BD1374B107EE607B@SUS-MA1IT01>
To: "DeltaV (E-mail)" <ietf-dav-versioning@w3.org>

It probably would have made sense to make it part of the
version-history feature instead of workspace feature, but
nobody asked for it at the time (probably because most of
the people that were planning on supporting the version 
history feature were also planning on supporting the workspace
feature, so they didn't care).

But to answer your specific question, it certainly is fine for
a server to support the VERSION-CONTROL extension without
supporting the workspace feature, but it isn't something that
an interoperable client would expect.


-----Original Message-----
From: Julian Reschke [mailto:julian.reschke@greenbytes.de]
Sent: Wednesday, August 21, 2002 8:34 AM
To: DeltaV (E-mail)
Subject: VERSION-CONTROL (6.7) vs resurrecting deleted VCRs


Given a VCR a and it's VHR b. The VCR is deleted. The workspace feature
(section 6) seems to provide a way to create a new VCR whose
DAV:version-history property points to b.

Now this seems like an extremely important feature in versioning, no matter
wether the server supports the workspace feature or not. So would it be
permissible to use VERSION-CONTROL to resurrect the VCR outside a workspace
(if no other VCR for that VHR exists on the server)?


<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Wednesday, 21 August 2002 18:50:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:48 UTC