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 >> >> > > > >
