Re: Questions on activities

From: Geoffrey M. Clemm (geoffrey.clemm@rational.com)
Date: Fri, Apr 21 2000

  • Next message: jamsden@us.ibm.com: "Re: Simplifying client access to advanced versioning"

    Date: Fri, 21 Apr 2000 08:09:37 -0400 (EDT)
    Message-Id: <200004211209.IAA25698@tantalum.atria.com>
    From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
    To: ietf-dav-versioning@w3.org
    Subject: Re: Questions on activities
    
    
       From: Michelle Harris <michelle.harris@starmedia.net>
    
       Aye, please forgive my humble opinion on this matter as I am very
       new to WebDAV and am only beginning to work with the most basic
       features. However, I am also following the Versioning conversation
       so that I can fully understand it when the time comes to implement
       that functionality. And the sections on Activities have been the
       more taxing ones on my brain...I keep looking for a clear, explicit
       explanation on how their envisioned use. If one exists, could you
       please point me to the location?
    
    Welcome aboard, Michelle!  It's great to have someone with a
    fresh perspective.
    
    From your comments, its clear that the section on "activities" in the
    advanced versioning semantics needs to be rewritten.  I'll try to get
    something done next week, and get it posted to the mailing list for
    your review.
    
       With that said, I would like to say that I agree with the idea that
       more guidance would be beneficial to advanced development on
       Versioning (especially activities). Many developers are really only
       familiar with CVS and may have a hard time abstracting out all the
       concepts necessary to successfully integrate pre-existing
       version-control with WebDAV.
    
    In some cases, an advanced versioning concept will not be present in
    an existing version-control system, which I believe is the case for
    activities and CVS.  But the concepts shold be made clear enough in
    protocol that it is obvious to an implementor which features of
    advanced versioning are needed, and what parts of an existing system
    they map to.
    
    Cheers,
    Geoff