Versioned Collections

From: Tim Ellison/OTT/OTI (Tim_Ellison@oti.com)
Date: Thu, Apr 27 2000

  • Next message: Tim Ellison/OTT/OTI: "4.1 Target-Selector"

    To: ietf-dav-versioning@w3.org
    From: "Tim Ellison/OTT/OTI" <Tim_Ellison@oti.com>
    Message-ID: <OF917C84C7.4D0F5F77-ON852568CF.00094800@ott.oti.com>
    Date: Thu, 27 Apr 2000 22:48:34 -0400
    Subject: Versioned Collections
    
       9.4 Versioned Collections
       para. 1
    
       There seems to be an unwritten subtext here<g>.  Disallowing 
    unversioned
       resources in a versioned collection is primarily for an (important)
       implementation optimization.  Allowing any resource would break the
       semantics of the versioning system per se.  I would be happier if this 
    was
       more explicit.
    
    <geoff>
    I added the statement that "this is restriction is required to allow
    essential implementation optimizations".  Probably don't want to spend
    too much space in the protocol on this issue though.  Folks that are
    implementing them will appreciate the restriction, and folks that aren't
    probably don't care (:-).
    </geoff>
    
    I agree -- and for the record, (if it wasn't obvious) I missed the key 
    word *not* out of the sentence:
       Allowing any resource would _not_ break the
       semantics of the versioning system per se.
    
    Tim