<?tei:SOF p2cobi.odd ?>
<!--* $Id: p2cobi.odd,v 1.13 1998/02/01 17:55:08 tei Exp $ *-->
<!--*
    *
    * $Log: p2cobi.odd,v $
    * Revision 1.13  1998/02/01 17:55:08  tei
    * fix log keyword (still need SGML normalization)
    *
    * Revision 1.12  98/01/28  11:44:14  cmsmcq
    * LB changes of Jan 1998 and RCS keywords added.
    * 
    * Revision 1.11  1994/03/27  21:45:15  msmcq
    * Correction of typos from DB, JL, HG, and WWP
    * 
    * Revision 1.10  1994/02/12  21:37:58  msmcq
    * strip ^Z
    * -->
<!-- ******************************************************** -->
<!-- P2 Cobi (old P2235)                                      -->
<!>
<!-- ******************************************************** -->
<!-- Revision History (add lines at top)                      -->
<!-- 10 jan 98 : LB : fix egs -->
<!-- 94-03-26 : MSM : corrections, changes from WWP team      -->
<!-- 94-03-26 : MSM : corrections from DB                     -->
<!-- 94-03-26 : MSM : typos from JL et al.                    -->
<!-- 9 jan: fixed spurious <items> element; change TeiH to teiH  -->
<!-- 29 dec 93 : fixed many erroneous  examples               -->
<!-- 27 dec 93: LB : removed individual, org etc -->
<!-- 25 dec 93: LB : resp/respstmt, city/pubPlace fixes       -->
<!--            added meeting, doubtfully                     -->
<!-- 92-12-09 : MSM : spelling corrections                    -->
<!-- 92-12-09 : MSM : date takes VALUE att, not STDVAL        -->
<!-- 92-12-07 : MSM : clean dtdFrag ids, contins              -->
<!-- 92-12-06 : MSM : clean up dtdfrag ids, refs              -->
<!-- 92-12-06 : MSM : correct minor syntax errors             -->
<!-- 92-12-06 : MSM : correct ref to fileDesc, TeiHeader      -->
<!-- 92-12-05 : MSM : finish (hard slog), add equiv list      -->
<!-- 92-12-03 : MSM : further changes, in part as per LB      -->
<!-- 92-12-02 : MSM : continued revisions                     -->
<!-- 92-12-01 : MSM : revise for release of CO                -->
<!-- 92-11-17 : MSM : change IDs to CObi*                     -->
<!-- 92-11-09 : MSM : suppress leading blanks in some elems   -->
<!-- 92-11-09 : MSM : rename BIBL from CITN                   -->
<!-- 26 May 92 MSM make comments all one line long for Script -->
<!--               modify dtdfrag ids                         -->
<!--  2 May 92 LB  added loadsa discussion; killed some tags; -->
<!--               added citn.full, address and its parts     -->
<!-- 26 Feb 92 LB     ODDified from TEI P1, sec.  6.6         -->
<!--       (last revision: 16 Oct 90 CMSMcQ  for Version 1.1) -->
 
<div2 id=COBI><head>Bibliographic Citations and References</head>
 
<p>Bibliographic references (that is, full descriptions of bibliographic
items such as books, articles, films, broadcasts, songs, etc.) or
pointers to them may appear at various places in a TEI text.  They are
required at several points within the TEI Header's source description,
as discussed in section <xref target=HD3>; they may also appear within
the body of a text, either singly, (for example within a footnote), or
collected together in a list as a distinct part of a text.
 
<p>In printed texts, the individual constituents of a bibliographic
reference are conventionally marked off from each other and from the
flow of text by such features as bracketing, italics, special
punctuation conventions, underlining, etc.  In electronic texts, such
distinctions are also important, whether in order to produce acceptably
formatted output or to facilitate intelligent retrieval processing,<note
place=foot>For example, to distinguish <cited>London</cited> as an
author's name from <cited>London</cited> as a place of publication or as
a component of a title.</note> quite apart from the need to distinguish
the reference itself as a textual object with particular linguistic
properties.
 
<p>It should be emphasized that for references as for other textual
features, the primary or sole consideration is not how the text should
be formatted when it is printed.  The distinctions permitted by the
scheme outlined here may not necessarily be all that particular
formatters or bibliographic styles require, although they should prove
adequate to the needs of many such commonly used software systems.<note
place=foot ed=MSM>Among the bibliographic software systems and
subsystems consulted in the design of the <gi>biblStruct</gi> structure
were BibTeX, Scribe, and ProCite.  The distinctions made by all three
may be preserved in <gi>biblStruct</gi> structures, though the nature of
their design prevents a simple one-to-one mapping from their data
elements to TEI elements.  For further information, see section <xref
target=COBIOT>.</note> The features distinguished and described below
(in section <xref target=COBICO>) constitute a set which has been useful
for a wide range of bibliographic purposes and in many applications, and
which moreover corresponds to a great extent with existing bibliographic
and library cataloguing practice.  For a fuller account of that practice
as applied to electronic texts see section <xref target=HD3>; for a
brief mention of related library standards see section <xref
target=HD8>.
 
<div3 id=COBITY><head>Elements of Bibliographic References</head>
 
<p>The following elements are used to mark individual bibliographic
references as wholes, or in groups:
 
<tagList>
<tagDesc tagDoc=BIBL>
<tagDesc tagDoc=BIBLSTRU>
<tagDesc tagDoc=BIBLFULL>
<tagDesc tagDoc=LISTBIBL>
</tagList>
 
These elements all share a number of possible component sub-elements.
For the <gi>bibl</gi> and <gi>biblStruct</gi> elements, exactly the
same sub-elements are concerned, and they are described together in
section <xref target=COBICO>; for the <gi>biblFull</gi> element, the
sub-elements concerned are fully described in section <xref target=HD2>.
 
