RE: Building a site progressively

From: Tim Ellison OTT (Tim_Ellison@oti.com)
Date: Wed, Feb 02 2000

  • Next message: Geoffrey M. Clemm: "Adding a DAV:default-revision property to versioned resources"

    From: Tim_Ellison@oti.com (Tim Ellison OTT)
    To: ietf-dav-versioning@w3.org ('Delta V')
    Message-ID: <2000Feb02.135000.1250.1466219@otismtp.ott.oti.com>
    Date: Wed, 02 Feb 2000 13:55:32 -0500
    Subject: RE: Building a site progressively
    
    
    <jim>
    You can use the target-selector/revision-selector to see the old versions, 
    diff them,etc. The target-selector specifies the workspace you want to use 
    and the revision-selector  provides the override, unusally a specific 
    revision label. Note that the only issues we've had with this are 1) the 
    actual names of the headers, and 2) what to do in the context of versioned 
    collections where it might be necessary to override more than just the 
    resoure bound to the leaf URL segment.
    </jim>
    
    This would work, but only for one resource at a time.  I was hoping to be 
    able to select 'arbitrary' revisions for numerous resources.
    
    <jim>
    To retain your new revision in the versioned resource history while 
    selecting an older version, you would change your workspace to include 
    (before the activity) a label on the older revision that you want to pick 
    up. Note that the workspace current activity is not automatically added to 
    the workspace revision selection rule just for this purpose. The user needs 
    to be able to determine where all revision selectors go in the revision 
    selection rule. The only implicit rule is checked-out resources are always 
    selected first.
    </jim>
    
    Using labels in this way would work too, and would allow me to label 
    multiple resources.
    This feels like a use for the "labelled configurations" that we have 
    mentioned a few times.  However, unlike a conventional configuration this 
    one is updated by the workspace when the label in the RSR is the workspace's 
    current-label.
    Maybe my RSRs should be (1) current-label and (2) baseline?
    
    <jim>
    If you want to get rid of the revision altogether, just delete it or "hop 
    over" it by checking out an older revision in the same activity and checking 
    it back in to create a new latest in the activity. We had said deleting 
    revisions might require special privliges at one time.
    </jim>
    
    I didn't want to delete it permanently, and I didn't really want to create a 
    new identical revision to make it latest.
    
    Thanks,
    Tim
    
    
    
    Tim_Ellison@oti.com (Tim Ellison OTT)@w3.org on 02/02/2000 12:34:56 PM
    
    Sent by:  ietf-dav-versioning-request@w3.org
    
    
    To:   ietf-dav-versioning@w3.org ('Delta V')
    cc:
    
    Subject:  Building a site progressively
    
    
    
    Imagine that I have a workspace selecting:
        1) my activity, or
        2) a baseline
    (and the workspace has my activity as the current activity.)
    
    This is cool because it will select new revisions that I check-in in
    preference to those from the baseline, so I get to see my changing work.
    
    However, what if I choose to back out of a change?  Now I want to select a
    particular revision of a resource.  Do I have to manually modify the
    activity to remove existing revisions and add in my selected revision?
    
    Note that if I had added a third rule (e.g., config) up front that would
    mask subsequent changes to the resource.
    
    Suggestions?
    Tim