<?xml version="1.0" encoding="UTF-8"?><!-- Start license statement: do not remove 

EpiDoc: Guidelines for Structured Markup of Epigraphic Texts in TEI
Copyright (C) 2000-2006 by all contributors listed in <div type="gl-responsibility">, below.
Additional contributors' copyright may be designated in individual source files.

This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA.

Information about the EpiDoc community can be obtained via 
http://epidoc.sf.net.

End license statement: do not remove -->
<!-- Start CVS information: do not remove -->
<!-- $Header: /cvsroot/epidoc/guidelines/src/div-bibliography.xml,v 1.3 2006/04/18 21:12:51 paregorios Exp $ -->
<!-- End CVS information: do not remove -->

<!DOCTYPE div SYSTEM "../dtd/tei-epidoc.dtd">
<div xmlns="http://www.tei-c.org/ns/1.0" xmlns:tei="http://www.tei-c.org/ns/1.0" xmlns:xi="http://www.w3.org/2001/XInclude" id="div-bibliography" lang="en" org="uniform" part="N" sample="complete">
   <head>Bibliography</head><!--
Copyright TEI Consortium. 
Licensed under the GNU General Public License. 
See the file COPYING for details.
$Date: 2006/04/18 21:12:51 $
$Author: paregorios $:
-->
<!-- This is the bibliography section from P5, with Elli's modifications. 
    Since we don't support biblStruct in Epidoc, I have tried to eradicate
    references to is, as well as to biblFull. However, I didn't remove it 
    from all the examples yet, since this section isn't totally fixed in P5
    yet, and we will have to merge changes at some point.  Most of my changes
    consist of commenting sections out. Some prose has been added. 
    
 -->

   <div2 type="section" xml:id="COBI">
   <head>Bibliographic Citations and References</head><!-- 
       ************ Commented out of Epidoc version *******************
       <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 <ptr 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>  
            *******************************************************************
        -->

   <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" anchored="yes">For example, to distinguish 
      <mentioned>London</mentioned> as an author's name from 
      <mentioned>London</mentioned> 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><!--
            ************ Commented out of Epidoc version *******************
            
        <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">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
                    <ptr target="#COBIOT"/>.</note> The features distinguished
            and described below (in section <ptr 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 <ptr target="#HD3"/>; for a brief
            mention of related library standards see section <ptr target="#HD8"
            />. </p>
           *******************************************************************
       -->
<!-- Epidoc Intro, based on TEI intro -->

   <p>Bibliographical entries can be encoded in several ways in an Epidoc document or corpus, depending on the complexity of the bibliography and of the document as a whole. 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. In all cases, bibliographical information is enclosed in <tag>tei:div type="bibliography</tag>. If the encoded inscription is a single document, or a collection of just a few inscriptions, it is sufficient to encode full bibliographic entries inside <tag>div type="bibliography"</tag>. Larger corpora, or inscriptions that are part of a bigger project with shared bibliography are better off listing bibliography inside <tag>tei:div type="bibliography</tag> as a series of references pointing to bibliographic entries collected in a separate file. </p>
   <p>Bibliographical information may be associated with several different sections, such as commentary, history or apparatus criticus. These relationships are indicated by grouping bibliographic items in a <tag>listBibl</tag> for each section. Display of bibliographic information is controlled by the output software, and can occur either in the appropriate section or all together in a group. Bibliographic citations are also required in several places in the TEI header.</p>
   <p>Examples of different categories of bibliographical reference. 
      <list type="simple">
         <item>bibliography supporting editions</item>
         <item>bibliography supporting discussions of text</item>
         <item>bibliography supporting commentary</item>
      </list></p>
   <p>The rest of this section is based on the corresponding chapter of the TEI P5 Guidelines. Epidoc recommends using a subsection of the all possible bibliographic elements. Epidoc also recommends marking bibliography according to normal modern bibliographic practice, as well as using consistent short references to refer to bibliographic items.</p>
   <div3 type="subsection" xml:id="COBITY">
   <head>Elements of Bibliographic References</head>
   <p>The following elements are used to mark individual bibliographic references as wholes, or in groups:
      <specList>
      <specDesc key="bibl"/>
      <specDesc key="biblItem"/><!--     <specDesc key="biblStruct"/>
                    <specDesc key="biblFull"/>  -->

      <specDesc key="listBibl"/></specList> 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 <ptr
                    target="#COBICO"/>; for the <gi>biblFull</gi> element, the
                sub-elements concerned are fully described in section <ptr
                    target="#HD2"/>. -->
 For the 
      <gi>bibl</gi> element, they are described in section 
      <ptr target="#COBICO" evaluate="all" targOrder="Y"/>, for 
      <gi>biblItem</gi> they are described in section 
      <ptr target="xx" evaluate="all" targOrder="Y"/>. 
      <gi>listBibl</gi> is described in section 
      <ptr target="xx" evaluate="all" targOrder="Y"/></p><!--        <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:<egXML xmlns="http://www.tei-c.org/ns/Examples">
                    <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.</p>
                </egXML> Indeed, some encoders may find it unnecessary to mark
                the bibliographic reference at all:<egXML
                    xmlns="http://www.tei-c.org/ns/Examples">
                    <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.</p>
                </egXML>
            </p>
            <p>Some bibliographic references are extremely elliptical, often
                only a string of the form <mentioned>Baxter, 1983</mentioned>.
                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>:<egXML
                    xmlns="http://www.tei-c.org/ns/Examples">All of this is of
                    course much more fully treated in <bibl>Baxter,
                    1983</bibl><![CDATA[.]]></egXML> In general, however, normal
                modern bibliographic practice, and these Guidelines, distinguish
                between a bibliographic <term rend="noindex">reference</term>,<index>
                    <term>references</term>
                    <index>
                        <term>bibliographic</term>
                    </index>
                </index><index>
                    <term>bibliographic references</term>
                </index> which is a self-sufficient description of a
                bibliographic item, and a bibliographic <term rend="noindex"
                    >pointer</term>,<index>
                    <term>bibliographic pointers</term>
                </index><index>
                    <term>pointers</term>
                    <index>
                        <term>bibliographic</term>
                    </index>
                </index> which is a short-form citation (e.g. <mentioned>Baxter,
                    1983</mentioned>) 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
                    <mentioned>Baxter, 1983</mentioned> is not as <gi>bibl</gi>
                elements but as cross-references to such elements; see section
                    <ptr target="#COBIXR"/> below. </p>
            <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.<egXML
                    xmlns="http://www.tei-c.org/ns/Examples">
                    <biblStruct>
                        <monogr>
                            <author>Edward R. Tufte</author>
                            <title>Envisioning Information</title>
                            <imprint>
                                <pubPlace>Cheshire, Conn.</pubPlace>
                                <publisher>Graphics Press</publisher>
                                <date>1990</date>
                            </imprint>
                        </monogr>
                    </biblStruct>
                </egXML>
            </p>
            <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 <ptr
                    target="#HD2"/>).
                <egXML xmlns="http://www.tei-c.org/ns/Examples">
                    <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>
                </egXML>
            </p> -->

   <p>A list of bibliographic items <!-- , of whatever kind, may be treated
                in the same way as any other list (see section <ptr
                    target="#COLI"/>). Alternatively, the specialized -->
 is encoded using 
      <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> -->
 which may contain only bibliographic elements, optionally preceded by a heading and a series of introductory paragraphs. 
      <gi>listBibl</gi> has takes an optional type attribute whose value is one of (list here). The type attribute is used to associate the bibliographic list contained within 
      <gi>listBibl</gi> with one of the content section of the Epidoc document. <!-- 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>                               -->

      <egXML xmlns="http://www.tei-c.org/ns/Examples">
      <listBibl default="NO">
      <head>Bibliography</head><!--    <biblStruct xml:id="NELSON80">
                            <analytic>
                                <author>Nelson, T. H.</author>
                                <title>Replacing the printed word: a complete
                                    literary system.</title>
                            </analytic>
                            <monogr>
                                <title>Information Processing '80: Proceedings
                                    of the IFIPS Congress, October 1980</title>
                                <editor>Simon H. Lavington</editor>
                                <imprint>
                                    <publisher>North-Holland</publisher>
                                    <pubPlace>Amsterdam</pubPlace>
                                    <date>1980</date>
                                </imprint>
                                <biblScope>pp 1013&#x2013;23 </biblScope>
                            </monogr>
                            <note>Apparently a draft of section 4 of
                                    <title>Literary Machines</title>.</note>
                        </biblStruct> -->

      <bibl xml:id="NELSON88" default="NO">Ted Nelson: 
      <title level="m" type="main">Literary Machines</title> (privately published, 1987)</bibl>
      <bibl xml:id="BAXTER88" default="NO">
      <author>Baxter, Glen</author>
      <title level="m" type="main">Glen Baxter His Life: the years of struggle</title> London: Thames and Hudson, 1988. </bibl></listBibl></egXML><!--  or a simple <gi>list</gi>:<egXML
                    xmlns="http://www.tei-c.org/ns/Examples">
                    <list>
                        <head>Bibliography</head>
                        <item>
                            <bibl xml:id="NEL80">
                                <author>Nelson, T. H.</author>
                                <title level="a">Replacing the printed word: a
                                    complete literary system.</title>
                                <title level="m">Information Processing '80:
                                    Proceedings of the IFIPS Congress, October
                                    1980</title>
                                <editor>Simon H. Lavington</editor>
                                <publisher>North-Holland</publisher>
                                <pubPlace>Amsterdam</pubPlace>
                                <date>1980</date>
                                <biblScope>pp 1013&#x2013;23 </biblScope>
                                <note>Apparently a draft of section 4 of
                                        <title>Literary Machines</title>.</note>
                            </bibl>
                        </item>
                        <item>
                            <bibl xml:id="NEL88">Ted Nelson: <title>Literary
                                    Machines</title> (privately published,
                            1987)</bibl>
                        </item>
                        <item>
                            <bibl xml:id="BAX88">
                                <author>Baxter, Glen</author>
                                <title>Glen Baxter His Life: the years of
                                    struggle</title> London: Thames and Hudson,
                                1988. </bibl>
                        </item>
                    </list>
                </egXML> -->
