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


From: Peter Raymond <Peter.Raymond@merant.com>
Date: Thu, 24 Jan 2002 14:12:22 -0000
Message-ID: <20CF1CE11441D411919C0008C7C5A13B03BF6350@stalmail.eu.merant.com>
To: "Kirmse, Daniel" <daniel.kirmse@sap.com>, "Ietf-Dav-Versioning (E-mail)" <ietf-dav-versioning@w3.org>

[Daniel said:]
>For COPY I'd expect to got a new VCR at the destination with an exact copy
>of properties. This implies that the new created VCR must share the
>version-history with the source VCR. Is this correct? Is this desirable?

I think this is desirable and correct but with one caveat...

Both in section 1.3 (where the workspace term is defined) and in section 6
the DeltaV specification says that you can only have one VCR for a given
version history in a workspace.  If copy created a new VCR but pointed to
the original VHR then this rule could be violated if the destination is in
the same workspace as the source of the copy.
If the copy does not break this rule then it would be fine to have two VCRs
pointing to the same version history.

I certainly wouldn't have thought that moving a VCR would create a new
history resource.
Peter Raymond - MERANT
Principal Architect (PVCS)
Tel: +44 (0)1727 813362
Fax: +44 (0)1727 869804
WWW: http://www.merant.com

-----Original Message-----
From: Kirmse, Daniel [mailto:daniel.kirmse@sap.com]
Sent: 24 January 2002 13:56
To: Ietf-Dav-Versioning (E-mail)
Subject: COPY, MOVE and VCR's


I wonder what happens when I copy or move a VCR? 
Defining this behavior as not expected by the user, I'd say COPY means
creation of a new version-history and copy of the checked-in version to that
new VH. With that the checked-in property of the copied VCR must change.
Same for MOVE except for the deletion of the source. 

Received on Thursday, 24 January 2002 09:15:57 UTC

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