<p>Different levels of specific tagging may be appropriate in different
situations.  In some cases, it may be felt necessary to mark just the
extent of the reference itself, with perhaps a few distinctions being
made within it (for example, between the part of the reference which
identifies a title or author and the rest).  Such references, containing
a mixture of text with specialized bibliographic elements, are regarded
as <gi>bibl</gi> elements, and tagged accordingly.  For example:
 
<eg><![ CDATA[
<p>A book which had a great influence on him
was <bibl>Tufte's <title>Envisioning
Information</title></bibl>, although he may
never have actually read it.
]]>
</eg>
 
Indeed, some encoders may find it unnecessary to mark the bibliographic
reference at all:
 
<eg><![ CDATA[
<p>A book which had a great influence on him
was Tufte's <title>Envisioning Information</title>,
although he may never have actually read it.
]]>
</eg>
 
<p>Some bibliographic references are extremely elliptical, often only a
string of the form <cited>Baxter, 1983</cited>.  If no further details of
Baxter's book are given in the source text and none are supplied by the
encoder, then the reference thus given should be tagged as a
<gi>bibl</gi>:
 
<eg>
<![ CDATA [
All of this is of course much more fully treated
in <bibl>Baxter, 1983</bibl>.
]]>
</eg>
 
In general, however, normal modern bibliographic practice, and these
Guidelines, distinguish between a bibliographic
<term rend='noindex'>reference</term>,
<indexed level1='references' level2='bibliographic'>
<indexed level1='bibliographic references'>
 
which is a self-sufficient description of a bibliographic item, and a
bibliographic <term rend='noindex'>pointer</term>,
<indexed level1='bibliographic pointers'>
<indexed level1='pointers' level2='bibliographic'>
 
which is a short-form citation (such as <cited>Baxter, 1983</cited>)
which serves usually as a place-holder or pointer to a full long-form
reference found elsewhere in the text.  The usual encoding of short-form
references such as <cited>Baxter, 1983</cited> is not as <gi>bibl</gi>
elements but as cross-references to such elements; see section <xref
target=COBIXR> below.
 
<p>In cases where the encoder wishes to impose more structure on the
bibliographic information, for example to make sure it conforms to a
particular style-sheet or retrieval processor, the <gi>biblStruct</gi>
element should be used.  Note that several of the features in this and
later examples are explained later in the current section.
 
<eg><![ CDATA[
<biblStruct>
    <monogr>
    <author>Edward R. Tufte</>
    <title>Envisioning Information</>
    <imprint>
         <pubPlace>Cheshire, Conn.</>
         <publisher>Graphics Press</>
         <date>1990</>
    </imprint></monogr>
</biblStruct>
]]>
</eg>
 
<p>The highest level of detail and the most complex structure supported
by the current proposals is provided by the <gi>biblFull</gi> element,
which closely resembles the <gi>fileDesc</gi> element of the TEI Header
(section <xref target=HD2>).
 
<!-- biblFull needs an analytic level. -MSM -->
 <!-- titstmt requires title first -->
<eg><![ CDATA[
<biblFull>
    <titleStmt>
         <title>Envisioning Information</title>
         <author>Tufte, Edward R[olf]</author>
      </titleStmt>
    <extent>126 pp.</extent>
    <publicationStmt>
         <publisher>Graphics Press</publisher>
         <pubPlace>Cheshire, Conn. USA</pubPlace>
         <date>1990</date>
    </publicationStmt>
</biblFull>
]]>
</eg>
<!-- MSM! please check/expand on these details: you have the book!  -->
<!-- Done.  Robinson corrected to Rolf, bracketed (titlep has R.)   -->
 
<p>A list of bibliographic items, of whatever kind, may be treated in
the same way as any other list (see section <xref target=COLI>).
Alternatively, the specialized <gi>listBibl</gi> element may be used.
The difference between the two is that a <gi>list</gi> contains
<gi>item</gi> elements, within which bibliographic elements (<gi>bibl</gi>,
<gi>biblStruct</gi> or <gi>biblFull</gi>) may appear, as well as other
phrase- and paragraph-level elements, whereas the <gi>listBibl</gi> may
contain only bibliographic elements, optionally preceded by a heading and a
series of introductory paragraphs.  The former would be appropriate
for a list of bibliographic elements in which descriptive prose
predominated, and the latter for a more formal bibliography.  The
following are thus both legal encodings of a list of bibliographic
entries:  a <gi>listBibl</gi>:
 
<!-- <note place=foot>In these examples, white space has      -->
<!-- been liberally used to help indicate the structure of    -->
<!-- the entries; it is not required and is not necessarily   -->
<!-- used in practice.  </note>                               -->
 
<eg><![ CDATA[
<listBibl>
<head>Bibliography</head>
<biblStruct id=NEL80>
    <analytic>
         <author>Nelson, T. H.</>
         <title>Replacing the printed word:
                a complete literary system.</>
    </analytic>
    <monogr>
         <title>Information Processing '80:  Proceedings of the IFIPS
                Congress, October 1980</>
         <editor>Simon H. Lavington</>
         <imprint>
              <publisher>North-Holland</>
              <pubPlace>Amsterdam</>
              <date>1980</>
         </imprint>
         <biblScope>pp 1013-23
    </monogr>
    <note>Apparently a draft of section 4 of <title>Literary
          Machines</title>.</note>
</biblStruct>
<bibl id=NEL88>Ted Nelson:  <title>Literary Machines</title>
    (privately published, 1987)</bibl>
<bibl id=BAX88>
    <author>Baxter, Glen</author>
    <title>Glen Baxter His Life: the years of struggle</title>
    London: Thames and Hudson, 1988.
    </bibl>
</listBibl>
]]>
</eg>
or a simple <gi>list</gi>:
<eg><![ CDATA[
<list><head>Bibliography</>
<item><bibl id=NEL80>
        <author>Nelson, T. H.</>
        <title level=a>Replacing the printed word:
             a complete literary system.</>
        <title level=m>Information Processing '80:
             Proceedings of the IFIPS Congress, October 1980</>
        <editor>Simon H. Lavington</>
        <publisher>North-Holland</>
        <pubPlace>Amsterdam</>
        <date>1980</>
        <biblScope>pp 1013-23
        <note>Apparently a draft of section 4 of <title>Literary
         Machines</title>.</note>
    </bibl></item>
<item><bibl id=NEL88>Ted Nelson:  <title>Literary Machines</title>
    (privately published, 1987)</bibl></item>
<item><bibl id=BAX88>
    <author>Baxter, Glen</author>
    <title>Glen Baxter His Life: the years of struggle</title>
    London: Thames and Hudson, 1988.
    </bibl></item>
</list>
]]>
</eg>
 