</p>
   <p>The formal declarations for these elements are as follows:
      <specGrp xml:id="DCOBI" n="Tags for Bibliographic                 References"><!--  &biblStruct;
                    &biblFull; -->
<?tei winita specGrpRef target="#DCOBILV"/?>

      <specGrpRef target="#DCOBICOR"/>
      <specGrpRef target="#DCOPUB"/></specGrp></p></div3>
   <div3 type="subsection" xml: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>
            <index><term>analytic level</term>
            <index><term>bibliographic</term></index></index>
            <index><term>monographic level</term>
            <index><term>bibliographic</term></index></index>
            <index><term>series level</term>
            <index><term>bibliographic</term></index></index>
            <index><term>bibliographic references</term>
            <index><term>analytic level</term></index></index>
            <index><term>bibliographic references</term>
            <index><term>monographic level</term></index></index>
            <index><term>bibliographic references</term>
            <index><term>series level</term></index></index> levels in a structured bibliographic reference</item>
         <item>titles of various kinds, and statements of intellectual responsibility (authorship, etc.)</item>
         <item>information relating to the publication, pagination, etc. of an item</item>
         <item>annotation, commentary, and further detail</item>
      </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 <ptr target="#COBICOO"/>).-->
 The list of elements is exhaustive, and it is likely that only projects with a particular emphasis on bibliography will use all of them. </p>
   <div4 type="Section" xml: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>
            <index><term>analytic level</term>
            <index><term>bibliographic</term></index></index> level, giving the title, author, etc., of the article; </item>
         <item>the <term rend="noindex">monographic</term>
            <index><term>monographic level</term>
            <index><term>bibliographic</term></index></index> level, giving the title, editor, etc., of the collection; </item>
         <item>the <term rend="noindex">series</term>
            <index><term>series level</term>
            <index><term>bibliographic</term></index></index> level, giving the title of the series, possibly the names of its editors, etc., and the number of the volume within that series. </item>
      </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><!--       <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:
                    <?tei winita
              <specList><specDesc key="analytic"/><specDesc key="monogr"/><specDesc key="series"/></specList> ?> 
               </p> -->

   <p>For purposes of TEI encoding, journals and anthologies are both treated as monographs; a journal title will thus be tagged as a 
      <gi>title level="j"</gi> element, or simply as a 
      <gi>title</gi> within a 
      <gi>monogr</gi> element. 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><!--     <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 German language series:<egXML
                        xmlns="http://www.tei-c.org/ns/Examples">
                        <biblStruct>
                            <analytic>
                                <author>Thaller, Manfred</author>
                                <title level="a">A Draft Proposal for a Standard
                                    for the Coding of Machine Readable
                                Sources</title>
                            </analytic>
                            <monogr>
                                <title level="j">Historical Social Research</title>
                                <imprint>
                                    <biblScope type="vol">40</biblScope>
                                    <date>October 1986</date>
                                    <biblScope type="pages">3-46</biblScope>
                                </imprint>
                            </monogr>
                            <monogr>
                                <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&#xFC;r
                                        Geschichte In Kommission bei Scripta
                                        Mercaturae Verlag</publisher>
                                    <date>1991</date>
                                </imprint>
                            </monogr>
                            <series xml:lang="de">
                                <title level="s">Halbgraue Reihe zur
                                    Historischen Fachinformatik</title>
                                <respStmt>
                                    <resp>Herausgegeben von</resp>
                                    <name type="person">Manfred Thaller</name>
                                    <name type="org">Max-Planck-Institut
                                        f&#xFC;r Geschichte</name>
                                </respStmt>
                                <title level="s">Serie A: Historische
                                    Quellenkunden</title>
                                <biblScope>Band 11</biblScope>
                            </series>
                        </biblStruct>
                    </egXML>
                </p> -->

   <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>
   <p>The formal declarations for the elements defined in this section are as follows:
      <specGrp xml:id="DCOBILV" n="Levels                     of bibliographic information"/></p></div4>
   <div4 type="Section" xml: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:
      <specList>
      <specDesc key="title"/>
      <specDesc key="author"/>
      <specDesc key="editor"/>
      <specDesc key="respStmt"/>
      <specDesc key="resp"/>
      <specDesc key="name"/>
      <specDesc key="meeting"/></specList></p>
   <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 
      <val>a</val> implies the analytic level; the values
      <val>m</val>, 
      <val>j</val>, and 
      <val>u</val> imply the monographic level; the value 
      <val>s</val> 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:
      <egXML xmlns="http://www.tei-c.org/ns/Examples">
      <biblStruct default="NO">
      <analytic>
      <author>Lucy Allen Paton</author>
      <title level="m" type="main">Notes on Manuscripts of the 
      <title level="m" xml:lang="fr" type="main">Prophécies de Merlin</title></title></analytic>
      <monogr>
      <title level="j" type="main">PMLA</title>
      <imprint>
      <biblScope type="vol">8</biblScope>
      <date>1913</date>
      <biblScope type="pages">122</biblScope></imprint></monogr></biblStruct></egXML> In this case, the analytic title 
      <q>Notes on Manuscripts of the<title level="m" type="main">Prophé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écies de Merlin,</q> does not create a semantic error because it is not directly contained by the 
      <gi>analytic</gi> element. </p>
   <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>
   <p>The following reference, from a national standard for bibliographic references,
      <note place="foot" anchored="yes">American National Standard for Bibliographic References, ANSI Z39.29-1977 (New York: American National Standards Institute, 1977), p. 34 (sec. A.2.2.1).</note> illustrates this type of analysis with its distinction between main and subordinate titles. <!-- Note that this uses the
                    more flexible<gi>bibl</gi>, rather than the structured
                        <gi>biblStruct</gi> element: consequently, there is no
                    requirement to tag all the components of the reference
                    (notably the authors). -->

      <egXML xmlns="http://www.tei-c.org/ns/Examples">
      <bibl default="NO">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>
      <title level="j" type="main">Ann. Acad. Sci. Fenn., Ser. A4</title>
      <date>1972</date>
      <biblScope type="vol: pp">187: 1-4</biblScope></bibl></egXML><!-- example from ANSI Z39.29, sec. A.2.2.1, p.34 -->
