As per Relevance of the word computer, we have this rfc below:
Network Working Group R.
Request For Comments: 1807
Obsoletes: 1357 D.
Category: Informational
June 1995
A Format for Bibliographic
Status of this
This memo provides information for the Internet community. This
does not specify an Internet standard of any kind. Distribution
this memo is unlimited
This RFC defines a format for bibliographic records
technical reports. This format is used by the Cornell
Dienst protocol and the Stanford University SIFT system.
original RFC (RFC 1357) was written by D. Cohen, ISI, July 1992.
This is a revision of RFC 1357. New fields include handle
other_access, keyword, and withdraw
Many universities and other 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
Publishing organizations that wish to use e-mail or file transfer
obtain these announcements can do so 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,
be easy to read ("human readable") and create without any
programs
This RFC defines the format of bibliographic records, not how
process them
Lasher & Cohen Informational [Page 1]
RFC 1807 A Format for Bibliographic Records June 1995
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
This RFC includes the CR-CATEGORY, a field useful for
Science publications. It is expected that similar fields will
added for other domains
This format, as described in RFC 1357, was implemented as part of
Dienst system and has been in use by the five ARPA-funded
science institutions to exchange bibliographic records (Cornell, SU
UC, MIT, and CMU). Programs have been written to map between
RFC and structured USMARC (format developed at the Library
Congress) cataloging records, also from USMARC to the RFC
The focus of this ARPA-funded research has been into many aspects
digital libraries including searching and accessing techniques
do not necessarily use bibliographic records (for example,
language processing, automatic and full-text indexing). However,
continued use of bibliographic records is expected to remain
important part of the library system environment of the future
its use is an important link between the physical world of
works and the on-line world of digital objects. The format
in this paper allows a link between these two worlds to be created
This format was developed with considerable help and involvement
Computer Science and Library personnel from several organizations
including Carnegie Mellon University, Corporation for
Research Initiatives (CNRI), Cornell University, University
Southern California/Information Sciences Institute (ISI),
(now called DynCorp), Massachusetts Institute of Technology,
University, and the University of California. Key contributions
provided by Jerry Saltzer of MIT, and Larry Lannom of DynCorp.
initial draft was prepared by Danny Cohen and Larry Miller of ISI
The revision was done by Rebecca Lasher from Stanford with
from the CS-TR participants
This RFC does not place any limitations on the dissemination of
bibliographic records. If there are limitations on the
of the publication, it should be protected by some means such
passwords. This RFC does not address this protection
The use of this format is encouraged. There are no limitations
its use
Lasher & Cohen Informational [Page 2]
RFC 1807 A Format for Bibliographic Records June 1995
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
OTHER_
CR-
MONITORING organization(s
FUNDING organization(s
CONTRACT number(s
GRANT number(s
LANGUAGE
Lasher & Cohen Informational [Page 3]
RFC 1807 A Format for Bibliographic Records June 1995
Meta
* Keep It Simple
* One bibliographic record for each publication, where
"publication" is whatever the publishing
defines 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
beginning of a new line with or without spaces before it),
followed by two colons ("::"), followed by the field data
* Continuation lines: Lines are limited to 79 characters
When needed, fields may continue over several lines, with
implied space in between. In order to simplify the use
special marking is used to indicate continuation line
Hence, fields are terminated by a line that starts (
from white space) with a word followed by two colons.
for the "END::" that is terminated by the end of line.)
improved human readability it is suggested to
continuation lines with some spaces
* Several fields are mandatory and must appear in the record
All fields (unless specifically not permitted to) may be
any order and may be repeated as needed (e.g., the
field). The order of the repeated fields is
preserved
* Only printable ASCII characters are to be used. The
characters are ASCII codes 040 (Space) through 176(~)
and line breaks which are \012 (LF) or \012\015 (CRLF).
Empty lines indicate paragraph break. \009 (tab) must
replaced by spaces. This specifically forbids tabs,
characters, DEL, backspaces, etc. (i.e., if used, the record
invalid.)
However full 8 bit ASCII may be used. WARNING:
electronic mailers cannot handle 8 bit ASCII and
records may need to be transported via other mechanisms
Throughout this document the word "publisher" means
publishing organization of a report (e.g., a university or
department thereof), not necessarily an organization
to issue ISBN numbers
Lasher & Cohen Informational [Page 4]
RFC 1807 A Format for Bibliographic Records June 1995
-------------------------------------------------------------
BIB-VERSION:: CS-TR-v2.1
ID:: OUKS//CS-TR-91-123
ENTRY:: January 15, 1992
ORGANIZATION:: Oceanview University, Kansas, Computer
TYPE:: Technical
REVISION:: January 5, 1995; FTP access information
TITLE:: Scientific Communication must be
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
for any academic use of the report
HANDLE:: hdl:oceanview.electr/CS-TR-91-123
OTHER_ACCESS:: url:http://electr.oceanview.edu/CS-TR-91-123
OTHER_ACCESS:: url:ftp://electr.oceanview.edu/CS-TR-91-123
RETRIEVAL:: send email to Finnegan@cs.ouks.edu with fax
KEYWORD:: Scientific
CR-CATEGORY:: D.0
CR-CATEGORY:: C.2.2 Computer Sys Org, Communication nets,
SERIES::
FUNDING::
CONTRACT:: FAS-91-C-1234
MONITORING::
LANGUAGE::
NOTES:: This report is the full version of the paper
the 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,689 characters (184
words) including about 249 characters (36 words) in the abstract
Lasher & Cohen Informational [Page 5]
RFC 1807 A Format for Bibliographic Records June 1995
The Actual
The term "Open Ended Format" in the following means arbitrary text
In the following double-quotes indicate complete strings. They
included only for grouping and are not expected to be used in
actual records
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
used to create this bibliographic record. This RFC
BIB-Version TR-v2.1
BIB-VERSIONs that start with the letter X (
independent) are considered experimental. Bib-
sent with such a BIB-VERSION should NOT be
in the permanent database of the recipient
Using this version of this format, this field is always
Format: BIB-VERSION:: CS-TR-v2.1
ID (M) -- This is the second field of any record. It is also
mandatory field. The ID field identifies the
record and is used in management of these records
Its format is "ID:: XXX//YYY", where XXX is
publisher-ID (the controlled symbol of the publisher
and YYY is the ID (e.g., report number) of
publication as assigned by the publisher. This ID
typically printed on the cover, and may contain slashes
The organization symbols "DUMMY" and "TEST" (
independent) are reserved for test records that should
be incorporated in the permanent database of
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 *****
Lasher & Cohen Informational [Page 6]
RFC 1807 A Format for Bibliographic Records June 1995
ENTRY (M) -- This is a mandatory field. It is the date
creating this bibliographic record
The format for ENTRY date is "Month Day, Year".
month must be alphabetic (spelled out). The "Day" is
1- or 2-digit 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
name is controlled together with the controlled symbol
the publisher (as discussed above for the ID field).
Avoid acronyms because there are many common acronyms
such as ISI and USC. Please provide it in
order, such as "X University, Y Department" (not "
Department, X University").
Format: ORGANIZATION::
Example: ORGANIZATION:: Stanford University, Department
Computer
TITLE (O) -- This is the title of the work as assigned by
author. This field should include the complete title
all the subtitles, if any
Format: TITLE::
Example: TITLE:: The Computerization of Oceanview
High Speed Fiber Optics
TYPE (O) -- Indicates the type of publication (summary,
project report, etc.) as assigned by the
organization
Format: TYPE::
Example: TYPE:: Technical
REVISION (O) -- Indicates that the current bibliographic record
a revision of a previously issued record and is
Lasher & Cohen Informational [Page 7]
RFC 1807 A Format for Bibliographic Records June 1995
to replace it. Revision information consists of a
and/or followed by a semicolon and by text in an
ended format. The revised bibliographic record
contain a complete record for the publication, not just
list of changes to the old record. If revision
omitted, the record is assumed to be a new record and
a revision. If the revision date is specified as 0,
is assumed to be January 1, 1900 (the previous RFC,
revision data of 0, 1, 2, 3, etc. this specification is
programs that might process records from RFC1357).
The text before the semicolon in this field is a date
the form month day, year. Any record with a more
revision date replaces completely any record with
earlier revision date (supplied either explicitly or
default). Use the text to describe the revision
Reasons to send out a revised record include an error
the original, or change in the access information
Format: REVISION:: January 1, 1995;
Example: REVISION:: January 1, 1995; FTP
WITHDRAW (O) Withdraw means the document is no
available. Some Institutions choose to delete the
others remove some of the fields. It is up to
institution to decide how to process withdraw records
A withdraw record has all of the mandatory fields plus
withdraw field and a mandatory revision field
The Withdraw field should indicate the reason for
withdraw in free text
Example for withdrawing a bibliographic record::
BIB-VERSION:: CS-TR-v2.1
ID:: OUKS//CS-TR-91-123
ENTRY:: January 21, 1995
ORGANIZATION:: Oceanview University, Kansas,
TITLE:: The Computerization of Oceanview
High Speed Fiber Optics
REVISION:: January 21, 1995
WITHDRAW:: Withdrawn, found to be
END:: OUKS//CS-TR-91-123
Lasher & Cohen Informational [Page 8]
RFC 1807 A Format for Bibliographic Records June 1995
AUTHOR (O) -- Personal names only. Normal last name
inversion. Editors should be listed here as well
identified with the usual "(ed.)" as shown below in the
example
If the report was not authored by a person (e.g., it
authored by a committee or a panel) use CORP-AUTHOR (
below) instead of AUTHOR
Multiple authors are entered by using multiple lines,
in 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
from 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
A CONTACT field for each author should be provided
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
Oceanview Univ., Oceanview, Kansas, 54321
Tel: 913-456-7890
Lasher & Cohen Informational [Page 9]
RFC 1807 A Format for Bibliographic Records June 1995
DATE (O) -- The publication date. The formats are "Month Year
and "Month Day, Year". The month must be
(spelled out). The "Day" is a 1- or 2-digit number.
"Year" is a 4- digit number
Format: DATE::
Example: DATE:: January 1992
Example: DATE:: January 15, 1992
PAGES (O) -- Total number of pages, without being too picky
it. Final numbered page is actually preferred, if it is
reasonable approximation to the total number of pages
Format: PAGES::
Example: PAGES:: 48
COPYRIGHT (O) -- Copyright information. Open ended format.
COPYRIGHT field applies to the cited report, rather
to the current bibliographic record
Format: COPYRIGHT::
Example: COPYRIGHT:: Copyright for the report (c) 1991,
by J. A. Finnegan. All
reserved
Permission is granted for any
use of the report
HANDLE (O) -- Handles are unique permanent identifiers that
used in the Handle Management System to retrieve
data. A handle is a printable string which when given
a handle server returns the location of the data
Handles are used to identify digital objects stored
a digital library. If the technical report is available
electronic form, the Handle MUST be supplied in
bibliographic record
Format is "HANDLE:: hdl:authority>/
of characters". The string of characters can be
report number of the technical report as assigned by
publisher. For more information on handles and
servers see the CNRI WEB page
Lasher & Cohen Informational [Page 10]
RFC 1807 A Format for Bibliographic Records June 1995
http://www.cnri.reston.va.us
**** NOTE: White space in HANDLE due to line wrap is ignored
Format: HANDLE:: hdl:authority>/string
Example: HANDLE:: hdl:oceanview.electr/CS-TR-91-123
OTHER_ACCESS (O) -- For URLs, URNs, and other yet to be
formatted retrieval systems
Only one URL or URN per occurrence of the field
URL and URN information is available in the
drafts from the IETF (Internet Engineering Task Force).
The most recent drafts can be found on the CNRI WEB
at http://www.cnri.reston.va.us
**** NOTE: White space in a URL or URN due to line wrap is ignored
Format: OTHER_ACCESS:: URL:
OTHER_ACCESS:: URN:
Example: OTHER_ACCESS:: URL:http://elib.stanford.edu/
nt/STANFORD.CS:CS-TN-94-1
Example: OTHER_ACCESS:: URL:ftp://JUPITER.CS.OUKS.EDU/PUBS
computerization.txt
When the URN standard is finalized naming authorities
be registered and URNs will be viable unique identifiers
Until then this is a place holder. For the latest
drafts see CNRI WEB page at http://www.cnri.reston.va.us
RETRIEVAL (O) -- Open-ended format describing how to
a copy of the full text. This is an optional,
field
No limitations are placed on the dissemination of
bibliographic records. If there are limitations on
dissemination of the publication, it should be
by some means such as passwords. This format does
address this protection
Format: RETRIEVAL::
Lasher & Cohen Informational [Page 11]
RFC 1807 A Format for Bibliographic Records June 1995
RETRIEVAL:: for full text with color
send a self-addressed stamped envelope
Prof. J.A. Finnegan, CS Dept
Oceanview University, Oceanview, KS 54321
KEYWORD (O) -- Specify any keywords, controlled or uncontrolled
This is an optional, repeatable field. Multiple
are entered using multiple lines in the form
"KEYWORD:: .
Format: KEYWORD::
Example: KEYWORD:: Scientific
KEYWORD:: Communication
CR-CATEGORY (O) -- Specify the CR-category. The CR-category (
Computer Reviews Category) index (e.g., "B.3")
always be included, optionally followed by the name of
category. If the name is specified it should be
specified with parent levels as needed to clarify it, as
the second example below. Use multiple lines for
categories
Every year, the January issue of CR has the full
of these categories, with a detailed discussion of
CR Classification System, and a full index. Typically
full index appears in every January issue, and the top
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).
primarily to progress reports, etc. Any format
acceptable, as long as the two dates are separated
" to " (the word "to" surrounded by spaces) and each
is in the format allowed for dates, as described above
the date field
Format: PERIOD:: to
Example: PERIOD:: January 1990 to March 1990
Lasher & Cohen Informational [Page 12]
RFC 1807 A Format for Bibliographic Records June 1995
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: GRANT::
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::
Example: LANGUAGE::
Lasher & Cohen Informational [Page 13]
RFC 1807 A Format for Bibliographic Records June 1995
NOTES (O) -- Miscellaneous free text
Format: NOTES::
Example: NOTES:: This report is the full version of
paper with the same title in IEEE Trans
Dec 1976
ABSTRACT (O) -- Highly recommended, but not mandatory.
though no limit is defined for its length, it is
not to expect applications to be able to handle more
10,000 characters
The ABSTRACT is expected to be used for subject
since titles are not enough. Even if the report is not
English, an English ABSTRACT is preferable. If no
abstract appears on document, the producers of
bibliographic records are encouraged to use pieces of
introduction, first paragraph, etc
Format: ABSTRACT:: xxxx ..............
xxxx ..............
xxxx ..............
xxxx ..............
END (M) -- This is a mandatory field. It must be the last
of a record, identifying the record that it ends, by
the same ID that was used at the beginning of the records
in its "ID::".
Format: END:: XXX//
Example: END:: OUKS//CS-TR-91-123
>>>>>>> [END OF FORMAT DEFINITION] <<<<<<<
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
Lasher & Cohen Informational [Page 14]
RFC 1807 A Format for Bibliographic Records June 1995
Rebecca Lasher (RLASHER@Forsythe.stanford.edu), of Stanford
with CNRI has agreed to coordinate this registration with the
for the publishers of Computer Science technical reports. It
suggested that before using this format the publishing
would coordinate with her (by e-mail) their symbols and the names
their organizations
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
This work was supported by the Advanced Research Projects
under Grant No. MDA-972-92-J-1029 with the Corporation for
Research Initiatives (CNRI). Its content does not
reflect the position or the policy of the Government or CNRI, and
official endorsement should be inferred
Authors'
Rebecca
Mathematical and Computer Sciences
M.S. 2125
Stanford
Stanford, CA, USA 94305
Phone: +1 415 723 0864
EMail: rlasher@forsythe.stanford.
Danny
325 N. Santa Anita Ave
Arcadia, CA 91006
Phone: +1 818 821 5555
EMail: Cohen@myri.
Lasher & Cohen Informational [Page 15]
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