<p>The formal declarations for these elements are as follows:
 
<dtdFrag id=DCOBI n="Tags for Bibliographic References">
<tagDecl tagDoc=BIBL>
<tagDecl tagDoc=BIBLSTRU>
<tagDecl tagDoc=BIBLFULL>
<tagDecl tagDoc=LISTBIBL>
</dtdFrag>
<!>
 
<div3 id=COBICO><head>Components of Bibliographic References</head>
 
<p>This section discusses a number of very commonly occurring component
elements of bibliographic references.  They fall into four groups:
<list type=bullets>
<item>elements for grouping components of the
 
<term rend='noindex'>analytic</term>,
<term rend='noindex'>monographic</term>,
and <term rend='noindex'>series</term>
<indexed level1='analytic level' level2='bibliographic'>
<indexed level1='monographic level' level2='bibliographic'>
<indexed level1='series level' level2='bibliographic'>
<indexed level1='bibliographic references' level2='analytic level'>
<indexed level1='bibliographic references' level2='monographic level'>
<indexed level1='bibliographic references' level2='series level'>
levels in a structured bibliographic reference
<item>titles of various kinds, and statements of intellectual
responsibility (authorship, etc.)
<item>information relating to the publication, pagination, etc. of an
item
<item>annotation, commentary and further detail
</list>
 
The following sections describe the elements which may be used to
represent such information within a <gi>bibl</gi> or
<gi>biblStruct</gi> element.  Within the former, any or all of these
may be used and in any order.  Within the latter, such of these elements
as exist for a given reference must be distinguished, and must also be
presented in a specific order, discussed further below (section <xref
target=COBICOO>).
 
<div4 id=COBICOL><head>Analytic, Monographic, and Series Levels</head>
 
<p>In common library practice a clear distinction is made between an
individual item within a larger collection and a free-standing book,
journal, or collection.  Similarly a book in a series is distinguished
sharply from the series within which it appears.  An article forming
part of a collection which itself appears in a series thus has a
bibliographic description with three quite distinct levels of
information:
 
<list type=ordered>
 
<item>the <term rend='noindex'>analytic</term>
<indexed level1='analytic level' level2='bibliographic'>
level, giving the title, author, etc., of the article;
 
<item>the <term rend='noindex'>monographic</term>
<indexed level1='monographic level' level2='bibliographic'>
level, giving the title, editor, etc., of the collection;
 
<item>the <term rend='noindex'>series</term>
<indexed level1='series level' level2='bibliographic'>
level, giving the title of the series, possibly the names of its
editors, etc., and the number of the volume within that series.
 
</list>
 
In the same way, an article in a journal requires at least two levels of
information:  the analytic level describing the article itself, and the
monographic level describing the journal.
 
<p>These three levels may be distinguished within a <gi>bibl</gi>
element, and must be distinguished within a <gi>biblStruct</gi> element
if present, by means of the following tags:
 
<tagList>
<tagDesc tagDoc='ANALYTIC'>
<tagDesc tagDoc='MONOGR'>
<tagDesc tagDoc='SERIES'>
</tagList>
 
<p>For purposes of TEI encoding, journals and anthologies are both
treated as monographs; a journal title will thus be tagged <tag>title
level=j</tag> or <tag>monogr</tag><tag>title</tag> ...
<tag>/title</tag> ...  <tag>/monogr</tag>.  Individual articles in the
journal or collected texts should be treated at the
<soCalled>analytic</soCalled> level.  When an article has been printed
in more than one journal or collection, the bibliographic reference may
have more than one <gi>monogr</gi> element, each possibly followed by
one or more <gi>series</gi> elements.  A <gi>series</gi> element always
relates to the most recently preceding <gi>monogr</gi> element.
(Whether reprints of an article are treated in the same bibliographic
reference or a separate one varies among different styles.  Library
lists typically use a different entry for each publication, while
academic footnoting practice typically treats all publications of the
same article in a single entry.)
 
<p>For example, the article cited in this example has been published
twice, once in a journal and once in a collection which appeared in a
series:
 