</p>
   <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" anchored="yes">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> Again, it is only because this example uses 
      <gi>bibl</gi> rather than 
      <gi>biblStruct</gi>, that specific punctuation may be included between the component elements of the reference.
      <egXML xmlns="http://www.tei-c.org/ns/Examples">
      <bibl default="NO">Tchaikovsky, Peter Ilich.
      <title level="m" type="main">The swan lake ballet</title> = 
      <title level="m" type="parallel" xml:lang="fr">Le lac des cygnes</title> : 
      <title level="m" type="subordinate" xml:lang="fr">grand ballet en 4 actes</title> : 
      <title level="m" type="subordinate">op. 20</title> [Score]. New York: Broude Brothers; [1951] (B.B. 59). vi, 685 p.</bibl></egXML><!-- example from ANSI Z39.29, sec. A.12.2, p.63 -->
</p>
   <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>
   <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>,
      <gi>persName</gi>, or 
      <gi>orgName</gi> element. Strings such as
      <q>unknwon</q> may be encoded using the 
      <gi>rs</gi> element. <!-- I'm mildly unahppy with this <rs>unknown</rs>, as it's not really a noun, is it? -sb -->
 At least one of the four naming elements (
      <gi>name</gi>,
      <gi>persName</gi>, 
      <gi>orgName</gi>, or 
      <gi>rs</gi> — at present the TEI schema files also permit 
      <gi>geogName</gi> and
      <gi>placeName</gi>, but these should not be used) and one
      <gi>resp</gi> element should be given within the 
      <gi>respStmt</gi> element, followed optionally by any number of any of them.</p>
   <p>Examples of secondary responsibility of this kind include the roles of illustrator, translator, encoder, and 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>
   <p>Examples of 
      <gi>author</gi> and 
      <gi>editor</gi> may be found in sections 
      <ptr target="#COBITY" evaluate="all" targOrder="Y"/>, and 
      <ptr target="#COBICOL" evaluate="all" targOrder="Y"/>; 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>
   <p>In this example, the 
      <gi>respStmt</gi> elements apply to the work as a whole, not merely to the first edition:
      <egXML xmlns="http://www.tei-c.org/ns/Examples">
      <bibl default="NO">
      <author>Lominadze, D. G.</author>
      <title level="m" type="main">Cyclotron waves in plasma.</title>
      <respStmt>
      <resp>translated by</resp>
      <name>A. N. Dellis;</name></respStmt>
      <respStmt>
      <resp>edited by</resp>
      <name>S. M. Hamberger.</name></respStmt>
      <edition>1st ed.</edition>
      <pubPlace>Oxford:</pubPlace>
      <publisher>Pergamon Press,</publisher>
      <date>1981.</date>
      <extent>206 p.</extent>
      <title level="s" type="main">International series in natural philosophy.</title>
      <note place="inline" anchored="yes">Translation of: 
      <title xml:lang="ru" level="m" type="main">Ciklotronnye volny v plazme.</title></note></bibl></egXML><!-- from ISO 690: 1987, clause 4.1, p. 2. -->
