As per Relevance of the word parameter, we have this rfc below:
Network Working Group E.
Request for Comments: 1872 Accurate Information Systems, Inc
Category: Experimental December 1995
The MIME Multipart/Related Content-
Status of this
This memo defines an Experimental Protocol for the
community. This memo does not specify an Internet standard of
kind. Discussion and suggestions for improvement are requested
Distribution of this memo is unlimited
The Multipart/Related content-type provides a common mechanism
representing objects that are aggregates of related MIME body parts
This document defines the Multipart/Related content-type and
examples of its use
1.
Several applications of MIME, including MIME-PEM, and MIME-
and other proposals, require multiple body parts that make sense
in the aggregate. The present approach to these compound objects
been to define specific multipart subtypes for each new object.
keeping with the MIME philosophy of having one mechanism to
the same goal for different purposes, this document describes
single mechanism for such aggregate or compound objects
The Multipart/Related content-type addresses the MIME
of compound objects. The object is categorized by a "type
parameter. Additional parameters are provided to indicate a
starting body part or root and auxiliary information which may
required when unpacking or processing the object
Responsibility for the display or processing of a Multipart/Related'
constituent entities rests with the application that handles
compound object
Levinson Experimental [Page 1]
RFC 1872 Multipart/Related December 1995
2. Multipart/Related Registration
The following form is copied from RFC 1590, Appendix A
To: IANA@isi.
Subject: Registration of new Media Type content-type/
Media Type name:
Media subtype name:
Required parameters: Type, a media type/subtype
Optional parameters: Start, a content-id
Start-info, a string or content-id list
Encoding considerations: Multipart content-types cannot
encodings
Security considerations: Depends solely on the referenced type
Published specification: This document
Person & email address to contact for further information
Edward
Accurate Information Systems, Inc
2 Industrial
Eatontown, NJ 07724
+1 908 389 5550
+1 908 389 5556 (fax
ELevinson@Accurate.
3. Intended
The Multipart/Related media type is intended for compound
consisting of several inter-related body parts. For
Multipart/Related object, proper display cannot be achieved
individually displaying the constituent body parts. The content-
of the Multipart/Related object is specified by the type parameter
The "start" parameter, if given, points, via a content-ID, to
body part that contains the object root. The default root is
first body part within the Multipart/Related body
The relationships among the body parts of a compound
distinguishes it from other object types. These relationships
often represented by links internal to the object's components
reference the other components. Within a single
environment the links are often file names, such links may
Levinson Experimental [Page 2]
RFC 1872 Multipart/Related December 1995
represented within a MIME message using content-IDs or the value
some other "Content-" header
3.1. The Type
The type parameter must be specified and its value is the MIME
type of the root body part. It permits a MIME user agent
determine the content-type without reference to the enclosed
part. If the value of the type parameter and the root body part'
content-type differ then the User Agent's behavior is undefined
Note: Constraining the "type" parameter's value to an existing
type allows the appropriate processing to be identified
creating yet another hierarchy of registered types. A
default action would have the MIME mail User Agent (MUA) to
the "start" entity alone when it could process the media type as
basic type but not as Multipart/Related
3.2. The Start
The start parameter, if given, is the content-ID of the
object's root. If not present the root is the first body part in
Multipart/Related entity. The root is the element the
processes first
In the case of a Multipart/Alternative body part containing
entities with identical content-IDs the start entity should
selected using the Multipart/Alternative rules
Note: The "start" parameter allows for types in which the
element gets generated by the sending application, perhaps on
fly. Such an application can create the "start" content-id
processing begins and then insert the body part when it is complete
3.3. The Start-Info
Additional information can be provided to an application by
start-info parameter. It contains either a string or points, via
content-ID, to another MIME entity in the message. A typical
might be to provide additional command line parameters or a
entity giving auxiliary information for processing the
object
Applications that use Multipart/Related must specify
interpretation of start-info. User Agents shall provide
parameter's value to the processing application. Processes
distinguish a start-info reference from a token or quoted-string
examining the first non-white-space character, "<" indicates
Levinson Experimental [Page 3]
RFC 1872 Multipart/Related December 1995
content-id reference
3.4.
related-param := [ ";" "start" "=" cid ]
[ ";" "start-info" "="
( cid-list / value ) ]
[ ";" "type" "=" type "/" subtype ]
; order
cid-list := cid cid-
cid := msg-id ; c.f. [822]
value := token / quoted-string ; c.f. [MIME
; value cannot begin with "<"
Note that the parameter values will usually require quoting. Msg-
contains the special characters "<", ">", "@", and perhaps
special characters. If msg-id contains quoted-strings, those
marks must be escaped. Similarly, the type parameter contains
special character "/".
4.
4.1 Application/X-
The X-FixedRecord content-type consists of one or more octet-
and a list of the lengths of each record. The root, which lists
record lengths of each record within the streams. The record
list, type Application/X-FixedRecord, consists of a set of
in ASCII format, one per line. Each INTEGER gives the number
octets from the octet-stream body part that constitute the
"record".
The example below, uses a single data block which the
processes on the fly to generate the record length list
Consequently the list appears after the data
Content-Type: Multipart/Related; boundary=example-1
start="<950120.aaCC@XIson.com>";
type="Application/X-FixedRecord
start-info="-o ps
--example-1
Content-Type: Application/octet-
Content-Description: The fixed length
Content-Transfer-Encoding: base64
Levinson Experimental [Page 4]
RFC 1872 Multipart/Related December 1995
Content-ID: <950120.aaCB@XIson.com
T2xkIE1hY0
BFIEkgTwpBbmQgb24gaGlzIGZhcm0
IHNvbWUgZHVja3
BxdWFjayBxdWFjayBoZXJlLAphIHF1YWNrIHF
YWNrIHRoZXJlLApldmVyeSB3aGVyZSBhIHF1
NrIHF1YWNrCkUgSSBFIEkgTwo
--example-1
Content-Type: Application/X-
Content-ID: <950120.aaCC@XIson.com
25
10
34
10
25
21
26
10
--example-1--
4.2 Text/X-
The Text/X-Okie is an invented markup language, similar
HTML, that permits the inclusion of images with text.
feature of this example is the inclusion of two
body parts, both picture. They are referred to internally
the encapsulated document via each picture's body
content-ID. Usage of "cid:", as in this example, may
useful for a variety of compound objects. It is not, however
a part of the Multipart/Related specification
Content-Type: Multipart/Related; boundary=example-2;
start="<950118.AEBH@XIson.com>"
type="Text/x-Okie
--example-2
Content-Type: Text/x-Okie; charset=iso-8859-1;
declaration="<950118.AEB0@XIson.com>"
Content-ID: <950118.AEBH@XIson.com
Content-Description:
{doc
This picture was taken by an automatic camera mounted ...
{image file=cid:950118.AECB@XIson.com
{para
Now this is an enlargement of the area ...
Levinson Experimental [Page 5]
RFC 1872 Multipart/Related December 1995
{image file=cid:950118.AFDH@XIson.com
{/doc
--example-2
Content-Type: image/
Content-ID: <950118.AFDH@XIson.com
Content-Transfer-Encoding: BASE64
Content-Description: Picture
[encoded jpeg image
--example-2
Content-Type: image/
Content-ID: <950118.AECB@XIson.com
Content-Transfer-Encoding: BASE64
Content-Description: Picture
[encoded jpeg image
--example-1--
5. User Agent
User agents that do not recognize Multipart/Related shall,
accordance with [MIME], treat the entire entity as Multipart/Mixed
MIME User Agents that recognize Multipart/Related entities but
unable to process the given type shall either suppress the
Multipart/Related body part or process the root alone. In
case the user should be notified of the MUA's action
Handling Multipart/Related differs from other media types in
processing cannot be reduced to handling the individual entities
Existing media types are handled by MIME-capable MUAs handle in
straightforward manner. For basic media types (e.g., text, image
etc.) the body of the entity can be directly passed to a
process. Composite media types can be reduced to handing one or
discrete types
Multipart/Related provides an irreducible composite media type
The following sections discuss what information the
application requires
It is possible that an application specific "receiving agent"
manipulate the entities, after initial processing by the MIME
Agent, prior to invoking actual application process. From
viewpoint of the MUA, the receiving agent is the application. Okie
above, demonstrates this; it may need a receiving agent to parse
document and substitute local file names for the originator's
names. Other applications may just require a table showing
correspondence between the local file names and the originator's
Levinson Experimental [Page 6]
RFC 1872 Multipart/Related December 1995
The receiving agent takes responsibility any for such processing
5.1 Data
MIME-capable MUAs are required to provide the application
(a) the bodies of the MIME entities and the entity Content-*
headers
(b) the parameters of the Multipart/Related Content-
header,
(c) the correspondence between each body's local file name
that body's header data, and, if present, the body part'
content-ID
5.2 Storing Multipart/Related
The Multipart/Related media type will be used for objects that
internal linkages between the body parts. When the objects
stored the linkages may require processing by the application or
receiving agent
5.3
MIME is a recursive structure. Hence one must expect
Multipart/Related entity to contain other Multipart/Related entities
When a Multipart/Related entity is being processed for display
storage, any enclosed Multipart/Related entities shall be
as though they were being stored. It shall be the responsibility
the application handling the outermost Multipart/Related to
the appropriate processing of embedded Multipart/Related entities
5.5 Configuration
It is suggested that MUAs that use configuration mechanisms,
[CFG] for an example, refer to Multipart/Related
Multipart/Related/, were is the value of the "type
parameter
6. Security
Security considerations relevant to Multipart/Related are
to those of the underlying content-type
Levinson Experimental [Page 7]
RFC 1872 Multipart/Related December 1995
7.
This proposal is the result of conversations the author has had
many people. In particular, similar work was described by Harald A
Alvestrand (early drafts of Multipart/Related), Dave
(Multipart/Families), and Keith Moore (Multipart/References).
addition, James Clark, Charles Goldfarb, Gary Houston, Ned Freed,
Moody, and Don Stinchfield, provided both encouragement
invaluable help. The author, however, take full responsibility
all errors contained in this document
8.
[822] Crocker, D., "Standard for the Format of
Internet Text Messages", STD 11, RFC 822, UDEL
August 1982.
[CFG] Borenstein, N., "A User Agent
Mechanism For Multimedia Mail Format Information",
RFC 1524, Bellcore, September 1993.
[MIME] Borenstein, N. and and N. Freed, "MIME (
Internet Mail Extensions) Part One: Mechanisms
Specifying and Describing the Format of Internet
Bodies", RFC 1521, Bellcore, Innosoft, September 1993.
9. Author's
Edward
Accurate Information Systems, Inc
2 Industrial
Eatontown, NJ 07724-2265
Phone: +1 908 389 5550
EMail: ELevinson@Accurate.
Levinson Experimental [Page 8]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
