[URN] draft Bibliographic Identifiers to URNs

[Cecilia Preston <[e-mail]>]

As promised for the next meeting.  Cliff, Ron and I are responsible for
content, I am responsible for typos etc.


--Cecilia


<fontfamily><param>Times</param><bigger>

</bigger></fontfamily><bigger><fontfamily><param>Courier</param>Internet
Draft                                Clifford
Lynch</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>draft-ietf-urn-biblio-00.txt
       University of
California</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>22 March 1997           
                    Cecilia
Preston</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>Expires in six months   
                    Preston &
Lynch</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>                        
                     Ron Daniel
Jr.</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>                        
     Los Alamos National
Laboratory</fontfamily><fontfamily><param>Times</param>



</fontfamily><fontfamily><param>Courier</param>          Using Existing
Bibliographic Identifiers</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>                        
    as </fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>                  
Uniform Resource Names</fontfamily><fontfamily><param>Times</param>



</fontfamily><fontfamily><param>Courier</param>Status of this
Document</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>This document is an
Internet-Draft.  Internet-Drafts are
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>working documents of the
Internet Engineering Task Force
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>(IETF), its areas, and
its working groups.  Note that other
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>groups may also
distribute working documents as
Internet-</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>Drafts.</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>Internet-Drafts are
draft documents valid for a maximum of
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>six months and may be
updated, replaced or made obsolete by
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>other documents at any
time.  It is inappropriate to use
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>Internet-Drafts as
reference material or to cite them other
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>than as works in
progress. </fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>Distribution of this
document is unlimited.  Please send
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>comments to
[e-mail] and
[e-mail].</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>This document does not
specify a standard; it is purely
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>informational.</fontfamily><fontfamily><param>Times</param>



</fontfamily><fontfamily><param>Courier</param>0.
Abstract</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>A system for Uniform
Resource Names (URNs) must be
capable</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>of supporting
identifiers from existing widely-used naming
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>systems.  This document
discusses how three major
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>bibliographic
identifiers (the ISBN, ISSN and SICI) can be
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>supported within the URN
framework and the currently
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>proposed syntax for
URNs.</fontfamily><fontfamily><param>Times</param>




</fontfamily><fontfamily><param>Courier</param>                        
                           [Page
1]</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>INTERNET
DRAFT:Bibliographic Identifiers as URNs    
3/1997</fontfamily><fontfamily><param>Times</param>