</p>
   <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.
      <egXML xmlns="http://www.tei-c.org/ns/Examples">
      <biblStruct default="NO">
      <monogr xml:lang="de">
      <title level="m" type="main">Des Minnesangs Frühling</title>
      <note place="inline" anchored="yes">Mit 1 Faksimile</note>
      <edition>36., neugestaltete und erweiterte Auflage</edition>
      <respStmt>
      <resp>Unter Benutzung der Ausgaben von 
      <name>Karl Lachmann</name> und 
      <name>Moriz Haupt</name>, 
      <name>Friedrich Vogt</name> und 
      <name>Carl von Kraus</name> bearbeitet von</resp>
      <name>Hugo Moser</name>
      <name>Helmut Tervooren</name></respStmt>
      <imprint>
      <biblScope type="volume">I</biblScope>
      <biblScope type="volume title">Texte</biblScope>
      <pubPlace>Stuttgart</pubPlace>
      <publisher>S. Hirzel Verlag</publisher>
      <date>1977</date></imprint></monogr></biblStruct></egXML><!-- 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.  -->
 With the exception of the 
      <gi>name</gi> element (for which see section
      <ptr target="#CONA" evaluate="all" targOrder="Y"/>), the elements described in this section are defined as follows:
      <specGrp xml:id="DCOBICOR" n="Author,                     title, etc."/></p></div4>
   <div4 type="Section" xml:id="COBICOI">
   <head>Imprint, Pagination, and Other Details</head>
   <p>By 
      <mentioned>imprint</mentioned> 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:
      <specList>
      <specDesc key="imprint"/>
      <specDesc key="address"/>
      <specDesc key="pubPlace"/>
      <specDesc key="publisher"/>
      <specDesc key="date"/>
      <specDesc key="idno"/>
      <specDesc key="extent"/>
      <specDesc key="biblScope"/></specList></p>
   <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. 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 
      <ptr target="#CONAAD" evaluate="all" targOrder="Y"/>. Alternatively, if desired, the
      <gi>rs</gi> or 
      <gi>name</gi> elements described in section 
      <ptr target="#CONARS" evaluate="all" targOrder="Y"/> may be used; this involves no claim that the information given is either a full address or the name of a city. </p>
   <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:
      <egXML xmlns="http://www.tei-c.org/ns/Examples">
      <biblStruct default="NO">
      <monogr>
      <author>Nicholas, Charles K.</author>
      <author>Welsch, Lawrence A.</author>
      <title level="m" type="main">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></egXML> and with dissertations:
      <egXML xmlns="http://www.tei-c.org/ns/Examples">
      <biblStruct default="NO">
      <monogr>
      <author>Hansen, W.</author>
      <title level="u" type="main">Creation of hierarchic text with a computer display</title>
      <note place="inline" anchored="yes">Ph.D. dissertation</note>
      <imprint>
      <publisher>Dept. of Computer Science, Stanford Univ.</publisher>
      <pubPlace>Stanford, CA</pubPlace>
      <date value="1971-06">June 1971</date></imprint></monogr></biblStruct></egXML><!-- 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>
   <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.
      <egXML xmlns="http://www.tei-c.org/ns/Examples">
      <biblStruct default="NO">
      <monogr>
      <author>Shirley, James</author>
      <title type="main" level="m">The gentlemen of Venice</title>
      <title type="subordinate" level="m">a tragi-comedie presented at the private house in Salisbury Court by Her Majesties servants</title>
      <note place="inline" anchored="yes">[Microform]</note>
      <imprint>
      <pubPlace>London</pubPlace>
      <publisher>H. Moseley</publisher>
      <date>1655</date></imprint>
      <extent>78 p.</extent></monogr>
      <monogr>
      <imprint>
      <pubPlace>New York</pubPlace>
      <publisher>Readex Microprint</publisher>
      <date>1953</date></imprint>
      <extent>1 microprint card, 23 x 15 cm.</extent></monogr>
      <series>
      <title level="m" type="main">Three centuries of drama: English, 1642–1700</title></series></biblStruct></egXML><!-- example from ANSI Z39.29, sec. A.3.12.1, p.41 -->