<eg>
<![ CDATA [
    <biblStruct>
         <analytic>
              <author>Thaller, Manfred</author>
              <title level=a>A Draft Proposal for a Standard for the
                     Coding of Machine Readable Sources</>
         </analytic>
         <monogr>
              <!-- In -->
              <title level=j>Historical Social Research</title>
              <imprint>
                    <biblScope type=vol>40</>
                    <date>October 1986</>
                    <biblScope type=pages>3-46</>
              </imprint>
         </monogr>
         <monogr>
              <!-- Rpt. in -->
              <title level=m>Modelling Historical Data:
                     Towards a Standard for Encoding and Exchanging
                     Machine-Readable Texts</title>
              <editor>Daniel I. Greenstein</editor>
              <imprint>
                   <pubPlace>St. Katharinen</pubPlace>
                   <publisher>Max-Planck-Institut f&uuml;r Geschichte
                         In Kommission bei
                         Scripta Mercaturae Verlag</publisher>
                   <date>1991</date>
              </imprint>
         </monogr>
         <series>
              <title level=s>Halbgraue Reihe
                   zur Historischen Fachinformatik</title>
              <respStmt><resp>Herausgegeben von</resp>
                    <name type=person>Manfred Thaller</>
                    <name type=org>Max-Planck-Institut f&uuml;r
                        Geschichte</>
              </respStmt>
              <title level=s>Serie A:  Historische Quellenkunden</>
              <biblScope>Band 11</biblScope>
         </series>
    </biblStruct>
]]>
</eg>
 
<p>Punctuation may not appear between the elements within a structured
bibliographic entry; if punctuation is to be given explicitly in the
encoding, it must be contained within the elements it delimits.  As the
example shows, it is possible to encode the entry without any
inter-element punctuation:  this facilitates use of the
<gi>biblStruct</gi> element in systems which can render bibliographic
references in any of several styles.
 
<p>The formal declarations for the elements defined in this section are
as follows:
 
<dtdFrag id=DCOBILV n='Levels of bibliographic information'
         contin=DCOBI>
<tagDecl tagDoc='ANALYTIC'>
<tagDecl tagDoc='MONOGR'>
<tagDecl tagDoc='SERIES'>
</dtdFrag>
 
<div4 id=COBICOR><head>Authors, Titles, and Editors</head>
 
<p>Bibliographic references typically begin with a statement of the
title being cited and the names of those intellectually responsible for
it.  For articles in journals or collections, such statements should
appear both for the analytic and for the monographic level.  The
following elements are provided for tagging such elements:
 
<tagList>
<tagDesc tagDoc=TITLE atts='level type'>
<tagDesc tagDoc=AUTHOR>
<tagDesc tagDoc=EDITOR>
<tagDesc tagDoc=RESP>
<tagDesc tagDoc=ROLE>
<tagDesc tagDoc=NAME>
<tagDesc tagDoc=MEETING>
</tagList>
 
<!-- some discussion of meeting shd be added but not sure where -->
 
<p>In bibliographic references, all titles should be tagged as such,
whether analytic, monographic, or series titles.  The single element
<gi>title</gi> is used for all these cases.  When it appears directly
within an <gi>analytic</gi>, <gi>monogr</gi>, or <gi>series</gi>
element, <gi>title</gi> is interpreted as belonging to the appropriate
level.  When it appears elsewhere, its <att>level</att> attribute should
be used to signal its bibliographic level.  It is a semantic error to
give a value for the <att>level</att> attribute which is inconsistent
with the context; such values may be ignored.  The <att>level</att>
value <code type=val>a</code> implies the analytic level; the values
<code type=val>m</code>, <code type=val>j</code>, and <code
type=val>u</code> imply the monographic level; the value <code
type=val>s</code> implies the series level.  Note, however, that the
semantic error occurs only if the nested title is directly enclosed by
the <gi>analytic</gi>, <gi>monogr</gi>, or <gi>series</gi> element; if
it is enclosed only indirectly, no semantic error need be present.  For
example, the analytic title may contain a monographic title:
 
<eg><![ CDATA [
<biblStruct>
    <analytic><author>Lucy Allen Paton</>
              <title>Notes on Manuscripts
                   of the <title level=m>Proph&eacute;cies
                   de Merlin</title></title>
    </analytic>
    <monogr><title level=j>PMLA</>
          <imprint><biblScope type=vol>8</>
            <date>1913</date>
            <biblScope type=pages>122</>
      </imprint>
    </monogr>
</biblStruct>
]]>
</eg>
 
In this case, the analytic title <q>Notes on Manuscripts of the
<title>Proph&eacute;cies de Merlin</title></q> needs no <att>level</att>
attribute because it is directly contained by the <gi>analytic</gi>
level; the monographic title contained within it, <q>Proph&eacute;cies
de Merlin,</q> does not create a semantic error because it is not
directly contained by the <gi>analytic</gi> element.
 
<p>In some bibliographic applications, it may prove useful to
distinguish main titles from subordinate titles, parallel titles, etc.
The <att>type</att> attribute is provided to allow this distinction to
be recorded.
 
<p>The following reference, from a national standard for bibliographic
references,<note place=foot><citation>American National Standard for
Bibliographic References, ANSI Z39.29-1977 (New York:  American
National Standards Institute, 1977), p. 34 (sec.
A.2.2.1).</citation></note>
illustrates this type of analysis with its distinction between main
and subordinate titles.
 
<eg><![ CDATA [
<bibl>Saarikoski, Pirkko-Liisa, and Paavo Suomalainen,
<title level=a type=main>Studies on the physiology of
the hibernating hedgehog, 15</title>
<title level=a type=subordinate>Effects of seasonal
and temperature changes on the in vitro
glycerol release from brown adipose tissue</>
<title level=j>Ann. Acad. Sci. Fenn., Ser. A4</>
<date>1972</> <biblScope type='vol: pp'>187: 1-4</>
</bibl>
]]>
</eg>
<!-- example from ANSI Z39.29, sec. A.2.2.1, p.34 -->
 
<p>Slightly more complex is the distinction made below among main,
subordinate, and parallel titles, in an example from the same source (p.
63).  The punctuation and the bibliographic analysis are those given in
ANSI Z39.29-1977; the punctuation is in the style prescribed by the
International Standard Bibliographic Description (ISBD).<note
place=foot>The analysis is not wholly unproblematic:  as the text of the
standard points out, the first subordinate title is subordinate only to
the parallel title in French, while the second is subordinate to both
the English main title and the French parallel title, without this
relationship being made clear, either in the markup given in the example
or in the reference structure offered by the standard.</note>
 
