Defn of versionable

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

  • Next message: Tim Ellison/OTT/OTI: "Predecessor set"

    To: ietf-dav-versioning@w3.org
    From: "Tim Ellison/OTT/OTI" <Tim_Ellison@oti.com>
    Message-ID: <OF3C15CE56.13668922-ON852568E3.0054388F@ott.oti.com>
    Date: Thu, 18 May 2000 11:38:14 -0400
    Subject: Defn of versionable
    
    Section 6.1
    -----------
    
    > Preconditions:
    > The request-URL MUST identify a versionable resource.
    
    This is a circular dependency, because in section 1.2 "versionable
    resource" is defined as "resource that can be placed under version
    control with a VERSION request".
    
    To break this circularity, I would like to propose the following
    wording for the definition of "versionable resource" in section 1.2:
    "any resource that evolves over time, that can be tracked in a
    history, and that has not yet been put under version control (or, in
    other words, has no versioned resource associated)".
    
    <tim>
    this definition is insufficient.  For example we have resources such as 
    activities that are not versionable resources but would satisfy this new 
    definition. 
    In practice, I have no problem with this circular definition.  However if 
    we could find an alternative description that was not self referencing 
    that would be preferable. 
    </tim>