</p>
   <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>
   <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>
   <p>For example:
      <egXML xmlns="http://www.tei-c.org/ns/Examples">
      <biblStruct default="NO">
      <analytic>
      <author>Wrigley, E. A.</author>
      <title level="m" type="main">Parish registers and the historian</title></analytic>
      <monogr>
      <editor role="editor">Steel, D. J.</editor>
      <title level="m" type="main">National index of parish registers</title>
      <imprint>
      <pubPlace>London</pubPlace>
      <publisher>Society of Genealogists</publisher>
      <date value="1968">1968</date></imprint>
      <biblScope type="volume">vol. 1</biblScope>
      <biblScope type="pages">pp. 155–167.</biblScope></monogr></biblStruct></egXML></p>
   <p>The <att>type</att> attribute on 
      <gi>biblScope</gi> is optional: both the following are legal examples:
      <egXML xmlns="http://www.tei-c.org/ns/Examples">
      <biblStruct default="NO">
      <analytic>
      <author>Boguraev, Branimir</author>
      <author>Neff, Mary</author>
      <title level="m" type="main">Text Representation, Dictionary Structure, and Lexical Knowledge</title></analytic>
      <monogr>
      <title level="j" type="main">Literary &amp; Linguistic Computing</title>
      <imprint>
      <biblScope type="volume">7</biblScope>
      <biblScope type="issue">2</biblScope>
      <date>1992</date>
      <biblScope type="pages">110-112</biblScope></imprint></monogr></biblStruct></egXML>
      <egXML xmlns="http://www.tei-c.org/ns/Examples">
      <biblStruct default="NO">
      <analytic>
      <author>Chesnutt, David</author>
      <title level="m" type="main">Historical Editions in the States</title></analytic>
      <monogr>
      <title level="j" type="main">Computers and the Humanities</title>
      <imprint>
      <biblScope>25.6</biblScope>
      <date value="1991-12">(December, 1991):</date>
      <biblScope>377–380</biblScope></imprint></monogr></biblStruct></egXML><!-- TYPE attribute dropped from biblScope in Chesnutt        -->