<eg><![ CDATA [
<bibl>Tchaikovsky, Peter Ilich.
<title level=m type=main>The swan lake ballet</>
= <title level=m type=parallel>Le lac des cygnes</>
: <title level=m type=subordinate>grand ballet en 4 actes</>
: <title level=m type=subordinate>op. 20</>
[Score].
New York:  Broude Brothers; [1951] (B.B. 59). vi, 685 p.
</bibl>
]]>
</eg>
<!-- example from ANSI Z39.29, sec. A.12.2, p.63 -->
 
<p>The elements <gi>author</gi> and <gi>editor</gi> have, for printed
books and articles, a fairly obvious significance; for other kinds of
bibliographic items their proper usage may be less obvious.  The
<gi>author</gi> element should be used for the person or agency with
primary responsibility for a work's intellectual content, and the
element <gi>editor</gi> for an editor of the work.  Thus an organization
such as a radio or television station is usually accounted
<soCalled>author</soCalled> of a broadcast, for example, while the
author of a Government report will usually be the agency which produced
it.
 
<p>For anyone else with responsibility for the work, the
<gi>respStmt</gi> element should be used.  The nature of the
responsibility is indicated by means of a <gi>resp</gi> element, and the
person, organization etc. responsible by a <gi>name</gi> element.  At
least one of each of these must be given within the <gi>respStmt</gi>
element, followed optionally by any number of either.  Examples of
secondary responsibility of this kind include the roles of illustrator,
translator, editor, annotator.  The <gi>respStmt</gi> element may also
be used for editors, if it is desired to record the specific terms in
which their role is described.
 
<p>Examples of <gi>author</gi> and <gi>editor</gi> may be found in
sections <xref target=COBITY>, and <xref target=COBICOL>; wherever
<gi>author</gi> and <gi>editor</gi> may occur, the <gi>respStmt</gi>
element may also occur.  When one of these elements precedes or
immediately follows a title, it applies to that title; when it follows
an <gi>edition</gi> element or occurs within an edition statement, it
applies to the edition in question.
 
<p>In this example, the <gi>respStmt</gi> elements apply to the work as
a whole, not merely to the first edition:
 
<eg><![ CDATA [ <bibl>
    <author>Lominadze, D. G.</>
    <title level=m>Cyclotron waves in plasma.</title>
    <respStmt><resp>translated by</> <name>A. N. Dellis;</name>
              <resp>edited by</> <name>S. M. Hamberger.</name>
    </respStmt>
    <edition>1st ed.</>
    <imprint><pubPlace>Oxford:</> <publisher>Pergamon Press,</>
       <date>1981.</></imprint>
    <extent>206 p.</>
    <title level=s>International series in natural philosophy.</>
    <note place=inline>Translation of:
      <title level=m lang=RU>Ciklotronnye volny v plazme.</></>
</bibl>
]]>
</eg>
<!-- from ISO 690: 1987, clause 4.1, p. 2. -->
 
<p>In this example, by contrast, the <gi>respStmt</gi> element applies
to the edition, and not to the collection per se (Moser and Tervooren
were not responsible for the first thirty-five printings); the elements
of the reference have been reordered from their appearance on the title
page of the volume in order to ensure the correct relationship of the
collection title, the edition statement, and the statement of
responsibility.
 
<eg><![ CDATA [
<biblStruct>
<monogr>
    <title>Des Minnesangs Fr&uuml;hling</title>
    <note place=inline>Mit 1 Faksimile</note>
    <edition>36., neugestaltete und erweiterte Auflage</edition>
    <respStmt>
         <resp>Unter Benutzung der Ausgaben
         von <name>Karl Lachmann</> und <name>Moriz Haupt</>,
         <name>Friedrich Vogt</> und <name>Carl von Kraus</>
         bearbeitet von
         </resp>
         <name>Hugo Moser</>
         <!-- und -->
         <name>Helmut Tervooren</>
    </respStmt>
    <imprint>
         <biblScope type=volume>I</>
         <biblScope type='volume title'>Texte</>
         <pubPlace>Stuttgart</>
         <publisher>S. Hirzel Verlag</>
         <date>1977</>
    </imprint>
</monogr>
</biblStruct>
]]>
</eg>
 
<!-- reference taken from book in hand by MSM. -->
<!-- note that from the book it is impossible to -->
<!-- tell whether this is the 36th edition of -->
<!-- MF or of Moser/Tervooren's edition.  -->
 
<!-- <p>The formal definition of the <gi>name</gi>,           -->
<!-- <gi>person</gi>, <gi>individual</gi>, <gi>org</gi>, and  -->
<!-- <gi>organization</gi> elements may be found in section   -->
<!-- <xref target=CONA>.  Definitions for the                 -->
<!-- <gi>respStmt</gi> and <gi>role</gi> elements are         -->
<!-- provided in section <xref target=HD6>.                   -->
<!-- This is a fat lie! (LB)                                  -->
 
With the exception of the <gi>name</gi> element (for which see section
<xref target=CONA>), the elements described in this section are defined
as follows:
 
<dtdFrag id=DCOBICOR n='Author, title, etc.' contin=DCOBI>
<tagDecl tagDoc=AUTHOR>
<tagDecl tagDoc=EDITOR>
<tagDecl tagDoc=RESP>
<tagDecl tagDoc=ROLE>
<tagDecl tagDoc=TITLE>
<tagDecl tagDoc=MEETING>
</dtdFrag>
 
<div4 id=COBICOI><head>Imprint, Pagination, and Other Details</head>
 
