James M Snell wrote:
Hey all,
Over the past couple of weeks we've been kicking around the -06 draft
and have seen a significant amount of spirited discussion and new
Paces. As I've been following the discussions, I've had a recurring
and nagging feeling that we this stuff could stand a drastic and
radical simplification. Unfortunately, it's not particularly easy to
describe what I have in mind in a series of individual paces so I've
decided to draft up my ideas as a single chunk included below.
...
...
Clients may append or modify metadata associated with a member
resource by sending an HTTP POST request to the IRI of the resource.
Is the general payload format of the HTTP POST part of the APP, or left
up to implementations?
...
Clients may request the creation of a new member resource by POSTing a
representation of the new member resource to the Collection resource's
IRI.
I'm wondering about the cat picture use case once again. Recall that
this is where I want to post a member resource consisting of XHTML which
references a cat picture in JPG format using the standard <img src...>
element. I think this is a sufficiently basic operation that the core
APP needs to support it in an interoperable manner (feel free to disagree).
How would I do this, assuming that I only have the IRI of a Collection
resource?
Given this proposal and no more, the only thing I can think of is
this: I could POST the JPG to the Collection resource. The server
could then accept it and return a Location: used to construct the
subsequent <img src...> snippet. Whether the Location: points at
something that is actually inside this Collection, or a different
Collection, is up to the server; as a client I don't care.
I think the consequence of this would be that for some servers, posting
such compound entries gives you two entries in a single Collection and
presumably a single syndication feed, and for other servers it doesn't.
I'm not worked up over it much, myself.
-John