<!-- example, as per WWP suggestion (otherwise lead-in makes  -->
<!-- no sense) (msm)                                          -->
</p>
   <p>Formal definitions for the elements described in this section are as follows:
      <specGrp xml:id="DCOPUB" n="Bibliographic                     subelements">
      <p>Note and date are defined elsewhere, as are extent, address, and idno.</p></specGrp></p></div4>
   <div4 type="Section" xml: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 
      <ptr target="#COBICOL" evaluate="all" targOrder="Y"/>) may be tagged
      <gi>editor</gi> or 
      <gi>respStmt</gi>. </p></div4>
   <div4 type="Section" xml: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. 
      <mentioned>[Score]</mentioned> or 
      <mentioned>[Microform]</mentioned>), or its provenance (e.g. 
      <mentioned>translation of ...</mentioned>) 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.
      <specList>
      <specDesc key="note"/></specList></p>
   <p>For example:
      <egXML xmlns="http://www.tei-c.org/ns/Examples">
      <bibl default="NO">
      <author>Coombs, James H., Allen H. Renear, and Steven J. DeRose.</author>
      <title level="a" type="main">Markup Systems and the Future of Scholarly Text Processing.</title>
      <title level="j" type="main">Communications of the ACM</title>
      <biblScope>30.11 (November 1987): 933–947.</biblScope>
      <note anchored="yes" place="not specified">Classic polemic supporting descriptive over procedural markup in scholarly work.</note></bibl></egXML></p></div4>
   <div4 type="Section" xml:id="COBICOO">
   <head>Order of Components within References</head>
   <p>The order of elements in 
      <gi>bibl</gi> elements is not constrained. </p><!-- <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 type="simple">
                        <item><gi>note</gi>s on the publication (and
                            <gi>meeting</gi> elements describing the conference,
                            in the case of a proceedings volume)</item>
                        <item><gi>edition</gi> elements, each followed by any
                                related<gi>editor</gi> or <gi>respStmt</gi>
                            elements</item>
                        <item>
                            <gi>imprint</gi>
                        </item>
                        <item>
                            <gi>biblScope</gi>
                        </item>
                    </list> Within <gi>imprint</gi>, the elements allowed may
                    appear in any order.</p>
                <p>Finally, within the <gi>series</gi> information in
                        a<gi>biblStruct</gi>, the sequence of elements is not
                    constrained. </p>
                <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 <ptr target="#HD2"/>. </p> -->
