new working draft (04.8) of versioning protocol available

From: Geoffrey M. Clemm (geoffrey.clemm@rational.com)
Date: Tue, Jun 13 2000

  • Next message: Clemm, Geoff: "RE: Protocol doc"

    Date: Tue, 13 Jun 2000 12:59:31 -0400 (EDT)
    Message-Id: <200006131659.MAA14559@tantalum.atria.com>
    From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
    To: ietf-dav-versioning@w3.org
    Subject: new working draft (04.8) of versioning protocol available
    
    <http://www.webdav.org/deltav/protocol/draft-ietf-deltav-versioning-04.8.html>
    A word version is available at:
    <http://www.webdav.org/deltav/protocol/draft-ietf-deltav-versioning-04.8.doc>
    
    Mostly, this contains the to-do items identified in the Seattle design
    team meeting.  The items I didn't get to are identified in the "Open
    Issues and Pending Changes" section.
    
    Please review this document and send me any remaining issues not
    already identified in that section.
    
    Beyond the issues identified in the Seattle notes, I'd like feedback
    on the following changes:
    
    - In order to more clearly distinguish properties that are part of the
    immutable state of a revision from mutable relations to that revision,
    I've tried marshalling "successors" and "checkouts" as reports rather
    than properties.  In addition to making the semantics cleaner/simpler,
    this also allows for indefinite caching of the content/properties of a
    revision-URL (for an immutable revision).
    
    - Since we now have a "history report" (which I've tentatively named
    the "revision-tree-report"), and since labeling acts on revisions
    (rather than on the versioned resource metadata), there does not
    appear to be a pressing need for a "history URL" or a "history
    resource" in core versioning, so I've moved it into advanced
    versioning.  I believe this will be a commonly implemented extension,
    but leaving it as an optional advanced feature simplifies core
    versioning with no loss of interoperability for the core versioning
    features (checkout, checkin, labeling).
    
    Cheers,
    Geoff