rfc1807.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.

WITHDRAW (O) Withdraw means the document is no longer
        available.  Some Institutions choose to delete the record
        others remove some of the fields.  It is up to each
        institution to decide how to process withdraw records.

        A withdraw record has all of the mandatory fields plus the
        withdraw field and a mandatory revision field.
        The Withdraw field should indicate the reason for the
        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, Computer
                           Science
            TITLE::        The Computerization of Oceanview with
                           High Speed Fiber Optics Communication
            REVISION::     January 21, 1995
            WITHDRAW::     Withdrawn, found to be irrelevant
            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 first
        inversion.  Editors should be listed here as well,
        identified with the usual "(ed.)" as shown below in the last
        example.

        If the report was not authored by a person (e.g., it was
        authored by a committee or a panel) use CORP-AUTHOR (see
        below) instead of AUTHOR.

        Multiple authors are entered by using multiple lines, each
        in the form of "AUTHOR:: <free-text>".

        The system preserves the order of the authors.

        Format:   AUTHOR:: <free-text>

        Example:  AUTHOR:: Finnegan, James A.
                  AUTHOR:: Pooh, Winnie The
                  AUTHOR:: Lastname, Firstname (ed.)


CORP-AUTHOR (O) -- The corporate author (e.g., a committee or a
        panel) that authored the report, which may be different
        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:: <free-text>

        Example:  CORP-AUTHOR:: Committee on long-range computing


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:: <free-text>

        Example:  CONTACT:: Prof. J. A. Finnegan, CS Dept,
                           Oceanview Univ., Oceanview, Kansas, 54321
                           Tel: [phone] <[e-mail]>





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 alphabetic
        (spelled out).  The "Day" is a 1- or 2-digit number.  The
        "Year" is a 4- digit number.

        Format:   DATE:: <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
        reasonable approximation to the total number of pages.

        Format:   PAGES:: <number>

        Example:  PAGES:: 48


COPYRIGHT (O) -- Copyright information.  Open ended format.  The
        COPYRIGHT field applies to the cited report, rather than
        to the current bibliographic record.

        Format:  COPYRIGHT:: <free-text>

        Example: COPYRIGHT:: Copyright for the report (c) 1991,
                            by J. A. Finnegan.  All rights
                            reserved.
                            Permission is granted for any academic
                            use of the report.


HANDLE (O) -- Handles are unique permanent identifiers that are
        used in the Handle Management System to retrieve location
        data.  A handle is a printable string which when given to
        a handle server returns the location of the data.

        Handles are used to identify digital objects stored within
        a digital library.  If the technical report is available in
        electronic form, the Handle MUST be supplied in the
        bibliographic record.

        Format is "HANDLE:: hdl:<naming authority>/string
        of characters".  The string of characters can be the
        report number of the technical report as assigned by the
        publisher.  For more information on handles and handle
        servers see the CNRI WEB page at



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:<naming authority>/string of
                          characters

        Example: HANDLE:: hdl:oceanview.electr/CS-TR-91-123


OTHER_ACCESS (O) -- For URLs, URNs, and other yet to be invented
       formatted retrieval systems.

        Only one URL or URN per occurrence of the field.

        URL and URN information is available in the internet
        drafts from the IETF (Internet Engineering Task Force).
        The most recent drafts can be found on the CNRI WEB page
        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:<URL>
                 OTHER_ACCESS:: URN:<URN>

        Example: OTHER_ACCESS:: URL:http://elib.stanford.edu/Docume
        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 will
        be registered and URNs will be viable unique identifiers.
        Until then this is a place holder.  For the latest URN
        drafts see CNRI WEB page at http://www.cnri.reston.va.us.


RETRIEVAL (O) -- Open-ended format describing how to get
        a copy of the full text.  This is an optional, repeatable
        field.

        No limitations are placed on the dissemination of the
        bibliographic records.  If there are limitations on the
        dissemination of the publication, it should be protected
        by some means such as passwords.  This format does not
        address this protection.

        Format:  RETRIEVAL:: <free-text>



Lasher & Cohen               Informational                     [Page 11]

RFC 1807           A Format for Bibliographic Records          June 1995


                 RETRIEVAL:: for full text with color pictures
                           send a self-addressed stamped envelope to
                           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 keywords
        are entered using multiple lines in the form of
        "KEYWORD::  <free-text>.

        Format:   KEYWORD:: <free-text>

        Example:  KEYWORD:: Scientific Communication
                  KEYWORD:: Communication Theory

