NCBI Bookshelf Tagging Guidelines [books]

Document Objects

These Document Objects refer to parts of the document (author/affiliation relationships, copyright information) and often include several XML elements in their tagging.

Index of objects

Abstracts

Chapters may contain multiple abstracts. The maximum length of any single <abstract> should not exceed 9900 characters.

Translated Abstracts Tag abstracts in any language other than the primary language of the book or chapter in <trans-abstract>. Specify the language in @xml:lang using two-letter, lowercase language codes as described in IETF RFC 5646. Values may be obtained from the IANA Language Subtag Registry: http://www.iana.org/assignments/language-subtag-registry.

Structured Abstracts Abstracts with multiple sections, that include titles or labels, should be tagged using <sec> and <title>, or <label>. Sections of an abstract should not be tagged within a style emphasis, such as <bold> or <italic>, separate from the <p>, using a colon.

Graphical Abstracts Use @abstract-type="graphical" and include the <graphic>(s) with @position="anchor".

Plain Language Summary A summary of the article intended for a layperson. Use @abstract-type="plain-language-summary".

PubMed excerpts Book or chapter records may be submitted to PubMed and the citation in PubMed may include an excerpt.

If a book or book-part includes a single <abstract>, then that abstract will be submitted to PubMed as the excerpt.

If book or book-part includes several <abstract>s, then indicate the excerpt by specifying @specific-use="pubmed-excerpt".

For book-parts, it is possible to mark up one or several sections or paragraphs in the body as excerpts. Use also @specific-use="pubmed-excerpt".

One of several abstracts tagged as the PubMed excerpt

<abstract specific-use="pubmed-excerpt">
  <p>This summary is for you if your health care professional has said you have 
   (or your child has) type 1 diabetes. This summary will tell you what researchers 
   have found about behavioral programs to help manage type 1 diabetes. It does not 
   cover specific treatments for diabetes.</p>
</abstract>

A section tagged as the PubMed excerpt

<sec specific-use="pubmed-excerpt">
  <title>Introduction</title>
  <p>This summary is for you if your health care professional has said you have 
   (or your child has) type 1 diabetes. This summary will tell you what researchers 
   have found about behavioral programs to help manage type 1 diabetes. It does not 
   cover specific treatments for diabetes.</p>
</sec>

A paragraph tagged as the PubMed excerpt

<p specific-use="pubmed-excerpt">This summary is for you if your health care 
 professional has said you have (or your child has) type 1 diabetes. This summary 
 will tell you what researchers have found about behavioral programs to help 
 manage type 1 diabetes. It does not cover specific treatments for diabetes.</p>

Affiliations

Tag affiliation information in the <contrib> or <contrib-group> containing the relevant <contrib>. See the related element <contrib-group> for more details. See also Author/Affiliation Relationship for examples.

See Alternate Versions of a Single Object for tagging alternate versions of affiliations.

Alternate Versions of a Single Object

Accessibility: do not use <alternatives> as a way to avoid providing an accessible version of an object. This guidance supports the JATS4R Accessibility Recommendation for alternatives.

Where multiple formats (gif image, text, jpg image) of a single object (figure, table) are available, tag all formats within the <alternatives> tag.

See the related element <alternatives> for more information.

A figure containing a movie and a still image from the movie:

<fig id="F1">
  <caption><label>Figure 1</label></caption>
  <alternatives>
    <media xlink:href="fig1.mov"/>
    <graphic xlink:href="fig1.jpg"/>
  </alternatives>
</fig>

An equation provided as <mml:math>, <tex-math>, and an image:

<disp-formula id="FD1">
  <label>Equation 1</label>
  <alternatives>
    <mml:math id="Eq0001-mml">
      <mml:mi>E</mml:mi>
      <mml:mo>=</mml:mo>
      <mml:mover>
        <mml:mrow>
          <mml:mi>m</mml:mi>
          <mml:mi>c</mml:mi>
        </mml:mrow>
        <mml:mn>2</mml:mn>
      </mml:mover>
    </mml:math>
    <tex-math>
     \documentclass[10pt]{article}
     \usepackage{wasysym}
     \usepackage[substack]{amsmath}
     \usepackage{amsfonts}
     \usepackage{amssymb}
     \usepackage{amsbsy}
     \usepackage[mathscr]{eucal}
     \usepackage{mathrsfs}
     \usepackage{pmc}
     \usepackage[Euler]{upgreek}
     \pagestyle{empty}
     \oddsidemargin -1.0in
     \begin{document}
     \[
     E = mc^{2}
     \]
     \end{document}
    </tex-math>
    <graphic xlink:href="biotes-01-100-e001.tif"/>
  </alternatives>
</disp-formula>

Affiliation Alternatives

To capture a single affiliation in multiple languages or for different uses, use <aff-alternatives>. If the affiliations are being used for different purposes (print vs. online display), all <aff> elements must specify @specific-use. Likewise, if <aff-alternatives> is being used to capture the affiliation in multiple languages, all <aff> elements but one must include @xml:lang. At least one <aff> must be the same language as the <book>, which can either be explicitly tagged or inherited from the <book>.

In this example, the <book> does not include an explicit @xml:lang, so the default value "en", as declared in the DTD, applies.

<book>
...
  <aff-alternatives>
    <aff>Department of Emergency Health Services, Graduate School, 
     University of Maryland, Baltimore County, USA.</aff>
    <aff xml:lang="es">Departamento de Servicios de Salud de Emergencia, 
     Escuela de Posgrado, Universidad de Maryland, Condado de Baltimore, USA.</aff>

Citation Alternatives

Multiple versions of a single citation may be captured using <citation-alternatives>. Examples include the same citation tagged as an <element-citation> for indexing purposes and <mixed-citation> to preserve the display or a single citation tagged in multiple languages.

If the same child element is used (<element-citation>, <mixed-citation>), they must specify either @specific-use or @xml:lang to indicate why alternatives are included.

This must not be confused with a single <ref> that contains multiple citations, which is covered under References.

<citation-alternatives> with one <element-citation> and one <mixed-citation>. No @specific-use or @xml:lang required.

<citation-alternatives>
  <element-citation publication-type="journal" publication-format="print">
    <name><surname>Petitti</surname><given-names>DB</given-names></name>
    <name><surname>Crooks</surname><given-names>VC</given-names></name>
    <name><surname>Buckwalter</surname><given-names>JG</given-names></name>
    <name><surname>Chiu</surname><given-names>V</given-names></name>
    <article-title>Blood pressure levels before dementia</article-title>
    <source>Arch Neurol</source><year>2005</year><month>Jan</month>
    <volume>62</volume><issue>1</issue><fpage>112</fpage>
    <lpage>116</lpage>
  </element-citation>
  <mixed-citation publication-type="journal" publication-format="print">
    <name><surname>Petitti</surname><given-names>DB</given-names></name>, 
    <name><surname>Crooks</surname><given-names>VC</given-names></name>,
    <name><surname>Buckwalter</surname><given-names>JG</given-names></name>,
    <name><surname>Chiu</surname><given-names>V</given-names></name>.
    <article-title>Blood pressure levels before dementia</article-title>.
    <source>Arch Neurol</source>. <year>2005</year> <month>Jan</month>;
    <volume>62</volume>(<issue>1</issue>):
    <fpage>112</fpage>-<lpage>116</lpage>.
  </mixed-citation>
</citation-alternatives>

<citation-alternatives> with two <mixed-citation> elements, differentiated with @xml:lang.

