Bill's mail addresses my concerns, and seems simple enough to
not needlessly complicate the model. Thanks!
Neil
Date: Tue, 2 Mar 1993 11:01:32 PST
Sender: Bill Janssen <janssen(_at_)parc(_dot_)xerox(_dot_)com>
This is why adding another subtype of multipart seems like a win -- you
are putting the the situational information about use at the right level
of the message ``document''.
I'd imagine the wording of the section describing
``multipart/attachments'' would be something like this:
7.2.4 The Multipart/attachments subtype
The multipart/attachments type is used when only one part of a
multipart message (called here the _primary_ part) is intended to be
displayed, the other parts acting as documents ``attached'' to that
primary part. User agents should only display the attachments in
some short form (.i.e., with a name or icon), but should display the
primary part in full. The primary part is specified to be the
*last* part of the multipart/attachments.