</fontfamily><fontfamily><param>Courier</param>1.
Introduction</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>The ongoing work of
several IETF working groups, most
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>recently in the Uniform
Resource Names working group, has
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>culminated the
development of a syntax for Uniform Resource
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>Names (URNs).   The
functional requirements and overall
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>framework for Uniform
Resource Names are specified in RFC
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>1737 [Sollins &
Masinter] and the current proposal for the
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>URN syntax is
draft-ietf-urn-syntax-04.txt
[Moats].</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>As part of the
validation process for the development of
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>URNs the IETF working
group has agreed that it is important
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>to demonstrate that the
current URN syntax proposal can
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>accommodate existing
identifiers from well managed
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>namespaces.  One such
well-established infrastructure for
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>assigning and managing
names comes from the bibliographic
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>community. 
Bibliographic identifiers function as names for
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>objects that exist both
in print and, increasingly, in
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>electronic formats. 
This Internet draft demonstrates the
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>feasibility of
supporting three representative bibliographic
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>identifiers within the
currently proposed URN framework and
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>syntax.</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>Note that this document
does not purport to define the
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>"official" standard way
of doing so; it merely demonstrates
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>feasibility.  It has not
been developed in consultation with
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>the standards bodies and
maintenance agencies that oversee
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>the existing
bibliographic identifiers.  Any actual Internet
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>standard for encoding
these bibliographic identifiers as
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>URNs will need to be
developed in consultation with the
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>responsible standards
bodies and maintenance
agencies.</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>In addition, there are
several open questions with regard to
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>the management and
registry of Namespace Identifiers (NIDs)
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>for URNs.  For purposes
of illustration, we have used the
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>three NIDs "ISBN",
"ISSN" and "SICI" for the three
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>corresponding
bibliographic identifiers discussed in this
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>document.  While we
believe this to be the most appropriate
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>choice, it is not the
only one.  The NIDs could be based on
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>the standards body and
standard number (e.g.
"US-ANSI-NISO-</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>Z39.56-1997" rather than
"SICI").  Alternatively, one could
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>lump all bibliographic
identifiers into a single
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>"BIBLIOGRAPHIC" name
space, and structure the
namespace-</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>                        
                          [Page
2]</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param> INTERNET
DRAFT:Bibliographic Identifiers as URNs    
3/1997</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>specific string to
specify which identifier is being
used.</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>We do not believe that
these are advantageous approaches,
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>but must wait for the
outcome of namespace management
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>discussions in the
working group. </fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>For the purposes of this
document, we have selected three
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>major bibliographic
identifiers (national and international)
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>to fit within the URN
framework.  These are the
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>International Standard
Book Number (ISBN) [ISO1], the
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>International Standard
Serials Number (ISSN) [NISO1,ISO2,
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>ISO3], and the Serial
Item and Contribution Identifier
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>(SICI) [NISO2].  ISBNs
are used to identify monographs
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>(books).  ISSNs are used
to identify serial publications
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>(journals, newspapers)
as a whole.  SICIs augment the ISSN
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>in order to identify
individual issues of serial
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>publications, or
components within those issues (such as an
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>individual article, or
the table of contents of a given
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>issue).  The ISBN and
ISSN are defined in the United States
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>by standards issued by
the National Information Standards
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>Organization (NISO) and
also by parallel international
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>standards issued under
the auspices of the International
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>Organization for
Standardization (ISO).  NISO is the
ANSI-</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>accredited standards
body serving libraries, publishers and
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>information services. 
The SICI code is defined by a NISO
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>document in the United
States and does not have a parallel
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>international standards
document at present. </fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>Many other bibliographic
identifiers are in common use (for
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>example, the CODEN,
numbers assigned by major bibliographic
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>utilities such as OCLC
and RLG, national library numbers
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>such as the Library of
Congress Control Number) or are under
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>development.  While we
do not discuss them in this document,
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>many of these will also
need to be supported within the URN
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>framework as it moves to
large scale implementation.  The
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>issues involved in
supporting those additional identifiers
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>are anticipated to be
broadly similar to those involved in
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>supporting ISBNs, ISSNs,
and SICIs.</fontfamily><fontfamily><param>Times</param>



</fontfamily><fontfamily><param>Courier</param>2. Identification vs.
Resolution</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>It is important to
distinguish between the resource
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>identified by a URN and
the resources that can reasonably be
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>provided when attempting
to resolve an identifier. 
For</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>                        
                           [Page
3]</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>INTERNET
DRAFT:Bibliographic Identifiers as URNs    
3/1997</fontfamily><fontfamily><param>Times</param>



</fontfamily><fontfamily><param>Courier</param>example, the ISSN
0040-781X identifies the
popular</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>"Time".  All of it,
every issue for from the start of
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>publication to present. 
Resolving such an identifier should
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>not result in the
equivalent of hundreds of thousands of
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>pages of text and photos
being dumped to the user's
machine.</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>It is more reasonable
for ISSNs to resolve to a navigational
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>system, such as an
HTML-based search form, so the user may
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>select issues or
articles of interest.  ISBNs and SICIs,
on</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>the other hand, do
identify finite, manageably-sized
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>objects, but they may
still be large enough that resolution
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>to a hierarchical system
is appropriate.  </fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>In addition, the
materials identified by an ISSN, ISBN or
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>SICI may exist only in
printed or other physical form, not
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>electronically.  The
best that a resolver may be able to
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>offer is information
about where to get the physical
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>resource, such as
library holdings or a bookstore or
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>publisher order form. 
The URN Framework provides resolution
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>services that may be
used to describe any differences
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>between the resource
identified by a URN and the resource
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>that would be returned
as a result of resolving that
URN.</fontfamily><fontfamily><param>Times</param>



</fontfamily><fontfamily><param>Courier</param>3. International
Standard Book Numbers</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>3.1
Overview</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>An International
Standard Book Number (ISBN) identifies an
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>edition of a monographic
work.  The ISBN is defined by the
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>standard NISO/ANSI/ISO
2108:1992 [ISO 1]</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>Basically, an ISBN is a
ten-digit number (actually, the last
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>digit can be the letter
"X" as well, as described below)
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>which is divided into
four variable length parts usually
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>separated by hyphens
when printed.  The parts are as follows
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>(in this order):
</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>* a group identifier
which specifies a group of publishers,
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>based on national,
geographic or some other
criteria,</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>* the publisher
identifier,</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>                        
                          [Page
4]</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>INTERNET
DRAFT:Bibliographic Identifiers as URNs    
3/1997</fontfamily><fontfamily><param>Times</param>



