On 10/31/05, Eric Scheid <[EMAIL PROTECTED]> wrote: > Floating an idea here: can we define a custom HTTP header for reporting the > location of the associated atom:entry? Thus a POST of an image would return > a "Location: URI-of-image" and also a "X-Atom-Location: URI-of-entry"?
The entry for a media/generic member has never been editable and that's been true across all the drafts in which media/generic collections have appeared. I do view that as a problem and did float one Pace to address that deficiency, PaceSimplifyCollections. Another way to solve this problem would be to have the POSTing to a media collection create two editable resources, the original resource and the atom:entry with the meta-data. Both URIs could be returned in membership lists: <link rel="edit" href="URI of atom:entry resource (metadata)."> <link rel="srcedit" href="URI of media resource"> This lets a client edit metadata of media collections members, but only requires one POST to create the member. The requirement of two steps in PaceSimplifyCollections is what killed it. -joe -- Joe Gregorio http://bitworking.org
