Comments on 08.1

From: Boris Bokowski/OTT/OTI (Boris_Bokowski@oti.com)
Date: Wed, Sep 20 2000

  • Next message: Geoffrey M. Clemm: "Re: Comments on 08.1"

    To: ietf-dav-versioning@w3.org
    Message-ID: <OF5AE693E5.F4043285-ON85256960.0059FFA3@ott.oti.com>
    From: "Boris Bokowski/OTT/OTI" <Boris_Bokowski@oti.com>
    Date: Wed, 20 Sep 2000 14:32:42 -0400
    Subject: Comments on 08.1
    
    Here are a few comments on the 08.1 spec:
    
    5.3.4 DAV:auto-version
     This property only makes sense for a checked in version selector.
    
    8 Versioning and existing methods, last paragraph
     If a server puts a newly created resource under version control 
    automatically, will the new version selector be in the checked in state or 
    in the checked out state? The spec should be explicit about this.
    
    10.2 CHECKOUT (Marshalling)
     The Target-Selector header is in the header, not in the body :-)
     The effect of the Target-Selector header is not specified. Should be 
    something like: If a Target-Selector header is included and the 
    request-URL identifies a version selector, a new working resource will be 
    created as if the request was applied to the version selected by the 
    Target-Selector header.
     The effect of the request body is not specified. Should be something 
    like: If a request body is present and it includes the DAV:target element 
    and the request-URL identifies a version selector, a new working resource 
    will be created as if the request was applied to the version selected by 
    the DAV:target property of the version selector.
    
    10.3 CHECKIN (Postconditions)
     Refers to the DAV:version property of versions, which was removed.
    
    10.4 UNCHECKOUT (Postconditions)
     Typo: "The version selector has not DAV:checked-out property value" -> 
    "... has no ..."
    
    10.6.1 example for LABEL
     In the example, there is white space around the label-name, but the 
    explanation says that the label "released" (not " released ") is applied 
    to the target version. Are servers supposed to strip away whitespace?
    
    12.1 Baseline
     The explanation should include the addition from 14.5.1: "(as well as the 
    target of the collection itself, if it is a version selector)"
    
    16.11 SET-TARGET
     The target of the collection itself (if it is a version selector) is 
    modified as well.
    
    17.1 MKWORKSPACE
     Should be "particular collections", "the locations of these collections" 
    (can be more than one)
     Same for 17.2 MKACTIVITY