<p>By <cited>imprint</cited> is meant all the information relating to the
publication of a work:  the person or organization by whose authority
and in whose name a bibliographic entity such as a book is made public
or distributed (whether a commercial publisher or some other
organization), the place of publication, and a date.  It may also
include a full address for the publisher or organization.
Full bibliographic references usually specify either the number of pages
in a print publication (or equivalent information for non-print
materials), or the specific location of the material being cited within
its containing publication.  The following elements are provided to hold
this information:
 
<tagList>
<tagDesc tagDoc=IMPRINT>
<tagDesc tagDoc=ADDRESS>
<tagDesc tagDoc=PUBPLACE>
<tagDesc tagDoc=PUBLISHR>
<tagDesc tagDoc=DATE>
<tagDesc tagDoc=IDNO atts='type'>
<tagDesc tagDoc=EXTENT>
<tagDesc tagDoc=BIBLSCOP atts='type'>
</tagList>
 
<p>For bibliographic purposes, usually only the place (or places) of
publication are required, possibly including the name of the country,
rather than a full address; the element <gi>pubPlace</gi> is provided
for this purpose.
<!-- for this reason, the element <gi>city</gi> may be supplied on -->
<!-- its own (outside of an <gi>address</gi> element) in this context.  -->
Where however the full postal address is likely to be of importance in
identifying or locating the bibliographic item concerned, it may be
supplied and tagged using the <gi>address</gi> element described in
section <xref target=CONAAD>.  Alternatively, if desired, the
<!-- <gi>place</gi> element described in section <xref target=CONANA> may be -->
<gi>rs</gi> or <gi>name</gi> elements described in section <xref
target=CONARS> may be used; this involves no claim that the information
given is either a full address or the name of a city.
 
<!-- <p>The name of the publisher of an item may be marked    -->
<!-- using the <gi>publisher</gi> tag; if the item is made    -->
<!-- public (<soCalled>published</soCalled>) by an            -->
<!-- organization other than a conventional publisher, it     -->
<!-- may be preferable to identify that organization using    -->
<!-- the <gi>org</gi> or <gi>organization</gi> element.       -->
<!-- This is frequently the case with technical reports:      -->
 
<p>The name of the publisher of an item should be marked using the
<gi>publisher</gi> tag even if the item is made public
(<soCalled>published</soCalled>) by an organization other than a
conventional publisher, as is frequently the case with technical
reports:
 
<eg><![ CDATA [
<biblStruct>
<monogr>
    <author>Nicholas, Charles K.</author>
    <author>Welsch, Lawrence A.</author>
    <title>On the interchangeability of SGML and ODA</title>
    <imprint>
         <pubPlace>Gaithersburg, MD</pubPlace>
         <publisher>National Institute of Standards and Technology
         </publisher>
         <date value='1992-01'>January 1992</date>
    </imprint>
    <extent>19 pp.</extent>
</monogr>
<idno type='NIST'>NISTIR 4681</idno>
</biblStruct>
]]>
</eg>
 
and with dissertations:
 
<eg><![ CDATA [
<biblStruct>
<monogr>
    <author>Hansen, W.</>
    <title level=u>Creation of hierarchic text
         with a computer display</>
    <note place=inline>Ph.D. dissertation</>
    <imprint>
         <publisher>Dept. of Computer Science, Stanford Univ.</>
         <pubPlace>Stanford, CA</>
         <date value='1971-06'>June 1971</>
    </imprint>
</monogr>
</biblStruct>
]]>
</eg>
 
<!-- reference is from p. 304, bibliography, of Reps and       -->
<!-- Teitelbaum, The Synthesizer Generator:  A system for     -->
<!-- constructing language-based editors.                     -->
<!-- or could maybe use a respStmt - if this were allowed in imprint -->
 
<p>When an item has been reprinted, especially reprinted without change
from a specific earlier edition, the reprint may appear in a
<gi>monogr</gi> element with only the <gi>imprint</gi> and other details
of the reprint.  In the following example, a microform reprint has been
issued without any change in the title or authorship.  The series
statement here applies only to the second <gi>monogr</gi> element.
 
<eg><![ CDATA [
<biblStruct>
<monogr>
    <author>Shirley, James</>
    <title type=main>The gentlemen of Venice</>
    <title type=subordinate>a tragi-comedie presented at
         the private house in Salisbury Court by
         Her Majesties servants</>
    <note place=inline>[Microform]</>
    <imprint>
         <pubPlace>London</>
         <publisher>H. Moseley</>
         <date>1655</>
    </imprint>
    <extent>78 p.</>
</monogr>
<monogr>
    <imprint>
         <pubPlace>New York</>
         <publisher>Readex Microprint</>
         <date>1953</>
    </imprint>
   <extent>1 microprint card, 23 x 15 cm.</>
</monogr>
<series>
    <title>Three centuries of drama:  English, 1642-1700</>
</series>
 </biblStruct>
]]>
</eg>
<!-- example from ANSI Z39.29, sec. A.3.12.1, p.41 -->
 
<p>A bibliographic description, particularly for an analytic title, will
often include some additional information specifying its location, for
example as a volume number, page number, range of page numbers, or name
or number of a subdivision of the host work.  The element
<gi>biblScope</gi> may be used to identify such information if it is
present.  Where it is desired to distinguish different classes of such
information (volume number, page number, chapter number, etc.), the
<att>type</att> attribute may be used with any convenient typology.
 
<p>When the item being cited is a journal article, the <gi>imprint</gi>
element describing the issue in which it appeared will typically contain
<gi>biblScope</gi> elements for volume and page numbers, together with a
<gi>date</gi> element.
 
<p>For example:
 