</fontfamily><fontfamily><param>Courier</param>* the title
identifier,</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>* and a modulus 11 check
digit, using X in lieu of
10.</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>The group and publisher
number assignments are managed in
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>such a way that the
hyphens are not needed to parse the ISBN
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>unambiguously into its
constituent parts.  However, the ISBN
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>is normally transmitted
and displayed with hyphens to make
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>it easy for human beings
to recognize these parts without
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>having to make reference
to or have knowledge of the number
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>assignments for group
and publisher
identifiers.</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>3.2 Encoding
Considerations</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>Embedding ISBNs within
the URN framework presents no
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>particular coding
problems, since all of the characters that
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>can appear in an ISBN
are valid in the identifier segment of
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>the URN.  %-encoding is
never needed.</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>Example:
URN:ISBN:0-395-36341-1</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>For the ISBN namespace,
some additional equivalence rules
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>are appropriate.  Prior
to comparing two ISBN URNs for
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>equivalence, it is
appropriate to remove all hyphens, and to
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>convert any occurrences
of the letter X to upper
case.</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>3.3 Additional
considerations</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>The ISBN standard and
related community implementation
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>guidelines define when
different versions of a work should
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>be assigned the same or
differing ISBNs.  In actuality,
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>however, practice varies
somewhat depending on publisher as
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>to whether different
ISBNs are assigned for paperbound vs.
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>hardbound versions of
the same work, electronic vs. printed
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>versions of the same
work, or versions of the same work
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>published for example in
the US and in Europe.  The choice
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>of whether to assign a
new ISBN or to reuse an existing one
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>when publishing a
revised printing of an existing edition of
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>a work or even a revised
edition of a work is
somewhat</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>subjective.  Practice
varies from publisher to publisher
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>(indeed, the distinction
between a revised printing and a
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>new edition is itself
somewhat subjective).  The use of
</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>                        
                           [Page
5]</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>INTERNET
DRAFT:Bibliographic Identifiers as URNs    
3/1997</fontfamily><fontfamily><param>Times</param>



</fontfamily><fontfamily><param>Courier</param>ISBNs within the URN
framework simply reflects these
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>existing practices. 
Note that it is likely that an ISBN URN
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>will often resolve to
many instances of the work (many
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>URLs).</fontfamily><fontfamily><param>Times</param>



</fontfamily><fontfamily><param>Courier</param>4. International
Standard Serials Numbers</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>4.1
Overview</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>International Standard
Serials Numbers (ISSN) identify a
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>work that is being
published on a continued basis in issues;
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>they identify the entire
(often open-ended, in the case of
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>an actively published)
work.  ISSNs are defined by the
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>standards ISO 3297:1986
[ISO 2] and ISO/DIS 3297 [ISO 3] and
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>within the United States
by NISO Z39.9-1992 [NISO 1].  The
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>ISSN International
Centre is located in Paris and
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>coordinates a network of
regional centers.  The National
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>Serials Data Program
within the Library of Congress is the
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>US Center of this
network.</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>ISSNs have the form
NNNN-NNNN where N is a digit, the last
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>digit may be an upper
case X as the result of the check
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>character calculation. 
Unlike the ISBN the ISSN components
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>do not have much
structure; blocks of numbers are passed out
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>to the regional centers
and publishers.</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>4.2 Encoding
Considerations</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>Again, there is no
problem representing ISSNs in the
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>namespace-specific
string of URNs since all characters valid
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>in the ISSN are valid in
the namespace-specific URN string,
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>and %-encoding is never
required. </fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>Example:
URN:ISSN:1046-8188</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>Supplementary comparison
rules are also appropriate for the
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>ISSN namespace.  Just as
for ISBNs, hyphens should be
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>dropped prior to
comparison and occurrences of 'x'
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>normalized to
uppercase.</fontfamily><fontfamily><param>Times</param>



</fontfamily><fontfamily><param>Courier</param>                        
                           [Page
6]</fontfamily><fontfamily><param>Times</param>



