stable URL's

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

  • Next message: Geoffrey M. Clemm: "LABEL vs. SET-LABEL-TARGET"

    Date: Fri, 26 May 2000 22:36:41 -0400 (EDT)
    Message-Id: <200005270236.WAA17968@tantalum.atria.com>
    From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
    To: ietf-dav-versioning@w3.org
    Subject: stable URL's
    
    
    At this weeks design meeting, it was proposed that we require that
    the server provide a URL to all resources that currently require a
    header.  In particular, that would be working resources and the
    metadata for versioned resources.
    
    It was also proposed that we not use the term "stable", and in the
    case of revisions, use the term "revision URL".  That works fine
    for working resources as well (i.e. use the term "working resource URL").
    
    So all we need is a term to distinguish a versioned resource URL
    that is affected by a target selector header, and one that is not
    (i.e. is a "stable URL for the versioned resource metadata").
    
    I propose that we keep the term "versioned resource URL" for
    the resource that is affected by the target selector header,
    and that we use the term "history URL" for the one that exposes
    the versioned resource metadata.
    
    So that leaves us with 4 kinds of URL's:
    
    - versioned resource URL's (affected by Target-Selector header)
    - revision URL's (stable)       
    - working resource URL's (stable)
    - history URL's (stable)
    
    Any objections?
    
    Cheers,
    Geoff