UserPreferences

PaceRequestURI


Abstract

Allow clients requesting the creation of an entry to request that a particular URI be used.

Status

Open

Rationale

URIs are not opaque. Choosing a memorable URI for a Web resource can increase its chances of being remembered and communicated accurately by humans. Furthermore, some search engines are known to place heavy weight on natural-language words that show up in URIs.

Proposal

FIRST, Add a pragraph to the end of section 8.1 (i.e. before 8.1.1 starts)

        When posting an atom:entry to a collection in order to add a new member,  
        a client may include an atom:link element with a rel attribute whose value 
        is "alternate".  This constitutes a request by the client that the new member 
        be given a URI which includes the content of the link element's href attribute.  
        The value of the href may be relative or absolute.  Server software MAY take 
        the value into account in generating the new member's URI.  For example, a 
        typical application would be an APP server which uses dates to construct part 
        of the URI path, e.g. "http://example.com/pub/2006/01/10", but which 
        allows clients to specify the last part of the URI path.

SECOND, remove the <link> element from the atom:entry in the first example in 8.1.1

THIRD, construct a second example in 8.1.1 which is identical to the first except that the atom:entry contains

        <link rel='alternate' href='atom-robots' />

and then what comes back includes:

        Location: http://example.org/edit/atom-robots.atom

Impacts

Notes


CategoryProposals