Extending Target-Selector

From: Tim Ellison OTT (Tim_Ellison@oti.com)
Date: Wed, Mar 01 2000

  • Next message: Tim Ellison OTT: "Disappearing CHECKINs"

    From: Tim_Ellison@oti.com (Tim Ellison OTT)
    To: ietf-dav-versioning@w3.org ('Delta V')
    Message-ID: <2000Mar01.160400.1250.1494398@otismtp.ott.oti.com>
    Date: Wed, 01 Mar 2000 16:04:37 -0500
    Subject: Extending Target-Selector
    
    
    Do we expect depth infinity operations to return stable URLs or 'users' 
    URLs.
    
    For example, PROPFIND depth infinity would be difficult to decode if the 
    URLs were all stable URLs--so I'll assume that they are user URLs in the 
    response.
    
    Now if you extend Target-Selector to be:
         All-But-Leaf-Selector: and
         Leaf-Selector:
    (we can argue about the names :-)
    How do you interpret the results?  Do the deep URLs conform to the same 
    All-But-Leaf-Selector: and Leaf-Selector: selection?  That's confusing since 
    the request-url used to have a leaf at the end, but in the deep operations 
    it's segments are all 'all-but-leaf' segments.  If the dep URLs don't 
    conform tot he same selection criteria what do they conform to?
    
    Tim