Versioning Conf Call 5/8/2000 - Unreserved checkout flag for activities

From: Jim Doubek (jdoubek@macromedia.com)
Date: Mon, May 08 2000

  • Next message: Chris Kaler: "RE: draft-ietf-deltav04.5 now available"

    From: "Jim Doubek" <jdoubek@macromedia.com>
    To: "Ietf-Dav-Versioning" <ietf-dav-versioning@w3.org>
    Date: Mon, 8 May 2000 13:55:03 -0700
    Message-ID: <NEBBKGCJHMKNLDINHHCEOEPBCBAA.jdoubek@macromedia.com>
    Subject: Versioning Conf Call 5/8/2000 - Unreserved checkout flag for activities
    
    Hi,
    
    During the last few minutes of today's conf call, a number of issues were
    raised about the 'unreserved' checkout flag. COnferees at the time were Tim
    Ellison, Jim W, Henry Harbury and myself. What follows is my interpretation,
    rather than minutes or notes, so others should feel free to correct where
    appropriate.
    
    As written, the 'unreserved' flag is is on the second checkout, not the
    first for a revision. This doesn't seem to match the term 'reserved' which
    would infer that the reservation is done by the first checkout, affecting
    all subsequent. How does one prevent a latecomer from checking out the
    second working resource?
    
    Several people raised the problems having multiple checkouts in a single
    branch introduces in doing a merge. Since an activity can contain only
    linear revisions, one cannot checkin both working resources before the
    merge, so how is this done?
    
    It was pointed out that an activity points to revisions, not working
    resources. How does an activity keep track of working resources that are
    checked out in its behalf. This actually is a bigger issue, since many ui's
    will want to show all checkouts (work in progress) for an activity. Note
    that because of the next point, one can not get this info by going through
    workspaces. Additionally, working resources for an activity may in fact be
    specified by via means other than workspace, it seems.
    
    Activities backpoints to workspaces that have it as current activity
    (DAV:workspace-set) but not to those containing working resources. The
    current activity for the workspces may have changed since checkout, so these
    two sets of workspaces are not necessarily the same. Since revisions are
    added to the activity in checkin, there doesn't seem to be a list of all the
    'work in progress' for an activity.
    
    It was observed that there is no way to add revisions or resources to an
    activity except via checkin. <jimd> In later looking at the properties of
    revision and working resource, it appears this can be done by setting the
    DAV:activity of the resource or revision, correct? </jimd>
    
    DAV:activity is single valued for revisions. There is no way to denote that
    a single checkin relates to multiple activities, which is often the case.
    
    - jim doubek
    
    ------------------------------------------
    Jim Doubek
    Macromedia, Inc.
    jdoubek@macromedia.com
    http://www.macromedia.com/
    (408)735-1839 / (650)622-2974