Re: WebDAV Versioning Scenarios

From: by way of (pridemore@worldnet.att.net)
Date: Mon, Mar 27 2000

  • Next message: Jim Whitehead: "Questions on activities"

    Message-Id: <3.0.5.32.20000327084840.030bc4c0@127.0.0.1>
    Date: Mon, 27 Mar 2000 08:48:40 -0500
    To: ietf-dav-versioning@w3.org
    From: Russ Pridemore <pridemore@worldnet.att.net> (by way of "Ralph R. Swick" <swick@w3.org>)
    Subject: Re: WebDAV Versioning Scenarios
    
    Message-ID: <38DE3344.7FB175A9@worldnet.att.net>
    Old-Date: Sun, 26 Mar 2000 10:56:52 -0500
    From: Russ Pridemore <pridemore@worldnet.att.net>
    Reply-To: Russ.Pridemore@bigfoot.com
    To: ietf-dav-versioning@w3.org
    References: <852568AE.0015A7B4.00@d54mta03.raleigh.ibm.com>
    
    This makes a lot of sense to me.  I would almost call it a
    breakthrough simplification.  One question did come to
    mind, however:  is a revision selection rule immutable?
    
    Russ
    
    jamsden@us.ibm.com wrote:
    
    > A workspace describes dynamic or variable a set of revisions. It represents
    > a place where a client or group of clients does work by making changes to
    > resources directed at some desired end result. A workspace has a revision
    > selection rule that describes the revisions that were selected by the
    > workspace creator. A workspace MAY dynamically update its contents based on
    > changes in the revision selection rule, or changes to resources managed by
    > the server, e.g., creation of new versioned resources, labeling revisions,
    > checking in working resources in an activity, updating a configuration,
    > etc. However, a server is not required to support dynamic revision
    > selection. Clients can use the REFRESH method to update the contents of a
    > workspace at any time. On REFRESH, the contents of the workspace is
    > refreshed with revisions as specified by the revision selection rule,
    > except for existing working resources. When a workspace is first created,
    > it MAY be empty. The first REFRESH populates the workspace with selected
    > revisions. On servers that do not support dynamic revision selection, the
    > revision selection rule only documents the revisions that were selected on
    > the last refresh, and cannot be relied upon to accurately reflect the exact
    > revisions that are contained in the workspace. Another refresh may be
    > required to update the revisions selected by the workspace.
    >