Sluggish member resources

[Tim Bray <Tim.Bray@xxxxxxx>]

Sylvain pointed out an Ape bug (it was using the old Title header for  
media resources) so I reviewed draft-14 and came up with the following.

The definition of "Member Resource" is AWOL (I think someone else may  
have caught this); it's used freely, even in defining other terms in  
the terminology section (http://bitworking.org/projects/atom/draft- 
ietf-atompub-protocol-14.html#terminology).  Symptom: I was looking  
at the spec for the Slug header (http://bitworking.org/projects/atom/ 
draft-ietf-atompub-protocol-14.html#rfc.section.9.7) and it says it's  
supposed to be used in the member resource URI.  Not 100% clear what  
that meant in the context of posting a JPEG, I did a browser search  
for "Member resource" and it would have been nice to find a crisp  
answer near the top of the doc.

Now, the other problem... when I post a JPEG with a Slug header,  
where would I like that Slug header used?  I think the whole point of  
the slug is that you'd like it to appear in URIs people or bots might  
actually see it.  So I don't think it really matters whether it shows  
up in the Media Link Entry URI, it's the Media Resource URI (the  
thing that shows up in entry/content@src.

So, I think that a slight revision to really clarify the intent of  
Slug might be in order:

Slug is a HTTP entity-header that, when accompanying a POST to a  
Collection, constitutes a request by the client that its value be  
used as part of any URIs that would normally be used to retrieve  
Entry or Media Resources.

 -Tim