W3C home > Mailing lists > Public > public-xml-processing-model-comments@w3.org > January 2010

Re: c:multipart content-type attribute vs. header

From: Florent Georges <fgeorges@fgeorges.org>
Date: Mon, 11 Jan 2010 18:22:02 +0100
Message-ID: <ebaca5bf1001110922n12e7047bw1373cb3571d43c16@mail.gmail.com>
To: public-xml-processing-model-comments@w3.org
2010/1/11 Alex Milowski wrote:


> You should be able to set the content type to whatever
> multipart/* content type you request.  The most common would be
> multipart/mixed and multipart/related but there are others [1].

  In the context of HTTP requests (op. to email messages) I think
multipart/form-data is quite regular too.

> If a value of "multipart/related" is assumed, that should only
> be in the case where there is no content type header
> value--either from a c:header element as in above or by the
> actual content-type attribute on c:multipart.

  I am not sure a default value is really relevant here.  That
saves the user of typing a few characters, but it does not sound
like a "real" default value (what people really want most of the
time).  Why not making c:multipart/@content-type required
instead, consistently with c:body/@content-type?


Florent Georges
Received on Monday, 11 January 2010 17:22:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:28:27 UTC