rfc2288.txt

来自「RFC 的详细文档！」· 文本 代码 · 共 564 行 · 第 1/2 页


RFC 2288                Bibligraphic Identifiers           February 1998


   within the publishing community as to when new ISSNs are assigned due
   to the change in the name of a periodical (e.g. Atlantic becomes
   Atlantic Monthly); or when a periodical is published both in printed
   and electronic versions (e.g. The New York Times).  The use of ISSNs
   in URNs will reflect these judgments and practices.

5. Serial Item and Contribution Identifiers

5.1 Overview

   The standard for Serial Item and Contribution Identifiers (SICI)
   codes, which has recently been extensively revised, is defined by
   NISO/ANSI Z39.56-1997 [NISO2].  The maintenance agency for the SICI
   code is the UnCover Corporation.

   SICI codes can be used to identify an issue of a serial, or a
   specific contribution (e.g., an article, or the table of contents)
   within an issue of a serial.  SICI codes are not assigned, they are
   constructed based on information about the issue or issue component
   in question.

   The complete syntax for the SICI code will not be discussed here; see
   NISO/ANSI Z39.56-1997 [NISO2] for details.  However, an example and
   brief review of the major components is needed to understand the
   relationship with the ISSN and how this identifier differs from an
   ISSN.  An example of a SICI code is: 0015-
   6914(19960101)157:1<62:KTSW>2.0.TX;2-F

   The first nine characters are the ISSN identifying the serial title.
   The second component, in parentheses, is the chronology information
   giving the date the particular serial issue was published.  In this
   example that date was January 1, 1996.  The third component, 157:1,
   is enumeration information (volume, number) for the particular issue
   of the serial.  These three components comprise the "item segment" of
   a SICI code.  By augmenting the ISSN with the chronology and/or
   enumeration information, specific issues of the serial can be
   identified.  The next segment, <62:KTSW>, identifies a particular
   contribution within the issue.  In this example we provide the
   starting page number and a title code constructed from the initial
   characters of the title.  Identifiers assigned to a contribution can
   be used in the contribution segment if page numbers are
   inappropriate.  The rest of the identifier is the control segment,
   which includes a check character.  Interested readers are encouraged
   to consult the standard for an explanation of the fields in that
   segment.






Lynch, et. al.               Informational                      [Page 6]

RFC 2288                Bibligraphic Identifiers           February 1998


5.2 Encoding Considerations and Lexical Equivalence

   The character set for SICIs is intended to be email-transport-
   transparent, so it does not present major problems.  However, all
   printable excluded and reserved characters from the URN syntax are
   valid in the SICI character set and must be %-encoded.

   Example of a SICI for an issue of a journal:

              URN:SICI:1046-8188(199501)13:1%3C%3E1.0.TX;2-F

   For an article contained within that issue:

          URN:SICI:1046-8188(199501)13:1%3C69:FTTHBI%3E2.0.TX;2-4

   Equivalence rules for SICIs are not appropriate for definition as
   part of the namespace and incorporation in areas such as cache
   management algorithms.  It is best left to resolver systems which try
   to determine if two SICIs refer to the same content.  Consequently,
   we do not propose any specific rules for equivalence testing through
   lexical manipulation.

5.3 Additional Considerations

   Since the serial is identified by an ISSN, some of the ambiguity
   currently found in the assignment of ISSNs carries over into SICI
   codes.  In cases where an ISSN may refer to a serial that exists in
   multiple formats, the SICI contains a qualifier that specifies the
   format type (for example, print, microform, or electronic).  SICI
   codes may be constructed from a variety of sources (the actual issue
   of the  serial, a citation or a record from an abstracting service)
   and, as such are based on the principle of using all available
   information, so there may be multiple SICI codes representing the
   same article [NISO2, Appendix D].  For example, one code might be
   constructed with access to both chronology and enumeration (that is,
   date of issue and volume, issue and page number), another code might
   be constructed based only on enumeration information and without
   benefit of chronology.  Systems that use SICI codes employ complex
   matching algorithms to try to match SICI codes constructed from
   incomplete information to SICI codes constructed with the benefit of
   all relevant information.










Lynch, et. al.               Informational                      [Page 7]

RFC 2288                Bibligraphic Identifiers           February 1998


6. Security Considerations

   This document proposes means of encoding several existing
   bibliographic identifiers within the URN framework. This document
   does not discuss resolution; thus questions of secure or
   authenticated resolution mechanisms are out of scope.  It does not
   address means of validating the integrity or authenticating the
   source or provenance of URNs that contain bibliographic identifiers.
   Issues regarding intellectual property rights associated with objects
   identified by the various bibliographic identifiers are also beyond
   the scope of this document, as are questions about rights to the
   databases that might be used to construct resolvers.

7. References

   [ISO1] NISO/ANSI/ISO 2108:1992 Information and documentation
         -- International standard book number (ISBN)
   [ISO2] ISO 3297:1986 Documentation -- International standard
         serial numbering (ISSN)
   [ISO3] ISO/DIS 3297 Information and documentation --
         International standard serial numbering (ISSN) (Revision of ISO
         3297:1986)
   [Moats] Moats, R., "URN Syntax", RFC 2141, May 1997.
   [NISO 1] NISO/ANSI Z39.9-1992 International standard serial
         numbering (ISSN)
   [NISO 2] NISO/ANSI Z39.56-1997 Serial Item and Contribution
         Identifier
   [Sollins & Masinter] Sollins, K., and L. Masinter, "Functional
         Requirements for Uniform Resource Names", RFC 1737, December
         1994.





















Lynch, et. al.               Informational                      [Page 8]

RFC 2288                Bibligraphic Identifiers           February 1998


8. Authors' Addresses

   Clifford Lynch
   Executive Director
   Coalition for Networked Information
   21 Dupont Circle
   Washington, DC 20036

   EMail: [e-mail]


   Cecilia Preston
   Preston & Lynch
   PO Box 8310
   Emeryville, CA 94662

   EMail: [e-mail]


   Ron Daniel Jr.
   Advanced Computing Lab, MS B287
   Los Alamos National Laboratory
   Los Alamos, NM, 87545

   EMail: [e-mail]


























Lynch, et. al.               Informational                      [Page 9]

RFC 2288                Bibligraphic Identifiers           February 1998


9.  Full Copyright Statement

   Copyright (C) The Internet Society (1998).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
























Lynch, et. al.               Informational                     [Page 10]