2006/6/8, Tim Bray <[EMAIL PROTECTED]>:
<co-chair-mode>
Here's the latest: http://intertwingly.net/wiki/pie/PaceMediaEntries5
Add to my -1 the second paragraph of section 8.4:
If the body of the client's POST is of a media type other than
application/atom+xml, this constitutes a request that the server create
a new resource as represented by the body of the post, called a "media
resource", and also an entry in the collection to which the POST was
addressed, called a "media link entry", and return both URIs.
This would prevent using the same URI endpoint for APP and HTML-form
(e.g. multipart/x-form-data) processing.
I still don't understand why you're willing to make things such
complicated (talking about media resources and media link entries is
only a facet of this) while actually it's real simple:
Whatever you POST, the server creates a resource with
an Atom-Entry representation.
(On the justification side, the Atom-Entry representation is mandatory
here because otherwise you won't be able to include it in an
Atom-Feed; in previous versions of APP where there were a "collection
document" format, there was no need for such a constraint. The
_standalone_ Atom-Entry representation is necessary if you want to let
clients update it; if a server implementation does not let clients
update the entry, then it's just an "unnecessary" added constraint,
but it hits the 80/20 mark as the server already has to provide an
Atom-Entry representation for inclusion in Atom-Feed representations
of collections)
With some more details: if you didn't POSTed an Atom-Entry, then the
Atom-Entry representation might use an out-of-line content (i.e.
atom:[EMAIL PROTECTED]); on the other hand, if you POSTed an Atom-Entry,
this Atom-Entry must not be linked from an out-of-line content.
If you don't want to constrain the Atom-Entry to be a representation
of the created resource (but might be another resource, describing the
created resource ; I personnally can't see a need for it but…), then
just say that whatever you POST, the server creates a resource and an
Atom-Entry representation, without saying whether this Atom-Entry is a
representation of the created resource or another one.
I've started editing PaceMediaEntries5 and hope to have a
PaceMediaEntriesX before the week end.
--
Thomas Broyer
