As per Relevance of the word messages, we have this rfc below:
NWG/RFC 744 JS5 8-Jan-78 21:59 42857
Network Working Group Joanne
Request for Comments: 744 JZS@
NIC: 42857 8 January 1978
MARS - A Message Archiving & Retrieval
I.
------------
This document describes a Message Archiving and Retrieval
(MARS) which has been developed at Computer Corporation of America;
utilizes the Datacomputer, a network database utility developed by
for ARPA. [Research and development of a prototype MARS system
supported by the Defense Advanced Research Projects Agency of
Department of Defense, under the ARPA Very Large Databases program
and was monitored by the Office of Naval Research under Contract No
N00014-76-C-0991.]
The Service is available, primarily, to groups for storage
teleconferencing transcripts. Is is also available, upon request,
individual ARPANET correspondents
There are both 'public' and 'private' messages in the database
Public messages may be retrieved by anyone. The public
includes the messages of the Header-People [@ MIT-MC] group, and
MsgGroup [@ USC-ISI] proceedings
Private messages may be retrieved only by the users who have
them, or anyone whose name appears on the list of message recipients
Messages archived using MARS are heavily indexed and can be
in a variety of ways, including Boolean combinations of
recipients, message composition date, any text words in the
subject, and text words in the message body. The MARS facilities
integrated very naturally into the existing collection
message-handling tools
. A message is designated for archiving by sending it
MARS-Filer @ CCA using one of the usual message-mailing tools
as SNDMSG
. A message is designated for retrieval by sending a request
ordinary mail to MARS-Retriever @ CCA
The Filer program checks for mail every hour; the Retriever
checks every quarter-hour. The periodicity can be altered to
demand but the intent is for MARS to operate as a background job
only during extremely low-activity periods
The next section (II) describes the indexing operation in
detail, and how to archive and retrieve messages. The last
(III) is an extractable user card
[Page 1]
NWG/RFC 744 JS5 8-Jan-78 21:59 42857
MARS - A Message Archiving & Retrieval
II. Using
----------
A. Message
----------------
For each message, a vector of parsed tokens is created. The
tokens are collected by the message-field in which they occurred --
be used as "indexes", i.e., values of inverted fields, by
Datacomputer
The Filer "indexes", essentially without analysis, except for
following
-- Each distinguishable section of the message is
separately; each header line is a separate inversion domain,
is the body of the message
-- The header lines which contain ARPANET addresses are analyzed
order to index separately on mailbox and host
-- The date-field is parsed and converted to the standard
internal date/time format, which is better adapted
less-than/greater-than comparisons, as in retrievals
specify a date range
-- One-character words in both the subject-field and
message-text field arbitrarily discarded
-- Two-character words in the message-text field are
discarded
-- Hyphenated phrases, i.e., words bound together by hyphens,
retained intact
-- All message formats which conform to RFC 733 standards
accommodated. The minimum requirements are: a date-field,
from-field, and a blank line between the message-header
message-body
[Page 2]
NWG/RFC 744 JS5 8-Jan-78 21:59 42857
MARS - A Message Archiving & Retrieval
B. To Archive
-------------------
There are three modes of filing currently supported by MARS, to wit
-- single-message mode, wherein the MARS-Filer mailbox appears
the message as an addressee
-- forwarded-message mode, wherein the MARS-Filer mailbox appears
the only primary recipient
-- batch mode, wherein the mailing envelope is addressed
MARS-Filer and the subject-field contains the keyword "batch".
Until the ARPANET standard for the format of messages is
universally, the variability amongst formats is still greater than
Filer can handle as it stands. Nonetheless, a user can
file any message in a "foreign" format by forwarding it to the
under the aegis of a mail-handling program which does produce
formats. Admittedly, the correct header-field indexing, as
above, will not be done on the enclosed message; but at least,
words in its unreadable header fields will appear as "text" words
the indexing
In the case of forwarded-message-mode filing, all interesting
information is extracted from the message-header of the
envelope prior to discarding it. The name of the archiver, the
and time the message was forwarded, and the subject-line
are recorded. The remainder is handled as though it were
non-forwarded message which had been CC'd to the Filer
A forwarded message may be 'annotated' by adding text (e.g., notes
comments, keywords) in the forwarding envelope. Annotations are
and retrieved as part of the archived message
In the case of batch-mode filing, only the archiver's name and
date and time s/he sent the package are extracted from the
envelope. The message-body portion is then treated as a series
individual messages
[Page 3]
NWG/RFC 744 JS5 8-Jan-78 21:59 42857
MARS - A Message Archiving & Retrieval
C. To Retrieve
--------------------
Retrievals are initiated by sending a Retrieval Request (which is
specially formatted message) to "MARS-Retriever@CCA".
messages are mailed back, one at a time, and will appear as new
in the requester's mailbox
Retrieval Request messages can be composed using any SNDMSG-type
program, as follows
. The recipient of the RR message must be MARS-Retriever @
. Other message header fields are ignored for
. The message body portion of the RR is used to compose
for performing the retrieval. Its format resembles a
header, or selected portions thereof
The following list defines which field names are recognized, and
notes on their interpretation. The scanning of each field
terminated by a carriage-return
DATE: The format of the date field is day-month-year. Use
hyphens is optional. This field will cause only
messages composed on the specified date to be retrieved
AFTER: Use of this field will retrieve messages composed
the specified date
SINCE: This field is interpreted like the AFTER: field
BEFORE: Use of this field will retrieve messages composed
the specified date
UNTIL: This field is interpreted like the BEFORE: field
FROM: This field is expected to contain a valid mailbox name
The host specification is optional. If more than one
is specified, ORing of the names is implicit
Retrieval based upon host specification alone has not
implemented
TO: This field is expected to contain one or more
mailbox names. The host specification is optional.
and commas between the names imply AND
[Page 4]
NWG/RFC 744 JS5 8-Jan-78 21:59 42857
MARS - A Message Archiving & Retrieval
SUBJECT: Use of this field will retrieve all messages
indexed subject-field contents match the
word(s). Spaces and commas imply AND. The use of
must be explicit
TEXT: Use of this field will retrieve all messages
indexed message-body contents match the
word(s). Spaces and commas imply AND. The use of
must be explicit
An interactive TENEX-based program for composing RRs is available
the filename is "RR.SAV". A copy of this program is stored on
Datacomputer, available via DFTP under node COMMON>MARS
There is also a copy of the program in CCA's directory at SRI-KA
another in the CCA-ACCAT directory at ISIA
[Page 5]
NWG/RFC 744 JS5 8-Jan-78 21:59 42857
MARS - A Message Archiving & Retrieval
III. MARS User
--------------
::
---------
Individual
. Include MARS-Filer@CCA on message distribution
. Forward message to MARS-Filer@CCA [Annotation is optional.]
Batches of
. Incorporate the mail file as the message-body of a
message sent to MARS-Filer@CCA with the clue "BATCH" in
subject-field
::
----------
Using RR
. RR is a TENEX-based interactive program designed to
Retrieval Request messages and to mail them to MARS-Retriever@CCA
Using SNDMSG-Type
. Send a message to MARS-Retriever@CCA, specifying the
criteria in the body of the message
Sample Retrieval
SUBJECT:RFC 733 or RFC733 ; OR must be
TEXT:MARS Project,goals ; spaces & commas imply
DATE: 14 November 1977
SINCE: 1 Nov 77 ; same as AFTER: 1 Nov 77
AFTER: 1 Dec 1977
UNTIL: 15 January 1978 ; same as BEFORE: 15 January 1978
BEFORE: Aug 7 76
FROM: JZS@CCA ; host specification is
FROM: Hacker,JZS ; comma implies OR (in FROM: field only
TO: CCA@SRI-KA ; host specification is
TO: SDD-0:,SDD-1: ; spaces and commas imply
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