<citation-alternatives>
  <mixed-citation publication-type="journal" publication-format="print" xml:lang="ja"> 
    <person-group person-group-type="author">
    <name name-style="eastern">
      <surname>柿崎</surname> 
      <given-names>一郎</given-names>
    </name></person-group>. <year>2000</year>. 
    <source>タイ経済と鉄道1835 年～1935 年</source>
    <publisher-name>日本経済評論社</publisher-name> 
  </mixed-citation>
  <mixed-citation publication-type="journal" publication-format="print" xml:lang="en">
    <person-group person-group-type="author">
      <name name-style="western">
        <surname>Kakizaki</surname>, <given-names>Ichiro</given-names>
      </name></person-group>. <year>2000</year>. 
    <source>Thai Economy and Railway 1885-1935</source>. 
    <publisher-loc>Tokyo</publisher-loc>: <publisher-name>Nihon Keizai 
     Hyoronsha</publisher-name>  (in Japanese)</mixed-citation>
</citation-alternatives>

Author Name Alternatives

Names of both individual and collaborative authors may be tagged with alternatives to capture the name for different purposes or in different languages. Use <name-alternatives> for individual contributors and <collab-alternatives> for collaborative authors. Except in the case of Indexed Name, the distinction between alternate versions must be specified with either @specific-use or @xml:lang.

Audio and Video

Accessibility: include a description or transcript for any audio or video content included in an article, following the JATS4R Accessibility Recommendations.

Descriptions: a description is a detailed summary of a recording. Use <long-desc> to capture a description.

Transcripts: a transcript is text that conveys spoken audio verbatim and includes descriptions of sounds or actions in the recording.

Capture any transcripts directly in the book part XML in which the audio or video belongs. Do not remove transcripts to a separate document.
Use one of the following methods to capture a transcript in the same book part XML that contains the recording:
- <sec sec-type="transcript"> in <back>, or
- in an appendix: <app content-type="transcript">
For tagging examples, refer to Example 5 in the JATS4R Accessibility Recommendation.

Author Contributions

Use the <role> element to tag author contributions.