</fontfamily><fontfamily><param>Courier</param>INTERNET
DRAFT:Bibliographic Identifiers as URNs    
3/1997</fontfamily><fontfamily><param>Times</param>



</fontfamily><fontfamily><param>Courier</param>4.3 Additional
Considerations</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>The ISSN standard and
related community implementation
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>guidelines specify when
new ISSNs should be assigned vs.
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>continuing to use an
existing one.  There are some
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>publications where
practice within the bibliographic
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>community varies from
site to site, such as annuals or
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>annual conference
proceedings.  In some cases these are
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>treated as serials and
ISSNs are used, and in some cases
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>they are treated as
monographs and ISBNs are used.  For
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>example SIGMOD Record
volume 24 number 2 June 1995 contains
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>the Proceedings of the
1995 ACM SIGMOD International
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>Conference on Management
of Data.  If you subscribe to the
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>journal (ISSN 0163-5808)
this is simply the June issue.  On
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>the other hand you may
have acquired this volume as the
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>conference proceedings
(a monograph) and as such would use
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>the ISBN 0-89791-731-6
to identify the work.  There are also
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>varying practices within
the publishing community as to when
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>new ISSNs are assigned
due to the change in the name of a
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>periodical (Atlantic
becomes Atlantic Monthly); or when a
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>periodical is published
both in printed and electronic
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>versions (The New York
Times).  The use of ISSNs as URNs
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>will reflect these
judgments and practices.</fontfamily><fontfamily><param>Times</param>



</fontfamily><fontfamily><param>Courier</param>5. Serial Item and
Contribution Identifiers</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>5.1
Overview</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>The standard for Serial
Item and Contribution Identifiers
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>(SICI) has recently been
extensively revised and is defined
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>by NISO/ANSI Z39.56-1997
[NISO 2].  The maintenance agency
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>for the SICI code is the
UnCover Corporation.</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>SICI codes can be used
to identify an issue of a serial, or
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>a specific contribution
(i.e., an article, or the table of
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>contents) within an
issue of a serial.  SICI codes are not
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>assigned, they are
constructed based on information about
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>the issue or issue
component in question.</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>The complete syntax for
the SICI code will not be discussed
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>here; see NISO/ANSI
Z39.56-1997 for details.  However an
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>example and brief review
of the major components is
needed</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>                        
                           [Page
7]</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>INTERNET
DRAFT:Bibliographic Identifiers as URNs    
3/1997</fontfamily><fontfamily><param>Times</param>



</fontfamily><fontfamily><param>Courier</param>to understand the
relationship with the ISSN and how this
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>identifier differs.  An
example of a SICI code
is:</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>0015-6914(19960101)157:1<<62:KTSW>2.0.TX;2-F</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>The first nine
characters are the ISSN identifying the
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>serial title.  The
second component, in parentheses, is the
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>chronology information
giving the date the particular serial
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>issue was published.  In
this example that date was January
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>1, 1996.  The third
component, 157:1, is enumeration
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>information (volume,
number) on the particular issue of the
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>serial.  These three
components comprise the "item segment"
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>of a SICI code.  By
augmenting the ISSN with the chronology
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>and/or enumeration
information, specific issues of the
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>serial can be
identified.  The next segment, <<62:KTSW>,
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>identifies a particular
contribution within the issue.  In
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>this example we provide
the starting page number and a title
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>code constructed from
the initial characters of the title.
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>Identifiers assigned to
a contribution can be used in the
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>contribution segment if
page numbers are inappropriate.  The
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>rest of the identifier
is the control segment, which
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>includes a check
character.  Interested readers are
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>encouraged to consult
the standard for an explanation of the
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>fields in that
segment.</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>5.2 Encoding
Considerations</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>The character set for
SICIs is intended to be
email-</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>transport-transparent,
so it does not present major
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>problems.  However, all
printable excluded and reserved
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>characters from the URN
syntax draft are valid in the SICI
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>character set and must
be %-encoded.</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>Example of a SICI for an
issue of a journal</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>    
URN:SICI:1046-8188(199501)13:1%3C%3E1.0.TX;2-F</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>For an article contained
within that issue</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>    
URN:SICI:1046-8188(199501)13:1%3C69:FTTHBI%3E2.0.TX;2-4</fontfamily><fontfamily><param>Times</param>



