<?xml version="1.0" ?><!-- ***********************	 ***** biblist.dtd *****	 ***********************			An XML document type definition for lists of citations from scientific and	scholarly articles. It is intended to facilitate exchange and processing of	citation information.		This DTD is also a component of article.dtd.			Conforms to http://www.w3.org/TR/1998/REC-xml-19980210 	(XML 1.0)	and is also compliant with SGML systems with an appropriate SGML	declaration file.			Version B.1.0  (1998-12-6)			Copyright 1998 Openly Informatics, Inc. and David Ephron.	All rights reserved.	Created by Eric Hellman and David Ephron.			Refer to this file as "http://nj.oclc.org/efirst/biblist-B.1.0.dtd"	or as PUBLIC "+//IDN www.openly.com//DTD biblist-B.1.0//EN//XML" 				Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditionsare met:    Redistributions of source  must retain the above copyright    notice, this list of conditions and the following disclaimer.     Redistributions in binary form must reproduce the above copyright    notice, this list of conditions and the following disclaimer in    the documentation and/or other materials provided with the    distribution.    The names of the authors may not be used to endorse or promote    products derived from this specification without specific prior written    permission.     "eFirst XML" is a Service Mark of Openly Informatics, Inc. The eFirst    name and logo may not be used to endorse or promote    products derived from this specification without specific prior written    permission of Openly Informatics, Inc.. THIS DOCUMENT TYPE DEFINITION IS PROVIDED ''AS IS'' AND ANY EXPRESSOR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSEARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANYDIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OROTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVENIF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 	--><!-- *********************	 ***** Standards *****	 *********************			The values of the attribute 'xml:lang' should conform to ISO639		(e.g. en=English, fr=French, de=German, etc.)	The values of the attribute 'dateStamp' should conform to		http://www.w3.org/TR/NOTE-datetime-970915 (yyyy-mm-ddThh:mm:ssZ)		(e.g. 1998, 1998-09, 1998-09-19, 1998-09-19T14Z, 1998-09-19T14:00:00Z)	The contents of the element <math> should conform to the specification		for MathML at http://www.w3.org/TR/REC-MathML	The values of the attribute 'type', where indicated to be MIME strings,		should conform to RFC 2045-2049 and the registered MIME types thereof																			-->																	  <!-- ********************************* --><!-- ***** Standard ISO Entities ***** --><!-- ********************************* --><!ENTITY % ISOnum PUBLIC "ISO 8879:1986//ENTITIES Numeric and Special Graphic//EN//XML" "ISOentities/ISOnum.pen" >%ISOnum;<!ENTITY % ISOpub PUBLIC "ISO 8879:1986//ENTITIES Publishing//EN//XML" "ISOentities/ISOpub.pen">%ISOpub;<!ENTITY % ISOtech PUBLIC "ISO 8879:1986//ENTITIES General Technical//EN//XML" "ISOentities/ISOtech.pen" >%ISOtech;<!ENTITY % ISOdia PUBLIC "ISO 8879:1986//ENTITIES Diacritical Marks//EN//XML" "ISOentities/ISOdia.pen" >%ISOdia;<!ENTITY % ISOlat1 PUBLIC "ISO 8879:1986//ENTITIES Added Latin 1//EN//XML" "ISOentities/ISOlat1.pen" >%ISOlat1;<!ENTITY % ISOlat2 PUBLIC "ISO 8879:1986//ENTITIES Added Latin 2//EN//XML" "ISOentities/ISOlat2.pen" >%ISOlat2;<!ENTITY % ISOamso PUBLIC "ISO 8879:1986//ENTITIES Added Math Symbols: Ordinary//EN//XML" "ISOentities/ISOamso.txt" >%ISOamso;<!ENTITY % ISOgrk1 PUBLIC "ISO 8879:1986//ENTITIES Greek Letters//EN//XML" "ISOentities/ISOgrk1.pen" >%ISOgrk1;<!ENTITY % ISOgrk3 PUBLIC "ISO 8879:1986//ENTITIES Greek Symbols//EN//XML" "ISOentities/ISOgrk3.pen" >%ISOgrk3;<!-- These entity files declare the standard ISO 8879 entities and translate them to their unicode equivalents. The AMS entities will be added when unicode translation files become available. --><!-- *************************** --><!-- ***** Custom Entities ***** --><!-- *************************** --><!ENTITY h "&#x210E;" ><!ENTITY hbar "&#x210F;" ><!-- ENTITY lambdabar --><!ENTITY onebar "<o>1</o>" ><!ENTITY twobar "<o>2</o>" ><!ENTITY lsaquo "‹" ><!ENTITY rsaquo "›" ><!-- ****************** --><!-- ***** MathML ***** --><!-- ****************** --><!-- Reference to the MathML standard will appear here. For now, <math> is reserved. --><!ELEMENT math EMPTY ><!-- ***************** --><!-- ***** Names ***** --><!-- ***************** -->					 <!ELEMENT pn (#PCDATA | meta | pn.prefix | pn.first | pn.middle | pn.last |			  pn.suffix)* ><!ATTLIST pn indexName CDATA #IMPLIED ><!ELEMENT pn.prefix (#PCDATA) >	<!-- Dr.; Prof.; Mrs.; The Honorable; etc. --><!ELEMENT pn.first (#PCDATA) >	<!-- John; Mary-Jane; J.; etc. --><!ELEMENT pn.middle (#PCDATA) >	<!-- Ivanovna; I.; Charles David Paul; etc. --><!ELEMENT pn.last (#PCDATA) >	<!-- Doe; Doe-Deer; von Dorn; etc. --><!ELEMENT pn.suffix (#PCDATA) >	<!-- Jr.; Sr.; IV; Regina; etc. --><!ELEMENT orgName (#PCDATA | meta)* ><!ATTLIST orgName indexName CDATA #IMPLIED ><!-- Dept of Physics, Harvard University; Microsoft Corp.; etc. --><!ELEMENT orgAddr (#PCDATA | br)* ><!ELEMENT br EMPTY ><!-- <pn> holds a person's name, optionally parsed into its components if possible. The component elements with the prefix "pn." should not contain extra white space or separating punctuation such as commas but should include meaningful hyphens, periods, and interior spaces; for example: <pn><pn.prefix>Dr.</pn.prefix>_<pn.first>John</pn.first>_<pn.last>Poe-Doe</pn.last>,_<pn.suffix>Jr.</pn.suffix></pn> where the underscores represent spaces. <dispName> holds the same name exactly as it should appear in print; <indexName> holds a name as it should appear in an alphabetical index, ususally in the form "lastname, firstname middlename" or "lastname, i. i." or "organization, the" etc. Use <br> to indicate natural line breaks in addresses; these will typically be shown as ", " in single line representations. Contact information should be stored in <meta> elements with reference to xmlns = "http://nj.oclc.org/resources/person/". Sample field names include PN.phone, PN.email, PN.fax, PN.webpage, PN.address, etc. --><!-- ************************** --><!-- ***** Basic elements ***** --><!-- ************************** --><!ELEMENT meta EMPTY ><!ATTLIST meta id ID #IMPLIED			   type (index | ident | person | org | bib | serial | special)					#IMPLIED			   name NMTOKEN #REQUIRED			   vers NMTOKEN #IMPLIED			   content CDATA #REQUIRED			   dateStamp NMTOKEN #IMPLIED			   scheme CDATA #IMPLIED			   comment CDATA #IMPLIED			   xml:lang NMTOKEN #IMPLIED ><!-- The <meta> element serves two related functions: a) a container for metadata, and b) a link to database information. In function (a), 'name' describes the metadata, such as URN, SICI, ISSN, DC.creator, PN.phone, etc. and 'content' holds the value. In function (b), 'name' indicates the name of the database and 'content' is the key. 'vers' distinguishes indexing schemes that may change in time, such as PACS. 'dateStamp' optionally contains a date that the information was verified. 'scheme' typically holds a uri that describes the encoding used in 'content'. 'xmlns' may optionally hold a uri that serves as standard marker for the terminology employed by 'name' and 'scheme'. Note that <meta> always describes the object associated with its parent element. --><!ELEMENT date (#PCDATA) ><!ATTLIST date dateStamp NMTOKEN #IMPLIED ><!-- The 'dateStamp' attribute contains the definitive date in the format specified in http://www.w3.org/TR/NOTE-datetime-970915 (yyyy-mm-ddThh:mm:ssZ). The content is a natural language representation for use by rendering apps. --><!-- ******************************************* --><!-- ***** HTML compatible text formatting ***** --><!-- ******************************************* --><!ENTITY % htmlText "#PCDATA | B | I | U | SUB | SUP" ><!ELEMENT B (%htmlText;)* ><!ELEMENT I (%htmlText;)* ><!ELEMENT U (%htmlText;)* ><!ELEMENT SUB (%htmlText;)* ><!ELEMENT SUP (%htmlText;)* ><!-- These are HTML compatible elements for use in bibliographic citations to allow applications to deliver or accept formatted references. These elements are distinct from the equivalent elements with the same names but in lowercase, defined in article.dtd; the latter have a different content model. These elements are also used in <styledEq> in article.dtd --><!-- ************************************ --><!-- ***** Bibliographic Containers ***** --><!-- ************************************ --><!ELEMENT bib (meta*, bib.html?, bib.tagged?, bib.data?, bib.link*) ><!ATTLIST bib id ID #REQUIRED			  relation (none | ibid | opCit | translationOf) "none"			  relatedTo IDREF #IMPLIED			  type (article | book |  patent | thesis | conf  | confPaper |					preprint | software | database | webPage | news | mag |					report |  private | otherType)  #IMPLIED			  otherName CDATA #IMPLIED			  published (yes | no)  #IMPLIED			  display (html | tagged) "html" ><!-- 'relation' would typically be used in a footnote if the reference has already been cited; 'relatedTo' specifies the initial reference. Processing applications must at some point check the integrity of these references, in particular because the order of notes may change during editing. When 'relation' is set to "ibid" or "opCit", the <bib> should only contain information that distinguishes the present reference from its antecedent, such as a new page number or range.'type' indicates the type of resource that is being cited:            article       -  can be a journal article or an article in an edited book     book          -  specify pages or sections to restrict the citation      conf          -  a conference or meeting as a whole     confPaper     -  a paper or presentation at a conference or meeting     thesis        -  a work submitted to a degree-granting institution     preprint      -  a work available from a preprint server     database      -  a record in a named database or the database as a whole     mag           -  something from a magazine     news          -  something from a newspaper     private       -  a private or personal communication     webPage       -  ref. to web pages (specify date verified in <bib.link>)     report        -  tag report numbers using <itemNum>     otherType     -  the type is specified in 'otherName'     The published="no" attribute has the same meaning as "to be published", "unpublished", "in press" etc. would have in the text of a citation. 		--><!-- Each <bib> may optionally have 4 "forks". These may be generated in rather different ways; the generator or source may be noted in the 'source' attribute, the generation date and comments may be stored in 'dateStamp' and 'comment'. The 'display' attribute indicates to rendering applications whether <bib.html> or <bib.tagged> is the preferred fork to use for displaying the citation. --> <!-- <bib.html> is minimal HTML text with formatting information only.  Thisitem is intended to store unparsed, formatted text coming from a manuscript. It can also be used to store formatted text for display. <bib.tagged> is content tagged text as familiar in SGML. <bib.data> is a structured content model designed for bibliographic databases. <bib.link> is provided to allow web links to be associated with a particular <bib>. The content should be text descriptive of the linked resource. Although URI's may be put in <ident>s, they are typically not reliable as identifiers. --><!ELEMENT bib.html (%htmlText;)* ><!ATTLIST bib.html source CDATA #IMPLIED 				   comment CDATA #IMPLIED 				   dateStamp NMTOKEN #IMPLIED ><!ELEMENT bib.tagged (#PCDATA |  au | ed | roleGroup | ti | jn | ident | vol |					  iss | segment | artNum | pp | pSeq | bibDate | yr |					  publisher | bibLoc | edition | itemNum | source | bibURI					  | bibOther)* ><!ATTLIST bib.tagged source CDATA #IMPLIED                      comment CDATA #IMPLIED                      dateStamp NMTOKEN #IMPLIED ><!ELEMENT bib.data (au?, ed?, roleGroup*,					(ti, ident*, (ti, ident*, (ti,ident*)?)?)?, (jn, ident*)?,					edition?, vol?, iss?, segment?, artNum?, pp?, pSeq?,					publisher?, (bibLoc | bibDate)*, (source, itemNum?)*,					bibURI?, bibOther*) ><!ATTLIST bib.data source CDATA #IMPLIED                   comment CDATA #IMPLIED                   dateStamp NMTOKEN #IMPLIED   ><!ELEMENT bib.link (#PCDATA) ><!ATTLIST bib.link id ID #IMPLIED				   href CDATA #REQUIRED				   source CDATA #IMPLIED				   comment CDATA #IMPLIED				   dateStamp NMTOKEN #IMPLIED				   xml:link CDATA #FIXED "simple" ><!-- **************************** --><!-- ***** Creator elements ***** --><!-- **************************** --><!ELEMENT au (#PCDATA | pn | orgName)* > <!-- the authors --><!ELEMENT ed (#PCDATA | pn)* > <!-- the editors --><!ELEMENT roleGroup (#PCDATA | pn)* > <!-- someone else with a role --><!ATTLIST roleGroup role (translator | seriesEditor | illustrator |						  photographer | sponsor) #REQUIRED ><!-- <au> holds a group of authors, <ed> a group of editors, and <roleGroup> others with a specified 'role'. <orgName> holds corporate authors (i.e. institutions acting as authors; e.g. IBM; The Trustees of Superior College; etc. --><!-- ************************** --><!-- ***** Title elements ***** --><!-- ************************** --><!ELEMENT ti (%htmlText;)* > <!-- the title of the cited work--><!ATTLIST ti role (title | subtitle | seriesTitle | containerTitle |                   confName) "title"			 xml:lang NMTOKEN #IMPLIED ><!-- If present, role = "title" should refer to the work being cited. role = "containerTitle" should refer to the title of a containing work. For example, when an article is in an edited book, the book title has role = "containerTitle", while the title of the article itself has role = "title". -->                      <!ELEMENT jn (%htmlText;)* > <!-- a journal or serial name --><!ATTLIST jn form (abbrev | full) "abbrev"			 sourceID IDREF #IMPLIED			 caption CDATA #IMPLIED			 xml:lang NMTOKEN #IMPLIED ><!-- The 'caption' attribute here and in <issue> and <volume> allows the insertion of tag lines like "Special Issue on Diverse Topics" or "The Journal Everybody Reads" --><!-- *********************** --><!-- ***** Identifiers ***** --><!-- *********************** --><!-- Identifiers can be provided in <meta> elements as well; <ident> is provided to accommodate the common practice of including them in bibliographic reference content. In <bib.data>, <ident>s imediately follow the <ti> or <jn> of the resource to which they refer. In <bib.tagged>, the processing application may attempt to infer the element to which an <ident> refers, and will always associate it with the preceding element if possible. An <ident> should uniquely identify a resource. A single <ident> element may have one or more of its attributes filled, and a citation may make use of one or more <ident>s to specify some or all of the possible fields. --><!ELEMENT ident EMPTY >                                   <!ATTLIST ident CODEN     NMTOKEN #IMPLIED                 ISSN      NMTOKEN #IMPLIED                ISBN      NMTOKEN #IMPLIED                PII       CDATA   #IMPLIED                DOI       CDATA   #IMPLIED                URN       CDATA   #IMPLIED                SICI      CDATA   #IMPLIED                LOCC      CDATA   #IMPLIED                otherID   CDATA   #IMPLIED                otherName CDATA   #IMPLIED ><!-- The possible identifiers include:            CODEN  -  a CODEN (administered by Chem Abstracts Service)            ISBN   -  International Standard Book Number              PII    -  Publisher Item Identifier            DOI    -  Digital Object Identifier             URN    -  Universal Resource Name            SICI   -  Serial Item Contribution Identifier            LOCC   -  Library of Congress Catalog Number            otherID-  special purpose ID's, specified by otherName			--><!-- *************************************** --><!-- ***** Bibliographic data elements ***** --><!-- *************************************** --><!-- The content of these elements should not include a label, such as "Volume" or "pp.". In <bib.tagged>, these labels should be left as untagged PCDATA (directly subordinate to the <bib.tagged> parent. In <bib.data>, they should be omitted entirely. The <segment> element is provided to accomodate other sorts of bibliographic pieces. --><!ELEMENT vol (#PCDATA) > <!-- a volume number --><!ATTLIST vol caption CDATA #IMPLIED><!ELEMENT iss (#PCDATA) > <!-- an issue number --><!ATTLIST iss caption CDATA #IMPLIED><!ELEMENT segment (#PCDATA) > <!-- a part, chapter, or section number. --><!ATTLIST segment type (part | chapter | section | otherType) #IMPLIED                otherName CDATA #IMPLIED ><!ELEMENT artNum ( #PCDATA ) > <!-- article number --><!ELEMENT pp (#PCDATA | pp.start | pp.end)* > <!-- page numbers --><!ELEMENT pp.start (#PCDATA)  > <!-- starting page number --><!ELEMENT pp.end (#PCDATA) > <!-- ending page number --><!ELEMENT pSeq (#PCDATA) > <!-- distinguishes multiple items on one page --><!ELEMENT bibDate (#PCDATA | yr | mo | dy | ssn)* > <!-- usu. the pub. date --><!ATTLIST bibDate dateStamp NMTOKEN #IMPLIED                  role (published | revised | confHeld | accessed |                  		issued) "published" ><!ELEMENT yr (#PCDATA) > <!-- a year --><!ELEMENT mo (#PCDATA) > <!-- a month --><!ELEMENT dy (#PCDATA) > <!-- a day --><!ELEMENT ssn (#PCDATA) > <!-- a season --><!ELEMENT publisher (#PCDATA) > <!-- publisher name --><!ATTLIST publisher sourceID IDREF #IMPLIED><!ELEMENT bibLoc (#PCDATA) > <!-- usually the publisher location --><!ATTLIST bibLoc role (published | confHeld | source) "published" ><!ELEMENT edition (#PCDATA) > <!-- the edition (for books) --><!ELEMENT source (#PCDATA) ><!ATTLIST source sourceID IDREF #IMPLIED ><!-- name of database, archive, patentissuer, institution issuing a report--><!ELEMENT itemNum (#PCDATA) ><!--item number for databases, archives, reports, patents used in conjunction with <source> --><!ELEMENT bibURI (#PCDATA) > <!-- a URI that appears explicitly in a cite --><!ATTLIST bibURI type (url | ftp | email) "url"				 sourceID IDREF #IMPLIED ><!ELEMENT bibOther (#PCDATA) ><!ATTLIST bibOther name CDATA #REQUIRED><!-- Use this element to customize bibliographic markup --><!-- ******************************* --><!-- ***** Metadata containers ***** --><!-- ******************************* --><!ELEMENT bibSources (bibSource)* ><!ELEMENT bibSource (ident | meta)* ><!ATTLIST bibSource id ID #REQUIRED                    type (journal | publisher | database | inst | archive |						  patentIssuer) "journal"                     source CDATA #IMPLIED                     comment CDATA #IMPLIED                     dateStamp NMTOKEN #IMPLIED ><!-- <bibSources> are journals, publishers, serials for which separate consolidated storage of metadata is appropriate. --><!ELEMENT link EMPTY ><!ATTLIST link href CDATA #IMPLIED			   rel NMTOKEN #REQUIRED			   type CDATA #IMPLIED               xml:link CDATA #FIXED "simple" ><!-- <link> is used to make logical links, including css stylesheets, RDF metadata, etc. --><!-- ********************************* --><!-- ***** Highest level element ***** --><!-- ********************************* --><!-- When this DTD is used to describe a list of citations independently, <biblist> is the highest level container element. This element is not used in article.dtd. --><!ELEMENT biblist (bib*, bibSources, link) ><!ATTLIST biblist dtdVer CDATA #REQUIRED				  xml:lang NMTOKEN "en" ><!-- The 'dtdVer' attribute should contain a url that specifies the version of the DTD in use when a document is created, modified, or checked. The correct url is indicated at the top of this DTD. The xml:lang attribute is assumed to be inherited, unless modified in a child element. -->