<!-- ============================================================= --> <!-- MODULE: Common (Shared) Elements Module --> <!-- VERSION: 1.1 --> <!-- DATE: November 1, 2003 --> <!-- --> <!-- ============================================================= --> <!-- ============================================================= --> <!-- PUBLIC DOCUMENT TYPE DEFINITION --> <!-- TYPICAL INVOCATION --> <!-- "-//NLM//DTD Archiving and Interchange DTD Suite Common (Shared) Elements Module v1.1 20031101//EN" Delivered as file "common.ent" --> <!-- ============================================================= --> <!-- ============================================================= --> <!-- SYSTEM: Archiving and Interchange DTD Suite --> <!-- --> <!-- PURPOSE: Defines the common parameter entities, calls the --> <!-- shared modules (such as special characters and --> <!-- notations) and provides declarations for elements --> <!-- that do not properly fit into one class, since --> <!-- they can be used at more than one structural level--> <!-- --> <!-- CONTAINS: 1) Default classes for elements defined in this --> <!-- module. May be overridden by values in the --> <!-- DTD's Customization Module --> <!-- 2) Parameter Entities for attribute values --> <!-- 3) Parameter Entities for content models --> <!-- 4) Parameter Entities for attribute lists --> <!-- 5) Elements used in many modules/classes --> <!-- - Address elements --> <!-- - Date elements --> <!-- - Personal name elements --> <!-- - Common metadata elements (shared by both --> <!-- article metadata and bibliographic --> <!-- reference metadata --> <!-- --> <!-- MODULES REQUIRED: --> <!-- 1) Standard XML Special Characters Module --> <!-- (%xmlspecchars.ent;) --> <!-- 2) Custom XML Special Characters (%chars.ent;) --> <!-- 3) Notation Declarations (%notat.ent;) --> <!-- --> <!-- CREATED FOR: --> <!-- Digital archives and publishers who wish to --> <!-- create a custom XML DTD for original markup of --> <!-- journal literature, books, and related material, --> <!-- or for archiving and transferring such material --> <!-- between archives. --> <!-- --> <!-- This DTD is in the public domain. An organization --> <!-- that wishes to create its own DTD from the suite --> <!-- may do so without permission from NLM. --> <!-- --> <!-- The suite has been set up to be extended using a --> <!-- new DTD file and a new DTD-specific customization --> <!-- module to redefine the many Parameter Entities. --> <!-- Do not modify the suite directly or redistribute --> <!-- modified versions of the suite. --> <!-- --> <!-- In the interest of maintaining consistency and --> <!-- clarity for potential users, NLM requests: --> <!-- --> <!-- 1. If you create a DTD from the Archiving and --> <!-- Interchange DTD Suite and intend to stay --> <!-- compatible with the suite, then please include --> <!-- the following statement as a comment in all of --> <!-- your DTD modules: --> <!-- "Created from, and fully compatible with, --> <!-- the Archiving and Interchange DTD Suite." --> <!-- --> <!-- 2. If you alter one or more modules of the suite, --> <!-- then please rename your version and all its --> <!-- modules to avoid any confusion with the --> <!-- original suite. Also, please include the --> <!-- following statement as a comment in all your --> <!-- DTD modules: --> <!-- "Based in part on, but not fully compatible --> <!-- with, the Archiving and Interchange DTD --> <!-- Suite." --> <!-- --> <!-- Suggestions for refinements and enhancements to --> <!-- the DTD suite should be sent in email to: --> <!-- archive-dtd@ncbi.nlm.nih.gov --> <!-- --> <!-- ORIGINAL CREATION DATE: --> <!-- December 2002 --> <!-- --> <!-- CREATED BY: Jeff Beck (NCBI) --> <!-- Deborah Lapeyre (Mulberry Technologies, Inc.) --> <!-- Bruce Rosenblum (Inera Inc.) --> <!-- --> <!-- NLM thanks the Harvard University Libraries, both --> <!-- for proposing that a draft archiving NLM DTD for --> <!-- life sciences journals be extended to accommodate --> <!-- journals in all disciplines and for sponsoring --> <!-- Bruce Rosenblum's collaboration with other DTD --> <!-- authors in completing Version 1.0. The Andrew W. --> <!-- Mellon Foundation provided support for these --> <!-- important contributions. --> <!-- --> <!-- ============================================================= --> <!-- ============================================================= --> <!-- DTD VERSION\CHANGE HISTORY --> <!-- ============================================================= --> <!-- ============================================================= Version Reason/Occasion (who) vx.x (yyyy-mm-dd) ============================================================= Version 1.1 (TRG) v1.1 (2003-11-01) 5. Made <copyright-statement> model into a parameter entity in order to add <ext-link> to the content model. Rationale: Permit linkage between copyright statement and copyright holder's site. 4. Added attribute "content-type" to element <ack>. Rationale: To identify and preserve the semantic intent of semantically rich source documents. 3. Added ID attribute to the following elements: - <ack> - <address> - <alt-text> - <ext-link> (by modifying %ext-link-atts;) - <institution> - <long-desc> - <notes> (by modifying parameter entity %notes-atts;) Rationale: Provide unique identifier so these elements can be linked to. 2. Added element <label> to content model of <aff> (by adding %label.class; to parameter %aff-elements;) Rationale: To provide <label> when needed for format over-ride. ============================================================= Version 1.0 Changes Before Public Release (Lapeyre) v1.0 (2002-12-25) 1. ETAL - Changed the content model of <etal> to replace the entier content model with a Parameter Entity, not just name some elements that may mix with #PCDATA. Rationale: The Authoring DTD would like to make <etal> EMPTY. --> <!-- ============================================================= --> <!-- PARAMETER ENTITY DEPENDENCIES Requires the following parameter entities be defined before calling this module, usually accomplished in the Customization Module for the specific DTD: %address-elements; %break.class; %emphasis.class; %ext-links.class; %inline-display.class; %just-rendition; %label.class; %link.class; %para-level; %references.class; %rendition-plus; %sec-back-matter-elements; %sec-level; %sec-opt-title-model; %simple-link.class; %simple-phrase; %simple-text; %subsup.class; %might-link-atts; --> <!-- ============================================================= --> <!-- ============================================================= --> <!-- DEFAULT CLASSES FOR ELEMENTS IN COMMON --> <!-- ============================================================= --> <!-- ACCESSIBILITY CLASS ELEMENTS --> <!-- Elements added to make it easier to process journal articles in ways that are more accessible to people and devices with special needs, for example the visually handicapped. <alt-text> is a short phrase description of an objects, <long-desc> is a more complete description of the content or intent of an object, and the <ext-link> in this grouping would point to an alternate form of the object. --> <!ENTITY % access.class "alt-text | ext-link | long-desc" > <!-- ADDRESS CLASS ELEMENTS --> <!-- Potential element components of an address; not a proper class --> <!ENTITY % address-elements "addr-line | country | email | fax | institution | phone | uri" > <!-- ADDRESS ELEMENTS INSIDE A PARAGRAPH --> <!-- Address elements that are allowed loose inside a paragraph --> <!ENTITY % inpara-address "email" > <!-- MODELS FOR NAMES OF INDIVIDUALS CLASS --> <!ENTITY % person-name.class "given-names | surname | suffix" > <!-- CITATION CLASS ELEMENTS --> <!-- Reference to an external document, as used within, for example, the text of a paragraph --> <!ENTITY % citation.class "citation" > <!-- CONFERENCE CLASS --> <!-- The element components of the description of a conference; not a proper class --> <!ENTITY % conference.class "conf-date | conf-name | conf-num | conf-loc | conf-sponsor | conf-theme | conf-acronym" > <!-- LABEL CLASS --> <!-- The label element, used to hold the number or character of a labeled object such as a table or footnote --> <!ENTITY % label.class "label" > <!-- PERSONAL NAMES CLASS --> <!-- The element components of a person's name, for the name of a contributor --> <!ENTITY % person-name.class "given-names | prefix | surname | suffix" > <!-- ============================================================= --> <!-- PARAMETER ENTITIES FOR ATTRIBUTE VALUES --> <!-- ============================================================= --> <!-- HISTORY DATE TYPES --> <!-- The <history> element contains one or more <date> elements that record events in the life of a publication. date-type Attribute should only be used if the date is one of the known types; otherwise omit the attribute. Values are: accepted - Date manuscript was accepted received - Date manuscript received rev-request - Date revisions were requested or manuscript was returned rev-recd - Date revised manuscript was received --> <!ENTITY % date-types "accepted | received | rev-request | rev-recd" > <!-- ARTICLE/PUBLICATION IDENTIFIER TYPES --> <!-- The "pub-id-type" attribute names the type of identifier, or the organization or system that defined this identifier for the identifier of the journal article or a cited publication. Used on the <article-id> element, which holds an identifier for the entire article. Also used on the <pub-id> element, which is an identifier for a publication cited in a bibliographic reference (citation). Valid Types include: coden - Obsolete PDB/CCDC identifier (may be present on older articles) doi - Digital Object Identifier for the article medline- NLM Medline identifier other - None of the named identifiers pii - Publisher Item Identifier, see /epub/piius.htm pmid - PUBMED ID (see www.ncbi.nlm.nih.gov/entrez/ query.fcgi?db=PubMed) publisher-id - Publisher's identifying number such as an 'article-id', 'artnum', 'identifier', 'article- number', etc. sici - Serial Item and Contribution Identifier (SICI). A journal article may have more than one SICI, one for a print version and one for an electronic version. --> <!ENTITY % pub-id-types "coden | doi | medline | other | pii | pmid | publisher-id | sici" > <!-- ============================================================= --> <!-- PARAMETER ENTITIES FOR COMMENT MODELS --> <!-- ============================================================= --> <!-- DATE ELEMENTS MODEL --> <!-- The content models for elements that describe dates, such as Publication Date <pub-date> and History Dates <date>. The <string-date> element holds dates for which months and years are not given, for example "first quarter", "spring", etc. --> <!ENTITY % date-model "(((day?, month?) | season)?, year?, string-date?)" > <!-- CONTENT MODEL FOR A STRUCTURAL SECTION --> <!-- The model for a section that requires that a section title be present, used for elements such as Section and Appendix. --> <!ENTITY % sec-model "label?, title, (%para-level;)*, (%sec-level;)*, (%sec-back-matter-elements;)*" > <!-- CONTENT MODEL FOR AN UNTITLED SECTION --> <!-- The model for a section-like structure that may or may not have an initial title --> <!ENTITY % sec-opt-title-model "label?, title?, (%para-level;)*, (%sec-level;)*, (%sec-back-matter-elements;)*" > <!-- LINK ELEMENTS --> <!-- Elements for use in the linking elements such as <xref>, <target>, and <ext-link> --> <!ENTITY % link-elements "| %emphasis.class; | %subsup.class;" > <!-- ARTICLE TITLES ELEMENTS --> <!-- Elements for use in all the title elements such as <title>, <subtitle>, <trans-title>, etc. --> <!ENTITY % title-elements "| %break.class; | %simple-phrase;" > <!-- ============================================================= --> <!-- PARAMETER ENTITIES FOR LINKING ATTRIBUTES --> <!-- ============================================================= --> <!-- XLINK LINK ATTRIBUTES --> <!-- Used for elements that are a link by definition, such as the <xref> element. xlink:href Provides an address or identifier of the object to which the link points, for example a URI or a filename xlink:role Provides a URI reference pointing to some resource that describes the role or function of this link xlink:title Describes the meaning of the link in a human-readable and displayable fashion xlink:show Describes the requested presentation when the link is traversed. Values are: embed Load the new presentation in the place of the link new Load a new window, frame, pane, or other presentation none No clue for the application other Look to other markup for a clue replace Load the new resource in the same window, frame, pane, or other presentation context as the link started in xlink:actuate When is the link traversed, and under whose control. Values are: none No clue for the application onLoad Traverse the link immediately upon loading the link onRequest User or software requests that the link be traversed other Look to other markup for a clue --> <!ENTITY % link-atts "xmlns:xlink CDATA #FIXED 'http://www.w3.org/1999/xlink' xlink:type (simple) #FIXED 'simple' xlink:href CDATA #REQUIRED xlink:role CDATA #IMPLIED xlink:title CDATA #IMPLIED xlink:show (embed | new | none | other | replace) #IMPLIED xlink:actuate (none | onLoad | onRequest | other) #IMPLIED" > <!-- MIGHT LINK XLINK ATTRIBUTES --> <!-- Used for elements which may need to link to external sources or other objects within the document, but may not necessarily act as a link at all. The attribute "xlink:href" identifies the object to which the link points. --> <!ENTITY % might-link-atts "xmlns:xlink CDATA #FIXED 'http://www.w3.org/1999/xlink' xlink:type (simple) #FIXED 'simple' xlink:href CDATA #IMPLIED xlink:role CDATA #IMPLIED xlink:title CDATA #IMPLIED xlink:show (embed | new | none | other | replace) #IMPLIED xlink:actuate (none | onLoad | onRequest | other) #IMPLIED" > <!-- ============================================================= --> <!-- PARAMETER ENTITIES FOR ATTRIBUTES LISTS --> <!-- ============================================================= --> <!-- AFFILIATION ATTRIBUTES --> <!-- Attributes for the Affiliation <aff> element --> <!ENTITY % aff-atts "id ID #IMPLIED rid IDREFS #IMPLIED" > <!-- COLLABORATION ATTRIBUTES --> <!-- Attributes for <collab> --> <!-- collab-type The type or role of the collaborators, what function did they play in the publication. Suggested values include: assignee - Group or company to whom a patent is awarded authors - Content creators editors - Content editors compliers - Put together a composite work from multiple sources guest-editors - A group of editors that have been invited to edit all or part of a work inventors - Idea, software, or machine creators translators - Translated the cited work from one language into another id Unique identifier so that the collaboration can be referenced xlink:href Provides an address or identifier of the object to which the link points, for example a URI or a filename --> <!ENTITY % collab-atts "collab-type CDATA #IMPLIED id ID #IMPLIED %might-link-atts;" > <!-- EXTERNAL LINK ATTRIBUTES --> <!-- Attribute list for external links ext-link-type Type of external link. Use this attribute if the type of external link is one of the ones below or another named type. Suggested values include: ec Enzyme nomenclature - see http://www.chem.qmw.ac.uk/iubmb/enzyme/ gen GenBank identifier genpept Translated Protein-encoding sequence Database highwire HighWire press intrajournal medline Medline or pubmed id pdb Protein data bank. See http://www.rcsb.org/pdb/ pgr Plant gene register. See http://www.tarweed.com/pgr/ pir Protein Information Resource see http://pir.georgetown.edu pirdb Protein Information Resource see http://pir.georgetown.edu pmc Used to link between articles in PubMedCentral access is PMID sprot Swiss-Prot. See http://www.ebi.ac.uk/swissprot/ aoi Astronomical Object Identifier doi Digital Object Identifier ftp File transfer protocol uri Website or web service id Unique identifier so the element may be referenced xlink:href Provides an address or identifier of the object to which the link points, for example a URI or a filename --> <!ENTITY % ext-link-atts "ext-link-type CDATA #IMPLIED id ID #IMPLIED %might-link-atts;" > <!-- CITATION ATTRIBUTES --> <!-- Attributes for <citation> citation-type Defines the type of work being referenced. Suggested values include: book Book conf-proceedings Conference proceedings discussion Dicussion among a group in some forum - public, private, or electronic, which may or may not be moderated gov Government publication journal Journal article list Listserv other None of the listed types patent Patent or patent application personal-communication Informal or personal communication, such as a phone call or an email message standard Standards document issued by a recognized standards body, such as ISO, ANSI, IEEE, OASIS, etc. thesis Work written as part of the completion of an advanced degree web Website id Unique identifier so the element may be referenced xlink:href Provides an address or identifier of the object to which the link points, for example a URI or a filename --> <!ENTITY % citation-atts "citation-type CDATA #IMPLIED id ID #IMPLIED %might-link-atts;" > <!-- ISSN ATTRIBUTES --> <!-- Attribute list for <issn> --> <!-- Used to record the type of publication, for example a print-only publication versus an electronic-only publication, in any of several life stages. Suggested values include: epub - Electronic publication ppub - Print publication epub-ppub - Published in both print and electronic form epreprint - Electronic preprint dissemination ppreprint - Print preprint dissemination ecorrected - Corrected in electronic pcorrected - Corrected in print eretracted - Retracted in electronic pretracted - Retracted in print --> <!ENTITY % issn-atts "pub-type CDATA #IMPLIED" > <!-- NOTE ATTRIBUTES --> <!-- Attribute list for <note> --> <!-- notes-type To identify the type of note, if the type can be/has been identified, for example, "note-in-proof" id Unique identifier so the element may be referenced --> <!ENTITY % notes-atts "id ID #IMPLIED notes-type CDATA #IMPLIED" > <!-- RELATED ARTICLE ATTRIBUTES --> <!-- Attributes for <related-article> related-article-type addendum Additional material for an article, generated too late to be added to the main text commentary-article Used in an commentary or editorial to link to the article on which it is commenting companion Used in an article to link to a companion (related or sibling) article corrected-article Used in a correction to link to the article being corrected. Sometimes called erratum. in-this-issue Related article in the same journal issue letter A letter to the publication or a reply to such a letter commentary Used in an article to link to its associated commentary or editorial correction-forward Used in an article to link forward to its associated correction (rarely used) retracted-article Used in a retraction to link to the article being retracted retraction-forward Used in an article to link forward to its associated retraction (rare) vol Volume of the journal in which the related article exists. It is best practice to limit the scope to the current journal, the one in which the current article resides. page Page number of the related article. It is best practice to limit the scope to the current journal, the one in which the current article resides. The values for this attribute should be a first page or a page range. xlink:href Provides an address or identifier of the object to which the link points, for example a URI or a filename. --> <!ENTITY % related-article-atts "related-article-type CDATA #REQUIRED vol CDATA #IMPLIED page CDATA #IMPLIED %might-link-atts;" > <!-- BIOGRAPHY ATTRIBUTES --> <!-- Attributes for <bio> element id Unique identifier so the element may be referenced rid Points to the identifier of an author or or authors xlink:href Provides an address or identifier of the object to which the link points, for example a URI or a filename. --> <!ENTITY % bio-atts "id ID #IMPLIED rid IDREFS #IMPLIED %might-link-atts;" > <!-- ============================================================= --> <!-- ELEMENT USED BY MORE THAN ONE CLASS --> <!-- ============================================================= --> <!-- ============================================================= --> <!-- COMMON METADATA/BIBLIOGRAPHIC ELEMENTS --> <!-- ============================================================= --> <!-- ARTICLE TITLE --> <!-- The title of the article in the language in which the article was originally published Remarks: The related element Translated Title <trans-title> should be used for a translation of the article into another language, for example, to hold the English version of a Japanese article title. --> <!ELEMENT article-title (#PCDATA %title-elements;)* > <!-- xml:lang The language in which the value of the element is expressed. Recommended best practice is to use values as defined in RFC 1766, typically 2-letter language codes such as "FR" (French), "EN" (English), and "DE" (German). These values are NOT case sensitive, so "EN" = "en". The values may include hyphenated differentiators such as "EN-AU" (Australian English) and "EN-US" (United States English). --> <!ATTLIST article-title xml:lang NMTOKEN #IMPLIED > <!-- AFFILIATION ELEMENTS --> <!-- Elements for use in the <aff> element --> <!ENTITY % aff-elements "| %address-elements; | %break.class; | %emphasis.class; | %label.class; | %link.class; | %subsup.class;" > <!-- AFFILIATION --> <!-- Name of a institution or organization such as a university or corporation. Authoring and Conversion Note: In a typical case, the "id" attribute will be pointed to by one or more contributors. Conversion Note: Any explicitly tagged numbers or symbols for author linkages should be discarded, as the linkage will be recreated from the "id" connection. Authoring Note: While this element contains an optional Label element, the Label element should be included only in those circumstances where a formatting override is needed; Label should NOT be used in the ordinary course of tagging. --> <!ELEMENT aff (#PCDATA %aff-elements;)* > <!-- id Unique identifier so that the affiliated institution may be referenced, for example by a contributor rid May be used to point to affiliation-related information within the document --> <!ATTLIST aff %aff-atts; > <!-- COLLABORATIVE (GROUP) AUTHOR ELEMENTS --> <!-- Elements for use in the <collab> element --> <!ENTITY % collab-elements " | %ext-links.class; | %simple-link.class; | %simple-text;" > <!-- COLLABORATIVE (GROUP) AUTHOR --> <!-- Used for groups of authors credited under one name, either as a collaboration in the strictest sense, or when an organization, institution, or corporation is the group. Remarks: When an author is an organization rather than a person, use the <collab> element rather than <surname>, for example: <collab>Aardvark Institute</collab> --> <!ELEMENT collab (#PCDATA %collab-elements;)* > <!-- collab-type The type or role of the collaborators, what function did they play in the publication. Suggested values include: assignee - Group or company to whom a patent is awarded authors - Content creators editors - Content editors compliers - Put together a composite work from multiple sources guest-editors - A group of editors that have been invited to edit all or part of a work inventors - Idea, software, or machine creators translators - Translated the cited work from one language into another one language into another id unique identifier so that the collaboration can be referenced xlink:href Provides an address or identifier of the object to which the link points, for example a URI or a filename. --> <!ATTLIST collab %collab-atts; > <!-- CONFERENCE DATE --> <!-- The date(s) on which the conference was held. Conference dates in journal headers are traditionally stored in one of two forms: as a single date ("May 1906") or as the first day and last day of the conference. Both types should be stored in this element; the dates that come from separate first and last elements should be combined: <conf-start>August 4, 2002</conf-start> <conf-end>August 9, 2002<conf-end> should become: <conf-date>August 4, 2002 - August 9, 2002</conf-date> --> <!ELEMENT conf-date (#PCDATA) > <!-- CONFERENCE LOCATION ELEMENTS --> <!-- Elements for use in the <conf-loc> element --> <!ENTITY % conf-loc-elements "| %simple-text;" > <!-- CONFERENCE LOCATION --> <!-- The physical location(s) of the conference. This may include a city, a country, or a campus or organization location if that is the only location available. Authoring and Conversion Note: If the conference is in the United States, the state should also be provided. A specific venue or address (e.g. conference hotel) should not be provided unless there is no other location information. --> <!ELEMENT conf-loc (#PCDATA %conf-loc-elements;)* > <!-- CONFERENCE NAME ELEMENTS --> <!-- Elements for use in the <conf-name> element--> <!ENTITY % conf-name-elements "| %simple-text;" > <!-- CONFERENCE NAME --> <!-- The full name of the conference, including any qualifiers such as "43rd Annual". When the name includes the year of the conference, (e.g. "Extreme 2002"), the year should appear in both the conference Name and the Conference Date elements. --> <!ELEMENT conf-name (#PCDATA %conf-name-elements;)* > <!-- COPYRIGHT STATEMENT MODEL --> <!-- Content model for <copyright-statement> --> <!ENTITY % copyright-statement-model "(#PCDATA | %ext-links.class; %rendition-plus;)*" > <!-- COPYRIGHT STATEMENT --> <!-- Copyright notice or statement, suitable for printing or display. Within the statement the copyright year should be identified, if expected to be displayed. --> <!ELEMENT copyright-statement %copyright-statement-model; > <!-- ISSN --> <!-- International Standard Series Number --> <!ELEMENT issn (#PCDATA) > <!-- Used to record the type of publication, for which this ISSN was issued, for example, a print-only publication versus an electronic-only publication, in any of several life stages. Suggested values include: epub - Electronic publication ppub - Print publication epub-ppub - Published in both print and electronic form epreprint - Electronic preprint dissemination ppreprint - Print preprint dissemination ecorrected - Corrected in electronic pcorrected - Corrected in print eretracted - Retracted in electronic pretracted - Retracted in print --> <!ATTLIST issn %issn-atts; > <!-- ISSUE --> <!-- The issue number, issue name, or other identifier of an issue of a journal --> <!ELEMENT issue (#PCDATA %just-rendition;)* > <!-- ============================================================= --> <!-- COMMON METADATA ELEMENTS CONTINUED --> <!-- PUBLISHER IDENTIFICATION ELEMENTS --> <!-- (COMMON ARTICLE METADATA/BIBLIOGRAPHIC) --> <!-- Used in article metadata and also inside --> <!-- a bibliographic reference (citation) --> <!-- ============================================================= --> <!-- ET AL CONTENT MODEL --> <!-- The content model for the <etal> element --> <!ENTITY % etal-model "(#PCDATA %just-rendition;)*" > <!-- ET AL --> <!-- Although most journals modeled this as an EMPTY element, typically used to generate the text "et al." in a stylesheet, some journal DTDs (Blackwell's, for example) expect content for this element, with such text as "Associates, coworkers, and colleagues". --> <!ELEMENT etal %etal-model; > <!-- PUBLISHER'S NAME --> <!-- Name of the publisher of the work --> <!ELEMENT publisher-name (#PCDATA %just-rendition;)* > <!-- PUBLISHER'S LOCATION ELEMENTS --> <!-- Elements for use in the Publisher Location <publisher-loc> element --> <!ENTITY % publisher-loc-elements "| %address-elements; | %emphasis.class; | %subsup.class;" > <!-- PUBLISHER'S LOCATION --> <!-- Place of publication, usually a city such as New York or London --> <!ELEMENT publisher-loc (#PCDATA %publisher-loc-elements;)* > <!-- ============================================================= --> <!-- COMMON METADATA ELEMENTS CONTINUED --> <!-- ============================================================= --> <!-- TRANSLATED TITLE --> <!-- An alternate version of the title that has been translated into a language other than that of the article title <article-title> Remarks: The related element Article Title <atitle-title> should be used for the title of the article in the original language in which it was published, this element used for a translation of that title, for example the English version of a Japanese article. --> <!ELEMENT trans-title (#PCDATA %title-elements;)* > <!-- xml:lang The language in which the value of the element is expressed. Recommended best practice is to use values as defined in RFC 1766, typically 2-letter language codes such as "FR" (French), "EN" (English), and "DE" (German). These values are NOT case sensitive, so "EN" = "en". The values may include hyphenated differentiators such as "EN-AU" (Australian English) and "EN-US" (United States English). Authoring and Conversion Note: For the Translated Title element, the xml:lang attribute should always be set if the value is known. The only reason the attribute was not made #REQUIRED was that there may be cases where the language is not known. --> <!ATTLIST trans-title xml:lang NMTOKEN #IMPLIED > <!-- VOLUME --> <!ELEMENT volume (#PCDATA %just-rendition;)* > <!-- ============================================================= --> <!-- COMMON METADATA ELEMENTS CONTINUED --> <!-- PAGE NUMBERING ELEMENTS --> <!-- ============================================================= --> <!-- FIRST PAGE --> <!-- The page number on which the article starts, for print journals that have page numbers --> <!ELEMENT fpage (#PCDATA) > <!-- seq Used for sequence number or letter for journals (such as continuous makeup journals) with more than one article starting on the same page --> <!ATTLIST fpage seq CDATA #IMPLIED > <!-- LAST PAGE --> <!-- The page number on which the article ends, for print journals that have page numbers --> <!ELEMENT lpage (#PCDATA) > <!-- ELECTRONIC LOCATION IDENTIFIER --> <!-- Used to identify an article that does not have traditional page numbers. For a printed article, when citations are sent through the Medline matcher to be turned into live links or when the metadata about an article is collected for complete identification, the first page number (and sometimes also the last page number) of the article is recorded to help indicate which article is being referenced. Electronic only journals have no page numbers, so this element is used as the equivalent identifier, the "electronic page number" that helps to identify the article. The value could be an article identifier, a doi, etc., for example, "E70". Remarks: This element is more accurately an electronic identifier, and it was considered renaming this element to that. The purpose of the name is to be a parallel with the <fpage>...<lpage> model. When neither first page or last page is appropriate, because the electronic journal has no pages, the <elocation-id> element is used instead. --> <!ELEMENT elocation-id (#PCDATA) > <!-- ============================================================= --> <!-- CITATION (BIBLIOGRAPHIC REFERENCE) --> <!-- ============================================================= --> <!-- CITATION MODEL --> <!-- Content model for the <citation> element. --> <!ENTITY % citation-model "(#PCDATA | %ext-links.class; | %label.class; | %references.class; | %simple-text;)*" > <!-- CITATION --> <!-- A citation is a description of a work, such as a journal article, book, or personal communication, that is cited in the text of the article. Although the DTD does not enforce it, a citation to a journal article *should* be tagged with as many as possible of the following, so that PubMed Central or other matching processing can make the citation into a live link: source The MEDLINE abbreviation of the journal name article-title Title of the article volume Volume of the journal issue Issue of the journal fpage Page number on which the article starts name Of an author or editor year Year of publication month Month of publication (if present) day Date of publication (if present) The other elements may be tagged if desired. The <title> element may be used for titles of books, conference proceedings, etc. Authoring and Conversion Note: In order to make citations into live links, as much of the author and date information as is available should be preserved. The most important date tag is year, and it should always be tagged if possible: <year>2003</year> The <day> and <month> tags will be used more rarely; they are provided because some of the citation matching services can use the month and the day if they are available. --> <!ELEMENT citation %citation-model; > <!-- citation-type Defines the type of work being referenced. Suggested values include: book Book personal-communication Informal or personal communication, such as a phone call or an email message conf-proceedings Conference proceedings discussion Dicussion among a group in some forum - public, private, or electronic, which may or may not be moderated gov Government publication journal Journal article list Listserv other None of the listed types patent Patent or patent application thesis Work written as part of the completion of an advanced degree web Website id Unique identifier so the element may be referenced xlink:href Provides an address or identifier of the object to which the link points, for example a URI or a filename --> <!ATTLIST citation %citation-atts; > <!-- ============================================================= --> <!-- ADDRESS ELEMENTS (BIBLIOGRAPHIC) --> <!-- ============================================================= --> <!-- ADDRESS MODEL --> <!-- Content model for the <address> element --> <!ENTITY % address-model "(%address-elements;)*" > <!-- ADDRESS/CONTACT INFORMATION --> <!-- Wrapper element for contact information such as address, phone, fax, email, url, country, etc. --> <!ELEMENT address (%address-model;) > <!-- id Unique identifier so the element may be referenced --> <!ATTLIST address id ID #IMPLIED > <!-- ADDRESS LINE ELEMENTS --> <!-- Elements for use in the <addr-line> element --> <!ENTITY % addr-line-elements "| %simple-text;" > <!-- ADDRESS LINE --> <!-- One line in an address --> <!-- Conversion Note: If the address is undifferentiated data characters, the entire address may be inside one of these elements. --> <!ELEMENT addr-line (#PCDATA %addr-line-elements;)* > <!-- COUNTRY: IN AN ADDRESS --> <!ELEMENT country (#PCDATA) > <!-- EMAIL ADDRESS --> <!ELEMENT email (#PCDATA) > <!-- xlink:href Provides an address or identifier of the object to which the link points, for example a URI or a filename --> <!ATTLIST email %might-link-atts; > <!-- FAX NUMBER: IN AN ADDRESS --> <!ELEMENT fax (#PCDATA %just-rendition;)* > <!-- INSTITUTION NAME ELEMENTS --> <!-- Elements for use in the <institution> element --> <!ENTITY % institution-elements "| %break.class; | %emphasis.class; | %subsup.class;" > <!-- INSTITUTION NAME: IN AN ADDRESS --> <!-- Name of a institution or organization such as a university or corporation --> <!ELEMENT institution (#PCDATA %institution-elements;)* > <!-- id Unique identifier so the element may be referenced xlink:href Provides an address or identifier of the object to which the link points, for example a URI or a filename --> <!ATTLIST institution id ID #IMPLIED %might-link-atts; > <!-- PHONE NUMBER: IN AN ADDRESS --> <!ELEMENT phone (#PCDATA %just-rendition;)* > <!-- URI --> <!-- URI such as a URL that may be used as a live link, typically naming a website, such as: <url>http://www.mulberrytech.com</url> Alternatively the element content may name the URL, e.g., "Mulberry's Website" and the "xlink:href" attribute may hold the real URL. <url xlink:href="https://www.mulberrytech. com">Mulberry's Website</url> Related Elements: A URI used outside the context of an address of contributor should be tagged as an External Link <ext-link> --> <!ELEMENT uri (#PCDATA %just-rendition;)* > <!ATTLIST uri %might-link-atts; > <!-- ============================================================= --> <!-- DATE ELEMENTS (PUBLICATION HISTORY) --> <!-- ============================================================= --> <!-- DATE --> <!-- The elements <day>, <month>, and <year> should ALWAYS be numeric values. The date may be represented as a string in <string-date>, but the numeric values should be present whenever possible. --> <!ELEMENT date (%date-model;) > <!-- date-type Attribute should only be used if the date is one of the known types, otherwise omit the attribute. Values are: accepted - Date manuscript was accepted received - Date manuscript received rev-request - Date revisions were requested or manuscript was returned rev-recd - Date revised manuscript was received --> <!ATTLIST date date-type (%date-types;) #IMPLIED > <!-- DAY --> <!-- The numeric value of a day of the month, used in both article metadata and inside a citation, in two digits as it would be stated in the "DD" in an international date format YYYY-MM-DD, for example "03", "25". --> <!ELEMENT day (#PCDATA) > <!-- MONTH --> <!-- Names one of the months of the year. Used in both article metadata and inside a citation, this element may contain a full month "December", an abbreviation "Dec", or, preferably, a numeric month such as "12". Authoring and Conversion Note: For ease in comparisons and searching, many archives prefer that months be converted to numeric Suggested values: 1 = January 2 = February 3 = March, etc. --> <!ELEMENT month (#PCDATA) > <!-- SEASON --> <!-- Season of publication, such as "Spring". Used in both article metadata and inside a citation --> <!ELEMENT season (#PCDATA) > <!-- YEAR --> <!-- Year of publication, which should be expressed as a 4-digit number: "1776" or "1924" --> <!ELEMENT year (#PCDATA) > <!-- DATE AS A STRING --> <!-- This is a representation of the date as a string. Usually used for dates for which months and years are not given, but may be used for any date as a string(i.e. "January, 2001" "Fall 2001" "March 11, 2001". It is better practice to tag the year and month as numbers with a date such as "January, 2001" or "March 11, 2001". --> <!ELEMENT string-date (#PCDATA) > <!-- ============================================================= --> <!-- PERSON'S NAME ELEMENTS (BIBLIOGRAPHIC) --> <!-- ============================================================= --> <!-- NAME OF PERSON --> <!-- Wrapper element for personal names. Authoring or Conversion Note: If the name parts are unknown or untagged, names should be placed within the Surname element <surname>. Design Note: The tag abuse of overloading the Surname tag is likely to lead to better searching in a repository than merely leaving the person's name untagged. --> <!ELEMENT name (surname, given-names?, prefix?, suffix?) > <!-- name-style Used for choosing an inversion algorithm or for sorting or other processing functions. The three values and approximate meanings are: Value Display Sort/Inversion western given family family given eastern family given family given islensk given patronymic given, patronymic --> <!ATTLIST name name-style (western | eastern | islensk) "western" > <!-- SURNAME --> <!-- The surname of an individual. If there is only one name, for example, "Cher" or "Pele", that is considered to be a surname for consistency purposes. --> <!ELEMENT surname (#PCDATA %just-rendition;)* > <!-- GIVEN (FIRST) NAMES --> <!-- Includes all given names for a person, such as the first name, middle names, maiden name if used as part of the married name, etc.) --> <!ELEMENT given-names (#PCDATA %just-rendition;)* > <!-- PREFIX --> <!-- Honorifics or other qualifiers that usually precede the surname, for example, Professor, Rev., President, Senator, Dr., Sir, The Honorable, et al. --> <!ELEMENT prefix (#PCDATA %just-rendition;)* > <!-- SUFFIX --> <!-- Text used as a suffix to a person's name, for example: Sr. Jr. III, 3rd --> <!ELEMENT suffix (#PCDATA %just-rendition;)* > <!-- ============================================================= --> <!-- EXTERNAL LINK ELEMENTS --> <!-- ============================================================= --> <!-- EXTERNAL LINK --> <!-- Link to an external file, such as Medline, Genbank, etc. Linking may be accomplished using the XLink linking attributes. --> <!ELEMENT ext-link (#PCDATA %link-elements;)* > <!-- ext-link-type Type of external link. Use this attribute if the type of external link is one of the ones below or another named type. Suggested values include: ec Enzyme nomenclature - see http://www.chem.qmw.ac.uk/iubmb/enzyme/ gen GenBank identifier genpept Translated Protein-encoding sequence Database highwire HighWire press intrajournal medline Medline or pubmed id pdb Protein data bank. See http://www.rcsb.org/pdb/ pgr Plant gene register. See http://www.tarweed.com/pgr/ pir Protein Information Resource see http://pir.georgetown.edu pirdb Protein Information Resource see http://pir.georgetown.edu pmc Used to link between articles in PubMedCentral access is PMID sprot Swiss-Prot. See http://www.ebi.ac.uk/swissprot/ aoi Astronomical Object Identifier doi Digital Object Identifier ftp File transfer protocol uri Website or web service id Unique identifier so the element may be referenced xlink:href Provides an address or identifier of the object to which the link points, for example a URI or a filename --> <!ATTLIST ext-link %ext-link-atts; > <!-- ============================================================= --> <!-- STRUCTURAL ELEMENTS --> <!-- ============================================================= --> <!-- TITLE ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of the <title> element --> <!ENTITY % struct-title-elements "| %break.class; | %simple-phrase;" > <!-- TITLE --> <!-- Heading or title for a structural element such as a Section, Figure, Boxed Text, etc.--> <!ELEMENT title (#PCDATA %struct-title-elements;)* > <!-- LABEL OF A FIGURE, REFERENCE, ETC. --> <!-- The number and any prefix word that comes before, for example, the caption of a Figure, such as "Figure 3." or "Exhibit 2.". This element can be used to preserve the prefix number or label of an element, for example for a reference or citation "25." or "[Lapeyre 2002]". This can be useful when reconstructing untagged cross references. --> <!ELEMENT label (#PCDATA | %emphasis.class; | %inline-display.class; | %subsup.class;)* > <!-- ============================================================= --> <!-- RELATED ARTICLE ELEMENTS --> <!-- ============================================================= --> <!-- RELATED ARTICLE INFORMATION MODEL --> <!-- Content model for the <related-article> element --> <!ENTITY % related-article-model "%emphasis.class; | %ext-links.class; | %references.class; | %subsup.class;" > <!-- RELATED ARTICLE INFORMATION --> <!-- Wrapper element, used as a container for text links to a related article, possibly accompanied by a very brief description such as "errata (correction)". Remarks: This element is slightly overloaded in that it has 2 uses, one inside the article metadata to name one or more related articles and as part of the link class, which can occur many places in textual content. This allows all such references, to companion articles within the same journal, to a previous part of a multi-part article, to a news item that summarizes the article, to the article for which this article is a correction or addendum, etc. wherever these occur in the article. --> <!ELEMENT related-article (#PCDATA | %related-article-model;)* > <!-- related-article-type addendum Additional material for an article, generated too late to be added to the main text commentary-article Used in an commentary or editorial to link to the article on which it is commenting companion Used in an article to link to a companion (related or sibling article) corrected-article Used in a correction to link to the article being corrected. Sometimes called erratum. in-this-issue Related article in the same journal issue letter A letter to the publication or a reply to such a letter commentary Used in an article to link to its associated commentary or editorial correction-forward Used in an article to link forward to its associated correction (rarely used) retracted-article Used in a retraction to link to the article being retracted retraction-forward Used in an article to link forward to its associated retraction (rare) vol Volume of the journal in which the related article exists. The scope is limited to the journal; in which the current article resides. page Page number of the related article. Scope is limited to the volume of the journal in which the current article resides. The values should be a first page or a page range. xlink:href Provides an address or identifier of the object to which the link points, for example a URI or a filename. --> <!ATTLIST related-article %related-article-atts; > <!-- ============================================================= --> <!-- FRONT MATTER/BACK MATTER ELEMENTS --> <!-- ============================================================= --> <!-- ACKNOWLEDGMENTS MODEL --> <!-- Content model for the <ack> element --> <!ENTITY % ack-model "%sec-opt-title-model;" > <!-- ACKNOWLEDGMENTS --> <!ELEMENT ack (%ack-model;) > <!-- id Unique identifier so the element may be referenced content-type Identification of the subject, type of content, or reason that this word or phrase is considered semantically special, as a means of preserving the semantic intent of the original tagging. --> <!ATTLIST ack id ID #IMPLIED content-type CDATA #IMPLIED > <!-- BIOGRAPHY --> <!-- Sort biography of a person, usually the author Authoring Note: The "xlink:href" attribute may be used to point to a graphic of the author or to his/her website, etc. --> <!ELEMENT bio (title?, p+) > <!-- id Unique identifier so the element may be referenced rid Points to the identifier of an author or or authors xlink:href Provides an address or identifier of the object to which the link points, for example a URI or a filename. --> <!ATTLIST bio %bio-atts; > <!-- NOTES MODEL --> <!-- Content model for the <notes> element --> <!ENTITY % notes-model "%sec-opt-title-model;" > <!-- NOTES --> <!-- A container element for the notes that may appear at the end of an Article or at the end of a Table. For example, a typical end-of-article note is a "Note in Proof". A Note in Proof contains late-breaking news items or other material produced while the article was being typeset or was otherwise in production, that therefore happened too late to be included in the text of the article. This is typically NOT peer-reviewed content and citations to other material is usually just integrated into the text, not listed separately in a References List. --> <!ELEMENT notes (%notes-model;) > <!-- id Unique identifier so the element may be referenced notes-type To identify the type of note, if the type can be/has been identified, for example, "note-in-proof" --> <!ATTLIST notes %notes-atts; > <!-- ============================================================= --> <!-- ACCESSIBILITY ELEMENTS --> <!-- ============================================================= --> <!-- ALTERNATE TITLE TEXT FOR A FIGURE, ETC. --> <!-- Short phrase used to display or pronounce as an alternative to providing the full graphic for accessibility display or graphic-limited websites or devices. For example, <alt-text> may be used to display "behind" a figure or graphic. Authoring and Conversion Note: Not to be used as a replacement for <caption>. --> <!ELEMENT alt-text (#PCDATA) > <!-- id Unique identifier so the element may be referenced xml:lang The language in which the value of the element is expressed. Recommended best practice is to use values as defined in RFC 1766, typically 2-letter language codes such as "FR" (French), "EN" (English), and "DE" (German). These values are NOT case sensitive, so "EN" = "en". The values may include hyphenated differentiators such as "EN-AU" (Australian English) and "EN-US" (United States English). --> <!ATTLIST alt-text id ID #IMPLIED xml:lang NMTOKEN #IMPLIED > <!-- LONG DESCRIPTION --> <!-- Description or summary of the content of a graphical object, table, or textual object such as a text box, used by some systems to make the object accessible, even to people or systems that cannot read/see/display the object. Authoring and Conversion Note: Not to be used as a replacement for <caption>. --> <!ELEMENT long-desc (#PCDATA) > <!-- id Unique identifier so the element may be referenced xml:lang The language in which the value of the element is expressed. Recommended best practice is to use values as defined in RFC 1766, typically 2-letter language codes such as "FR" (French), "EN" (English), and "DE" (German). These values are NOT case sensitive, so "EN" = "en". The values may include hyphenated differentiators such as "EN-AU" (Australian English) and "EN-US" (United States English). --> <!ATTLIST long-desc id ID #IMPLIED xml:lang NMTOKEN #IMPLIED > <!-- DEFINITION LIST: DEFINITION --> <!-- Used in two senses: 1) The definition, description, or other explanation of the word, phrase, or picture of a 2-part or definition list 2) The definition or expansion of an abbreviation or acronym <abbrev> --> <!ELEMENT def (p+) > <!-- id Unique identifier so the element may be referenced rid Points to the identifier of a term, so that a term and definition may be linked --> <!ATTLIST def rid IDREFS #IMPLIED id ID #IMPLIED > <!-- ================== End Common (Shared) Elements Module ====== -->