</fontfamily><fontfamily><param>Courier</param>                        
                           [Page
8]</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>INTERNET
DRAFT:Bibliographic Identifiers as URNs    
3/1997</fontfamily><fontfamily><param>Times</param>



</fontfamily><fontfamily><param>Courier</param>Special equivalence
rules for SICIs are not appropriate for
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>definition as part of
the namespace and incorporation in
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>areas such as cache
management algorithms.  These are best
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>left to resolver systems
which try to determine if two SICIs
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>refer to the same
content.  Consequently, we do not propose
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>any specific rules for
equivalence testing through lexical
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>manipulation.</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>5.3 Additional
Considerations</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>Since the serial is
identified by an ISSN, some of the
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>ambiguity currently
found in the assignment of ISSNs carries
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>over into SICI codes. 
In cases where an ISSN may refer to a
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>serial that exists in
multiple formats, the SICI contains a
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>qualifier that specifies
the format type (for example,
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>print, microform, or
electronic).  SICI codes may be
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>constructed from a
variety of sources (the actual issue of
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>the  serial, a citation
or a record from an abstracting
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>service) and, as such
are based on the principle of using
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>all available
information, so there may be multiple SICI
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>codes representing the
same article [NISO2, Appenidx D]. 
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>For example, one code
might be constructed with access to
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>both chronology and
enumeration (that is, date of issue and
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>volume, issue and page
number), another code might be
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>constructed based only
on enumeration information and
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>without benefit of
chronology.  Systems that use SICI codes
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>employ complex matching
algorithms to try to match SICI
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>codes constructed from
incomplete information to SICI codes
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>constructed with the
benefit of all relevant
information.</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>6. Security
Considerations</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>This document proposes
means of encoding several existing
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>bibliographic
identifiers within the URN framework.  It does
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>not discuss resolution;
thus questions of secure or
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>authenticated resolution
mechanisms are out of scope.  It
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>does not address means
of validating the integrity or
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>authenticating the
source or provenance of URNs that contain
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>bibliographic
identifiers.  Issues regarding intellectual
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>property rights
associated with objects identified by
the</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>various bibliographic
identifiers are also beyond the scope
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>of this document, as are
questions about rights to the
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>databases that might be
used to construct
resolvers.</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>                        
                           [Page
9]</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>INTERNET
DRAFT:Bibliographic Identifiers as URNs    
3/1997</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>7.
References</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>[ISO1] NISO/ANSI/ISO
2108:1992 Information and documentation
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>       -- International
standard book number
(ISBN)</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>[ISO2] ISO 3297:1986
Documentation -- International standard
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>       serial numbering
(ISSN)</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>[ISO3] ISO/DIS 3297
Information and documentation --
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>       International
standard serial numbering (ISSN)
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>       (Revision of ISO
3297:1986)</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>[Moats] R. Moats, "URN
Syntax"
draft-ietf-urn-syntax-</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>       04.text. March
1997</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>[NISO 1] NISO/ANSI
Z39.9-1992 International standard
serial</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>       numbering
(ISSN)</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>[NISO 2] NISO/ANSI
Z39.56-1997 Serial Item and
Contribution</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>      
Identifier</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>[Sollins & Masinter] K.
Sollins and L. Masinter,
"Functional</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>       Requirements for
Uniform Resource Names", RFC 1737
</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>       December
1994.</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>8. Author's
Addresses</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>Clifford
Lynch</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>University of California
Office of the President</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>300 Lakeside Drive, 8th
floor</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>Oakland CA
94612-3550</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>[e-mail]</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>Cecilia
Preston</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>Preston &
Lynch</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>PO Box
8310</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>Emeryville, CA
94662</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>[e-mail]</fontfamily><fontfamily><param>Times</param>


</fontfamily><fontfamily><param>Courier</param>Ron Daniel
Jr.</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>Advanced Computing Lab,
MS B287</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>Los Alamos National
Laboratory</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>Los Alamos, NM,
87545</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>voice: +1 505 665
0597</fontfamily><fontfamily><param>Times</param>

</fontfamily><fontfamily><param>Courier</param>fax: [phone]
4939</fontfamily><fontfamily><param>Times</param>

<bigger>http://www.acl.lanl.gov/~rdaniel</bigger>





</fontfamily><fontfamily><param>Courier</param>                        
                          [Page
10]</fontfamily><fontfamily><param>Times</param>

</fontfamily></bigger>