As per Relevance of the word organization, we have this rfc below:
Network Working Group D.
Request For Comments: 1357
July 1992
A Format for E-mailing Bibliographic
Status of this
This memo provides information for the Internet community
It does not specify an Internet standard. Distribution
this memo is unlimited
This memo defines a format for E-mailing bibliographic records
technical reports. It is intended to accelerate the
of information about new Computer Science Technical Reports (CS-TR).
------------
Many Computer Science R&D organizations routinely announce
technical reports by mailing (via the postal services)
bibliographic records of these reports
These mailings have non-trivial cost and delay. In addition,
recipients cannot conveniently file them, electronically, for
retrieval and searches
Therefore, it is suggested that the publishing organizations
e-mail these announcements by using the following format
Organizations may automate to any degree (or not at all) both
creation of these records (about their own publications) and
handling of the records received from other organizations
This format is designed to be simple, for people and for machines
to be easy to read ("human readable") and create without any
programs, and to be compatible with E-mail
This format defines how bibliographic records are to be transmitted
It does not define what to do with them when received
This format is a "tagged" format with self-explaining
tags. It should be possible to prepare and to read
records using any text editor, without any special programs
Cohen (ed.) [Page 1]
RFC 1357 Format for E-mailing Bibliographic Records July 1992
This format was developed with considerable help and involvement
Computer Science and Library personnel from several organizations
including CMU, CNRI, Cornell, ISI, Meridian, MIT, Stanford, and UC
Key contributions were provided by Jerry Saltzer of MIT, and
Lannom of Meridian. The initial draft was prepared by Danny
and Larry Miller of ISI
The use of this format is encouraged. There are no limitations
its use
THE INFORMATION
----------------------
The various fields should follow the format described below
means Mandatory; a record without it is invalid
means Optional
The tags (aka Field-IDs) are shown in upper case
BIB-VERSION of this bibliographic records
ENTRY
CORP-
CONTACT for the author(s
DATE of
PAGES
COPYRIGHT, permissions and
RETRIEVAL
CR-
FUNDING organization(s
MONITORING organization(s
CONTRACT number(s
GRANT number(s
LANGUAGE
Cohen (ed.) [Page 2]
RFC 1357 Format for E-mailing Bibliographic Records July 1992
META
-----------
* Keep It Simple
* One bibliographic record for each publication, where
"publication" is whatever the publishing institution
as such
* A record contains several fields
* Each field starts with its tag (aka the field-ID) which is
reserved identifier (containing no separators) at the
of a new line with or without spaces before it), followed by
colons ("::"), followed by the field data
* Continuation lines: Lines are limited to 79 characters.
needed, fields may continue over several lines, with an
space in between. In order to simplify the use no special
is used to indicate continuation line. Hence, fields
terminated by a line that starts (apart from white space)
a word followed by two colons. Except for the "END::" that
terminated by the end of line.) For improved human
it is suggested to start continuation lines with some spaces
* Several fields are mandatory and must appear in the record.
fields (unless specifically not permitted to) may be in any
and may be repeated as needed (e.g., the AUTHOR field). The
of the repeated fields is always preserved
* Only printable ASCII characters may be used. Hence,
permissible characters are ASCII codes 040 (Space) through 176(~)
and line breaks which are \012 (LF) or \012\015 (CRLF).
lines indicate paragraph break. \009 (tab) must be replaced
spaces before submission. This specifically forbids tabs,
characters, DEL, backspaces, etc. (i.e., if used, the record
invalid.)
Throughout this document the word "publisher" means the
organization of a report (e.g., a university or a
thereof), not necessarily an organization authorized to issue
numbers
Cohen (ed.) [Page 3]
RFC 1357 Format for E-mailing Bibliographic Records July 1992
-----------------------------------------------------------------------
BIB-VERSION:: CS-TR-v2.0
ID:: OUKS//CS-TR-91-123
ENTRY:: January 15, 1992
ORGANIZATION:: Oceanview University, Kansas, Computer
TITLE:: The Computerization of Oceanview with
Speed Fiber Optics
TYPE:: Technical
REVISION:: 2, FTP retrieval information
AUTHOR:: Finnegan, James A
CONTACT:: Prof. J. A. Finnegan, CS Dept, Oceanview Univ, Oceanview
KS 54321 Tel: 913-456-7890
AUTHOR:: Pooh, Winnie
CONTACT:: 100 Aker
DATE:: December 1991
PAGES:: 48
COPYRIGHT:: Copyright for the report (c) 1991, by J. A. Finnegan
All rights reserved. Permission is granted for
academic use of the report
RETRIEVAL:: For full text with color pictures send a self-
stamped envelope to Prof. J. A. Finnegan, CS Dept
Oceanview University, Oceanview, KS 54321.
RETRIEVAL:: ASCII available via FTP from JUPITER.CS.OUKS.EDU with
pathname PUBS/computerization.txt. Login with FTP
username ANONYMOUS and password GUEST
File size: 123,456
CR-CATEGORY:: D.0
CR-CATEGORY:: C.2.2 Computer Sys Org, Communication nets, Net
SERIES::
FUNDING::
CONTRACT:: FAS-91-C-1234
MONITORING::
LANGUAGE::
NOTES:: This report is the full version of the paper with
same title in IEEE Trans ASSP Dec 1976
ABSTRACT::
Many alchemists in the country work on important fusion problems
All of them cooperate and interact with each other through
scientific literature. This scientific communication
has many advantages. Timeliness is not one of them
END:: OUKS//CS-TR-91-123
---------------------------- End of Example ---------------------------
For reference, the above example has about 1,750 characters (220
words) including about 250 characters (40 words) in the abstract
Cohen (ed.) [Page 4]
RFC 1357 Format for E-mailing Bibliographic Records July 1992
THE ACTUAL
-----------------
In the following double-quotes indicate complete strings. They
included only for grouping and are not expected to be used in
actual records
The term "Open Ended Format" in the following means arbitrary text
The BIB-VERSION, ID, ENTRY, and END field must appear as the first
second, third, and last fields, and may not be repeated in
record. All other fields may be repeated as needed
BIB-VERSION (M) -- This is the first field of any record. It is
mandatory field. It identifies the version of the format
to create this bibliographic record
BIB-VERSIONs that start with the letter X (case independent
are considered experimental. Bib-records sent with such
BIB-VERSION should NOT be incorporated in the permanent
of the recipient
Using this version of this format, this field is always
Format: BIB-VERSION:: CS-TR-v2.0
ID (M) -- This is the second field of any record. It is also
mandatory field. Its format is "ID:: XXX//YYY", where XXX
the publisher-ID (the controlled symbol of the publisher
and YYY is the ID (e.g., report number) of the publication
assigned by the publisher. This ID is typically printed
the cover, and may contain slashes
The organization symbols "DUMMY" and "TEST" (case independent
and any organization symbol starting with (
independent) are reserved for test records that should
be incorporated in the permanent database of the recipients
Format: ID:: <publisher-ID>//
Example: ID:: OUKS//CS-TR-91-123
**** See the note at the end regarding the ****
**** controlled symbols of the publishers *****
Cohen (ed.) [Page 5]
RFC 1357 Format for E-mailing Bibliographic Records July 1992
ENTRY (M) -- This is a mandatory field. It is the date of creating
bibliographic record
The format for ENTRY date is "Month Day, Year". The month
be alphabetic (spelled out). The "Day" is a 1- or 2-
number. The "Year" is a 4-digit number
Format: ENTRY::
Example: ENTRY:: January 15, 1992
ORGANIZATION (O) -- It is the full name spelled out (no acronyms
please) of the publishing organization. The use of this
is controlled together with the controlled symbol of
publisher (as discussed above for the ID field).
Avoid acronyms because there are many common acronyms, such
ISI and USC. Please provide it in ascending order, such
"X University, Y Department" (not "Y Department, X University").
Format: ORGANIZATION::
Example: ORGANIZATION:: Stanford University, Computer
TITLE (O) -- This is the title of the work as assigned by the author
This field should include the complete title with all
subtitles, if any
If the publication has no title (e.g., in withdrawal), a
TITLE field should be included
Format: TITLE::
Example: TITLE:: The Computerization of Oceanview with
Speed Fiber Optics
TYPE (O) -- Indicates the type of publication (summary, final
report, etc.) as assigned by the issuing organization
Format: TYPE::
Example: TYPE:: Technical
Cohen (ed.) [Page 6]
RFC 1357 Format for E-mailing Bibliographic Records July 1992
REVISION (O) -- Indicates that the current bibliographic record
a revision of a previously issued record and is intended
replace it. Revision information consists of an
followed by a comma, and by text in an open ended format
The revised bibliographic record should contain a
record for the publication, not just a list of changes
the old record. The default assumption is that a record
not a revision (i.e., specify only if it is), with that
being zero
The first token in this field is an integer revision number
Higher numbers indicate later revisions. Use the text
describe the revision. Reasons to send out a revised
include an error in the original, change in the
information, or withdrawal (see below).
Format: REVISION:: N,
Example: REVISION:: 2, FTP retrieval information
WITHDRAWING: A withdrawal of a record is a special case of
it. Hence, the standard way to withdraw records is by sending
revision record with (at least) all the mandatory fields, and
optional explanation in the NOTES field
It is OK on withdrawal to eliminate the title, by not
the TITLE field it or by providing it with no text (blank).
Example for withdrawing a bibliographic record::
BIB-VERSION:: CS-TR-v2.0
ID:: OUKS//CS-TR-91-123
ENTRY:: January 25, 1992
ORGANIZATION:: Oceanview University, Kansas, Computer
TITLE::
REVISION:: 4,
NOTES:: Withdrawn, found to be
END:: OUKS//CS-TR-91-123
This new record will replace all the fields of the
record for that publication. In this example it will
the title, the retrieval information provided earlier, and
mention the authors
Cohen (ed.) [Page 7]
RFC 1357 Format for E-mailing Bibliographic Records July 1992
AUTHOR (O) -- Personal names only. Normal last name first inversion
Editors should be listed here as well, identified with
usual "(ed.)" as shown below in the last example
If the report was not authored by a person (e.g., it
authored by a committee or a panel) use CORP-AUTHOR (see below
instead of AUTHOR
Multiple authors are entered by using multiple lines, each
the form of "AUTHOR:: ".
The system preserves the order of the authors
Format: AUTHOR::
Example: AUTHOR:: Finnegan, James A
AUTHOR:: Pooh, Winnie
AUTHOR:: Lastname, Firstname (ed.)
CORP-AUTHOR (O) -- The corporate author (e.g., a committee or
panel) that authored the report, which may be different
the ORGANIZATION issuing the report
In entering the corporate name please omit initial "the" or "a".
If it is really part of the name, please invert it
Format: CORP-AUTHOR::
Example: CORP-AUTHOR:: Committee on long-range
CONTACT (O) -- The contact for the author(s).
Open-ended, most likely E-mail and postal addresses
You may provide a CONTACT field for each author separately
or for all the AUTHOR fields
E-mail addresses should always be in "pointy brackets
(as in the example below).
Format: CONTACT::
Example: CONTACT:: Prof. J. A. Finnegan, CS Dept,
Univ., Oceanview, Kansas, 54321
Tel: 913-456-7890
Cohen (ed.) [Page 8]
RFC 1357 Format for E-mailing Bibliographic Records July 1992
DATE (O) -- The publication date. The formats are "Month Year"
"Month Day, Year". The month must be alphabetic (spelled out).
The "Day" is a 1- or 2-digit number. The "Year" is a 4-
number
Format: DATE::
Example: DATE:: January 1992
Example: DATE:: January 15, 1992
PAGES (O) -- Total number of pages, without being too picky about it
Final numbered page is actually preferred, if it is a
approximation to the total number of pages
Format: PAGES::
Example: PAGES:: 48
COPYRIGHT (O) -- Copyright, permissions and disclaimers.
ended format. The COPYRIGHT field applies to the
report, rather than to the current bibliographic record
On advice of counsel it is suggested that you seek
advice of yours
Format: COPYRIGHT::
Example: COPYRIGHT:: Copyright for the report (c) 1991,
by J. A. Finnegan. All rights reserved
Permission is granted for any
use of the report
RETRIEVAL INFORMATION (O) -- Open-ended format describing how to
a copy of the full text. It may include anything from
instructions to a variety of files (e.g., ASCII, TeX,
PostScript) to "Send $4.50 to ..." or "Send E-mail to ".
It is suggested to repeat this field for each retrieval
(e.g., one line for the FTP instructions to the ASCII version
and another for the PostScript version). When offering
like TeX all the related files (e.g., "\input mystyle")
be included. Please provide file sizes (in characters).
Means are not defined yet for providing the information
for automatic retrieval of files (such as via FTP). They
expected to be defined in the near future
Cohen (ed.) [Page 9]
RFC 1357 Format for E-mailing Bibliographic Records July 1992
No limitations are placed on the dissemination of
bibliographic records. If there are limitations on
dissemination of the publication, it should be protected
some means such as passwords. This format does not
this protection
Format: RETRIEVAL::
Example: RETRIEVAL:: For full text with color pictures
a self-addressed stamped envelope
Prof. J. A. Finnegan, CS Dept
Oceanview University, Oceanview, KS 54321.
RETRIEVAL:: ASCII available via FTP
JUPITER.CS.OUKS.EDU with the
PUBS/computerization.txt
Login with FTP, username ANONYMOUS
password GUEST
File size: 123,456
CR-CATEGORY (O) -- Specify the CR-category. The CR-category (
Computer Reviews Category) index (e.g., "B.3") should always
included, optionally followed by the name of that category.
the name is specified it should be fully specified with
levels as needed to clarify it, as in the second example below
Use multiple lines for multiple categories
The January 1992 issue of CR has the full list of
categories, with a detailed discussion of the CR
System, and a full index. Typically the full index appears
every January issue, and the top two levels in every issue
Format: CR-CATEGORY::
Example: CR-CATEGORY:: D.1
Example: CR-CATEGORY:: B.3 Hardware, Memory
PERIOD (O) -- Time period covered (date range). Applicable primarily
progress reports, etc. Any format is acceptable, as long as
two dates are separated with " to " (the word "to" surrounded
spaces) and each date is in the format allowed for dates,
described above for the date field
Format: PERIOD:: to
Example: PERIOD:: January 1990 to March 1990
Cohen (ed.) [Page 10]
RFC 1357 Format for E-mailing Bibliographic Records July 1992
SERIES (O) -- Series title, including volume number within series
Open-ended format, with producing institution
encouraged to be internally consistent
Format: SERIES::
Example: SERIES::
FUNDING (O) -- The name(s) of the funding organization(s).
Format: FUNDING::
Example: FUNDING::
MONITORING (O) -- The name(s) of the monitoring organization(s).
Format: MONITORING::
Example: MONITORING::
CONTRACT (O) -- The contract number(s).
Format: CONTRACT::
Example: CONTRACT:: MMA-90-23-456
GRANT (O) -- The grant number(s).
Format: CONTRACT::
Example: GRANT:: NASA-91-2345
LANGUAGE (O) -- The language in which the report is written
Please use the full English name of that language
Please include the Abstract in English, if possible
If the language is not specified, English is assumed
Format: LANGUAGE::
Example: LANGUAGE::
Cohen (ed.) [Page 11]
RFC 1357 Format for E-mailing Bibliographic Records July 1992
NOTES (O) -- Miscellaneous free text
Format: NOTES::
Example: NOTES:: This report is the full version of the
with the same title in IEEE Trans ASSP
1976
ABSTRACT (O) -- Highly recommended, but not mandatory. Even though
limit is defined for its length, it is suggested not to
applications to be able to handle more than 10,000 characters
The ABSTRACT is expected to be used for subject searching
titles are not enough. Even if the report is not in English,
English ABSTRACT is preferable. If no formal abstract
on document, the producers of the bibliographic records
encouraged to use pieces of the introduction, first paragraph
etc
Format: ABSTRACT:: xxxx ..............
xxxx ..............
xxxx ..............
xxxx ..............
END (M) -- This is a mandatory field. It must be the last entry of
record, identifying the record that it ends, by stating the
ID that was used at the beginning of the records, in its "ID::".
Format: END::
Example: END:: OUKS//CS-TR-91-123
>>>>>>> [END OF FORMAT DEFINITION] <<<<<<<
Cohen (ed.) [Page 12]
RFC 1357 Format for E-mailing Bibliographic Records July 1992
A Note Regarding the Controlled Symbols of the
In order to avoid conflicts among the symbols of the
organizations (the XXX part of the "ID:: XXX//YYY") it is
that the various organizations that publish reports (such
universities, departments, and laboratories) register
<publisher-ID> symbols and names, in a way similar to
registration of other key parameters and names in the Internet
Danny Cohen of ISI, has agreed to coordinate
registration for the publishers of Computer Science
reports. It is suggested that before using this format
publishing organizations would coordinate with him (by e-mail)
symbols and the names of their organizations. [Discussions are
progress to have these publisher-IDs registered with the
Assigned Numbers Authority (IANA) and listed in future editions
the Assigned Numbers document.]
In order to help automated handling of the received
records, it is expected that the producers of bibliographic
will always use the same name, exactly, in the ORGANIZATION field
Security
Security issues are not discussed in this memo
Author's
Danny
USC - Information Sciences
4676 Admiralty
Marina del Rey, California 90292-6695
Phone: 310-822-1511
Fax: 310-823-6714
EMail: Cohen@ISI.
Cohen (ed.) [Page 13]
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
