RFC relevance of structure

As per Relevance of the word structure, we have this rfc below:

RFC:767

A STRUCTURED FORMAT FOR TRANSMISSION OF MULTI-MEDIA

Jonathan B.

August 1980

Information Sciences
University of Southern
4676 Admiralty
Marina del Rey, California 90291

(213) 822-1511

< INC-PROJECT, MMMSFS.NLS.21, >, 5-Sep-80 20:19 JBP ;;;;

August 1980
A Structured Format for Transmission of Multi-Media

TABLE OF

PREFACE ........................................................

1. INTRODUCTION ..................................................... 1

1.1. Motivation ................................................... 1
1.2. Scope ........................................................ 1
1.3. Terminology .................................................. 1
1.4. Document Description ......................................... 2
1.5. Other Work ................................................... 2

2. SPECIFICATION .................................................... 3

2.1. Document ..................................................... 3
2.2. Message Objects ............................................. 5
2.3. Body Structures ............................................. 13
2.3.1. Simple Elements ........................................... 13
2.3.2. Structured Text ........................................... 13
2.3.3. NLS File Example .......................................... 13
2.3.4. Multimedia Structures ..................................... 15
2.3.5. The Media ................................................. 21
2.3.6. TEXT ...................................................... 22
2.3.7. VOICE ..................................................... 22
2.3.8. FACSIMILE ................................................. 23
2.3.9. GRAPHICS .................................................. 24

3. EXAMPLES & SCENARIOS ............................................ 25

Example 1: Text Example .......................................... 25
Example 2: Multimedia Example .................................... 28

REFERENCES .......................................................... 31

