I've updated the pace to reflect the recent discussion
http://www.intertwingly.net/wiki/pie/PaceSlugHeader
#pragma section-numbers off
== Abstract ==
Alternative to PaceMinimalSlug that uses an HTTP header instead
(therefore, it works for media posts as well as entry posts).
For draft-09...
== Status ==
Proposed
== Rationale ==
Same rationale as PaceMinimalSlug: "Many existing weblog software
implementations allow clients to request specific URI content entries.
APP should also support this capability"
== Proposal ==
{{{
8.5 Slug: Header
When posting a resource to a collection in order to add a new member, a
client MAY include a Slug request header. This constitutes a request by
the client that the URI assigned to the new resource incorporate the
string provided in the value of the Slug header. Server implementations
MAY attempt to comply with the request.
For example,
POST /myblog/fotes HTTP/1.1
Host: example.org
Content- Type: image/png
Content- Length: nnnn
Slug: a_picture_of_my_house
...binary data...
The syntax of this header MUST conform to the augmented BNF grammar in
section 2.1 of the HTTP/1.1 specification [RFC2616]. The [TEXT] rule is
described in section 2.2 of the same document. Words of *TEXT MAY
contain characters from character sets other than [ISO88591] only when
encoded according to the rules of [RFC2047].
Server implementations are more likely to be able to incorporate
requested strings if they are constructed with sensitivity to URI syntax
rules [RFC3986]. In particular, strings containing characters with
syntactic significance, in particular the path-separator character "/",
are apt to cause server implementations difficulty.
}}}
== Impacts ==
== Notes ==
----
CategoryProposals