</div4></div3>
   <div3 type="subsection" xml:id="COBIxx">
   <head>Structure of Bibliographic Items</head>
   <p>Although TEI provides for many different and powerful ways to structure bibliographic entries, Epidoc recommends using one of two basic models: a flat, traditional bibliographic entry, using a 
      <gi>bibl</gi>, or a nested entry that facilitates data entry, which uses the 
      <gi>biblItem</gi> element.</p>
   <div4 type="Section" xml:id="COBIxx">
   <head>Traditional Bibliographic Entries</head>
   <p>This form of bibliographic entry is best suited to small corpora or publications of single inscriptions, where the bibliography for each inscription is contained within the 
      <gi>div type="bibliography"</gi> section. If bibliography for many inscriptions is collected into a single file, then this model is best suited when there aren't many entries.</p>
   <p>Traditional bibliography uses the bibliographic components, and just lists the author, title, publisher year and specific reference if there is one.</p>
   <p>Add Example here</p></div4>
   <div4 type="subsection" xml:id="COBIxx">
   <head>Nested Bibliographic Entries</head>
   <p>Nested bibliographic items use the 
      <gi>biblItem</gi> element. This element contains other 
      <gi>biblItem</gi> elements, each of which has a role attribute describing its relationship to its containing element. The most common value will be "contained." <hi rend="bold">EM: name is up for grabs.</hi>. The intent of this structure is to eliminate the need to retype entries for publications that contain other publication. So, in the case of journal article, the outermost 
      <gi>biblItem</gi> will document the journal, a second level 
      <gi>biblItem</gi> documents the volume, and the innermost 
      <gi>biblItem</gi> documents the article. Likewise for edited collections, the innermost 
      <gi>biblItem</gi> represents the article, which is then contained by a 
      <gi>biblItem</gi> representing the volume. <hi rend="bold">EM: note that this element may disappear from P5, so we'll have to edit to make this section describe bibl, which will most likely take over its function. Also, need better description.</hi></p>
   <p>Add Example here.</p></div4></div3>
   <div3 type="subsection" xml: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 
      <ptr target="#COXR" evaluate="all" targOrder="Y"/>). 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:
      <egXML xmlns="http://www.tei-c.org/ns/Examples">As shown above (
      <ptr target="#NEL80" evaluate="all" targOrder="Y"/>) ...</egXML> It is best to avoid the use of the 
      <gi>ptr</gi> element. </p>
   <p>Where the form of the reference is important, or contains additional qualifying information which is to be distinguished from the surrounding text, the 
      <gi>ref</gi> element should be used, as in the following example:
      <egXML xmlns="http://www.tei-c.org/ns/Examples">CIL
      <ref target="#CIL" evaluate="all" targOrder="Y">II 345</ref> ...</egXML> In this way, an overall bibliography may be maintained separately, and references to it may be placed where they are necessary, without risking typing errors and inconsistencies. The 
      <attribute>target</attribute> points to the id of the appropriate 
      <gi>bibl</gi> or 
      <gi>biblItem</gi>, and the content of the 
      <attribute>ref</attribute> element contains a reference to a page or item number.. </p><!--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: -->