Postel [Page i

August 1980
A Structured Format for Transmission of Multi-Media

[Page ii]

August 1980
A Structured Format for Transmission of Multi-Media

This is the first edition of this format specification and should
treated as a request for comments, advice, and suggestions. A
deal of prior work has been done on computer aided message systems
some of this is listed in the reference section. This specification
shaped by many discussions with members of the ARPA research community
and others interested in the development of computer aided
systems. This document was prepared as part of the ARPA
Internetwork Concepts Research Project at ISI

Jon

Postel [Page iii

August 1980
A Structured Format for Transmission of Multi-Media

Postel [Page iv

RFC: 767 J.
USC-
August 1980

A STRUCTURED FORMAT FOR TRANSMISSION OF MULTI-MEDIA

1.

This document describes a format for transmitting structured
representations of multimedia documents. This format is intended to
used with the Internet Message Protocol in an internetwork
delivery system. That system is designed to transmit messages
processes in host computers called Message Processing Modules (MPMs).
MPMs are located in several networks and together constitute
internetwork message delivery system. The Internet Message
defines a message as being composed of an Identification, a Command,
a Document. This report is intended to define the format of
Documents. The reader is assumed to be familiar with the
Message Protocol [1].

1.1.

Computer applications are being implemented which interact with
in a variety of media (text, graphics, facsimile, speech).
computer devices become available to process multimedia information
becomes desirable to use computers to exchange multimedia
between programs and users via various mechanisms including
mail

1.2.

This format is intended to be used for the transmission of
documents in the internetwork message delivery system, but it
thought that it has a wider applicability

1.3.

The messages are routed by a process called the Message
Module or MPM. Messages are created and consumed by User
Programs (UIPs) in conjunction with users

The basic unit transferred between MPMs is called a message.
message is made up of a transaction identifier (which
identifies the message), a command (which contains the
information for delivery), and document. The document is a
structure

For a personal letter the document body corresponds to the contents

Postel [Page 1]

August 1980
A Structured Format for Transmission of Multi-Media

the letter; the document header corresponds to the date line
greeting, and signature

For an inter-office memo the document body corresponds to the text
the document header corresponds to the header of the memo

The commands correspond to the information used by the Post Office
the mail room to route the letter or memo. Some of the information
the command is supplied by the UIP

1.4. Document

The document is composed of fields. Each field will carry
identifying name. Typical fields are DATE, TO, SUBJECT, and BODY
Most of the fields will be very simple, some will be complex.
body field may be quite complex. For example, the DATE is a
constrained character string specifying the date and time in
format. A more complex example is the TO field which is a list
mailboxes, where a mailbox is itself a property list of
information items. The BODY may be simply a character string, or
very structured collection of data representing information
different media

The BODY may be structured to indicate a controlled presentation
multimedia information. There is provision for the inclusion of text
graphics, facsimile, and voice information in the body of documents
The presentation of information units may sequential, independent,
simultaneous

1.5. Other

This protocol the benefited from the earlier work on message
in the ARPA Network [2,3,4,5,6], and the ideas of others about
design of computer message systems [7,8,9,10,11,12,13,14,15,16,17,18].

[Page 2]

August 1980
A Structured Format for Transmission of Multi-Media

2.

The structured format of a document is built on the basic data
used in the Internet Message Protocol [1].

2.1.

The document is a property list of pairs called fields
A few fields are specifically required and many are optional. Some
the field values are simple and a few are quite complicated.
particular the body value may be highly structured

Older message systems have considered the document to be divided
a header and a body, and have used keywords to indicate
header fields (e.g., date, to, subject). Roughly speaking,
functionality is provided in this new structured format by
the name part of the pair to be a keyword. In addition
this new structured format eliminates the separate treatment of
body

It is impossible to foresee the many forms documents will take so
standard for a document header must be flexible. The approach here
to define a set of basic fields and allow addition of whatever
are necessary. Features added in this fashion may not be
by others

The minimum document is a property list of the following fields

Name
---- -----
DATE date string (name
SENDER a
SUBJECT subject string (text
BODY a data

A typical document is a property list containing the following fields

Name
---- -----
DATE date string (name
SENDER a
FROM list of
TO list of
CC list of
SUBJECT subject string (text
BODY a data

Postel [Page 3]

August 1980
A Structured Format for Transmission of Multi-Media

An elaborate document might contain the following fields

Name
---- -----
DATE date string (name
SENDER a
FROM list of
TO list of
CC list of
BCC list of
REPLY-TO list of
SUBJECT subject string (text
COMMENTS comment string (text
MESSAGE-ID message identifier of this message (text
IN-REPLY-TO message identifier of previous message (text
REFERENCES message identifiers of other messages (text
KEYWORDS key terms used in this message (text
BODY a data

One of the key objects is the mailbox. It appears in the sender
from, to, cc, bcc, and reply-to fields. The mailbox is a
list of objects that combine to specify a destination recipient for
message. Most of the pairs that make up a mailbox
identical to those used in the deliver command in the Internet
Protocol [1]. A few additional pairs are defined for
in a mailbox in the document context. In particular, there is a
for the real name of a person in contrast to the "user name"
identifies a computer account

In addition there is a field to specify a distribution group name
Such group names are used to indicate that a document is being sent
a group of recipients. This essentially presents an alternate
for a mailbox which consists of the single pair for
group name. There is no required relationship between a group
mailbox and other mailboxes in the same list

For example, all of the following situations are allowed

. a mailbox list consisting of a single mailbox specifying
particular user

. a mailbox list consisting of a single mailbox with a group name

. a mailbox list consisting of a mailbox with a group name and
mailbox specifying a particular user, with either the user in
not in the group

. a mailbox list consisting of a mailbox with a group name and

[Page 4]

August 1980
A Structured Format for Transmission of Multi-Media

several mailboxes specifying a particular users, with some
in the group and some not

. a mailbox list consisting of several mailboxes specifying
names and a several mailboxes specifying a particular users,
some users in the groups and some not

2.2. Message

In the documents of messages, we use a set of objects such as
or date. These objects are encoded in basic data elements.
objects are simple things like integers or character strings,
objects are more complex things like lists or property lists.
following is a list of the objects used in messages. The
descriptions are in alphabetical order

The account information. Represented by a name element

Address is intended to contain the minimum information necessary
identify a user, and no more (compare with mailbox).

An address is a property list which contains the
pairs

name
---- -----------
NET network
HOST host
USER user

or

name
---- -----------
MPM mpm-
USER user

A yes (true) or no (false) answer to a question. Represented by
boolean element

Postel [Page 5]

August 1980
A Structured Format for Transmission of Multi-Media

A list of mailboxes. The addresses of those who receive "
carbon copies" of the message

A data structure. This may be as simple as a character
(represented by a name or text element), or complex structure
lists. It may be encrypted in part or in whole. Section 3.3
describes some possible structured bodies

A character. Represented by a name element

A list of mailboxes. When copies of a message are sent to others
addition to the addresses in the To object, those to whom the
are sent will have their addresses recorded here

A city. Represented by a name element

A comment string. Represented by a text element

A count of items of some sort. Represented by a integer element

A country. Represented by a name element

[Page 6]

August 1980
A Structured Format for Transmission of Multi-Media

The date and time are represented according to the
Standards Organization (ISO) recommendations [19,20,21].
together the ISO recommendations 2014, 3307, and 4031 result in
following representation of the date and time

yyyy-mm-dd-hh:mm:ss,fff+hh:

Where yyyy is the four-digit year, mm is the two-digit month, dd
the two-digit day, hh is the two-digit hour in 24 hour time, mm
the two-digit minute, ss is the two-digit second, and fff is
decimal fraction of the second. To this basic date and time
appended the offset from Greenwich as plus or minus hh hours and
minutes

The time is local time and the offset is the difference
local time and Coordinated Universal Time (UTC). To convert
local time to UTC algebraically subtract the offset from the
time

For example, when the time
Los Angeles is 14:25:00-08:00
the UTC is 22:25:00

or when the time
Paris is 11:43:00+01:00
the UTC is 10:43:00

A device name. Represented by a name element

A property list of fields

Distribution

An distribution group is a property list which contains
following pair

name
---- -----------
GROUP document distribution group

This construct is used so that a distribution group will be
special case of a mailbox

Postel [Page 7]

August 1980
A Structured Format for Transmission of Multi-Media

Facsimile

A facsimile data structure. Represented by a property list

A file name. Represented by a name element

A format indicator. Represented by a name element

A list of mailboxes. The From is the name of the author of
document

Graphics

A graphics data structure. Represented by a property list

A document distribution group name. Represented by a name element

A host name. Represented by a name element

The identifier of a person, usually their initials. Represented
a name element

In-Reply-

The message identifier of previous message. Represented by a
element

Internet

This identifies a host in the ARPA internetwork environment.
internet address is a 32 bit number, the higher order 8
identify the network, and the lower order 24 bits identify the
on that network [22]. For use in this format the internet
is divided into eight bit fields and the value of each field
represented in decimal digits. For example, the ARPANET address
ISIE is 167837748 and is represented as 10,1,0,52. Further,

[Page 8]

August 1980
A Structured Format for Transmission of Multi-Media

representation may be extended to include an address within a host
such as the TCP port of an MPM, for example, 10,1,0,52,0,45.

The key terms used in this message. Represented by a text element

This is the destination address of a user of the internetwork
system. Mailbox contains information such as network, host
location, and local user identifier of the recipient of the message
The mailbox may contain information in addition to the
required for delivery

As an example, when one sends a message to someone for the
time, he may include many items to aid in identifying the
recipient. However, once he gets a reply to this message, the
will contain an Address (as opposed to Mailbox) which may be
from then on

A mailbox is a property list. A mailbox might contain
following pairs

name
---- -----------
MPM mpm-
NET network
HOST host
PORT address of MPM within the
USER user name (computer account name
PERSON the real name of a
GROUP document distribution
ORG organization
CITY
STATE
COUNTRY
ZIP zip
PHONE phone

The minimum mail box is an Address or a Distribution Group

Message-

The message identifier of this message. This is not related to
MPM message identification, but is a UIP long term
identifier. Represented by a text element

Postel [Page 9]

August 1980
A Structured Format for Transmission of Multi-Media

MPM-

The internetwork address of an MPM. This may be the ARPA
Address or an X.121 Public Data Network Address [23].
mpm-identifier is a property list which has one pair
This unusual structure is used so that it will be easy to
the type of address used

A network name. Represented by a name element

NLS

The information in an NLS node. Represented by a property list

NLS

An NLS block and substructure. Represented by a property list

NLS

A list of NLS nodes. Represented by a list

An organization name. Represented by a name element

A paragraph of text. Represented by a text element

The basic unit of voice data. Represented by a bitstr element

The real name of a person. Represented by a name element

A password. Represented by a name element

A phone number. Represented by a name element

[Page 10]

August 1980
A Structured Format for Transmission of Multi-Media

A pointer to information stored outside this data structure.
property list containing the information necessary to locate
external data, the information necessary to gain access to
external data, and the information necessary to apply the
interpretation to the external data. For example, this
include

name
---- -----------
NET network
HOST host
FILE file
USER user name (computer account name
PASSWORD
ACCOUNT
FORMAT

The address of MPM within the host. Represented by a name element

Presentation

A property list of pairs, where the name is an
indicator, and the value is a presentation element. The
indicators are SEQUENTIAL, SIMULTANEOUS, and INDEPENDENT

Presentation

A property list of media structures

The name of the coding scheme used for a medium. Represented by
name element

The message identifiers of other messages. Represented by a list
text elements

Reply-

A list of mailboxes. Sometimes it will be desired to direct
replies of a message to some address other than the from or
sender. In such a case the reply-to object can be used

Postel [Page 11]

August 1980
A Structured Format for Transmission of Multi-Media

R 450

The unit of Rapicom 450 data (585 bits). Represented by a
element

A mailbox. The sender will contain the address of the
who sent the message. In some cases this is NOT the same as
author of the message. Under such a condition, the author should
specified in the from object

An NLS statement indetifier. Represented by a integer element

A state name. Represented by a name element

The subject of the message. Represented by a text element

Text

A text data structure. Represented by a property list

A list of mailboxes. To identifies the addressees of the message

A user name (computer account name). Represented by a name element

A version number. Represented by a index element

A vocoder name. Represented by a name element

Voice

A voice data structure. Represented by a property list

[Page 12]

August 1980
A Structured Format for Transmission of Multi-Media

X121

This identifies a host in the Public Data Network environment.
used as a part of identifier, it identifies the originating host
a message. The X121 address is a sequence of up to 14 digits [23].
For use in this format the X121 address is represented in
digits

A zip code. Represented by a name element

2.3. Body

2.3.1. Simple

The body could simply be a single data element. For example
single text element can represent a lengthy character string

:=

text:"this is the actual text of the body

2.3.2. Structured

The body could be thought of as paragraphs, where each paragraph
represented by a text element. The paragraphs are then the
of a list

:= LIST (<paragraph>, <paragraph>, ...)

<paragraph> :=

list:(text:"paragraph one", text:"paragraph two", ...)

2.3.3. NLS File

It is possible to represent the data from NLS files in this format
NLS is a large multipurpose system which operates on structured
files. The files are tree structured, and there is data
with each node of the tree. There are several fields
with each node as well

Postel [Page 13]

August 1980
A Structured Format for Transmission of Multi-Media

An NLS file is

proplist(
name:"FILENAME", name: name of
name:"CREATION-DATE", name: creation date and
name:"VERSION", index: file version
name:"SID-COUNT", integer current SID
name:"LAST-WRITER", name: last writer of
name:"OWNER", name: owner of
name:"LAST-WRITE-TIME", name: last write date and
name:"LEFT-NAME-DELIM-DEFAULT", name: default
name:"RIGHT-NAME-DELIM-DEFAULT", name:
name:"SUBSTRUCTURE",
)

An NLS substructure is

list:(
node is defined
.
.
.
)

An NLS node is

proplist:(
name:"BLOCK", block defined
name:"SUBSTRUCTURE",
)

An NLS block is

proplist:(
name:"LEFT-NAME-DELIM", name: left name
name:"RIGHT-NAME-DELIM", name: right name
name:"SID", integer: SID
name:"CREATOR", name: statement
name:"CREATION-TIME", name: creation date and
name:"DATA", data defined
)

[Page 14]

August 1980
A Structured Format for Transmission of Multi-Media

NLS data is

proplist:(
name:"", . .
. .
. .
)

For text, data is

proplist:(
name:"TEXT", text:"text of statement"
)

2.3.4. Multimedia

One can conceive of graphical information being displayed along
a running commentary, much as seminars use slides. A slide and
description are tied together. The coordination of such
presentation is central to its understanding. This
should be captured within the document structure

There are three fundamentally different types of time
control which are needed within the document structure. These are

Simultaneous data is intended for synchronous presentation.
implication is that this data is presented in parallel

Sequential data items will be presented one at a time, in the
listed. The ordering is strictly left to right

Independent data can be presented in any time order. It is
ordered in any manner

The data is broken into small information units called
elements or PEs. The PEs can be combined in structures to
the presentation order. A PE is a property list of
representing information of various media. For example

:= proplist
name:"VOICE", structure>,
name:"GRAPHICS", <graphics-structure
)

Postel [Page 15]

August 1980
A Structured Format for Transmission of Multi-Media

PEs are combined into larger controled presentations
presentation-descriptors or PDs. A PD is a property list
specifies the type of time ordering of the PEs in its list

:= <> | <> | <>

<> := name:"SEQUENTIAL",
<> := name:"SIMULTANEOUS",
<> := name:"INDEPENDENT",
A PE is a property list of the media pairs, or PDs

:= <> | <> | <<facsimile>>
| <<graphics>> |
<> := name:"TEXT", structure

<> := name:"VOICE", structure

<<facsimile>> := name:"FACSIMILE", <facsimile structure

<<graphics>> := name:"GRAPHICS", <graphics structure

If more than one pair is present within a PE the
are presented on different output devices in the order specified
the PE's parent PD. The order of appearance within the proplist
important only in the event that the parent PD specified
ordering

The structure of multimedia messages which use this scheme will
demonstrated by a few simple examples chosen to illustrate a
text document and the different ordering options. The last
will suggest some more exotic uses

[Page 16]

August 1980
A Structured Format for Transmission of Multi-Media

Plain Text

A simple text body could be represented in a single text
structure. To give the simplest example of a structured body
show a simple text body represented in the multimedia structure

:=
:= <>

<> := name:"SEQUENTIAL",
:= name:"TEXT", structure

proplist: (name:"SEQUENTIAL",
proplist:(
name:"TEXT", structure
)
)

Simultaneous

This ordering option is used to indicate when separate streams
to be presented in parallel. For example, assume GRAPHICS
VOICE data were to be presented using simultaneously

:=
:= <>

<> := name:"SIMULTANEOUS",
:= name:"VOICE", structure
name:"GRAPHICS", <graphics structure

proplist:(
name:"SIMULTANEOUS",
proplist:(
name:"VOICE", structure
name:"GRAPHICS", <graphics structure
)
)

Postel [Page 17]

August 1980
A Structured Format for Transmission of Multi-Media

Sequential

This option is used to indicate sequential time ordering.
media in the sub-tree below this PD are not separate streams
Using again the example above, assume GRAPHICS and VOICE data
to be presented using sequential ordering

:=
:= <>

<> := name:"SEQUENTIAL",
:= name:"VOICE", structure
name:"GRAPHICS", <graphics structure

proplist:(
name:"SEQUENTIAL",
proplist:(
name:"VOICE", structure
name:"GRAPHICS", <graphics structure
)
)

Independent

It is apparent that some output devices are very slow
comparison to others. An example which demonstrates this
facsimile. The majority of facsimile devices are slow.
detailed picture transmitted at 9600 baud takes minutes to print
It is inconvenient for the user to wait on such a device when
voice or text information which accompanies it is short

For example, if the document a facsimile image and the
"Hello Frank, here's a copy of that picture you requested."
user need not wait for the picture. The facsimile machine
be spooled, in which case he would pick up the picture later.
a sense the picture was time independent of the text

[Page 18]

August 1980
A Structured Format for Transmission of Multi-Media

:=
:= <>

<> := name:"INDEPENDENT",
:= name:"FACSIMILE", <facsimile structure
name:"TEXT", structure

proplist:(
name:"INDEPENDENT",
proplist:(
name:"FACSIMILE", <facsimile structure
name:"TEXT", structure
)
)

A Stream

By making use of the structure and the sequential ordering
it is possible to initiate a stream. The stream will proceed
its own pace until concluded

:=
:= <>

<> := name:"SEQUENTIAL",
:=
:= <>

<> := name:"SIMULTANEOUS",
:= name:"VOICE", structure
name:"GRAPHICS", <graphics structure

Postel [Page 19]

August 1980
A Structured Format for Transmission of Multi-Media

proplist:(
name:"SEQUENTIAL",
proplist:(
name:"SIMULTANEOUS",
proplist:(
name:"VOICE", structure
name:"GRAPHICS", <graphics structure
)endlist
name:"SIMULTANEOUS",
proplist:(
name:"VOICE", structure
name:"GRAPHICS", <graphics structure
)endlist
.
.
.
)
)

Such a document structure suggests a slide presentation

Multiple Active Stream

This example is exotic but illustrates what is possible. By
use of the structure and the simultaneous ordering it is
to start in parallel two or more separate streams. Each
will proceed at its own pace until all are concluded

:=
:= name:"SIMULTANEOUS",
=
:= name:"SEQUENTIAL",
=
:= name:"SIMULTANEOUS",
:= name:"VOICE",
structure
name:"GRAPHICS",
<graphics structure

[Page 20]

August 1980
A Structured Format for Transmission of Multi-Media

proplist:(
name:"SIMULTANEOUS",
proplist:(
name:"SEQUENTIAL",
proplist:(
name:"SIMULTANEOUS",
proplist:(
name:"VOICE", structure
name:"GRAPHICS", <graphics structure
)endlist
name:"SIMULTANEOUS",
proplist:(
name:"VOICE", structure
name:"GRAPHICS", <graphics structure
)endlist
.
.
.
)
name:"SEQUENTIAL",
proplist:(
name:"SIMULTANEOUS",
proplist:(
name:"VOICE", structure
name:"GRAPHICS", <graphics structure
)endlist
.
.
.
)
)
)

2.3.5. The

So far no explicit description has been given for the media
which fit into a PE. It is not known what types of media will
supported in the various document stations in the future. Those
which support is in part already available are

Standard formats for data in each of these media must be defined

Postel [Page 21]

August 1980
A Structured Format for Transmission of Multi-Media

2.3.6.

The text data may be structured according to a variety of
(yet to be defined). The top level of the data structure is
property list which identifies the protocol, and the version of
protocol

name:"TEXT", proplist:(
name:"PROTOCOL", <protocol>,
name:"VERSION", ,
name:"DATA", )

The first protocol is called PARAGRAPH, and the data is a list
paragraphs, where each paragraph is a text element

name:"DATA", list:(
text: <paragraph
text: <paragraph
.
.
.
)

2.3.7.

Since a good deal of research has been done towards implementing
transmission of voice data on the ARPANET, the Network
Protocol (NVP) provides the basis for the standard for voice
[24].

Voice data a property list which specifies the vocoder being used
the transmission protocol and the parcel data. The parcel data
is specific to the protocol used and is grouped in lists

name:"VOICE", proplist:(
name:"VOCODER", ,
name:"PROTOCOL", <protocol>,
name:"VERSION", ,
name:"DATA", )

The NVP protocol has a number of parameters, the version
specifies a certain set of the parameters used by the
hardware and software to set up timing and define the type of
used. It is not expected that within a document the version
will change

[Page 22]

August 1980
A Structured Format for Transmission of Multi-Media

NVP itself supports negotiation of these parameters to insure
ends of a network speech connection 'understand' one another.
no such interactive negotiation is possible in a document system
negotiation capabilities have been excluded. As differing
becomes available new versions may be defined

For the NVP protocol the data list will take the following form

name:"DATA", list:(
bitstr: bitstr: .
.
.
)

The items in the list are parcels. The individual parcels are
string data elements whose contents and length are predefined by
version number. The number of parcels in a parcel group
available from the item count in the enclosing list header

2.3.8.

There are a number of facsimile devices in use. While standards
being established by CCITT [25], of the devices available today
are incompatible due to proprietary compression algorithms.
description of fax data will allow for the possibility of
protocols

name:"FACSIMILE", proplist:(
name:"DEVICE", ,
name:"PROTOCOL", <protocol>,
name:"DATA", )

There are few facsimile devices interfaced to computers though,
the existing experiments in the ARPANET all use the RAPICOM 450.
first facsimile standard format will be based on the data
used for this machine [26]. That is, for device RAPICOM450
protocol BLOCK, the data will be

name:"DATA", list:(
bitstr:,
bitstr:,
.
.
.
)

Postel [Page 23]

August 1980
A Structured Format for Transmission of Multi-Media

Where an r450-block is a 585 bit unit

2.3.9.

The situation for graphics bears much similarity to facsimile
Devices on the market today have a variety of user interfaces
options. A similar structure is defined

name:"GRAPHICS", proplist:(
name:"DEVICE", ,
name:"PROTOCOL", <protocol>,
name:"DATA", )

There are several candidate protocols for use in describing
data in documents. One is the Network Graphics Protocol [27],
another is the Graphics Language [28,29], and a third is
SIGGRAPH Core System [30].

[Page 24]

August 1980
A Structured Format for Transmission of Multi-Media

3. EXAMPLES &

Example 1: Text

Suppose we want to send the following message

Date: 1979-03-29-11:46-08:00
From: Jon Postel Subject: Meeting
To: Danny Cohen CC:

Danny

Please mark your calendar for our meeting Thursday at 3 pm

--jon

It will be encoded in the structured format. The following
present successive steps in the top down generation of this message
The identification and command portions of the messages will not
expanded here (see [1]).

1.

2. (identification, command, document

3. (ID:<<identification>>,
CMD:<>,
DOC:( date, from, subject, to, cc, body))

4. (ID:<<identification>>,
CMD:<>,
DOC:(DATE:date
FROM:
SUBJECT:subject
TO:to
CC:cc
BODY:body))

5. (ID:<<identification>>,
CMD:<>,
DOC:(DATE: 1979-03-29-11:46-08:00,
FROM: (NET:ARPANET,HOST:ISIF,USER:Postel,PERSON:Jon Postel),
SUBJECT: Meeting Thursday
TO: (NET:ARPANET,HOST:ISIB,USER:Cohen,PERSON:Danny Cohen),
CC: (NET:ARPANET,HOST:ISIF,USER:Linda),
BODY
Danny

Postel [Page 25]

August 1980
A Structured Format for Transmission of Multi-Media
Examples &

Please mark your calendar for our
Thursday at 3 pm

--jon.))

6. PROPLIST
(ID:<<identification>>,
CMD:<>,
DOC
PROPLIST:(
DATE: 1979-03-29-11:46-08:00,
FROM
LIST:(
PROPLIST:(
NET:ARPANET
HOST:ISIF
USER:Postel
PERSON:Jon Postel
)ENDLIST
)ENDLIST
SUBJECT: Meeting Thursday
TO
LIST:(
PROPLIST:(
NET:ARPANET
HOST:ISIB
USER:Cohen
PERSON:Danny Cohen
)ENDLIST
)ENDLIST
CC
LIST:(
PROPLIST:(
NET:ARPANET
HOST:ISIF
USER:Linda
)ENDLIST
)ENDLIST
BODY
Danny

Please mark your calendar for our
Thursday at 3 pm

--jon
)
)

[Page 26]

August 1980
A Structured Format for Transmission of Multi-Media
Examples &

7. proplist:(
name:"ID", <<identification>>,
name:"CMD", <>,
name:"DOC",
proplist:(
name:"DATE", name:"1979-03-29-11:46-08:00",
name:"FROM",
list:(
proplist:(
name:"NET", name:"ARPANET",
name:"HOST", name:"ISIF",
name:"USER", name:"Postel",
name:"PERSON", name:"Jon Postel",
)endlist
)endlist
name:"SUBJECT", text:"Meeting Thursday",
name:"TO",
list:(
proplist:(
name:"NET", name:"ARPANET",
name:"HOST", name:"ISIB",
name:"USER", name:"Cohen",
name:"PERSON", name:"Danny Cohen",
)endlist
)endlist
name:"CC",
list:(
proplist:(
name:"NET", name:"ARPANET",
name:"HOST", name:"ISIF",
name:"USER", name:"Linda",
)endlist
)endlist
name:"BODY",
text:"Danny

Please mark your calendar for
meeting Thursday at 3 pm

--jon."
)
)

Postel [Page 27]

August 1980
A Structured Format for Transmission of Multi-Media
Examples &

Example 2: Multimedia

proplist:(
name:"ID", <<identification>>,
name:"CMD", <>,
name:"DOC",
proplist:(
name:"DATE", name:"1980-08-06-11:46-08:00",
name:"FROM",
list:(
proplist:(
name:"NET", name:"ARPANET",
name:"HOST", name:"ISIF",
name:"USER", name:"Postel",
name:"PERSON", name:"Jon Postel",
)endlist
)endlist
name:"SUBJECT", text:"Multimedia Test Message",
name:"TO",
list:(
proplist:(
name:"GROUP", name:"Multimedia Experiment List",
)endlist
)endlist
name:"CC",
list:(
proplist:(
name:"NET", name:"ARPANET",
name:"HOST", name:"ISIF",
name:"USER", name:"Linda",
)endlist
)endlist
name:"BODY",
proplist:(
name:"SEQUENTIAL",
proplist:(
name:"TEXT",
proplist:(
name:"PROTOCOL", name:"PARAGRAPH",
name:"VERSION", index:"1",
name:"DATA",
list:(
text:"This is a test of multimedia mail."
text:"I hope you like it."
)
)

[Page 28]

August 1980
A Structured Format for Transmission of Multi-Media
Examples &

name:"SIMULTANEOUS",
proplist:(
name:"VOICE",
proplist:(
name:"VOCODER", name:,
name:"PROTOCOL", name:"NVP",
name:"VERSION", index:"1",
name:"DATA",
list:(
bitstr: bitstr: )
)
name:"GRAPHICS",
proplist:(
name:"DEVICE", name:,
name:"PROTOCOL", name:<protocol>,
name:"VERSION", index:,
name:"DATA", )
)
)
name:"SEQUENTIAL",
proplist:(
name:"TEXT
proplist:(
name:"PROTOCOL", name:"PARAGRAPH",
name:"VERSION", index:"1",
name:"DATA",
list:(
text:"That was supposed to be some
and graphics in parallel."
text:"--jon."
)
)
)
)
)
)

Postel [Page 29]

August 1980
A Structured Format for Transmission of Multi-Media

[Page 30]

August 1980
A Structured Format for Transmission of Multi-Media

[1] Postel, J., "Internet Message Protocol," RFC 759, 113,
USC/Information Sciences Institute, August 1980.

[2] Bhushan, A., K. Pogran, R. Tomlinson, and J. White, "
Network Mail Headers," RFC 561, NIC 18516, September 1973.

[3] Myer, T., and D. Henderson, "Message Transmission Protocol,"
RFC 680, NIC 32116, 30 April 1975.

[4] Crocker, D., J. Vittal, K. Pogran, and D. Henderson, "Standard
the Format of ARPA Network Text Messages," RFC 733, NIC 41952,
21 November 1977.

[5] Barber, D., and J. Laws, "A Basic Mail Scheme for EIN," INWG 192,
February 1979.

[6] Braaten, O., "Introduction to a Mail Protocol,"
Computing Center, INWG 180, August 1978.

[7] Crocker, D., E. Szurkowski, and D. Farber, "An Internetwork
Distribution Capability - MMDF," Sixth Data
Symposium, ACM/IEEE, November 1979.

[8] Haverty, J., D. Henderson, and D. Oestreicher, "
Specification of an Inter-site Message Protocol," 8 July 1975.

[9] Thomas, R., "Providing Mail Services for NSW Users," BBN
Working Note 24, Bolt Beranek and Newman, October 1978.

[10] White, J., "A Proposed Mail Protocol," RFC 524, NIC 17140,
International, 13 June 1973.

[11] White, J., "Description of a Multi-Host Journal," NIC 23144,
International, 30 May 1974.

[12] White, J., "Journal Subscription Service," NIC 23143,
International, 28 May 1974.

[13] Levin, R., and M. Schroeder, "Transport of Electronic
Through a Network," Teleinformatics 79, Boutmy & Danthine (eds.)
North Holland Publishing Co., 1979.

[14] Earnest, L., and J. McCarthy, "DIALNET: A Computer
Study," Computer Science Department, Stanford University,
1978.

Postel [Page 31]

August 1980
A Structured Format for Transmission of Multi-Media

[15] Crispin M., "DIALNET: A Telephone Network Data
Protocol," DECUS Proceedings, Fall 1979.

[16] Caulkins, D., "The Personal Computer Network (PCNET) Project:
Status Report," Dr. Dobbs Journal of Computer Calisthenics
Orthodontia, v.5, n.6, June 1980.

[17] Postel, J., "NSW Transaction Protocol (NSWTP)," USC/
Sciences Institute, IEN 38, May 1978.

[18] Haverty, J., "MSDTP -- Message Services Data
Protocol," RFC 713, NIC 34739, April 1976.

[19] ISO-2014, "Writing of calendar dates in all-numeric form,"
Recommendation 2014, International Organization
Standardization, 1975.

[20] ISO-3307, "Information Interchange -- Representations of time
the day," Recommendation 3307, International Organization
Standardization, 1975.

[21] ISO-4031, "Information Interchange -- Representation of local
differentials," Recommendation 4031, International
for Standardization, 1978.

[22] Postel, J., "DOD Standard Internet Protocol," USC/
Sciences Institute, IEN 128, NTIS number AD A079730, January 1980.

[23] CCITT-X.121, "International Numbering Plan for Public
Networks," Recommendation X.121, CCITT, Geneva, 1978.

[24] Cohen, D., "Specifications for the Network Voice Protocol (NVP),"
NIC 42444, RFC 741, NSC 68, RR-75-39, USC/Information
Institute, January 1976.

[25] CCITT-T.30, "Procedures for Document Facsimile Transmission in
General Switched Telephone Network," Recommendation T.30,
Book, V. 7, The International Telephone and Telegraph
Committee, International Telecommunication Union, Geneva, 1977.

[26] Treadwell, S., "FAX File Format," ARPANET Message, 14
1979.

[27] Sproull, R., and E. Thomas, "A Network Graphics Protocol,"
NIC 24308, Xerox Palo Alto Research Center, August 1974.

[Page 32]

August 1980
A Structured Format for Transmission of Multi-Media

[28] Bisbey, R., and D. Hollingworth, "A Distributable
Display-Device-Independent Vector Graphics System for Command
Control," RR-80-87, USC/Information Sciences Institute, July 1980.

[29] Bisbey, R., D. Hollingworth, and B. Britt, "Graphics Language,"
TM-80-18, USC/Information Sciences Institute, July 1980.

[30] Graphics Standard Planning Committee, "Core System,"
Graphics, V. 13, N. 3, SIGGRAPH, ACM, August 1979.

Postel [Page 33]

August 1980
A Structured Format for Transmission of Multi-Media

[Page 34]

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