John Panzer wrote:
James M Snell wrote:
...
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?
Left up to implementations. Generally speaking, however, if I have a
PNG and I want to modify the atom:title and atom:summary that is
displayed in the atom:entry representing the media resource, I would
POST an atom:entry with the modified values. I have a few other ideas
on this that I will likely post sometime in the next couple of days.
...
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?
This would be handled exactly as described in the current -06 section 11
(http://bitworking.org/projects/atom/draft-ietf-atompub-protocol-06.html#rfc.section.11)
- James