<eg><![ CDATA [
<biblStruct>
<analytic>
    <author>Wrigley, E. A.</>
    <title>Parish registers and the historian</>
</analytic>
<!-- in -->
<monogr>
    <editor>Steel, D. J.</>
    <title>National index of parish registers</>
    <imprint>
         <pubPlace>London</pubPlace>
         <publisher>Society of Genealogists</>
         <date value='1968'>1968</>
    </imprint>
    <biblScope type=volume>vol. 1</>
    <biblScope type=pages>pp. 155-167.</>
</monogr>
</biblStruct>
]]>
</eg>
 
<p>The <att>type</att> attribute on <gi>biblScope</gi> is optional:
both the following are legal examples:
 
<eg><![ CDATA [
<biblStruct>
<analytic>
    <author>Boguraev, Branimir</>
    <author>Neff, Mary</>
    <title>Text Representation, Dictionary Structure,
         and Lexical Knowledge</>
</analytic>
<!-- in -->
<monogr>
    <title level=j>Literary & Linguistic Computing</>
    <imprint>
         <biblScope type=volume>7</>
         <biblScope type=issue>2</>
         <date>1992</>
         <biblScope type=pages>110-112</>
    </imprint>
</monogr>
</biblStruct>
]]>
</eg>
 
<eg><![ CDATA [
<biblStruct>
<analytic>
    <author>Chesnutt, David</>
    <title>Historical Editions in the States</>
</analytic>
<!-- in -->
<monogr>
    <title level=j>Computers and the Humanities</>
    <imprint>
         <biblScope>25.6</>
         <date value='1991-12'>(December, 1991):</>
         <biblScope>377-380</>
    </imprint>
</monogr>
</biblStruct>
]]>
</eg>
 
<!-- TYPE attribute dropped from biblScope in Chesnutt        -->
<!-- example, as per WWP suggestion (otherwise lead-in makes  -->
<!-- no sense) (msm)                                          -->
 
<p>Formal definitions for the elements described in this section are as
follows:
 
<dtdFrag id=DCOPUB n='Bibliographic subelements' contin=DCOBI>
<tagDecl tagDoc=IMPRINT>
<tagDecl tagDoc=PUBLISHR>
<tagDecl tagDoc=BIBLSCOP>
<tagDecl tagDoc=PUBPLACE>
 
<commDecl>Note and date are defined elsewhere, as are extent, address,
and idno.</commDecl>
</dtdFrag>
 
<div4 id=COBICOS><head>Series Information</head>
 
<p>Series information may (in <gi>bibl</gi> elements) or must (in
<gi>biblStruct</gi> elements) be enclosed in a <gi>series</gi> element
or (in a <gi>biblFull</gi> element) a <gi>seriesStmt</gi> element.  The
title of the series may be tagged <tag>title level=s</tag>, the
volume number <tag>biblScope type=volume</tag>, and responsibility
statements for the series (e.g. the name and affiliation of the editor,
as in the example in section <xref target=COBICOL>) may be tagged
<tag>editor</tag> or <tag>respStmt</tag>.
 
<div4 id=COBICON><head>Notes and Other Additional Information</head>
 
<p>Explanatory notes about the publication of unusual items, the form of
an item (e.g.  <cited>[Score]</cited> or <cited>[Microform]</cited>), or
its provenance (e.g.  <cited>translation of ...</cited>) may be tagged
using the <gi>note</gi> element.  The same element may be used for any
descriptive annotation of a bibliographic entry in a database.
 
<tagList>
<tagDesc tagDoc=NOTE atts='type place'>
</tagList>
 
<p>For example:
 
<eg><![ CDATA[
<bibl><author>Coombs, James H., Allen H. Renear,
       and Steven J. DeRose.</author>
       <title level=a>Markup Systems and the Future of Scholarly
       Text Processing.</title>
       <title level=j>Communications of the ACM</title>
       <biblScope>30.11 (November 1987):  933-947.</biblScope>
       <note>Classic polemic supporting descriptive over procedural
            markup in scholarly work.</note>
]]>
</eg>
 
<div4 id=COBICOO><head>Order of Components within References</head>
 
<p>The order of elements in <gi>bibl</gi> elements is not constrained.
 
<p>In <gi>biblStruct</gi> elements, the <gi>analytic</gi> element, if
it occurs, must come first, followed by one or more <gi>monogr</gi> and
<gi>series</gi> elements, which may appear intermingled (as long as a
<gi>monogr</gi> element comes first).  Within <gi>analytic</gi>, the
title(s), author(s), editor(s), and other statements of responsibility
may appear in any order; it is recommended that all forms of the title
be given together.  Within <gi>monogr</gi>, the author, editor, and
statements of responsibility may either come first or else follow the
monographic title(s).  Following these, the elements must appear in the
following order:
 
<list>
<item><gi>note</gi>s on the publication (and <gi>meeting</gi> elements
describing the conference, in the case of a proceedings volume)
<item><gi>edition</gi> elements, each followed by any related
<gi>editor</gi> or <gi>respStmt</gi> elements
<item><gi>imprint</gi>
<item><gi>biblScope</gi>
</list>
Within <gi>imprint</gi>, the elements allowed may appear in any
order.
<p>Finally, within the <gi>series</gi> information in a
<gi>biblStruct</gi>, the sequence of elements is not constrained.
 
<p>If more detailed structuring of a bibliographic description is
required, the <gi>biblFull</gi> element should be used.  This is not
further described here, as its contents are essentially equivalent to
those of the <gi>fileDesc</gi> element in the <gi>teiHeader</gi>, which
is fully described in section <xref target=HD2>.
 
<div3 id=COBIXR><head>Bibliographic Pointers </head>
 
