Yes I'm sorry I was vague. What I actually meant was is there some way I can associate this Atom Entry with another one so that when I GET the Atom Entry at http://example.org/edit/first-post.atom (which should really be the media file's metadata; please correct me if I'm wrong) I have a way to GET another Atom Entry that this one is associated with (like the relation between a blog post and an attachment/media file associated with it)?
Thank you, Sammy "James M Snell" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > a) Use atom:category > > b) not sure if this is what you mean, but when I GET the media resource, > I would likely return an edit Link header in the response. > > Request; > GET /media/abc123.png HTTP/1.1 > Host: example.org > > Response: > HTTP/1.1 200 OK > Date: nnn > Content-Type: image/png > Content-Length: nnnn > Link: <http://example.org/edit/first-post.atom>; rel="edit" > > {binary data} > > - James > > Sammy wrote: >> Very nice. I would like to hear how you would personally implement (a) >> tagging and (b) which Atom Entry this media resource belongs to. >> >> Thank you, >> Sammy >> >> "James M Snell" <[EMAIL PROTECTED]> wrote >> in >> message news:[EMAIL PROTECTED] >>> >>> >>> Sammy wrote: >>>> [snip] >>>> What does the location "http://example.org/edit/first-post.atom"; now >>>> refer >>>> to? If I'm assuming correctly it should refer to an Atom Entry >>>> containing >>>> the metadata for the created media resource. Is this true or false? >>>> >>> True. With this revision, Location would *always* point to an editable >>> Atom Entry. >>> >>> - James >>> >>> >> >> >> >> > >
