On 9 Mar 2006, at 19:02, James M Snell wrote:
For example as Aleksander Slominsky just recently pointed out, he
would
like to edit the metadata of media collections. In order to do
this the
header would also have to include a link to the edit location of the
entry. And perhaps we should also return the id of the entry in the
header too, just so that the server know the relation between this id
and the media resource just posted, without having to search through
collections.
Look at PaceFixMediaCollections again,
Location: http://...
Link: <http://...>; rel="edit",
<http://...>; rel="alternate"
Oh on reading the Pace more carefully, I see that you are right.
This is what I saw:
[[
HTTP/1.1 201 Created
Date: nnnn
Location: http://example.org/media/1.png
Link: <http://example.org/media/1.png?edit>; rel="edit",
<http://cdn.example.org/photos/1.png>; rel="alternate"
]]
both links seem to me to point to a png file. I know there is a
rel="edit" link, but it was not obvious to me immediately that this
was a url to edit the metadata. I was expecting something more like:
[[
HTTP/1.1 201 Created
Date: nnnn
Location: http://example.org/media/1.png
Link: <http://example.org/media/1.atom>; rel="edit",
<http://cdn.example.org/photos/1.png>; rel="alternate"
]]
But ok.
+1 for the pace.
Now I suppose the question is if that link should be obligatory. Or
else are we not in
the same situation as the we are in now, where an entry may or may
not be returned?
Henry
The edit link rel points to the editable metadata representation.
The alternate link rel points to the alternate referenceable
representation.
This link header would be included in the POST response AND in the
response to a GET/HEAD on the Location URI, giving you a consistent
and
persistent link between the various resource representations and URLs.