CR-CATEGORY (O) -- Specify the CR-category.  The CR-category (the
        Computer Reviews Category) index (e.g., "B.3") should
        always be included, optionally followed by the name of that
        category.  If the name is specified it should be fully
        specified with parent levels as needed to clarify it, as in
        the second example below.  Use multiple lines for multiple
        categories.

        Every year, the January issue of CR has the full list
        of these categories, with a detailed discussion of the
        CR Classification System, and a full index.  Typically the
        full index appears in every January issue, and the top two
        levels in every issue.

        Format:   CR-CATEGORY:: <free-text>

        Example:  CR-CATEGORY:: D.1

        Example:  CR-CATEGORY:: B.3 Hardware, Memory Structures


PERIOD (O) -- Time period covered (date range).  Applicable
        primarily to progress reports, etc.  Any format is
        acceptable, as long as the two dates are separated with
        " to " (the word "to" surrounded by spaces) and each date
        is in the format allowed for dates, as described above for
        the date field.

        Format:   PERIOD:: <date> to <date>

        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 strongly
        encouraged to be internally consistent.

        Format:   SERIES:: <free-text>

        Example:  SERIES:: Communication


FUNDING (O) -- The name(s) of the funding organization(s).

        Format:   FUNDING:: <free-text>

        Example:  FUNDING:: ARPA


MONITORING (O) -- The name(s) of the monitoring organization(s).

        Format:   MONITORING:: <free-text>
        Example:  MONITORING:: ONR


CONTRACT (O) -- The contract number(s).

        Format:   CONTRACT:: <free-text>

        Example:  CONTRACT:: MMA-90-23-456


GRANT (O) -- The grant number(s).

        Format:   GRANT:: <free-text>

        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:: <free-text>

        Example:  LANGUAGE:: English
        Example:  LANGUAGE:: French




Lasher & Cohen               Informational                     [Page 13]

RFC 1807           A Format for Bibliographic Records          June 1995


NOTES (O) -- Miscellaneous free text.

        Format:   NOTES:: <free-text>

        Example:  NOTES:: This report is the full version of the
                        paper with the same title in IEEE Trans ASSP
                        Dec 1976


ABSTRACT (O) -- Highly recommended, but not mandatory.  Even
        though no limit is defined for its length, it is suggested
        not to expect applications to be able to handle more than
        10,000 characters.

        The ABSTRACT is expected to be used for subject searching
        since titles are not enough.  Even if the report is not in
        English, an English ABSTRACT is preferable.  If no formal
        abstract appears on document, the producers of the
        bibliographic records are encouraged to use pieces of the
        introduction, first paragraph, etc.

        Format:  ABSTRACT:: xxxx .............. xxxxxxxx
                            xxxx .............. xxxxxxxx

                            xxxx .............. xxxxxxxx
                            xxxx .............. xxxxxxxx

END (M) -- This is a mandatory field.  It must be the last entry
        of a record, identifying the record that it ends, by stating
        the same ID that was used at the beginning of the records,
        in its "ID::".

        Format:   END:: XXX//YYY

        Example:  END:: OUKS//CS-TR-91-123


             >>>>>>>   [END OF FORMAT DEFINITION]   <<<<<<<


A Note Regarding the Controlled Symbols of the Publishers

   In order to avoid conflicts among the symbols of the publishing
   organizations (the XXX part of the "ID:: XXX//YYY") it is suggested
   that the various organizations that publish reports (such as
   universities, departments, and laboratories) register their
   <publisher-ID> symbols and names, in a way similar to the
   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 ([e-mail]), of Stanford working
   with CNRI has agreed to coordinate this registration with the IANA
   for the publishers of Computer Science technical reports.  It is
   suggested that before using this format the publishing organizations
   would coordinate with her (by e-mail) their symbols and the names of
   their organizations.

   In order to help automated handling of the received bibliographic
   records, it is expected that the producers of bibliographic records
   will always use the same name, exactly, in the ORGANIZATION field.

Security Considerations

   Security issues are not discussed in this memo.

Acknowledgements

   This work was supported by the Advanced Research Projects Agency
   under Grant No. MDA-972-92-J-1029 with the Corporation for National
   Research Initiatives (CNRI).   Its content does not necessarily
   reflect the position or the policy of the Government or CNRI, and no
   official endorsement should be inferred.

Authors' Addresses

   Rebecca Lasher
   Mathematical and Computer Sciences Library
   M.S. 2125
   Stanford University
   Stanford, CA, USA 94305

   Phone: [phone]
   EMail: [e-mail]


   Danny Cohen
   Myricom
   325 N. Santa Anita Ave.
   Arcadia, CA 91006
   USA

   Phone: [phone]
   EMail: [e-mail]








Lasher & Cohen               Informational                     [Page 15]