<p>References which are pointers to bibliographic items, of whatever
kind, should be treated in the same way as other cross-references (see
section <xref target='COXR'>).  As discussed in that section, cross
referencing within TEI texts is in general represented by means of
<gi>ptr</gi> or <gi>ref</gi> elements.  A <att>target</att> attribute on
these elements is used to supply an identifying value for the target of
the cross reference, which should be, in the case of bibliographic
elements, a bibliographic reference of some kind.  Where the form of the
reference itself is unimportant, or may be reconstructed mechanically,
or is not to be encoded, the <gi>ptr</gi> element is used, as in the
following example:
 
<eg><![ CDATA[
As shown above (<ptr target=NEL80>)...
]]>
</eg>
 
<p>Where the form of the reference is important, or contains additional
qualifying information which is to be kept but distinguished from the
surrounding text, the <gi>ref</gi> element should be used, as in the
following example:
 
<eg><![ CDATA[
Nelson claims <ref target=NEL80>(ibid, passim)</ref> ...
]]>
</eg>
 
<!--Following suggestion is only possible if <biblScope> becomes a phrase. -->
<!--Which it currently isnt.  -->
 
 
<!--<p>When it is desired to distinguish the short form of the reference -->
<!--itself from the additional qualifying information added to it, the -->
<!--additional information may be marked as a <gi>biblScope</gi> element: -->
<!--  -->
<!--<eg><![ CDATA[ -->
<!--Nelson claims (<ref target=NEL80>Nelson [1980], <biblScope>especially -->
<!--pages 13-37</ref>) ... -->
<!--]]> -->
<!--</eg> -->
<!--  -->
<!--(This distinction between the short form and the qualifying information -->
<!--may be useful in the context of document production or normalization of -->
<!--bibliographic references.) -->
 
It may be important to distinguish between the short form of a
bibliographic reference and some qualifying or additional information.
The latter should not appear within the scope of the <gi>ref</gi>
element when this is the case, as for example in an application
concerned to normalize bibliographic references:
 
<eg><![ CDATA[
Nelson claims (<ref target=NEL80>Nelson [1980]</ref>, pages 13-37) ...
]]>
</eg>
 
<div3 id=COBIOT><head>Relationship to Other Bibliographic Schemes</head>
 
<p>The bibliographic tagging defined here can capture the distinctions
required by most bibliographic encoding systems; for the benefit of
users of some commonly used systems, the following lists of equivalences
are offered, showing the relationship of the markup defined here to the
fields defined for bibliographic records in the Scribe, BibTeX, and
ProCite systems.
 
<p>The various bibliographic fields defined for use in the Scribe and
BibTeX systems of bibliographic databases have the following equivalents
in the scheme presented here:<note place=foot>The BibTeX scheme is
intentionally compatible with that of Scribe, although it omits some
fields used by Scribe.  Hence only one list of fields is given
here.</note>
<!-- need bibliographic references for Scribe and BibTeX. -msm -->
Elements and structures available in the tag set defined here which
have no analogues in Scribe and BibTeX are not noted.
 
<list type=gloss>
<label>address     <item>tag as <tag>city</tag>, <tag>place</tag>,
or <tag>address</tag>
<label>annote      <item>tag as <tag>note</tag>
<label>author      <item>tag as <tag>author</tag>
<label>booktitle   <item>tag as <tag>title level=m</tag>
or <tag>title</tag> within <tag>monogr</tag>
<label>chapter     <item>tag as <tag>biblScope type=chapter</tag>
<label>date        <item>used only to record date entry was made in the
bibliographic database; not supported
<label>edition     <item>tag as <tag>edition</tag>
<label>editor      <item>tag as <tag>editor</tag> or <tag>respStmt</tag>
<label>editors     <item>tag as multiple <tag>editor</tag>
or <tag>respStmt</tag> elements
<label>fullauthor  <item>use the <att>reg</att> attribute
on <tag>author</tag> or <tag>name</tag>
<label>fullorganization <item>use the <att>reg</att> attribute
on <tag>name type=org</tag>
<label>howpublished  <item>tag as <tag>note</tag>, possibly using
the form <tag>note place=inline</tag>
<label>institution <item>used only for issuer of technical reports;
tag as <tag>publisher</tag>
<!-- , <tag>org</tag>,  or <tag>organization</tag> -->
<label>journal     <item>tag as <tag>title level=j</tag>
or <tag>title</tag> within <tag>monogr</tag>
<label>key         <item>used to specify an alternate sort key for
the bibliographic item, for use instead of
author's or editor's name; not supported
<label>meeting     <item>tag as <tag>meeting</tag> or as <tag>note</tag>
<label>month       <item>use <tag>date</tag>; if the date is not in a
trivially parseable form, use the <att>value</att>
attribute to provide an ISO-format equivalent
<label>note        <item>tag as <tag>note</tag>
<label>number      <item>tag as <tag>biblScope type=issue</tag>
or <tag>biblScope type=number</tag>; for
technical report numbers, use <tag>idno
type=docno</tag>
<label>organization <item>used only for sponsor of conference;
use <tag>name type=org</tag>
within <tag>respStmt</tag>
within <tag>meeting</tag> element
<label>pages       <item>tag as <tag>biblScope type=pages</tag>
<label>publisher   <item>tag as <tag>publisher</tag>
<label>school      <item>used only for institutions at which
thesis work is done; tag as <tag>publisher</tag>
<!-- org</tag>  or <tag>organization</tag> -->
<label>series      <item>tag as <tag>title level=s</tag>
or <tag>title</tag> within <tag>series</tag>
<label>title       <item>tag as <tag>title</tag> in appropriate
context or with appropriate <att>level</att>
value
<label>volume      <item>tag as <tag>biblScope type=volume</tag>
<label>year        <item>tag as <tag>date</tag>; if the date is not in a
trivially parseable form, use the <att>value</att>
attribute to provide an ISO-format equivalent
</list>
<!-- need similar list for ProCite -->
<?tei:EOF p2cobi.odd ?>
