COPY semantics

From: Tim Ellison/OTT/OTI (Tim_Ellison@oti.com)
Date: Mon, Apr 03 2000

  • Next message: Tim Ellison/OTT/OTI: "Stable URLs"

    To: ietf-dav-versioning@w3.org
    Message-ID: <OF13E682AD.26BED8A0-ON852568B6.00695085@ott.oti.com>
    From: "Tim Ellison/OTT/OTI" <Tim_Ellison@oti.com>
    Date: Mon, 3 Apr 2000 15:15:43 -0400
    Subject: COPY semantics
    
    (I've posed this question before, but it didn't get much discussion...)
    
    What does COPY mean for a versioned resource?
    
    Options might be:
    (1) create a new versioned resource at the destination whose initial
    revision is the same as the revision selected by the source,
    (2) copy all the history of the source to a new versioned resource at the
    destination,
    (3) make a new unversioned resource that has looks like the selected source
    (i.e., looses it's versioned status).
    
    Then how does that differ if the selected resource is a working resource?
    We disallow a working resource without a corresponding versioned resource
    with at least an initial revision.
    Option (1) seems the most likely candidate to me.
    
    Tim