CRediTWhen tagging contributions, use the NISO CRediT (https://credit.niso.org/) and JATS4R guidance (https://jats4r.org/credit-taxonomy). Do not use the former CASRAI taxonomy (https://casrai.org/credit/).

See <role> for tagging examples.

Term	URI
Conceptualization	https://credit.niso.org/contributor-roles/conceptualization/
Data curation	https://credit.niso.org/contributor-roles/data-curation/
Formal analysis	https://credit.niso.org/contributor-roles/formal-analysis/
Funding acquisition	https://credit.niso.org/contributor-roles/funding-acquisition/
Investigation	https://credit.niso.org/contributor-roles/investigation/
Methodology	https://credit.niso.org/contributor-roles/methodology/
Project administration	https://credit.niso.org/contributor-roles/project-administration/
Resources	https://credit.niso.org/contributor-roles/resources/
Software	https://credit.niso.org/contributor-roles/software/
Supervision	https://credit.niso.org/contributor-roles/supervision/
Validation	https://credit.niso.org/contributor-roles/validation/
Visualization	https://credit.niso.org/contributor-roles/visualization/
Writing – original draft	https://credit.niso.org/contributor-roles/writing-original-draft/
Writing – review & editing	https://credit.niso.org/contributor-roles/writing-review-editing/

Author Names

Tag each author name and their associated information in <contrib>.

Set the following attributes on <contrib> for these situations.

Situation	attribute
corresponding author	@corresp="yes"
author is deceased	@deceased="yes"
author contributed equally	@equal-contrib="yes"

For example, if an author is a "Corresponding Author", you can use @corresp="yes". If, however, there is more information than can be represented with a simple yes/no, do not use the attribute and instead tag the information in <fn> in <author-notes>.

The first two authors contributed equally and the information is presented as a simple yes/no.

<contrib contrib-type="author" equal-contrib="yes">
  <name>
    <surname>Yuan</surname>
    <given-names>Shuofeng</given-names>
  </name>
</contrib>
<contrib contrib-type="author" equal-contrib="yes">
  <name>
    <surname>Gao</surname>
    <given-names>Xiaopan</given-names>
  </name>
</contrib>
<contrib contrib-type="author">
  <name>
    <surname>Tang</surname>
    <given-names>Kaiming</given-names>
  </name>
</contrib>

The first, second, third, and tenth authors contributed equally and the information is presented in a footnote.

<contrib contrib-type="author">
  <name>
    <surname>Nozaki</surname>
    <given-names>Miho</given-names>
  </name>
  <xref rid="fn1" ref-type="author-notes"><sup>&#x02020;</sup></xref>
</contrib>
<contrib contrib-type="author">
  <name>
    <surname>Raisler</surname>
    <given-names>Brian J.</given-names>
  </name>
  <xref rid="fn1" ref-type="author-notes"><sup>&#x02020;</sup></xref>
</contrib>
<contrib contrib-type="author">
  <name>
    <surname>Sakurai</surname>
    <given-names>Eiji</given-names>
  </name>
  <xref rid="fn1" ref-type="author-notes"><sup>&#x02020;</sup></xref>
</contrib>
<contrib contrib-type="author"> ... </contrib>
<contrib contrib-type="author"> ... </contrib>
<contrib contrib-type="author"> ... </contrib>
<contrib contrib-type="author"> ... </contrib>
<contrib contrib-type="author"> ... </contrib>
<contrib contrib-type="author"> ... </contrib>
<contrib contrib-type="author">
  <name>
    <surname>Baffi</surname>
    <given-names>Judit Z.</given-names>
  </name>
  <xref rid="fn1" ref-type="author-notes"><sup>&#x02020;</sup></xref>
</contrib>
...
<author-notes>
  <fn id="fn1" fn-type="equal">
    <p><sup>&#x02020;</sup>M.N., B.J.R., E.S., and J.Z.B. contributed equally to this work.</p>
  </fn>
</author-notes>

Author Notes

This includes all information related to authors that cannot be expressed with the <contrib> attributes (@corresp, @equal-contrib, etc.).

Information that applies to the entire document must be tagged in <fn-group> in <back>, not in <author-notes>.

See element <author-notes>.

Author Pronouns

Tag an author's pronouns using an <author-comment> with @content-type="pronouns". Include all punctuation, like parentheses.

<author-comment content-type="pronouns">
  <p>(ze/zir/zirs)</p>
</author-comment>

Author/Affiliation Relationship

All author/affiliations should be tagged in the same style within a given book.

A. If there is an address or affiliation supplied for each <contrib>, include the <aff> in the tagging for the <contrib>.

Lorraine Tanabe^§

National Center for Biotechnology Information, National Library of Medicine, NIH, 8600 Rockville Pike, Bethesda, MD, USA

Lynne H. Thom

Consolidated Safety Services, 10335 Democracy Lane, Suite 202, Fairfax, VA, USA

^§Corresponding author

<contrib-group>
  <contrib contrib-type="author" corresp="yes">
    <name>
      <surname>Tanabe</surname>
      <given-names>Lorraine</given-names>
    </name>
    <aff>National Center for Biotechnology Information, National Library of
     Medicine, NIH, 8600 Rockville Pike, Bethesda, MD, USA</aff>
  </contrib>
  <contrib contrib-type="author">
    <name>
      <surname>Thom</surname>
      <given-names>Lynne H.</given-names>
    </name>
    <aff>Consolidated Safety Services, 10335 Democracy Lane, Suite 202,
     Fairfax, VA, USA</aff>
  </contrib>
</contrib-group>

B. If there is one affiliation supplied for all of the contributors, include the <aff> in the tagging for the <contrib-group>.

Authors: Gabor T. Marth¹, Eva Czabarka, Janos Murvai, & Stephen T. Sherry.

Affiliations: National Center for Biotechnology Information, National Library of Medicine, National Institutes of Health, Bethesda, Maryland 20894

¹Present affiliation: Department of Biology, Boston College, Chestnut Hill, Massachusetts 02467.

<contrib-group>
  <contrib contrib-type="author">
    <name>
      <surname>Marth</surname>
      <given-names>Gabor T.</given-names>
    </name>
    <xref ref-type="author-notes" rid="FN1">1</xref>
  </contrib>
  <contrib contrib-type="author">
    <name>
      <surname>Czabarka</surname>
      <given-names>Eva</given-names>
    </name>
  </contrib>
  <contrib contrib-type="author">
    <name>
      <surname>Murvai</surname>
      <given-names>Janos</given-names>
    </name>
  </contrib>
  <contrib contrib-type="author">
    <name>
      <surname>Sherry</surname>
      <given-names>Stephen T.</given-names>
    </name>
  </contrib>
  <aff>National Center for Biotechnology Information, National Library of
   Medicine, National Institutes of Health, Bethesda, Maryland 20894</aff>
</contrib-group>

C. If there are multiple <contrib-group> elements, each with a different <aff>, include the relevant <aff> in the tagging for the <contrib-group>.

Lorraine Tanabe^§ and Natalie Xie

National Center for Biotechnology Information, National Library of Medicine, NIH, 8600 Rockville Pike, Bethesda, MD, USA

Lynne H. Thom and Wayne Matten

Consolidated Safety Services, 10335 Democracy Lane, Suite 202, Fairfax, VA, USA

^§Corresponding author

<contrib-group>
  <contrib contrib-type="author" corresp="yes">
    <name>
      <surname>Tanabe</surname>
      <given-names>Lorraine</given-names>
    </name>
  </contrib>
  <contrib contrib-type="author">
    <name>
      <surname>Xie</surname>
      <given-names>Natalie</given-names>
    </name>
  </contrib>
  <aff>National Center for Biotechnology Information, National Library of
   Medicine, NIH, 8600 Rockville Pike, Bethesda, MD, USA</aff>
</contrib-group>
<contrib-group>
  <contrib contrib-type="author">
    <name>
      <surname>Thom</surname>
      <given-names>Lynne H.</given-names>
    </name>
  </contrib>
  <contrib contrib-type="author">
    <name>
      <surname>Matten</surname>
      <given-names>Wayne</given-names>
    </name>
  </contrib>
  <aff>Consolidated Safety Services, 10335 Democracy Lane, Suite 202,
   Fairfax, VA, USA</aff>
</contrib-group>

D. If there are complex relationships between authors and contributors, and the relationships are defined by symbols (including letters/numbers) as below, set the <xref> element with @ref-type="aff" to refer to the corresponding @id on <aff>. The <xref> should be contained within the <contrib>. If there are multiple <xref> elements in the same <contrib>, do not include punctuation between them.

All of the affiliations should follow the single <contrib-group> in this case.

Olga V. Moroz¹, Maria Harkiolaki^1,2, Michael Y. Galperin³, Alexei A. Vagin¹, Dolores González-Pacanowska⁴ and Keith S. Wilson¹

¹Structural Biology Laboratory, Department of Chemistry, University of York, Heslington, York YO10 5YW, UK;

²Cancer Research UK Cell Signalling Group and Weatherall Institute of Molecular Medicine, Oxford, OX3 9DS, UK;

³National Center for Biotechnology Information, National Library of Medicine, National Institutes of Health, Bethesda, Maryland 20894, USA;

⁴Instituto de Parasitología y Biomedicina "López-Neyra", C/Ventanilla, 11. 18001 Granada, Spain

<contrib-group>
  <contrib contrib-type="author">
    <name>
      <surname>Moroz</surname>
      <given-names>Olga V.</given-names>
    </name>
    <xref ref-type="aff" rid="A1">1</xref>
  </contrib>
  <contrib contrib-type="author">
    <name>
      <surname>Harkiolaki</surname>
      <given-names>Maria</given-names>
    </name>
    <xref ref-type="aff" rid="A1">1</xref>
    <xref ref-type="aff" rid="A2">2</xref>
  </contrib>
  <contrib contrib-type="author">
    <name>
      <surname>Galperin</surname>
      <given-names>Michael</given-names>
    </name>
    <xref ref-type="aff" rid="A3">3</xref>
  </contrib>
  <contrib contrib-type="author">
    <name>
      <surname>Vagin</surname>
      <given-names>Alexei A.</given-names>
    </name>
    <xref ref-type="aff" rid="A1">1</xref>
  </contrib>
  <contrib contrib-type="author">
    <name>
      <surname>Gonz&#x00E1;lez-Pacanowska</surname>
      <given-names>Delores</given-names>
    </name>
    <xref ref-type="aff" rid="A4">4</xref>
  </contrib>
  <contrib contrib-type="author">
    <name>
      <surname>Wilson</surname>
      <given-names>Keith S.</given-names>
    </name>
    <xref ref-type="aff" rid="A1">1</xref>
    <xref ref-type="author-notes" rid="FN1">*</xref>
  </contrib>
</contrib-group>
<aff id="A1">
  <label>1</label>Structural Biology Laboratory, Department of Chemistry,
   University of York, Heslington, York YO10 5YW, UK;
</aff>
<aff id="A2">
  <label>2</label>Cancer Research UK Cell Signalling Group and Weatherall
   Institute of Molecular Medicine, Oxford, OX3 9DS, UK;
</aff>
<aff id="A3">
  <label>3</label>National Center for Biotechnology Information, National
   Library of Medicine, National Institutes of Health, Bethesda, Maryland 20894,
   USA;
</aff>
<aff id="A4">
  <label>4</label>Instituto de Parasitolog&#x00ED;a y Biomedicina
   "L&#x00F3;pez-Neyra", C/Ventanilla, 11. 18001 Granada, Spain
</aff>

E. If the affiliation information has been presented as a single block of text where the relationships between author and affiliation are complex and cannot be separated easily, tag the entire affiliation block in one <aff>. Most of the time, the authors' names or initials will be sprinkled through this block of text. This is OK. Also, this block of text might contain other information not exactly related to affiliations. This is OK as well.

Set all of the authors in one <contrib-group> and set the <aff> in this <contrib-group>.

Heloisa P. Soares

Ambuj Kumar

Stephanie Daniels

Suzanne Swann

Alan Cantor

Iztok Hozo

Mike Clark

Fadila Serdarevic

Clement Gwede

Andy Trotti

Benjamin Djulbegovic

Author Affiliations: H. Lee Moffitt Cancer Center & Research Institute at University of South Florida, Tampa (Drs Soares, Kumar, Cantor, Serdarevic, Gwede, Trotti, and Djulbegovic and Ms Daniels); Department of Statistics, Radiation Therapy Oncology Group, Philadelphia, Pa (Dr Swann); Department of Mathematics, University of Indiana Northwest, Gary (Dr Hozo); UK Cochrane Centre, Oxford, England (Dr Clark).

<contrib-group>
  <contrib contrib-type="author">
    <name>
      <surname>Soares</surname>
      <given-names>Heloisa P.</given-names>
    </name>
  </contrib>
  <contrib contrib-type="author">
    <name>
      <surname>Kumar</surname>
      <given-names>Ambuj</given-names>
    </name>
  </contrib>
  <contrib contrib-type="author">
    <name>
      <surname>Daniels</surname>
      <given-names>Stephanie</given-names>
    </name>
  </contrib>
  <contrib contrib-type="author">
    <name>
      <surname>Swann</surname>
      <given-names>Suzanne</given-names>
    </name>
  </contrib>
  <contrib contrib-type="author">
    <name>
      <surname>Cantor</surname>
      <given-names>Alan</given-names>
    </name>
  </contrib>
  <contrib contrib-type="author">
    <name>
      <surname>Hozo</surname>
      <given-names>Iztok</given-names>
    </name>
  </contrib>
  <contrib contrib-type="author">
    <name>
      <surname>Clark</surname>
      <given-names>Mike</given-names>
    </name>
  </contrib>
  <contrib contrib-type="author">
    <name>
      <surname>Serdarevic</surname>
      <given-names>Fadila</given-names>
    </name>
  </contrib>
  <contrib contrib-type="author">
    <name>
      <surname>Gwede</surname>
      <given-names>Clement</given-names>
    </name>
  </contrib>
  <contrib contrib-type="author">
    <name>
      <surname>Trotti</surname>
      <given-names>Andy</given-names>
    </name>
  </contrib>
  <contrib contrib-type="author">
    <name>
      <surname>Djulbegovic</surname>
      <given-names>Benjamin</given-names>
    </name>
  </contrib>
  <aff>Author Affiliations: H. Lee Moffitt Cancer Center & Research Institute at 
   University of South Florida, Tampa (Drs Soares, Kumar, Cantor, Serdarevic, 
   Gwede, Trotti, and Djulbegovic and Ms Daniels); Department of Statistics, 
   Radiation Therapy Oncology Group, Philadelphia, Pa (Dr Swann); Department of 
   Mathematics, University of Indiana Northwest, Gary (Dr Hozo); UK Cochrane 
   Centre, Oxford, England (Dr Clark).</aff>
</contrib-group>

James B. Leverenz, MD

Mark A. Fishel, MD

Elaine R. Peskind, MD

Thomas J. Montine, MD, PhD

David Nochlin, MD

Ellen Steinbart, RN, MA

Murray A. Raskin, MD

Gerard D. Schellenberg, PhD

Thomas D. Bird, MD

Debby Tsuang, MD, MS

Author Affiliations: Parkinson's Disease (Dr Leverenz), Mental Illness (Drs Leverenz, Peskind, Raskind, Schellenberg, and Tsuang and Ms Steinbart), Research, Education, and Clinical Centers, Veterans Affairs Puget Sound Health Care System, Seattle, Wash; and Departments of Neurology (Drs Leverenz, Fishel, and Bird) and Psychiatry and Behavioral Science (Drs Leverenz, Peskind, Raskind, and Tsuang), Division of Neuropathology, Department of Pathology (Drs Montine and Nochlin), and Division of Gerontology/Geriatrics, Department of Medicine (Dr Schellenberg), University of Washington School of Medicine, Seattle.

<contrib-group>
  <contrib>
    <name>
      <surname>Leverenz</surname>
      <given-names>James B.</given-names>
    </name>
    <degrees>MD</degrees>
  </contrib>
  <contrib>
    <name>
      <surname>Fishel</surname>
      <given-names>Mark A.</given-names>
    </name>
    <degrees>MD</degrees>
  </contrib>
  <contrib>
    <name>
      <surname>Peskind</surname>
      <given-names>Elaine R.</given-names>
    </name>
    <degrees>MD</degrees>
  </contrib>
  <contrib>
    <name>
      <surname>Montine</surname>
      <given-names>Thomas J.</given-names>
    </name>
    <degrees>MD, PhD</degrees>
  </contrib>
  <contrib>
    <name>
      <surname>Nochlin</surname>
      <given-names>David</given-names>
    </name>
    <degrees>MD</degrees>
  </contrib>
  <contrib>
    <name>
      <surname>Steinbart</surname>
      <given-names>Ellen</given-names>
    </name>
    <degrees>RN, MA</degrees>
  </contrib>
  <contrib>
    <name>
      <surname>Raskin</surname>
      <given-names>Murray A.</given-names>
    </name>
    <degrees>MD</degrees>
  </contrib>
  <contrib>
    <name>
      <surname>Schellenberg</surname>
      <given-names>Gerard D.</given-names>
    </name>
    <degrees>PhD</degrees>
  </contrib>
  <contrib>
    <name>
      <surname>Bird</surname>
      <given-names>Thomas D.</given-names>
    </name>
    <degrees>MD</degrees>
  </contrib>
  <contrib>
    <name>
      <given-names>Debby Tsuang</surname>
    </name>
    <degrees>MD, MS</degrees>
  </contrib>
  <aff>Author Affiliations: Parkinson's Disease (Dr Leverenz), Mental Illness 
   (Drs Leverenz, Peskind, Raskind, Schellenberg, and Tsuang and Ms Steinbart), 
   Research, Education, and Clinical Centers, Veterans Affairs Puget Sound Health 
   Care System, Seattle, Wash; and Departments of Neurology (Drs Leverenz, 
   Fishel, and Bird) and Psychiatry and Behavioral Science (Drs Leverenz, 
   Peskind, Raskind, and Tsuang), Division of Neuropathology, Department of 
   Pathology (Drs Montine and Nochlin), and Division of Gerontology/Geriatrics, 
   Department of Medicine  (Dr Schellenberg), University of Washington School 
   of Medicine, Seattle.</aff>
</contrib-group>

Back

The chapter back contains information that is published with the chapter but outside of its main narrative flow. Tag reference lists, acknowledgments, appendices, glossaries, and chapter-level footnotes in the back matter.

See <ack>, <ref-list>, <app-group>, <glossary>.

Body

Within a chapter body, all sections must have a label, a title, or both. Bookshelf will unwrap (remove the section tagging for) sections without either a label or title during the conversion process, so do not tag empty sections to adjust the display of section headings.

All chapter content that appears outside of the main narrative flow is part of the chapter <back>. This includes (but is not limited to) acknowledgments, glossaries, appendices, and reference lists.

Tag display objects in the chapter body, immediately following the first reference to that object.

Boxed Text

If the box contains any display objects (<fig>, <table>, <media>), set them with with @position="anchor".

Collaborative Authors

Use <collab> when a group of authors is credited under a single name. Note that if an author is identified as writing on behalf of a collaboration or organization, you must use <on-behalf-of>, not <collab>.

To include all members of a collaborative author, add a <contrib-group> into the <collab> after the text of the collaborative author name.

Deanna M. Church, Leo Goodstadt, LaDeana W. Hillier, and The Mouse Genome Sequencing Consortium

<contrib-group>
  <contrib contrib-type="author">
    <name>
      <surname>Church</surname>
      <given-names>Deanna M.</given-names>
    </name>
  </contrib>
  <contrib contrib-type="author">
    <name>
      <surname>Goodstadt</surname>
      <given-names>Leo</given-names>
    </name>
  </contrib>
  <contrib contrib-type="author">
    <name>
      <surname>Hillier</surname>
      <given-names>LaDeana W.</given-names>
    </name>
  </contrib>
  <contrib contrib-type="author">
    <collab>The Mouse Genome Sequencing Consortium
      <contrib-group>
        <contrib>
          <name>
            <surname>Kelly</surname>
            <given-names>Laura A.</given-names>
          </name>
        </contrib>
        <contrib>
          <name>
            <surname>Randall</surname>
            <given-names>Daniel Lee</given-names>
            <suffix>Jr.</suffix>
          </name>
        </contrib>
      </contrib-group>
    </collab>
  </contrib>
</contrib-group>

When individual collaborative authors are not cited elsewhere under a group name, use @content-type="collaborators".

Deanna M. Church, Leo Goodstadt, LaDeana W. Hillier

<contrib-group content-type="collaborators">
  <contrib>
    <name>
      <surname>Church</surname>
      <given-names>Deanna M.</given-names>
    </name>
  </contrib>
  <contrib>
    <name>
      <surname>Goodstadt</surname>
      <given-names>Leo</given-names>
    </name>
  </contrib>
  <contrib>
    <name>
      <surname>Hillier</surname>
      <given-names>LaDeana W.</given-names>
    </name>
  </contrib>
</contrib-group>

Conflict of Interest Statements

Conflict of Interest (COI) statements are statements about possible conflicts of interest. A statement of "The authors declare that no conflicts exist" is a COI statement. COI statements may appear as <fn> in <author-notes> or <fn-group>, as <p> or <sec> in <ack>, as a <sec> in the <body> or <back>, or within the text of one of these objects.

Conflict of Interest statements should always be identified with the appropriate content type attribute, depending on the element. For Conflict of Interest statements captured as footnotes (<fn>) specify @fn-type="COI-statement". For Conflict of Interest statements captured as a section (<sec>) specify @sec-type="COI-statement". For all other cases use the appropriate content type attribute with a value "COI-statement". Identify the object that most directly includes the COI statement (footnote, paragraph, section, etc.).

COI statement in a footnote (from https://www.ncbi.nlm.nih.gov/books/NBK575742/)

<fn fn-type="COI-statement">
  <p><bold>Conflict of Interest:</bold> The authors declare no potential conflicts 
   of interest with respect to research, authorship and/or publication of this manuscript.</p>
</fn>

COI statement in a body subsection (from https://www.ncbi.nlm.nih.gov/books/NBK579412/)

<sec id="guideline">
  <title>Guideline Development Methodology</title>
  <sec id="guideline.s1">
    <title>Funding</title>
    <p>The development of this guideline was funded by Michigan Medicine.</p>
  </sec>
  <sec id="guideline.s2" sec-type="COI-statement">
    <title>Guideline Development Team and Disclosures</title>
    <p>The multidisciplinary guideline development team consisted of:</p>

COI statement in a paragraph in Acknowledgments (from https://www.ncbi.nlm.nih.gov/books/NBK559432/)

<ack id="ack">
  <title>Acknowledgments</title>
  <p>Editorial and project management services were provided by Debbie Kendall of Kendall 
   Editorial in Richmond, VA.</p>
  <p content-type="COI-statement"><bold>Dualities of Interest</bold></p>

Contributor ID

Contributor identifiers, such as ORCID iDs, must be tagged within the <contrib> to which they apply.

When tagging an ORCID iD, tag the full identifier, including "http://orcid.org/" and the 16-digit number.

<contrib contrib-type="author">
  <contrib-id contrib-id-type="orcid">http://orcid.org/0000-0002-7361-560X</contrib-id>
  <name>
    <surname>Randall</surname>
    <given-names>Laura</given-names>
  </name>
</contrib>

Tag all copyright information within <permissions>.

Set any copyright information that is included in the source material in <copyright-statement> and <copyright-year> tags. This information may be in a page header or footer or immediately following the abstract.

Copyright information usually consists of the word "Copyright", a copyright symbol, the copyright year, and the name of the copyright holder. It might also contain notes, such as Disclaimers.

Include the complete copyright statement (with the date and symbol), in <copyright-statement>. Tag the copyright year in <copyright-year>, whether or not it appears as part of the <copyright-statement>.

Bookshelf displays the content of <copyright-statement> and does not use other copyright elements to build display content.

Do not include licensing information in the <copyright-statement>. See the Licensing Information tagging guidelines for more information.

<permissions>
  <copyright-statement>Copyright &#xA9; 2005, Medical Publishing Corp.</copyright-statement>
  <copyright-year>2005</copyright-year>
</permissions>

<permissions>
  <copyright-statement>Copyright &x#A9; Medical Publishing Corp.</copyright-statement>
  <copyright-year>2005</copyright-year>
</permissions>

CRediT

NISO formalized the CRediT taxonomy. Use https://credit.niso.org/. Follow the JATS4R guidance (https://jats4r.org/credit-taxonomy).

See Author Contributions and <role> for tagging guidance.

Data Availability Statements

Data availability statements, also commonly known as data accessibility statements, should be tagged as a <sec>. Include @sec-type="data-availability" as an attribute.

<sec sec-type="data-availability">
  <title>Data Availability</title>
  <p>These links to Internal UMHS Guidelines contain proprietary information so are only accessible 
   to appropriate Michigan Medicine staff. For more information, contact the authors or publisher.</p>
</sec>

Data Citations

Data citations should facilitate access to the data and any associated metadata, code, or related materials.

Data citations may be included in a traditional <ref-list> along with literature citations, or they may be in their own <ref-list> that includes only data citations.

Follow JATS4R guidance (https://jats4r.org/data-citations), which is briefly summarized below.

Indicate a data citation with @publication-type="data" on <mixed-citation> or <element-citation>.
<data-title> and/or <source> must be present in each data citation. Use <data-title> for the title of the data set. Use <source> to contain the name of the repository. Use both if applicable.
Use <pub-id> to hold the repository ID. Put the full URI to the data, if applicable, in @xlink:href. Use @pub-id-type to hold the type of identifier and @assigning-authority for the agency or entity responsible for that identifier.
```
<pub-id pub-id-type="doi" assigning-authority="figshare" 
 xlink:href="https://doi.org/10.1234/1234321">10.1234/1234321</pub-id>
            
```

Example from JATS4R:

S Gavrilov, RP Harvey & VE Papaioannou. Mus musculus T-box 2 (Tbx2), mRNA. NCBI Nucleotide. 2014:NM_009324.2. NM_009324

<!--Data reference: NCBI Nucleotide: pub-id-type="accession" assigning-authority="NCBI" 
  contains version details-->
<ref id="bib13">
  <element-citation publication-type="data">
    <person-group person-group-type="author">
      <name>
        <surname>Gavrilov</surname>
        <given-names>S</given-names>
      </name>
      <name>
        <surname>Harvey</surname>
        <given-names>RP</given-names>
      </name>
      <name>
        <surname>Papaioannou</surname>
        <given-names>VE</given-names>
      </name>
    </person-group>
    <year iso-8601-date="2014">2014</year>
    <data-title>Mus musculus T-box 2 (Tbx2), mRNA</data-title>
    <source>NCBI Nucleotide</source>
    <pub-id pub-id-type="accession" assigning-authority="NCBI"
      xlink:href="http://www.ncbi.nlm.nih.gov/nuccore/120407038"
      >NM_009324</pub-id>
    <version designator="NM_009324.2">NM_009324.2</version>
  </element-citation>
</ref>

Dates

Within metadata, there are two date elements, <date> and <pub-date>. Tag publication dates in <pub-date> and history dates in <date> inside <pub-history>. The date model is the same for both. It allows parsed date information (<day>, <month>, <season>, <year>).

Tag <day>, <month>, and <year> as integers.

<season> is text.

Tag month ranges (April-June) and yearly seasons (Winter, Spring, etc.) in <season>. Do not set the year in <season>. Month ranges should use 3-letter abbreviations separated by a hyphen (-).

Received: January 14, 2012

<date date-type="received">
  <day>14</day>
  <month>1</month>
  <year>2012</year>
</date>

Spring-Summer 2012

<pub-date date-type="pub"
 publication-format="print">
  <season>Spring-Summer</season>
  <year>2012</year>
</pub-date>

Oct-Nov 2012

<pub-date date-type="collection"
 publication-format="electronic">
  <season>Oct-Nov</season>
  <year>2012</year>
</pub-date>

March 15, 2012

<pub-date date-type="pub"
 publication-format="electronic">
  <day>15</day>
  <month>3</month>
  <year>2012</year>
</pub-date>

Disclaimers

Tag as <notes> in book-meta with @notes-type="disclaimer".

The contents of articles or advertising in the journal are not to be construed as official statements or endorsements by the Medical Publishing Corp.

<notes notes-type="disclaimer">
  <p>The contents of articles or advertising in the journal are not to
  be construed as official statements or endorsements by the Medical Publishing
  Corp.</p>
</notes>

Display Formula

Tag all <disp-formula> with <mml:math>.

Although we would prefer to have all of the math tagged as MathML, it is acceptable to include images of formulas.

Use the <disp-formula> element so that the object can still be identified as a display formula (and referenced) in the chapter. <disp-formula> allows <graphic>, which should be used to call the image.

Display Object Groups

Only use display object groups (<fig-group>, <table-wrap-group>, <disp-formula-group>) to tag objects with labels or captions that are part of a larger grouping.

As a general rule, objects that have unique labels or captions and are grouped under a single, common title are display-object groups. Limit the use of display object groups to situations where multi-part objects must have ids, labels, or captions on each individual part and on the group as a whole.

Do not tag single objects with multiple components in a group.

Display Quote

Use <disp-quote> to tag all block quotes. This allows for visual separation of the quote from the surrounding text, and more accurate tagging, because block quotes generally do not contain textual markers such as quotation marks.

He goes on to integrate these essential histological observations with his knowledge of physiological mechanisms and theorizes on the information flow of cortical circuits. He states:

… it is evident that each a impulse causes the cortical cells to be bombarded by a succession of impulses, thus creating in them a constant state of facilitation, and eventually stimulating them to discharge their axons.

In these propositions, Lorente de Nó essentially describes the dynamic, rapid, and flexible operation of groups of cells, which Hebb would call “cell assemblies,” in a modern physiological framework.

<sec>
  <p>He goes on to integrate these essential histological 
   observations with his knowledge of physiological mechanisms 
   and theorizes on the information flow of cortical circuits. 
   He states:</p> 
  <disp-quote> 
    <p>&#x02026; it is evident that each a impulse causes 
     the cortical cells to be bombarded by a succession of impulses, 
     thus creating in them a constant state of facilitation, and 
     eventually stimulating them to discharge their axons.</p> 
  </disp-quote> 
  <p>In these propositions, Lorente de N&#x000f3; 
   essentially describes the dynamic, rapid, and flexible 
   operation of groups of cells, which Hebb would 
   call &#x0201c;cell assemblies,&#x0201d; in a modern 
   physiological framework.</p> 
</sec>

DOCTYPE declaration

The root element is <book> or <book-part-wrapper>.

Set the PUBLIC identifier to "-//NLM//DTD BITS Book Interchange DTD v2.0 20151225//EN".

Set the SYSTEM identifier to "BITS-book2.dtd".

<!DOCTYPE book PUBLIC "-//NLM//DTD BITS Book Interchange DTD v2.0 20151225//EN"
 "BITS-book2.dtd">

External Links

Tag external links with <ext-link>. Bookshelf will use the text in the <ext-link> element as the active link. The text may be a repeat of the content in the @xlink:href or it may be different.

Accessibility: where possible, use concise and meaningfully descriptive text as the content of <ext-link>, rather than re-use of the content of @xlink:href, following the JATS4R Accessibility Recommendation for external linking.

Use the following @ext-link-type values to tag references to these external objects. Do not include the Resource base URL in the @xlink:href value except for @ext-link-type values of "uri" and "ftp".

Resource or Protocol	ext-link-type value	Resource URI
Any URL	uri	resource defined in @xlink:href
FTP	ftp	resource defined in @xlink:href
DOIs	doi	https://www.doi.org/
PubMed	pmid	https://pubmed.ncbi.nlm.nih.gov/
PMC	pmcid	https://www.ncbi.nlm.nih.gov/pmc/
Entrez Gene	gene	https://www.ncbi.nlm.nih.gov/gene/
OMIM	omim	https://omim.org/
GenBank	gen	https://www.ncbi.nlm.nih.gov/nuccore/
Translated protein-encoding sequence database	genpept	https://www.ncbi.nlm.nih.gov/protein/
Protein Data Bank	pdb	https://www.rcsb.org/

URLs Use @ext-link-type="uri" to identify web addresses. Tag the complete address in @xlink:href.

... details are available at https://www.nlm.nih.gov/.

... details are available at <ext-link ext-link-type="uri"
 xlink:href="https://www.nlm.nih.gov/">https://www.nlm.nih.gov/</ext-link>.

DOIs Use @ext-link-type="doi" to identify DOIs. Tag the DOI name only in the @xlink:href, do not include the Resource URL.

... further details available in, https://doi.org/10.1016/B978-0-444-62627-1.00023-8.

... further details available in, <ext-link ext-link-type="doi"
 xlink:href="10.1016/B978-0-444-62627-1.00023-8">https://doi.org/10.1016/B978-0-444-62627-
 1.00023-8</ext-link>.

GenBank Tag GenBank numbers with @ext-link-type="gen".

Readings were assembled with a redundancy greater than 10 over 211,190 bp [GenBank: EU008541].

Readings were assembled with a redundancy greater than 10 over 211,190 bp
 [GenBank: <ext-link ext-link-type="gen" xlink:href="EU008541">EU008541</ext-link>].

Figures

Figures are the chapter-level objects that usually contain an image.

Tag all figures that must be displayed in place in the text with @position="anchor". Tag figures that may appear anywhere in the text without losing meaning with @position="float".

Common characteristics of figures with @position="float":

It has a label like "Fig. 1" or "Schema IV" or even just "Figure"
It has a title or caption
It is referenced by an <xref> with @ref-type="fig"

If the figure has none of these characteristics or is a child of <boxed-text> or <app>, set the @position="anchor".

Tag any image that must remain at the paragraph level as a <graphic> in a <p> or <sec>.

Set any image that needs to be displayed in the flow of the text as <inline-graphic> in a <p>.

Accessibility: follow the JATS4R accessibility recommendations for graphical content. In each <graphic> and <inline-graphic>, use <alt-text> to capture a brief, meaningful description of the image.

On rare occasions, a named figure (usually it is called something different, like "Scheme") must stay anchored in its position in the text. There may be a <label> and <caption>. In these instances, use @position="anchor" on <fig>.

See also Display Object Groups.

Figure & Table Callouts

Referenced figures and tables should be tagged at each callout in the text. Unreferenced figures and tables should be tagged in <floats-group>. See Figures and Tables for more details.

Footnotes

Capture a footnote in relative proximity to the part of the book in which it is referenced. For instance, capture author footnotes in <author-notes> and footnotes that apply to the chapter as a whole in a <fn-group> in the book <back>.

See <fn-group>, <author-notes>, <fn>.

Funding Information

Tag funding information for the document in the <funding-group> element in the metadata.

Grant and Contract Information

See Funding Information.

Headings

Accessibility: ensure that each <sec> contains a <title>, and that all sections and sub-sections are properly nested. To create accessible headings, <title> must be included in each <sec>, following the JATS4R Recommendation for accessible headings.

IDs

The following elements require an @id attribute:

Element	Context
<ack>	when child of <back>, <body>, <book-app-group>, <book-back>, <front-matter>, or <named-book-part-body>
<app>	all
<app-group>	all
<bio>	when child of <back>, <book-back>, or <front-matter>
<book-app>	all
<book-app-group>	all
<book-part>	all
<boxed-text>	all
<dedication>	all
<element-citation>	outside <ref>
<fig>	all
<fig-group>	all
<foreword>	all
<front-matter-part>	all
<glossary>	when child of <back>, <book-back>, or <front-matter>
<mml:math>	all
<mixed-citation>	outside <ref>
<notes>	when child of <back>, <book-back>, or <front-matter>
<preface>	all
<ref>	all
<ref-list>	when child of <back>, <book-back>, or <front-matter>
<sec>	when child of <back>, <body>, <book-app-group>, or <named-book-part-body>
<table-wrap>	all
<table-wrap-group>	all
<tex-math>	all

Inline formula

Only tag inline math in MathML if it cannot be represented with regular elements. For example, any radical or built fraction.

Inline images

Set any image that must remain at the paragraph level as a <graphic> within the <p> or <sec>.

Set any image that must be displayed in the flow of the text as <inline-graphic> in a <p>.

Accessibility: in each <graphic> and/or <inline-graphic>, use <alt-text> to capture a brief, meaningful description of the image, following the JATS4R accessibility recommendations for graphical content.

Inline tabular material

Set simple inline tabular material as <array>. If the tabular material is too complicated to be represented with <array>, use <table-wrap> with @position="anchor".

See Tables for more details.

Labels

Do not include formatting elements in the content of any label.

Licensing Information

Licensing information explains how the content may be used, as authorized by the copyright holder. This is separate information from the copyright, which indicates who owns the rights to control distribution of the content.

The license and permissions elements allow tagging as recommended by JATS4R (https://jats4r.org/permissions).

Machine-readable Creative Commons licenses must be tagged with URLs in one of the canonical Creative Commons formats. These are URLs that point to the license deed (not to the legalcode) on https://creativecommons.org. Allowable URL formats include:

```
https://creativecommons.org/licenses/[type]/[version]/
```
the use of http or https is allowed, https is preferred; [type] the type must be included and be one of the allowed URL codes for CC licenses, e.g. by, by-nc, by-nc-nd; [version] the version number must be one of the CC versions defined by Creative Commons, e.g. 4.0; a trailing slash is recommended, but not required.
```
http://creativecommons.org/license/by-nc/4.0
```
sample format here uses http and includes an actual type and version number; trailing slash is omitted.

Tag the machine-readable license URL as the content of <ali:license_ref>. Only one <ali:license_ref> with a Creative Commons URL is allowed per license. Use @ali:start_date only if the license has a different start date from the article publication date.

Use <ali:free_to_read> to indicate any article that is not behind access barriers. This is not a license but an indicator of availability only.

<license-p> is intended for display only. If it contains a machine-readable URL for the license (e.g. in an <ext-link>) then it must exactly match the machine-readable URL in <ali:license_ref>.

<permissions>
  <copyright-statement>&#xA9; 2017 Gunderson et al.</copyright-statement>
  <copyright-year>2017</copyright-year>
  <copyright-holder>Gunderson et al.</copyright-holder>
  <ali:free_to_read/>
  <license>
    <ali:license_ref start_date="2017-10-12"
     >https://creativecommons.org/licenses/by/4.0/</ali:license_ref>
    <license-p>This is an open access article licensed under a <ext-link
     ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative
     Commons Attribution 4.0 International License</ext-link>, which permits unrestricted use,
     distribution, reproduction and adaptation in any medium and for any purpose provided that it 
     is properly attributed.</license-p>
  </license>
</permissions>

Lists

Use the <list> only to represent content in lists. Do not use it for formatting.

There are labeled and unlabeled lists. These styles are controlled by the @list-type. The labels will be applied based on the @list-type.

A <list> may be included in the contents of a <list-item> to build a multi-level list or outline.

For further guidance on simple, numbered, and bulleted lists, see: <list>. For further guidance on lists of defined terms or abbreviations, see: <def-list>.

Accessibility: this guidance follows the JATS4R Accessibility Recommendation for lists.

To ensure accessibility in lists, follow the BITS specifications for the following elements and attributes: <list>, <list-item>, <def-list>, <def>, @list-type, @prefix-word, and @continued-from.
Where possible, avoid using <label> to describe a <list-item>. Instead, use standard ordered-list numbering or an unordered list that specifies its display using @list-type.

Math

<mml:math> is the root element for MathML.

Fences:

Elements <mml:msub>, <mml:msup>, and <mml:msubsup> must enclose the entire contents of the expression they affect, not just the closing fence. Fences include: ] } ) 〉 〉 ⟩ .

Child Element Restrictions:

These elements require exactly 2 child elements:

<mml:mfrac>
<mml:mroot>
<mml:msub>
<mml:msup>
<mml:munder>
<mml:mover>

These elements require exactly 3 child elements:

<mml:munderover>
<mml:msubsup>

Allowed only as children of <mml:mmultiscripts>

<mml:mprescripts>
<mml:none>

Allowed only as children of <mml:semantics>

<mml:annotation>
<mml:annotation-xml>

Allowed only as a child of <mml:math>

<mml:semantics>

MathML Attribute Requirements:

@mathvariant:

@numalign, @denomalign, @columnalign:

Only the following values are allowed for these attributes: ( left | center | right )

@rowalign:

Only the following values are allowed for this attribute: ( top | bottom | center | baseline | axis )

@groupalign:

Only the following values are allowed for this attribute: ( left | right | center | decimalpoint )

@equalrows, @equalcolumns, @bevelled:

Only the following values are allowed for these attributes: ( true | false )

@display:

Only the following values are allowed for this attribute: ( inline | block )

Accessibility:

Encode all math in MathML. Do not use <graphic> to capture math. This guidance supports the JATS4R Accessibility Recommendation for math.

Pronouns

See Author Pronouns for tagging Author's pronouns.

Publication in Multiple Languages

For a book or document that is simultaneously published in multiple languages, tag the book or document in each language in a separate XML document. In each XML book or document:

Use @xml:lang on <book> or <book-part> to identify the language of publication.
To correctly identify each language in @xml:lang, follow the BITS language code specifications.
Include a <related-object> element that specifies the source book or document in the other languages.

Pull Quotes

Do not set pull quotes. Pull quotes are pieces of text that have been copied from the article and displayed in the margin of the article to highlight it.

References

A reference list (<ref-list>) is a series of references (<ref>). Generally each reference item contains only one citation element (<mixed-citation> or <element-citation>), but occasionally a single reference item may have more than one citation.

Multiple citations in one reference

6. (a) De Albuquerque IL, Galeffi C, Casinovi CG, Marini-Bettolo GB. Gazz Chim Ital. 1964;94:287. (b) Alcantara, A. F. de C.;Souza, MR.; Pilo-Veloso, D. Fitoterapia. 2000;71:613.

<ref id="R6">
  <label>6</label>
  <element-citation publication-type="journal">
    <label>(a)</label>
    <name>
      <surname>De Albuquerque</surname>
      <given-names>I. L.</given-names>
    </name>
    <name>
      <surname>Galeffi</surname>
      <given-names>C.</given-names>
    </name>
    <name>
      <surname>Casinovi</surname>
      <given-names>C. G.</given-names>
    </name>
    <name>
      <surname>Marini-Bettolo</surname>
      <given-names>G. B.</given-names>
    </name>
    <source>Gazz. Chim. Ital.</source>
    <year>1964</year>
    <volume>94</volume>
    <fpage>287</fpage>
  </element-citation>
  <element-citation publication-type="journal">
    <label>(b)</label>
    <name>
      <surname>Alcantara</surname>
      <given-names>A. F. de C.</given-names>
    </name>
    <name>
      <surname>Souza</surname>
      <given-names>M. R.</given-names>
    </name>
    <name>
      <surname>Pilo-Veloso</surname>
      <given-names>D.</given-names>
    </name>
    <source>Fitoterapia</source>
    <year>2000</year>
    <volume>71</volume>
    <fpage>613</fpage>
  </element-citation>
</ref>

Notes or end notes in a reference

9. The addition of water (100 mol %) afforded the cyclic ether 2 in quantitative yield and with excellent selectivity (entry 4). This further supports the notion that triethylsilyl bromide is not the active catalyst.

<ref id="R9">
  <label>9</label>
  <note>
    <p>The addition of water (100 mol %) afforded the cyclic ether <bold>2</bold> 
     in quantitative yield and with excellent selectivity (entry 4). This further supports 
     the notion that triethylsilyl bromide is not the active catalyst.</p>
  </note>
</ref>

Note with a citation

8. For an alternative mechanistic proposal that suggests the triethylsilyl bromide formed from triethylsilane and bismuth tribromide behaves as a Lewis acid catalyst, see: Bajwa JS, Jiang X, Slade J, Prasad K, Repic O, Blacklock TJ. Tetrahedron Lett. 2002;43:6709.

<ref id="R8">
  <label>8</label>
  <note>
    <p>For an alternative mechanistic proposal that suggests the triethylsilyl 
     bromide formed from triethylsilane and bismuth tribromide behaves as a Lewis
     acid catalyst, see: <element-citation publication-type="journal">
      <name>
        <surname>Bajwa</surname>
        <given-names>J. S.</given-names>
      </name>
      <name>
        <surname>Jiang</surname>
        <given-names>X.</given-names>
      </name>
      <name>
        <surname>Slade</surname>
        <given-names>J.</given-names>
      </name>
      <name>
        <surname>Prasad</surname>
        <given-names>K.</given-names>
      </name>
      <name>
        <surname>Repic</surname>
        <given-names>O.</given-names>
      </name>
      <name>
        <surname>Blacklock</surname>
        <given-names>T. J.</given-names>
      </name>
      <source>Tetrahedron Lett.</source>
      <year>2002</year>
      <volume>43</volume>
      <fpage>6709</fpage>
      </element-citation>
    </p>
  </note>
</ref>

Note with citations and text mixed

17. Chatterjee AK, Morgan JP, Scholl M, Grubbs RH. J Am Chem Soc. 2000;122:3783. For a recent review on olefin cross-metathesis, see: Connon SJ, Blechert S. Angew Chem Int Ed. 2003;42:1900.

<ref id="R17">
  <label>17</label>
  <note>
    <p>
      <element-citation publication-type="journal">
        <name>
          <surname>Chatterjee</surname>
          <given-names>A. K.</given-names>
        </name>
        <name>
          <surname>Morgan</surname>
          <given-names>J. P.</given-names>
        </name>
        <name>
          <surname>Scholl</surname>
          <given-names>M.</given-names>
        </name>
        <name>
          <surname>Grubbs</surname>
          <given-names>R. H.</given-names>
        </name>
        <source>J. Am. Chem. Soc.</source>
        <year>2000</year>
        <volume>122</volume>
        <fpage>3783</fpage>
      </element-citation>
      For a recent review on olefin cross-metathesis, see:
      <element-citation publication-type="journal">
        <name>
          <surname>Connon</surname>
          <given-names>S. J.</given-names>
        </name>
        <name>
          <surname>Blechert</surname>
          <given-names>S.</given-names>
        </name>
        <source>Angew. Chem. Int. Ed.</source>
        <year>2003</year>
        <volume>42</volume>
        <fpage>1900</fpage>
      </element-citation>
    </p>
  </note>
</ref>

Sections/Subsections

Sections and subsections are identifiable by their titles or labels. If a chapter or book-part does not have a labeled or titled opening section, do not tag one in the XML.

Introduction

Planning in advance is widely encouraged as a way to improve quality of care at the end of life.¹ Cross cultural studies have shown that healthcare providers and patients often differ in their views on health related matters....

Methods

We carried out a focused ethnographic study⁸ within a care programme for elderly people in east Baltimore, United States. For the past 20 years this programme has provided medical and nursing care to generally frail housebound elderly people (mean age 77 years) in a largely working class community.

<body>
  <sec>
    <title>Introduction</title>
    <p>Planning in advance is widely encouraged as a way to improve quality
     of care at the end of life.<xref ref-type="bibr" id="R1">1</xref>
     Cross cultural studies have shown that healthcare providers and patients
     often differ in their views on health related matters....</p>
  </sec>
  <sec>
    <title>Methods</title>
    <p>We carried out a focused ethnographic study
     <xref ref-type="bibr" id="R1">8</xref> within a care programme
     for elderly people in east Baltimore, United States. For the past 20
     years this programme has provided medical and nursing care to
     generally frail housebound elderly people (mean age 77 years) in a
     largely working class community.</p>

It has now been 50 years since Briggs and King...published their paper showing that normal hatched tadpoles can be obtained by transplanting the nucleus of a blastula cell to the enucleated eggs of Rana pipiens. This finding provided an initial answer to the long-standing question of whether the process of development and cell differentiation requires a loss or stable change in the genetic constitution of cells....

Amphibia

Briggs and King's immediate pursuit of their 1952 breakthrough gave the somewhat surprising result that, whereas blastula nuclei supported normal tadpole development in up to 40% of all tests, gastrula nuclei were markedly less successful. By the tail-bud stage, nuclei of the endoderm (and in later work nuclei of other germ layers) gave only abnormal embryo development ..., even though the nuclei of tail-bud germ cells gave a high proportion of tadpole development....

<body>
  <p>It has now been 50 years since Briggs and King...published their paper
   showing that normal hatched tadpoles can be obtained by transplanting the
   nucleus of a blastula cell to the enucleated eggs of Rana pipiens. This 
   finding provided an initial answer to the long-standing question of whether
   the process of development and cell differentiation requires a loss or
   stable change in the genetic constitution of cells....</p>
  <sec>
    <title>Amphibia</title>
    <p>Briggs and King's immediate pursuit of their 1952 breakthrough gave
     the somewhat surprising result that, whereas blastula nuclei supported
     normal tadpole development in up to 40% of all tests, gastrula nuclei were
     markedly less successful. By the tail-bud stage, nuclei of the endoderm
     (and in later work nuclei of other germ layers) gave only abnormal embryo
     development ..., even though the nuclei of tail-bud germ cells gave a high
     proportion of tadpole development....</p>

Signatures

Signature blocks should be captured in <sig-block> with each signature tagged in its own <sig>.

Denton A. Cooley, MD, Surgeon-in-Chief,

Texas Heart Institute at St. Luke's Episcopal Hospital, Houston

<sig-block>
  <sig>Denton A. Cooley, MD, Surgeon-in-Chief,<break/>
   Texas Heart Institute at St. Luke's Episcopal Hospital, Houston</sig>
</sig-block>

Supplementary Material

Supplementary material (<supplementary-material>) is treated as a chapter-level object (like <fig> or <table-wrap>).

Referenced <supplementary-material> must have an @id. All <supplementary-material> may have a <label>. Use <media> or <graphic> within <supplementary-material> to describe the supplemental file.

Bookshelf

Document Objects

Getting Started

Resources

Popular

Featured

NCBI Information