On Fri, 2005-04-08 at 12:01 +0200, Michael Haardt wrote:
And that's what I say: If something is optional, it should be specified
as such.
How is a MIME entity be used to form a message? A multi part message is
a very different thing from a single part message and what will be used
sounds pretty application specific to me, so the application specification
should say something about it, even if both are fine.
RFC 2046 says:
The use of the "multipart" media type with only a single body part
may be useful in certain contexts, and is explicitly permitted.
this is as explicit as your other examples. a multi-part message with a
single leaf entity should be presented to the user as if it was a
single-part message.
--
Kjetil T.