<!--  -->
<!--<egXML xmlns="http://www.tei-c.org/ns/Examples">-->
<!--Nelson claims (<ref target='NEL80'>Nelson [1980], <biblScope>especially -->
<!--pages 13&ndash;37</ref>) ... -->
<!--]]> -->
<!--</egXML> -->
<!--  -->
<!--(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:<egXML
                    xmlns="http://www.tei-c.org/ns/Examples">Nelson claims (<ref
                        target="#NEL80">Nelson [1980]</ref> pages 13â€“37)
                ...</egXML>
            </p> -->
</div3>
   <div3 type="subsection" xml:id="COBIOT">
   <head>Relationship to Other Bibliographic Schemes</head>
   <p>The bibliographic markup described in this section is a subset of the bibliographic markup provided by TEI P5. For more information about how it maps to other commonly used systems like ProCite and BibText, please read the corresponding section of P5.</p><!--    <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>
            <p>Listed below are the equivalences between the various
                bibliographic fields defined for use in the Scribe and BibTeX
                systems of bibliographic databases and the elements defined in
                this tag set.<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>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 </label>
                    <item>tag as <gi>city</gi>, <gi>place</gi>, or
                        <gi>address</gi></item>
                    <label>annote </label>
                    <item>tag as <gi>note</gi></item>
                    <label>author </label>
                    <item>tag as <gi>author</gi></item>
                    <label>booktitle </label>
                    <item>tag as <gi>title level="m"</gi> or <gi>title</gi>
                        within <gi>monogr</gi></item>
                    <label>chapter </label>
                    <item>tag as <tag>biblScope type="chapter"</tag></item>
                    <label>date </label>
                    <item>used only to record date entry was made in the
                        bibliographic database; not supported</item>
                    <label>edition </label>
                    <item>tag as <gi>edition</gi></item>
                    <label>editor </label>
                    <item>tag as <gi>editor</gi> or <gi>respStmt</gi></item>
                    <label>editors </label>
                    <item>tag as multiple <gi>editor</gi> or <gi>respStmt</gi>
                        elements</item>
                    <label>fullauthor </label>
                    <item>use the <att>reg</att> attribute on <gi>author</gi> or
                            <gi>name</gi></item>
                    <label>fullorganization </label>
                    <item>use the <att>reg</att> attribute on <tag>name
                            type="org"</tag></item>
                    <label>howpublished </label>
                    <item>tag as <gi>note</gi>, possibly using the form
                            <tag>note place="inline"</tag></item>
                    <label>institution </label>
                    <item>used only for issuer of technical reports; tag as
                            <gi>publisher</gi>
                    </item>
                    <label>journal </label>
                    <item>tag as <tag>title level="j"</tag> or <gi>title</gi>
                        within <gi>monogr</gi></item>
                    <label>key </label>
                    <item>used to specify an alternate sort key for the
                        bibliographic item, for use instead of author's or
                        editor's name; not supported</item>
                    <label>meeting </label>
                    <item>tag as <gi>meeting</gi> or as <gi>note</gi></item>
                    <label>month </label>
                    <item>use <gi>date</gi>; if the date is not in a trivially
                        parseable form, use the <att>value</att> attribute to
                        provide a normalized equivalent in ISO 8601 format</item>
                    <label>note </label>
                    <item>tag as <gi>note</gi></item>
                    <label>number </label>
                    <item>tag as <tag>biblScope type="issue"</tag> or
                            <tag>biblScope type="number"</tag>; for technical
                        report numbers, use <tag>idno type="docno"</tag></item>
                    <label>organization </label>
                    <item>used only for sponsor of conference; use <tag>name
                            type="org"</tag> within <gi>respStmt</gi> within
                            <gi>meeting</gi> element</item>
                    <label>pages </label>
                    <item>tag as <tag>biblScope type="pages"</tag></item>
                    <label>publisher </label>
                    <item>tag as <gi>publisher</gi></item>
                    <label>school </label>
                    <item>used only for institutions at which thesis work is
                        done; tag as <gi>publisher</gi>
                    </item>
                    <label>series </label>
                    <item>tag as <tag>title level="s"</tag> or <gi>title</gi>
                        within <gi>series</gi></item>
                    <label>title </label>
                    <item>tag as <gi>title</gi> in appropriate context or with
                        appropriate <att>level</att> value</item>
                    <label>volume </label>
                    <item>tag as <tag>biblScope type="volume"</tag></item>
                    <label>year </label>
                    <item>tag as <gi>date</gi>; if the date is not in a
                        trivially parseable form, use the <att>value</att>
                        attribute to provide an ISO-format equivalent</item>
                 </list></p> -->
</div3></div2>
   <div id="changeme-responsibility" type="gl-responsibility" org="uniform" part="N" sample="complete">
      <head>Responsibility for this section</head>
      <listBibl default="NO">
         <bibl default="NO"><respStmt><resp>author</resp><name>to be added</name></respStmt></bibl>
      </listBibl>
   </div>
   <div id="changeme-cvs" type="gl-cvs" org="uniform" part="N" sample="complete">
      <head><abbr expan="Concurrent Versioning System">CVS</abbr> Information</head>
      <p id="changeme-cvs-revision-number">Revision number: <seg n="cvs-revision-number" cert="high" part="N">$Revision: 1.3 $</seg></p>
      <p id="changeme-cvs-revision-name">Revision name (if any): <seg n="cvs-revision-name" cert="high" part="N">$Name: r-4-beta-1 $</seg></p>
      <p id="changeme-cvs-revision-date">Revision date: <seg n="cvs-revision-date" cert="high" part="N">$Date: 2006/04/18 21:12:51 $</seg></p>
      <p id="changeme-cvs-revision-author">Revision committed by: <seg n="cvs-revision-author" cert="high" part="N">$Author: paregorios $</seg></p>
   </div>
</div>