Re: AtomPub Multipart Open Issues

["Thomas Broyer" <t.broyer@xxxxxxxxx>]

On Wed, Jul 2, 2008 at 10:52 AM, Sylvain Hellegouarch wrote:
>
> I have to agree with Bill. "related" is only one use of the multipart
> subtypes. Joe, rather than post-options="multipart", why not using
> multipart="related|form-data|alternative|...".

Except that not all multipart types don't have the notion of a "root part":
 - multipart/form-data is likely to be used with parts such as
"title", "summary", "summary-type", "content", "content-type",
"author", etc. and even if an Atom Entry would be sent, there's no
notion of a "root part"
 - how would you use multipart/alternative? And you cannot reference
one "alternative" from another using a cid: URI, it would be a
multipart/related (eventually included as one of the "alternative"
parts).

> That convention would at least allow for compatibility with future
> extensions that would like to deal with other MIME subtypes. Interestingly
> your draft could be duplicated almost as-is to support "mixed" and
> "alternative".

I'm not so sure... (see above)


@Joe: what's the problem with advertising
<app:accept>multipart/related;type="application/atom+xml;type=entry"</app:accept>?

-- 
Thomas Broyer