Elements Elements
These XML elements have specific style rules associated with them. This is not a complete list of XML elements included in the tag set. For guidance using elements not listed here, consult the appropriate tag library.
Index of elements
Articles may contain more than one abstract. For each abstract beyond the first, specify the attribute @abstract-type.
Capture only the abstract in this tag. Other metadata like copyright information, citation information, and keywords are not part of the abstract.
Sections within abstracts must have either a <title> or a <label>. If neither exists, do not use <sec>. Do not use @sec-type on <sec> within abstracts.
Use the <trans-abstract> element to tag abstracts in languages different from that of the primary article.
Example: More than one abstract in an article.
The first abstract is the main abstract and is a structured abstract and therefore is tagged with multiple sections with titles and no @sec-type. The second abstract is meant to display on a table of contents page of a journal and is tagged with @abstract-type="toc". The third is a graphical abstract with @abstract-type="graphical". The fourth is a plain language summary with @abstract-type="plain-language-summary". The text of the examples is excerpted from Krieger et al. PLoS Med 2005 Jul; 2(7): e162 and Gotfried MH et al. Pulm Ther. 2018 Jun;4(1):59-71.
<abstract>
<sec>
<title>Background</title>
<p>Important controversies exist about the extent to which people's health
status as adults is shaped by their living conditions in early life compared
to adulthood....</p>
</sec>
<sec>
<title>Methods and Findings</title>
<p>Our study employed data from a cross-sectional survey and physical
examinations of twins in a population-based....</p>
</sec>
<sec>
<title>Conclusion</title>
<p>These results provide novel evidence that lifetime socioeconomic position
influences adult health and highlight the utility of studying social plus
biological aspects of twinship.</p>
</sec>
</abstract>
<abstract abstract-type="toc">
<p>Differing socioeconomic positions in adult life are associated with
differences in the health of twins raised together.</p>
</abstract>
<abstract abstract-type="graphical">
<title>Graphical Abstract</title>
<p>
<graphic xlink:href="87795_abs.jpg" position="anchor"/>
</p>
</abstract>
<abstract abstract-type="plain-language-summary">
<title>Plain Language Summary</title>
<p>Idiopathic pulmonary fibrosis (IPF) is a progressive, irreversible, and fatal
lung disease. Pirfenidone is a medication that slows disease progression in patients with
IPF....</p>
</abstract>
Set any label or symbol in the <label> element. Do not create symbols or labels in the XML if they do not exist in the published article. Follow copy for all punctuation.
Tag all non-label content as simple text within the element. Do not tag individual address elements in the affiliation. The only exception is email addresses which should be identified in <email>.
See Author/Affiliation Relationship for information on how authors and affiliations are "linked".
<aff id="aff1">
<label>1</label>University of Groningen, University Medical Center Groningen, University Center
for Psychiatry, Rob Giel Research Center, Groningen, the Netherlands<aff>
1.3
Used to capture one affiliation in multiple languages or for multiple purposes.
<aff-alternatives id="aff1">
<aff xml:lang="ja-Jpan">国立言語学博物館</aff>
<aff xml:lang="en">National Museum of Linguistics</aff>
</aff-alternatives>
1.2
Used to capture one affiliation in multiple languages or for multiple purposes.
<aff-alternatives id="aff1">
<aff xml:lang="ja-Jpan">国立言語学博物館</aff>
<aff xml:lang="en">National Museum of Linguistics</aff>
</aff-alternatives>
1.1
Used to capture one affiliation in multiple languages or for multiple purposes.
<aff-alternatives id="aff1">
<aff xml:lang="ja-Jpan">国立言語学博物館</aff>
<aff xml:lang="en">National Museum of Linguistics</aff>
</aff-alternatives>
1.0
Used to capture one affiliation in multiple languages or for multiple purposes.
<aff-alternatives id="aff1">
<aff xml:lang="ja-Jpan">国立言語学博物館</aff>
<aff xml:lang="en">National Museum of Linguistics</aff>
</aff-alternatives>
3.0
Element is not available in this version.
2.3
Element is not available in this version.
1.3
This is an element defined by the NISO Access and License Indicators project for tagging references to licenses. See https://www.niso.org/standards-committees/access-and-license-indicators for more information.
Use <ali:license_ref> to capture the license URL. See <license> for additional information.
1.2
This is an element defined by the NISO Access and License Indicators project for tagging references to licenses. See https://www.niso.org/standards-committees/access-and-license-indicators for more information.
Use <ali:license_ref> to capture the license URL. See <license> for additional information.
1.1
This is an element defined by the NISO Access and License Indicators project for tagging references to licenses. See https://www.niso.org/standards-committees/access-and-license-indicators for more information.
Use <ali:license_ref> to capture the license URL. See <license> for additional information.
1.0
Element is not available in this version.
3.0
Element is not available in this version.
2.3
Element is not available in this version.
1.3
This is an element defined by the NISO Access and License Indicators project that indicates that an article is free to read. See https://www.niso.org/standards-committees/access-and-license-indicators for more information.
1.2
This is an element defined by the NISO Access and License Indicators project that indicates that an article is free to read. See https://www.niso.org/standards-committees/access-and-license-indicators for more information.
1.1
This is an element defined by the NISO Access and License Indicators project that indicates that an article is free to read. See https://www.niso.org/standards-committees/access-and-license-indicators for more information.
1.0
Element is not available in this version.
3.0
Element is not available in this version.
2.3
Element is not available in this version.
1.3
When alternatives are specified in these elements, PMC will choose the alternative for display based on the following priority (broken down by category).
| Category: | Included elements: | Processing priority: |
|---|---|---|
| Display text: |
<disp-quote> <boxed-text> |
<textual-form> <graphic> |
| Formulas and chemical structures: |
<chem-struct> <chem-struct-wrap> <disp-formula> <inline-formula> |
<mml:math> <tex-math> <graphic> |
| Signatures: |
<sig> <sig-block> |
<graphic> <textual-form> |
| Supplementary material |
<inline-supplementary-material> <supplementary-material> |
<media> <graphic> <table> <textual-form> |
| Appendix | <app> |
<textual-form> <media> |
| Array | <array> |
<tbody> (inside <table>) <preformat> <textual-form> |
| Figures | <fig> |
<media> <graphic> |
| Glossary | <glossary> |
<textual-form> <graphic> |
| Table | <table-wrap> |
<table> <array> <graphic> <preformat> <textual-form> |
| Table cells | <td>, <th> |
<textual-form> <media> <graphic> |
If none of these objects exist in the <alternatives> element, the article will fail to pass PMC style. Contact PMC if your data cannot be captured using these combinations.
If a child element of <alternatives> specifies @specific-use "archive-only", "print-only", "thumbnail" or "web-only", that object will not be displayed in PMC's rendering.
Some elements must not contain a child of <alternatives> that is the same element as itself. The following are not allowed: <array>, <chem-struct>, <inline-supplementary-material>, <supplementary-material>.
1.2
When alternatives are specified in these elements, PMC will choose the alternative for display based on the following priority (broken down by category).
| Category: | Included elements: | Processing priority: |
|---|---|---|
| Display text: |
<disp-quote> <boxed-text> |
<textual-form> <graphic> |
| Formulas and chemical structures: |
<chem-struct> <chem-struct-wrap> <disp-formula> <inline-formula> |
<mml:math> <tex-math> <graphic> |
| Signatures: |
<sig> <sig-block> |
<graphic> <textual-form> |
| Supplementary material |
<inline-supplementary-material> <supplementary-material> |
<media> <graphic> <table> <textual-form> |
| Appendix | <app> |
<textual-form> <media> |
| Array | <array> |
<tbody> (inside <table>) <preformat> <textual-form> |
| Figures | <fig> |
<media> <graphic> |
| Glossary | <glossary> |
<textual-form> <graphic> |
| Table | <table-wrap> |
<table> <array> <graphic> <preformat> <textual-form> |
| Table cells | <td>, <th> |
<textual-form> <media> <graphic> |
If none of these objects exist in the <alternatives> element, the article will fail to pass PMC style. Contact PMC if your data cannot be captured using these combinations.
If a child element of <alternatives> specifies @specific-use "archive-only", "print-only", "thumbnail" or "web-only", that object will not be displayed in PMC's rendering.
Some elements must not contain a child of <alternatives> that is the same element as itself. The following are not allowed: <array>, <chem-struct>, <inline-supplementary-material>, <supplementary-material>.
1.1
<alternatives> may only be contained in the following elements
- <app>
- <array>
- <bio>
- <boxed-text>
- <chem-struct>
- <chem-struct-wrap>
- <disp-formula>
- <disp-quote>
- <element-citation>
- <fig>
- <glossary>
- <inline-supplementary-material>
- <inline-formula>
- <mixed-citation>
- <p>
- <sig>
- <sig-block>
- <supplementary-material>
- <table-wrap>
- <td>
- <th>
When alternatives are specified in these elements, PMC will choose the alternative for display based on the following priority (broken down by category).
| Category: | Included elements: | Processing priority: |
|---|---|---|
| Display text: |
<disp-quote> <boxed-text> |
<textual-form> <graphic> |
| Formulas and chemical structures: |
<chem-struct> <chem-struct-wrap> <disp-formula> <inline-formula> |
<mml:math> <tex-math> <graphic> |
| Signatures: |
<sig> <sig-block> |
<graphic> <textual-form> |
| Supplementary material |
<inline-supplementary-material> <supplementary-material> |
<media> <graphic> <table> <textual-form> |
| Appendix | <app> |
<textual-form> <media> |
| Array | <array> |
<tbody> (inside <table>) <preformat> <textual-form> |
| Figures | <fig> |
<media> <graphic> |
| Glossary | <glossary> |
<textual-form> <graphic> |
| Table | <table-wrap> |
<table> <array> <graphic> <preformat> <textual-form> |
| Table cells | <td>, <th> |
<textual-form> <media> <graphic> |
If none of these objects exist in the <alternatives> element, the article will fail to pass PMC style. Contact PMC if your data cannot be captured using these combinations.
If a child element of <alternatives> specifies @specific-use "archive-only", "print-only", "thumbnail" or "web-only", that object will not be displayed in PMC's rendering.
Some elements must not contain a child of <alternatives> that is the same element as itself. The following are not allowed: <array>, <chem-struct>, <inline-supplementary-material>, <supplementary-material>.
1.0
<alternatives> may only be contained in the following elements
- <app>
- <array>
- <bio>
- <boxed-text>
- <chem-struct>
- <chem-struct-wrap>
- <disp-formula>
- <disp-quote>
- <element-citation>
- <fig>
- <glossary>
- <inline-supplementary-material>
- <inline-formula>
- <mixed-citation>
- <p>
- <sig>
- <sig-block>
- <supplementary-material>
- <table-wrap>
- <td>
- <th>
When alternatives are specified in these elements, PMC will choose the alternative for display based on the following priority (broken down by category).
| Category: | Included elements: | Processing priority: |
|---|---|---|
| Display text: |
<disp-quote> <boxed-text> |
<textual-form> <graphic> |
| Formulas and chemical structures: |
<chem-struct> <chem-struct-wrap> <disp-formula> <inline-formula> |
<mml:math> <tex-math> <graphic> |
| Signatures: |
<sig> <sig-block> |
<graphic> <textual-form> |
| Supplementary material |
<inline-supplementary-material> <supplementary-material> |
<media> <graphic> <table> <textual-form> |
| Appendix | <app> |
<textual-form> <media> |
| Array | <array> |
<tbody> (inside <table>) <preformat> <textual-form> |
| Figures | <fig> |
<media> <graphic> |
| Glossary | <glossary> |
<textual-form> <graphic> |
| Table | <table-wrap> |
<table> <array> <graphic> <preformat> <textual-form> |
| Table cells | <td>, <th> |
<textual-form> <media> <graphic> |
If none of these objects exist in the <alternatives> element, the article will fail to pass PMC style. Contact PMC if your data cannot be captured using these combinations.
If a child element of <alternatives> specifies @specific-use "archive-only", "print-only", "thumbnail" or "web-only", that object will not be displayed in PMC's rendering.
Some elements must not contain a child of <alternatives> that is the same element as itself. The following are not allowed: <array>, <chem-struct>, <inline-supplementary-material>, <supplementary-material>.
3.0
<alternatives> may only be contained in the following elements
- <app>
- <array>
- <bio>
- <boxed-text>
- <chem-struct>
- <chem-struct-wrap>
- <disp-formula>
- <disp-quote>
- <element-citation>
- <fig>
- <glossary>
- <inline-supplementary-material>
- <inline-formula>
- <mixed-citation>
- <p>
- <sig>
- <sig-block>
- <supplementary-material>
- <table-wrap>
- <td>
- <th>
When alternatives are specified in these elements, PMC will choose the alternative for display based on the following priority (broken down by category).
| Category: | Included elements: | Processing priority: |
|---|---|---|
| Display text: |
<disp-quote> <boxed-text> |
<textual-form> <graphic> |
| Formulas and chemical structures: |
<chem-struct> <chem-struct-wrap> <disp-formula> <inline-formula> |
<mml:math> <tex-math> <graphic> |
| Signatures: |
<sig> <sig-block> |
<graphic> <textual-form> |
| Supplementary material |
<inline-supplementary-material> <supplementary-material> |
<media> <graphic> <table> <textual-form> |
| Appendix | <app> |
<textual-form> <media> |
| Array | <array> |
<tbody> (inside <table>) <preformat> <textual-form> |
| Figures | <fig> |
<media> <graphic> |
| Glossary | <glossary> |
<textual-form> <graphic> |
| Table | <table-wrap> |
<table> <array> <graphic> <preformat> <textual-form> |
| Table cells | <td>, <th> |
<textual-form> <media> <graphic> |
If none of these objects exist in the <alternatives> element, the article will fail to pass PMC style. Contact PMC if your data cannot be captured using these combinations.
If a child element of <alternatives> specifies @specific-use "archive-only", "print-only", "thumbnail" or "web-only", that object will not be displayed in PMC's rendering.
Some elements must not contain a child of <alternatives> that is the same element as itself. The following are not allowed: <array>, <chem-struct>, <inline-supplementary-material>, <supplementary-material>.
2.3
Element is not available in this version.
The @article-type attribute is required and must be one of the values listed below. The @article-type attribute is not the value used in generating the categories for the Table of Contents. Those values are specified in <article-categories>.
attributes:
- article-type—Most of the articles should have the value of "research-article". Allowed values are: "abstract", "addendum", "announcement", "article-commentary", "author-comment", "book-review", "books-received", "brief-report", "calendar", "case-report", "community-comment", "correction", "data-paper" (v2.3 must use Green), "discussion", "editor-report", "editorial", "expression-of-concern" (v2.3 must use Green), "in-brief", "introduction", "letter", "meeting-report", "methods-article" (v2.3 must use Green), "news", "obituary", "oration ", "other", "product-review", "reply", "research-article", "retraction", "review-article", "reviewer-report", "systematic-review" (v2.3 must use Green). See the Article Types for descriptions of these values.(#REQUIRED)
This is a required element that holds subject and other "sorting" type information about the article. PMC requires that there be a <subj-group> with @subj-group-type="heading" to hold headings used to sort the articles on the TOC.
Required element which must contain exactly one @subj-group-type="heading".
Articles may contain more than one <subj-group> but only one may have @subj-group-type="heading".
1.3
Contains any unique identifier assigned to the article, such as DOI, publisher-id, or PubMed ID.
Only one <article-id> with any given @pub-id-type is allowed per article with the exception of these values of @pub-id-type: "publisher-id", "publisher-manuscript", and "other".
To comply with best practices, @pub-id-type should only be used to describe the type values and @assigning-authority should be used to name the responsible agency. For example:
<article-id pub-id-type="doi" assigning-authority="crossref">10.0000/sample.1</article-id>
attributes:
- pub-id-type—Supported values:
- "art-access-id": Generic article accession identifier for interchange and retrieval between archives.
- "arxiv": arXiv archive of electronic preprints.
- "doaj": Directory of Open Access Journals.
- "doi": Digital Object Identifier.
- "isbn": International Standard Book Number.
- "pmcid": PubMed Central identifier.
- "pmid": PubMed identifier.
- "publisher-id": Publisher's identifier, such as an "article-id", "artnum", "identifier", "article-number", "pub-id", etc.
- "publisher-manuscript": Publisher's identifier specific to tracking the manuscript through the editorial process.
- "sici": Serial Item and Contribution Identifier.
- "other": Identifier type not described by those listed above.
1.2
Contains any unique identifier assigned to the article, such as DOI, publisher-id, or PubMed ID.
Only one <article-id> with any given @pub-id-type is allowed per article with the exception of these values of @pub-id-type: "publisher-id", "publisher-manuscript", and "other".
To comply with best practices, @pub-id-type should only be used to describe the type values and @assigning-authority should be used to name the responsible agency. For example:
<article-id pub-id-type="doi" assigning-authority="crossref">10.0000/sample.1</article-id>
attributes:
- pub-id-type—Supported values:
- "art-access-id": Generic article accession identifier for interchange and retrieval between archives.
- "arxiv": arXiv archive of electronic preprints.
- "doaj": Directory of Open Access Journals.
- "doi": Digital Object Identifier.
- "isbn": International Standard Book Number.
- "pmcid": PubMed Central identifier.
- "pmid": PubMed identifier.
- "publisher-id": Publisher's identifier, such as an "article-id", "artnum", "identifier", "article-number", "pub-id", etc.
- "publisher-manuscript": Publisher's identifier specific to tracking the manuscript through the editorial process.
- "sici": Serial Item and Contribution Identifier.
- "other": Identifier type not described by those listed above.
- assigning-authority—Optional; use only when the authority is known.
1.1
Contains any unique identifier assigned to the article, such as DOI, publisher-id, or PubMed ID.
Only one <article-id> with any given @pub-id-type is allowed per article with the exception of these values of @pub-id-type: "publisher-id", "publisher-manuscript", and "other".
<article-id pub-id-type="doi">10.0000/sample.1</article-id>
attributes:
- pub-id-type—Supported values:
- "art-access-id": Generic article accession identifier for interchange and retrieval between archives.
- "arxiv": arXiv archive of electronic preprints.
- "doaj": Directory of Open Access Journals.
- "doi": Digital Object Identifier.
- "isbn": International Standard Book Number.
- "pmcid": PubMed Central identifier.
- "pmid": PubMed identifier.
- "publisher-id": Publisher's identifier, such as an "article-id", "artnum", "identifier", "article-number", "pub-id", etc.
- "publisher-manuscript": Publisher's identifier specific to tracking the manuscript through the editorial process.
- "sici": Serial Item and Contribution Identifier.
- "other": Identifier type not described by those listed above.
1.0
Contains any unique identifier assigned to the article, such as DOI, publisher-id, or PubMed ID.
Only one <article-id> with any given @pub-id-type is allowed per article with the exception of these values of @pub-id-type: "publisher-id", "publisher-manuscript", and "other".
<article-id pub-id-type="doi">10.0000/sample.1</article-id>
attributes:
- pub-id-type—Supported values:
- "art-access-id": Generic article accession identifier for interchange and retrieval between archives.
- "arxiv": arXiv archive of electronic preprints.
- "doaj": Directory of Open Access Journals.
- "doi": Digital Object Identifier.
- "isbn": International Standard Book Number.
- "pmcid": PubMed Central identifier.
- "pmid": PubMed identifier.
- "publisher-id": Publisher's identifier, such as an "article-id", "artnum", "identifier", "article-number", "pub-id", etc.
- "publisher-manuscript": Publisher's identifier specific to tracking the manuscript through the editorial process.
- "sici": Serial Item and Contribution Identifier.
- "other": Identifier type not described by those listed above.
3.0
Contains any unique identifier assigned to the article, such as DOI, publisher-id, or PubMed ID.
Only one <article-id> with any given @pub-id-type is allowed per article with the exception of these values of @pub-id-type: "publisher-id", "publisher-manuscript", and "other".
<article-id pub-id-type="doi">10.0000/sample.1</article-id>
attributes:
- pub-id-type—Supported values:
- "art-access-id": Generic article accession identifier for interchange and retrieval between archives.
- "arxiv": arXiv archive of electronic preprints.
- "doaj": Directory of Open Access Journals.
- "doi": Digital Object Identifier.
- "isbn": International Standard Book Number.
- "pmcid": PubMed Central identifier.
- "pmid": PubMed identifier.
- "publisher-id": Publisher's identifier, such as an "article-id", "artnum", "identifier", "article-number", "pub-id", etc.
- "publisher-manuscript": Publisher's identifier specific to tracking the manuscript through the editorial process.
- "sici": Serial Item and Contribution Identifier.
- "other": Identifier type not described by those listed above.
2.3
Contains any unique identifier assigned to the article, such as DOI, publisher-id, or PubMed ID.
Only one <article-id> with any given @pub-id-type is allowed per article with the exception of these values of @pub-id-type: "publisher-id", "publisher-manuscript", and "other".
<article-id pub-id-type="doi">10.0000/sample.1</article-id>
attributes:
- pub-id-type—Supported values:
- "art-access-id": Generic article accession identifier for interchange and retrieval between archives.
- "arxiv": arXiv archive of electronic preprints.
- "doaj": Directory of Open Access Journals.
- "doi": Digital Object Identifier.
- "isbn": International Standard Book Number.
- "pmcid": PubMed Central identifier.
- "pmid": PubMed identifier.
- "publisher-id": Publisher's identifier, such as an "article-id", "artnum", "identifier", "article-number", "pub-id", etc.
- "publisher-manuscript": Publisher's identifier specific to tracking the manuscript through the editorial process.
- "sici": Serial Item and Contribution Identifier.
- "other": Identifier type not described by those listed above.
Tag all article metadata for each article. All articles must contain <article-categories>, <title-group>, <pub-date>, and <fpage> or <elocation-id>.
Contains only the article title.
Do not use emphasis tags to mimic formatting.
For product reviews, use the explicit title found on the article. If no explicit title is present, use the title of the first (or only) product being reviewed. See Article Title for examples.
See also <subtitle>, <trans-title>.
Tag notes directly related to the author(s) in <author-note>. If the information can be captured by the attributes available on <contrib>, do not include it as an author note. Tag correspondence information (beyond a simple corresponding author yes/no; see Author Names) in <corresp>. Set all other author-related footnotes in <fn>. Appropriate @fn-type values include:
| Value | Meaning |
|---|---|
| "com" | article was communicated by |
| "con" | article was contributed by |
| "current-aff" | current affiliation |
| "deceased" | person has died since the article was written |
| "equal" | contributed equally in the creation of the document |
| "present-address" | contributor's current address |
Jane Doe and Marcus Dorsey
Please address all correspondence to Jane Doe at author@affiliation.edu.
<contrib-group>
<contrib contrib-type="author">
<name>
<surname>Doe</surname>
<given-names>Jane</given-names>
</name>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Doresy</surname>
<given-names>Marcus</given-names>
</name>
<xref ref-type="corresp" rid="cor1"/>
</contrib>
<contrib-group>
...
<author-notes>
<corresp id="cor1">Please address all correspondence to Dr. Jane Doe at
<email>author@affiliation.edu</email>.
</corresp>
</author-notes>
Laura Kelly*, Jeff Beck, Anne Jones
*Corresponding author
<contrib-group>
<contrib contrib-type="author" corresp="yes">
<name>
<surname>Kelly</surname>
<given-names>Laura</given-names>
</name>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Beck</surname>
<given-names>Jeff</given-names>
</name>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Jones</surname>
<given-names>Anne</given-names>
</name>
</contrib>
</contrib-group>
1.3
Tag only one award id per <award-id> element.
1.2
Tag only one award id per <award-id> element.
1.1
Tag only one award id per <award-id> element.
1.0
Tag only one award id per <award-id> element.
3.0
Tag only one award id per <award-id> element.
2.3
Element is not available in this version. See <contract-num> and <grant-num>.
Typical content includes (but is not limited to) appendices (<app-group>), glossaries (<glossary>), reference-lists (<ref-list>), and article-level footnotes (<fn-group>).
Carries all of the article body. It allows <p> and all paragraph-level objects and then repeating recursive sections (<sec>).
Use <sec> to enclose all subsections within the body or within a section. Do not set the section titles in <bold> or some other formatting.
Back matter elements, such as <app-group>, <glossary> and <ref-list>, should be tagged in <back>, not at the end of <body>.
Within the caption, tag the <title> separately from from the rest of the caption text. Do not include the object’s label in <caption>; use the <label> tag.
Fig 6. JATS to EPUB pipeline.
Graphical representation of the pipeline converting JATS data to EPUB.
<label>Fig 6.</label>
<caption>
<title>JATS to EPUB pipeline.</title>
<p>Graphical representation of the pipeline converting JATS data to EPUB.</p>
</caption>
1.3
Element is not available in this version. See <element-citation> and <mixed-citation>.
1.2
Element is not available in this version. See <element-citation> and <mixed-citation>.
1.1
Element is not available in this version. See <element-citation> and <mixed-citation>.
1.0
Element is not available in this version. See <element-citation> and <mixed-citation>.
3.0
Element is not available in this version. See <element-citation> and <mixed-citation>.
2.3
Contains a bibliographic description of a work.
attributes:
- citation-type—The type of work being cited (for example, book or journal).(#REQUIRED)
1.3
Used to capture one citation in multiple languages, formats, or for multiple purposes. If a <ref> contains multiple citations, do not use <citation-alternatives>; see <ref>.
<ref>
<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>
</ref>
1.2
Used to capture one citation in multiple languages, formats, or for multiple purposes. If a <ref> contains multiple citations, do not use <citation-alternatives>; see <ref>.
<ref>
<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>
</ref>
1.1
Used to capture one citation in multiple languages, formats, or for multiple purposes. If a <ref> contains multiple citations, do not use <citation-alternatives>; see <ref>.
<ref>
<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>
</ref>
1.0
Used to capture one citation in multiple languages, formats, or for multiple purposes. If a <ref> contains multiple citations, do not use <citation-alternatives>; see <ref>.
<ref>
<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>
</ref>
3.0
Element is not available in this version.
2.3
Element is not available in this version.
1.3
Used to capture one collaborative author in multiple languages or for multiple purposes. See also <name-alternatives>.
<collab-alternatives>
<collab>脳卒中急性期患者データベース構築研究(JSSRS)グループ</collab>
<collab xml:lang="en">JSSRS Group</collab>
</collab-alternatives>
1.2
Used to capture one collaborative author in multiple languages or for multiple purposes. See also <name-alternatives>.
<collab-alternatives>
<collab>脳卒中急性期患者データベース構築研究(JSSRS)グループ</collab>
<collab xml:lang="en">JSSRS Group</collab>
</collab-alternatives>
1.1
Used to capture one collaborative author in multiple languages or for multiple purposes. See also <name-alternatives>.
<collab-alternatives>
<collab>脳卒中急性期患者データベース構築研究(JSSRS)グループ</collab>
<collab xml:lang="en">JSSRS Group</collab>
</collab-alternatives>
1.0
Used to capture one collaborative author in multiple languages or for multiple purposes. See also <name-alternatives>.
<collab-alternatives>
<collab>脳卒中急性期患者データベース構築研究(JSSRS)グループ</collab>
<collab xml:lang="en">JSSRS Group</collab>
</collab-alternatives>
3.0
Element is not available in this version.
2.3
Element is not available in this version.
1.3
Element is not available in this version. See <funding-group>.
1.2
Element is not available in this version. See <funding-group>.
1.1
Element is not available in this version. See <funding-group>.
1.0
Element is not available in this version. See <funding-group>.
3.0
Element is not available in this version. See <funding-group>.
2.3
This element must link to a <contract-sponsor>.
1.3
Element is not available in this version. See <funding-group>.
1.2
Element is not available in this version. See <funding-group>.
1.1
Element is not available in this version. See <funding-group>.
1.0
Element is not available in this version. See <funding-group>.
3.0
Element is not available in this version. See <funding-group>.
2.3
Set <contract-sponsor> only once, even if there are multiple grants listed. It must link to at least one <contract-num>.
1.3
Tag only one contributor per <contrib>.
Whenever possible, tag the contributor’s affiliation inside the <contrib> tag. See Author/Affiliation Relationship for examples.
attributes:
- contrib-type—Value is usually "author" or "editor". Attribute is required unless <contrib> is a descendant of <collab>.
- corresp—Set as "yes" if the author is listed as the corresponding author.
- deceased—Set as "yes" if the author is indicated to have passed on. This information will not display in PMC.
- equal-contrib—Set as "yes" on each author that is indicated to have "contributed equally to this work".
- id—Do not use. Set contributor identifiers in <contrib-id>.
- rid—Do not use.
1.2
Tag only one contributor per <contrib>.
Whenever possible, tag the contributor’s affiliation inside the <contrib> tag. See Author/Affiliation Relationship for examples.
attributes:
- contrib-type—Value is usually "author" or "editor". Attribute is required unless <contrib> is a descendant of <collab>.
- corresp—Set as "yes" if the author is listed as the corresponding author.
- deceased—Set as "yes" if the author is indicated to have passed on. This information will not display in PMC.
- equal-contrib—Set as "yes" on each author that is indicated to have "contributed equally to this work".
- id—Do not use. Set contributor identifiers in <contrib-id>.
- rid—Do not use.
1.1
Tag only one contributor per <contrib>.
Whenever possible, tag the contributor’s affiliation inside the <contrib> tag. See Author/Affiliation Relationship for examples.
attributes:
- contrib-type—Value is usually "author" or "editor". Attribute is required unless <contrib> is a descendant of <collab>.
- corresp—Set as "yes" if the author is listed as the corresponding author.
- deceased—Set as "yes" if the author is indicated to have passed on. This information will not display in PMC.
- equal-contrib—Set as "yes" on each author that is indicated to have "contributed equally to this work".
- id—Do not use. Set contributor identifiers in <contrib-id>.
- rid—Do not use.
1.0
Tag only one contributor per <contrib>.
Whenever possible, tag the contributor’s affiliation inside the <contrib> tag. See Author/Affiliation Relationship for examples.
attributes:
- contrib-type—Value is usually "author" or "editor". Attribute is required unless <contrib> is a descendant of <collab>.
- corresp—Set as "yes" if the author is listed as the corresponding author.
- deceased—Set as "yes" if the author is indicated to have passed on. This information will not display in PMC.
- equal-contrib—Set as "yes" on each author that is indicated to have "contributed equally to this work".
- id—Do not use. Set contributor identifiers in <contrib-id>.
- rid—Do not use.
3.0
Tag only one contributor per <contrib>.
Whenever possible, tag the contributor’s affiliation inside the <contrib> tag. See Author/Affiliation Relationship for examples.
attributes:
- contrib-type—Value is usually "author" or "editor". Attribute is required unless <contrib> is a descendant of <collab>.
- corresp—Set as "yes" if the author is listed as the corresponding author.
- deceased—Set as "yes" if the author is indicated to have passed on. This information will not display in PMC.
- equal-contrib—Set as "yes" on each author that is indicated to have "contributed equally to this work".
- id—Do not use.
- rid—Do not use.
2.3
Tag only one contributor per <contrib> element unless tagging Collaborative Authors.
Whenever possible, tag the contributor’s affiliation inside the <contrib> tag. See Author/Affiliation Relationship for examples.
attributes:
- contrib-type—Value is usually "author" or "editor". Attribute is required unless <contrib> is a descendant of <collab>.
- corresp—Set as "yes" if the author is listed as the corresponding author.
- deceased—Set as "yes" if the author is indicated to have passed on. This information will not display in PMC.
- equal-contrib—Set as "yes" on each author that is indicated to have "contributed equally to this work".
- id—Only use when tagging Collaborative Authors.
- rid—Only use when tagging Collaborative Authors.
1.3
Contains one or more <contrib>
When used inside <collab> to tag collaboration members, it must not contain descendant <collab> elements.
If affiliation information is presented for the entire contributor group, tag the <aff> element inside the <contrib-group>.
See Author/Affiliation Relationships for more information and examples.
1.2
Contains one or more <contrib>
When used inside <collab> to tag collaboration members, it must not contain descendant <collab> elements.
If affiliation information is presented for the entire contributor group, tag the <aff> element inside the <contrib-group>.
See Author/Affiliation Relationships for more information and examples.
1.1
Contains one or more <contrib>
When used inside <collab> to tag collaboration members, it must not contain descendant <collab> elements.
If affiliation information is presented for the entire contributor group, tag the <aff> element inside the <contrib-group>.
See Author/Affiliation Relationships for more information and examples.
1.0
Contains one or more <contrib>
When used inside <collab> to tag collaboration members, it must not contain descendant <collab> elements.
If affiliation information is presented for the entire contributor group, tag the <aff> element inside the <contrib-group>.
See Author/Affiliation Relationships for more information and examples.
3.0
Contains one or more <contrib>
When used inside <collab> to tag collaboration members, it must not contain descendant <collab> elements.
If affiliation information is presented for the entire contributor group, tag the <aff> element inside the <contrib-group>.
See Author/Affiliation Relationships for more information and examples.
2.3
Contains one or more <contrib>
If affiliation information is presented for the entire contributor group, tag the <aff> element inside the <contrib-group>.
See Author/Affiliation Relationships for more information and examples.
1.3
Identifier of a contibutor as assigned by the authority named in @contrib-id-type.
Do not use on collaborative contributors.
<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>LA</given-names>
</name>
</contrib>
1.2
Identifier of a contibutor as assigned by the authority named in @contrib-id-type.
Do not use on collaborative contributors.
<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>LA</given-names>
</name>
</contrib>
1.1
Identifier of a contibutor as assigned by the authority named in @contrib-id-type.
Do not use on collaborative contributors.
<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>LA</given-names>
</name>
</contrib>
1.0
Identifier of a contibutor as assigned by the authority named in @contrib-id-type.
Do not use on collaborative contributors.
<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>LA</given-names>
</name>
</contrib>
3.0
Element is not available in this version. See Contributor ID.
2.3
Element is not available in this version. See Contributor ID.
Contains the complete copyright statement as it appears in the source.
The contents will usually be the word "Copyright", a copyright symbol, the copyright year, and the name of the copyright holder. Tag the year of copyright in <copyright-year>, whether or not it appears as part of the <copyright-statement>.
PMC displays the content of <copyright-statement> and does not use other copyright elements to build display content.
Do not include licensing information. See the Licensing Information tagging guidelines for more information.
Must be contained in <permissions>.
Set any label or symbol in the <label> element. Do not create symbols or labels in the XML if they do not exist in the published article. Follow copy for all punctuation.
Tag all non-label content as simple text within the element except for email addresses which should be tagged in <email>.
1.3
Do not include punctuation. Tag references that require punctuation in the XML with <mixed-citation>.
1.2
Do not include punctuation. Tag references that require punctuation in the XML with <mixed-citation>.
1.1
Do not include punctuation. Tag references that require punctuation in the XML with <mixed-citation>.
1.0
Do not include punctuation. Tag references that require punctuation in the XML with <mixed-citation>.
3.0
Do not include punctuation. Tag references that require punctuation in the XML with <mixed-citation>.
2.3
Element is not available in this version. See <citation>.
Use only when article does not have a <fpage>. Used mostly for electronic-only articles.
Used to tag link information to objects outside of the article.
Details on tagging links supported by PMC are under External Links.
See additional rules for usage in <license> under Licensing Information.
attributes:
- ext-link-type—Holds an identifier of the external resource.(#REQUIRED)
- xlink:href—Holds an identifier of or locator to an object available through or at that resource.(#REQUIRED)
1.3
Floating <fig> elements (location in content does not affect meaning) should be tagged at the first reference to the <fig>. Unreferenced floating <fig> elements should be tagged in <floats-group>. All floating <fig> elements should include @position="float". Anchored <fig> elements (location in content does affect meaning) must be tagged with @position="anchor".
1.2
Floating <fig> elements (location in content does not affect meaning) should be tagged at the first reference to the <fig>. Unreferenced floating <fig> elements should be tagged in <floats-group>. All floating <fig> elements should include @position="float". Anchored <fig> elements (location in content does affect meaning) must be tagged with @position="anchor".
1.1
Floating <fig> elements (location in content does not affect meaning) should be tagged at the first reference to the <fig>. Unreferenced floating <fig> elements should be tagged in <floats-group>. All floating <fig> elements should include @position="float". Anchored <fig> elements (location in content does affect meaning) must be tagged with @position="anchor".
1.0
Floating <fig> elements (location in content does not affect meaning) should be tagged at the first reference to the <fig>. Unreferenced floating <fig> elements should be tagged in <floats-group>. All floating <fig> elements should include @position="float". Anchored <fig> elements (location in content does affect meaning) must be tagged with @position="anchor".
3.0
Floating <fig> elements (location in content does not affect meaning) should be tagged at the first reference to the <fig>. Unreferenced floating <fig> elements should be tagged in <floats-group>. All floating <fig> elements should include @position="float". Anchored <fig> elements (location in content does affect meaning) must be tagged with @position="anchor".
2.3
Floating <fig> elements (location in content does not affect meaning) should be tagged at the first reference to the <fig>. Unreferenced floating <fig> elements should be tagged in <floats-wrap>. All floating <fig> elements should include @position="float". Anchored <fig> elements (location in content does affect meaning) must be tagged with @position="anchor".
See Display Object Groups for information on when to use this element.
The first page of the article.
If more than one article shares the same first page, specify @seq. Tag the first article with @seq="a", the second @seq="b", etc. See description of Continuous Makeup Articles.
1.3
Element is not available in this version. See <floats-group>.
1.2
Element is not available in this version. See <floats-group>.
1.1
Element is not available in this version. See <floats-group>.
1.0
Element is not available in this version. See <floats-group>.
3.0
Element is not available in this version. See <floats-group>.
2.3
Tag all unreferenced, floating objects (<fig>, <table-wrap>) in this element with @position="float".
1.3
Tag all unreferenced, floating objects (<fig>, <table-wrap>) in this element with @position="float".
1.2
Tag all unreferenced, floating objects (<fig>, <table-wrap>) in this element with @position="float".
1.1
Tag all unreferenced, floating objects (<fig>, <table-wrap>) in this element with @position="float".
1.0
Tag all unreferenced, floating objects (<fig>, <table-wrap>) in this element with @position="float".
3.0
Tag all unreferenced, floating objects (<fig>, <table-wrap>) in this element with @position="float".
2.3
Element is not available in this version. See <floats-wrap>.
1.3
Tag footnotes specifically relating to contributors in <author-notes>.
Tag footnotes that apply to the article as a whole in <fn-group> in <back>.
For Conflict of Interest Statements captured as footnotes, specify @fn-type="coi-statement" if tagged in the Journal Publishing (Blue) DTD, or @fn-type="COI-statement" if tagged in the Journal Archiving (Green) DTD.
Information concerning grants, contracts, sponsors, or other funding for the research should be captured in <funding-group>.
Tag article Disclaimers as <notes> in the front matter.
Tag keywords in <kwd-group>, not in a footnote.
Tag table footnotes in <table-wrap-foot>.
1.2
Tag footnotes specifically relating to contributors in <author-notes>.
Tag footnotes that apply to the article as a whole in <fn-group> in <back>.
For Conflict of Interest Statements captured as footnotes, specify @fn-type="coi-statement" if tagged in the Journal Publishing (Blue) DTD, or @fn-type="COI-statement" if tagged in the Journal Archiving (Green) DTD.
Information concerning grants, contracts, sponsors, or other funding for the research should be captured in <funding-group>.
Tag article Disclaimers as <notes> in the front matter.
Tag keywords in <kwd-group>, not in a footnote.
Tag table footnotes in <table-wrap-foot>.
1.1
Tag footnotes specifically relating to contributors in <author-notes>.
Tag footnotes that apply to the article as a whole in <fn-group> in <back>.
For Conflict of Interest Statements captured as footnotes, specify @fn-type="conflict" if tagged in the Journal Publishing (Blue) DTD, or @fn-type="COI-statement" if tagged in the Journal Archiving (Green) DTD.
Information concerning grants, contracts, sponsors, or other funding for the research should be captured in <funding-group>.
Tag article Disclaimers as <notes> in the front matter.
Tag keywords in <kwd-group>, not in a footnote.
Tag table footnotes in <table-wrap-foot>.
1.0
Tag footnotes specifically relating to contributors in <author-notes>.
Tag footnotes that apply to the article as a whole in <fn-group> in <back>.
For Conflict of Interest Statements captured as footnotes, specify @fn-type="conflict" if tagged in the Journal Publishing (Blue) DTD, or @fn-type="COI-statement" if tagged in the Journal Archiving (Green) DTD.
Information concerning grants, contracts, sponsors, or other funding for the research should be captured in <funding-group>.
Tag article Disclaimers as <notes> in the front matter.
Tag keywords in <kwd-group>, not in a footnote.
Tag table footnotes in <table-wrap-foot>.
3.0
Tag footnotes specifically relating to contributors in <author-notes>.
Tag footnotes that apply to the article as a whole in <fn-group> in <back>.
For Conflict of Interest Statements captured as footnotes, specify @fn-type="conflict" if tagged in the Journal Publishing (Blue) DTD, or @fn-type="COI-statement" if tagged in the Journal Archiving (Green) DTD.
Information concerning grants, contracts, sponsors, or other funding for the research should be captured in <funding-group>.
Tag article Disclaimers as <notes> in the front matter.
Tag keywords in <kwd-group>, not in a footnote.
Tag table footnotes in <table-wrap-foot>.
2.3
Tag footnotes specifically relating to contributors in <author-notes>.
Tag footnotes that apply to the article as a whole in <fn-group> in <back>.
For Conflict of Interest Statements captured as footnotes, specify @fn-type="conflict" if tagged in the Journal Publishing (Blue) DTD, or @fn-type="COI-statement" if tagged in the Journal Archiving (Green) DTD.
Sponsorship and financial disclosures that apply to the article as a whole must be captured in <fn-group> in <back> with the appropriate @fn-type.
Tag article Disclaimers as <notes> in the front matter.
Tag keywords in <kwd-group>, not in a footnote.
Tag table footnotes in <table-wrap-foot>.
attributes:
- fn-type—Use an appropriate value. Suggested values include, but are not limited to:
Value Meaning "abbr" Abbreviations "supplementary-material" Points to or describes supplementary material for the article "corresp" Corresponding author information not identified separately, but merely footnoted "equal" Contributed equally to the creation of the document "present-address" Contributor's current address - id—(#REQUIRED)
- symbol—Do not use. Capture information in <label>.
<journal-meta> and <article-meta> are required.
1.3
Tag only information about the reported research funding. Do not tag copyright or license information in <funding-group>. Tag multiple <award-group> in a single <funding-group>.
1.2
Tag only information about the reported research funding. Do not tag copyright or license information in <funding-group>. Tag multiple <award-group> in a single <funding-group>.
1.1
Tag only information about the reported research funding. Do not tag copyright or license information in <funding-group>. Tag multiple <award-group> in a single <funding-group>.
1.0
Tag only information about the reported research funding. Do not tag copyright or license information in <funding-group>. Tag multiple <award-group> in a single <funding-group>.
3.0
Tag only information about the reported research funding. Do not tag copyright or license information in <funding-group>. Tag multiple <award-group> in a single <funding-group>.
2.3
Element is not available in this version. See <contract-num>, <contract-sponsor>, <grant-num>, <grant-sponsor>.
1.3
Tag the complete funding statement in this element, regardless of whether or not other elements within the <funding-group> duplicate the information. PMC displays the content of <funding-statement> and does not use other funding elements to build display content.
1.2
Tag the complete funding statement in this element, regardless of whether or not other elements within the <funding-group> duplicate the information. PMC displays the content of <funding-statement> and does not use other funding elements to build display content.
1.1
Tag the complete funding statement in this element, regardless of whether or not other elements within the <funding-group> duplicate the information. PMC displays the content of <funding-statement> and does not use other funding elements to build display content.
1.0
Tag the complete funding statement in this element, regardless of whether or not other elements within the <funding-group> duplicate the information. PMC displays the content of <funding-statement> and does not use other funding elements to build display content.
3.0
Tag the complete funding statement in this element, regardless of whether or not other elements within the <funding-group> duplicate the information. PMC displays the content of <funding-statement> and does not use other funding elements to build display content.
2.3
Element is not available in this version. See <contract-num>, <contract-sponsor>, <grant-num>, <grant-sponsor>.
1.3
Element is not available in this version. See <funding-group>.
1.2
Element is not available in this version. See <funding-group>.
1.1
Element is not available in this version. See <funding-group>.
1.0
Element is not available in this version. See <funding-group>.
3.0
Element is not available in this version. See <funding-group>.
2.3
This element must link to a <contract-sponsor>.
1.3
Element is not available in this version. See <funding-group>.
1.2
Element is not available in this version. See <funding-group>.
1.1
Element is not available in this version. See <funding-group>.
1.0
Element is not available in this version. See <funding-group>.
3.0
Element is not available in this version. See <funding-group>.
2.3
Set <grant-sponsor> only once, even if there are multiple grants listed. It must link to at least one <grant-num>.
Describes an external file containing a still image. Usually contained within <fig>.
Use <inline-graphic> for images appearing in the flow of text.
attributes:
- xlink:href—The name of the file.(#REQUIRED)
Contains one or more <date> elements describing the article's processing history.
Common history dates include received, accepted, and revised.
If an article is put online after the official print publication, capture that within <history> as <date> with @date-type="online". This only applies to journals following the Print-only and Print–Online Coincident models of publication described in <pub-date>.
Received 2021 Dec 22; Revised 2022 Jun 20; Accepted 2022 Aug 9.
<history>
<date date-type="received">
<day>22</day><month>12</month><year>2021</year>
</date>
<date date-type="rev-recd">
<day>20</day><month>6</month><year>2022</year>
</date>
<date date-type="accepted">
<day>9</day><month>8</month><year>2022</year>
</date>
</history>
1.3
Describes supplementary material that must be displayed in the textual flow of an article.
Include the full filename, including file extension, in the @xlink:href value on <inline-supplementary-material>.
1.2
Describes supplementary material that must be displayed in the textual flow of an article.
Include the full filename, including file extension, in the @xlink:href value on <inline-supplementary-material>.
1.1
Describes supplementary material that must be displayed in the textual flow of an article.
Include the full filename, including file extension, in the @xlink:href value on <inline-supplementary-material>.
1.0
Describes supplementary material that must be displayed in the textual flow of an article.
Include the full filename, including file extension, in the @xlink:href value on <inline-supplementary-material>.
3.0
Describes supplementary material that must be displayed in the textual flow of an article.
Include the full filename, including file extension, in the @xlink:href value on <inline-supplementary-material>.
2.3
Element is not available in this version.
1.3
Contains the media-specific (print, electronic) ISSN(s) for the journal. Articles must have at least one <issn>.
Do not use for linking ISSN. See <issn-l>.
<issn pub-type="ppub">0027-8424</issn>
<issn pub-type="epub">1091-6490</issn>
<issn-l>0027-8424</issn-l>
1.2
Contains the media-specific (print, electronic) ISSN(s) for the journal. Articles must have at least one <issn>.
Do not use for linking ISSN. See <issn-l>.
<issn pub-type="ppub">0027-8424</issn>
<issn pub-type="epub">1091-6490</issn>
<issn-l>0027-8424</issn-l>
1.1
Contains the media-specific (print, electronic) ISSN(s) for the journal. Articles must have at least one <issn>.
Do not use for linking ISSN. See <issn-l>.
<issn pub-type="ppub">0027-8424</issn>
<issn pub-type="epub">1091-6490</issn>
<issn-l>0027-8424</issn-l>
1.0
Contains the media-specific (print, electronic) ISSN(s) for the journal. Articles must have at least one <issn>.
Do not use for linking ISSN. See <issn-l>.
<issn pub-type="ppub">0027-8424</issn>
<issn pub-type="epub">1091-6490</issn>
<issn-l>0027-8424</issn-l>
3.0
Contains the ISSN(s) for the journal. Articles must have at least one <issn>.
<issn pub-type="ppub">0027-8424</issn>
<issn pub-type="epub">1091-6490</issn>
2.3
Contains the ISSN(s) for the journal. Articles must have at least one <issn>.
<issn pub-type="ppub">0027-8424</issn>
<issn pub-type="epub">1091-6490</issn>
attributes:
- pub-type—Set as "ppub" for a print ISSN and "epub" for an electronic ISSN. If a journal has both, include two successive <issn> tags.(#REQUIRED)
1.3
Capture only the linking ISSN of the publication. For media-specific ISSNs, use <issn>.
1.2
Capture only the linking ISSN of the publication. For media-specific ISSNs, use <issn>.
1.1
Capture only the linking ISSN of the publication. For media-specific ISSNs, use <issn>.
1.0
Capture only the linking ISSN of the publication. For media-specific ISSNs, use <issn>.
3.0
Element is not available in this version. See <issn>
2.3
Element is not available in this version. See <issn>
Tag numeric issues as an integer only. If Roman numerals are used, tag as the Roman numeral only. Do not include the word "issue" in the tag.
Tag "Part" issues as "Pt [integer]". If the Part or Supplement has no integer, then tag as "Pt" or "Suppl" only.
Do not use <supplement> to identify a supplementary issue in <article-meta>, instead capture as "Suppl [integer]" in <issue>.
If there is no issue number, do not tag at all.
Do not tag more than one issue in <article-meta> or <front-stub>.
Multiple journal-ids may be tagged. Specify type of id in @journal-id-type. If the PubMed abbreviation is available, tag with @journal-id-type="nlm-ta".
attributes:
- journal-id-type—(#REQUIRED)
1.3
Contains all information about the journal.
1.2
Contains all information about the journal.
1.1
Contains all information about the journal.
1.0
Contains all information about the journal.
3.0
Contains all information about the journal.
2.3
Contains all information about the journal.
Contains label information only (Table 1, Figure 1). Does not include <caption> data, such as <title>.
Do not include emphasis that encompasses the entire contents.
Fig 6. JATS to EPUB pipeline.
Graphical representation of the pipeline converting JATS data to EPUB.
<label>Fig 6.</label>
<caption>
<title>JATS to EPUB pipeline.</title>
<p>Graphical representation of the pipeline converting JATS data to EPUB.</p>
</caption>
1.3
Contains Licensing Information for the article. Do not tag Copyright Information in the <license> element.
Must be contained in <permissions>.
Include the license URL in the <ali:license_ref> element. If the license URL is also included in an <ext-link> in the <license-p> element, the URLs must match exactly (case, slashes, etc.). See Licensing Information for additional information.
<permissions>
<copyright-statement>© 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>
1.2
Contains Licensing Information for the article. Do not tag Copyright Information in the <license> element.
Must be contained in <permissions>.
Include the license URL in the <ali:license_ref> element. If the license URL is also included in an <ext-link> in the <license-p> element, the URLs must match exactly (case, slashes, etc.). See Licensing Information for additional information.
<permissions>
<copyright-statement>© 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>
1.1
Contains Licensing Information for the article. Do not tag Copyright Information in the <license> element.
Must be contained in <permissions>.
Include the license URL in the <ali:license_ref> element. If the license URL is also included in an <ext-link> in the <license-p> element, the URLs must match exactly (case, slashes, etc.). See Licensing Information for additional information.
<permissions>
<copyright-statement>© 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>
1.0
Contains Licensing Information for the article. Do not tag Copyright Information in the <license> element.
Must be contained in <permissions>.
Whenever possible, include a URL to identify the license using @xlink:href.
When including a URL for a license, a machine-readable URL must be included in either the <license> in @xlink:href or in an <ext-link> in the content of the <license-p>. If tagged in both places, the URL must match exactly (case, slashes, etc.). See Licensing Information for additional information.
<license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
<license-p>This article is licensed under a
Creative Commons Attribution 4.0 International License, which permits unrestricted use,
distribution, and reproduction in any medium, provided the original
work is properly cited.
</license-p>
</license>
<license license-type="open-access">
<license-p>This work is licensed under a Creative Commons Attribution
3.0 Unported License. To view a copy of this license, visit
<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/3.0/">
https://creativecommons.org/licenses/by/3.0/</ext-link>
</license-p>
</license>
3.0
Contains Licensing Information for the article. Do not tag Copyright Information in the <license> element.
Must be contained in <permissions>.
Whenever possible, include a URL to identify the license using @xlink:href.
When including a URL for a license, a machine-readable URL must be included in either the <license> in @xlink:href or in an <ext-link> in the content of the <license-p>. If tagged in both places, the URL must match exactly (case, slashes, etc.). See Licensing Information for additional information.
<license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
<license-p>This article is licensed under a
Creative Commons Attribution 4.0 International License, which permits unrestricted use,
distribution, and reproduction in any medium, provided the original
work is properly cited.
</license-p>
</license>
<license license-type="open-access">
<license-p>This work is licensed under a Creative Commons Attribution
3.0 Unported License. To view a copy of this license, visit
<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/3.0/">
https://creativecommons.org/licenses/by/3.0/</ext-link>
</license-p>
</license>
2.3
Contains Licensing Information for the article. Do not tag Copyright Information in the <license> element.
Must be contained in <permissions>.
Whenever possible, include a URL to identify the license using @xlink:href.
When including a URL for a license, a machine-readable URL must be included in either the <license> in @xlink:href or in an <ext-link> in the content of the <license>. If tagged in both places, the URL must match exactly (case, slashes, etc.). See Licensing Information for additional information.
<license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
<p>This article is licensed under a
Creative Commons Attribution 4.0 International License, which permits unrestricted use,
distribution, and reproduction in any medium, provided the original
work is properly cited.
</p>
</license>
<license license-type="open-access">
<p>This work is licensed under a Creative Commons Attribution
3.0 Unported License. To view a copy of this license, visit
<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/3.0/">
https://creativecommons.org/licenses/by/3.0/</ext-link>
</p>
</license>
<list> may or may not have a title. It must have one <list-item> for each point in the list.
attributes:
- list-type—Allowed values: "order", "bullet", "alpha-lower", "alpha-upper", "roman-lower", "roman-upper", "simple".(#REQUIRED)
- prefix-word—This is for a word that should prefix the generated label in the list, e.g. "Step".
The numeric last page of the article. Tag the value even if it is the same as the first page.
Describes an external file containing a media object.
attributes:
- xlink:href—The name of the file, including file extension(#REQUIRED)
- mimetype—Media type, such as video or application. Omit if the value is unknown.
- mime-subtype—Media subtype, such as pdf, xls, or mp4. Omit if the value is unknown.
1.3
Maintain all punctuation from the original copy. Tag a minimum of the following tags if they are part of the original citation: <name> of the author, editor, etc.; <source>; <year>; pagination; DOI.
1.2
Maintain all punctuation from the original copy. Tag a minimum of the following tags if they are part of the original citation: <name> of the author, editor, etc.; <source>; <year>; pagination; DOI.
1.1
Maintain all punctuation from the original copy. Tag a minimum of the following tags if they are part of the original citation: <name> of the author, editor, etc.; <source>; <year>; pagination; DOI.
1.0
Maintain all punctuation from the original copy. Tag a minimum of the following tags if they are part of the original citation: <name> of the author, editor, etc.; <source>; <year>; pagination; DOI.
3.0
Maintain all punctuation from the original copy. Tag a minimum of the following tags if they are part of the original citation: <name> of the author, editor, etc.; <source>; <year>; pagination; DOI.
2.3
Element is not available in this version. See <citation>.
<mml:math> is the root element for MathML.
Breaking long formulas
Do not set long formulas in <mml:mtable> just to get them to break. Capture potential or desired breaks with <mml:mspace linebreak="newline"/>. Do not use @linebreak="goodbreak". If the formula was broken in a print version, enter a <mml:mspace linebreak="newline"/> at that point, and the break will be used if necessary during rendering.
Subscripts and Superscripts with 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: ] } ) 〉 〉 ⟩ .
(x + y)2
Correct Tagging (where the 2 is superscript to the entire expression):
<mml:math>
<mml:msup>
<mml:mrow>
<mml:mo>(</mml:mo>
<mml:mi>x</mml:mi>
<mml:mo>+</mml:mo>
<mml:mi>y</mml:mi>
<mml:mo>)</mml:mo>
</mml:mrow>
<mml:mn>2</mml:mn>
</mml:msup>
</mml:math>
Incorrect Tagging:
<mml:math>
<mml:mo>(</mml:mo>
<mml:mi>x</mml:mi>
<mml:mo>+</mml:mo>
<mml:mi>y</mml:mi>
<mml:msup>
<mml:mo>)</mml:mo>
<mml:mn>2</mml:mn>
</mml:msup>
</mml:math>
Child Element Restrictions:
These elements require exactly 2 child elements. If either of the sub-expressions is complex, wrap it in an <mml:mrow>.
- <mml:mfrac> — the first child is the numerator, the second the denominator.
- <mml:mroot> — the first child is the base, the second is the index.
- <mml:msub> — the first child is the base, the second is the subscript expression.
- <mml:msup> — the first child is the base, the second is the superscript expression.
- <mml:munder> — the first child is the base, the second is the underscript.
- <mml:mover> — the first child is the base, the second is the overscript.
These elements require exactly 3 child elements. If any of the sub-expressions is complex, wrap it in an <mml:mrow>.
- <mml:munderover> — the first child is the base, the second is the underscript, the third is the overscript.
- <mml:msubsup> — the first child is the base, the second is the subscript expression, the third is the superscript expression. The subscript and superscript will be stacked.
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:
Only the following values are allowed for this attribute: ( normal | bold | italic | bold-italic | double-struck | bold-fraktur | script | bold-script | fraktur | sans-serif | bold-sans-serif | sans-serif-italic | sans-serif-bold-italic | monospace )
@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 )
attributes:
- id—(#REQUIRED)
Must be an integer from 1 to 12.
Tag any month range (January-March) as a <season>.
1.3
Use when tagging a single name in multiple languages or forms.
<contrib contrib-type="author">
<name-alternatives>
<name>
<surname>Canut Jordana</surname>
<given-names>M Isabel</given-names>
</name>
<name content-type="index">
<surname>Canut</surname>
<given-names>MI</given-names>
</name>
</name-alternatives>
</contrib>
<name-alternatives>
<name name-style="eastern" xml:lang="ja-Jpan">
<surname>中西</surname>
<given-names>秀彦</given-names>
</name>
<name name-style="western" xml:lang="en">
<surname>Nakanishi</surname>
<given-names>Hidehiko</given-names>
</name>
<name name-style="eastern" xml:lang="ja-Kana">
<surname>ナカニシ</surname>
<given-names>ヒデヒコ</given-names>
</name>
</name-alternatives>
1.2
Use when tagging a single name in multiple languages or forms.
<contrib contrib-type="author">
<name-alternatives>
<name>
<surname>Canut Jordana</surname>
<given-names>M Isabel</given-names>
</name>
<name content-type="index">
<surname>Canut</surname>
<given-names>MI</given-names>
</name>
</name-alternatives>
</contrib>
<name-alternatives>
<name name-style="eastern" xml:lang="ja-Jpan">
<surname>中西</surname>
<given-names>秀彦</given-names>
</name>
<name name-style="western" xml:lang="en">
<surname>Nakanishi</surname>
<given-names>Hidehiko</given-names>
</name>
<name name-style="eastern" xml:lang="ja-Kana">
<surname>ナカニシ</surname>
<given-names>ヒデヒコ</given-names>
</name>
</name-alternatives>
1.1
Use when tagging a single name in multiple languages or forms.
<contrib contrib-type="author">
<name-alternatives>
<name>
<surname>Canut Jordana</surname>
<given-names>M Isabel</given-names>
</name>
<name content-type="index">
<surname>Canut</surname>
<given-names>MI</given-names>
</name>
</name-alternatives>
</contrib>
<name-alternatives>
<name name-style="eastern" xml:lang="ja-Jpan">
<surname>中西</surname>
<given-names>秀彦</given-names>
</name>
<name name-style="western" xml:lang="en">
<surname>Nakanishi</surname>
<given-names>Hidehiko</given-names>
</name>
<name name-style="eastern" xml:lang="ja-Kana">
<surname>ナカニシ</surname>
<given-names>ヒデヒコ</given-names>
</name>
</name-alternatives>
1.0
Use when tagging a single name in multiple languages or forms.
<contrib contrib-type="author">
<name-alternatives>
<name>
<surname>Canut Jordana</surname>
<given-names>M Isabel</given-names>
</name>
<name content-type="index">
<surname>Canut</surname>
<given-names>MI</given-names>
</name>
</name-alternatives>
</contrib>
<name-alternatives>
<name name-style="eastern" xml:lang="ja-Jpan">
<surname>中西</surname>
<given-names>秀彦</given-names>
</name>
<name name-style="western" xml:lang="en">
<surname>Nakanishi</surname>
<given-names>Hidehiko</given-names>
</name>
<name name-style="eastern" xml:lang="ja-Kana">
<surname>ナカニシ</surname>
<given-names>ヒデヒコ</given-names>
</name>
</name-alternatives>
3.0
Element is not available in this version.
2.3
Element is not available in this version.
Used for article-level notes. These often appear at the beginning or end of the article.
Tag notes relating to the author(s) in <author-notes>.
Tag article Disclaimers as <notes> in the front matter.
Tag Notes in Proof as <notes> in the back matter.
attributes:
- notes-type—Set as "disclaimer" for article Disclaimers. Set as "note-in-proof" for Notes in Proof.
Used when a contributor is participating as a representative of an organization. Do not confuse with <collab>.
Rodrigo Teresa, Joan A Caylà, and Martí Casals for the Working Group on Completion of Tuberculosis Treatment in Spain
<contrib-group>
<contrib contrib-type="author" corresp="yes" id="A1">
<name>
<surname>Rodrigo</surname>
<given-names>Teresa</given-names>
</name>
</contrib>
<contrib contrib-type="author" id="A2">
<name>
<surname>Caylà</surname>
<given-names>Joan A</given-names>
</name>
</contrib>
<contrib contrib-type="author" id="A3">
<name>
<surname>Casals</surname>
<given-names>Martí</given-names>
</name>
</contrib>
<on-behalf-of>Working Group on Completion of Tuberculosis Treatment in Spain</on-behalf-of>
</contrib-group>
1.3
Used to hold text describing funding used to pay any open access fees associated with the article's publication. Do not include the license text (see <license>).
1.2
Used to hold text describing funding used to pay any open access fees associated with the article's publication. Do not include the license text (see <license>).
1.1
Used to hold text describing funding used to pay any open access fees associated with the article's publication. Do not include the license text (see <license>).
1.0
Used to hold text describing funding used to pay any open access fees associated with the article's publication. Do not include the license text (see <license>).
3.0
Used to hold text describing funding used to pay any open access fees associated with the article's publication. Do not include the license text (see <license>).
2.3
Element is not available in this version.
Tag the citation information of the product as completely as possible. Tag information that cannot be described by elements in a <comment>. Tag associated images (book covers, for example) with <inline-graphic> within <product>.
See Book Reviews and Product Reviews for additional information.
1.3
Tag only one publication date per <pub-date> element.
Articles cannot have more than one <pub-date> with the same combination of @date-type and @publication-format.
Any article with a specified @date-type="collection" must also have one <pub-date> with @date-type="pub" and @publication-format="electronic". Epub dates must contain a <day>, <month>, and <year>.
The most common @publication-format values are "electronic" and "print"; the most common @date-type values are "pub" and "collection". When an article is published in more than one medium, there will be more than one <pub-date>. The number and types of tagged <pub-date> elements depends on the publication model of the journal.
There are two basic classes of publication: issue-based publication and article-based publication.
- Issue-based publication is when an entire issue is "published" at one time — in print, online, or both. Issue publication dates and article publication dates coincide, so the issue publication date is all that is needed.
- Article-based publication is when articles are "published" individually or in small groups. They may be published in Issues (e.g. all of the articles published online in June 2005 are in the "June" issue) which may or may not be printed. Even if the articles are not collected in Issues, they are collected in some way - perhaps by random collection dates, by volume, or by year. This "collection" date usually does not coincide with the article publication date.
Here are several examples of publishing models and their corresponding publication dates.
Print-only Model — This is the traditional print model. Articles are collected by the editor, formed into issues, and published an issue-worth at a time. All articles have the same publication date, which coincides with the Issue cover date. For this model, each article will have <pub-date> with @date-type="pub" and @publication-format="print". In this model, the issues may go "online" the same day as the print date or sometime thereafter, but the official publication date is controlled by the Issue cover date.
Print–Online Coincident Model — This is a similar model to the Print-only Model, except there is a little more emphasis on the fact that the online version of the issue is published on the same date. For this model, each article will have <pub-date> with @date-type="pub" and @publication-format="electronic-print".
Print with Electronic Articles Prepublished Model — In this model, some or all of the articles are published (their official publication date) online before the publication date of the print issue. For this model, each prepublished article will have <pub-date> with @pub-type="epub" to represent its individual online publication date, and every article will have a <pub-date> with @date-type="pub" and @publication-format="print" to represent the printed issue date.
Print with Electronic "Preprints" — This is similar to the "Print with Electronic Articles Prepublished Model" where articles from an issue appear online before the publication date of the issue. The difference, however, is that the online versions of the articles are electronic preprints and are not officially published. All of the articles are published on the issue cover date, and they all have the same publication date. For this model, each preprint article will have <pub-date> with @date-type="preprint" and @publication-format="electronic" to represent date it was available online, and every article will have a <pub-date> with @date-type="pub" and @publication-format="print" to represent the printed issue date.
Articles Published Online and Collected into Print Issues Model — For this model, each article will have <pub-date> with @date-type="pub" and @publication-format="electronic" to represent its individual publication date and a <pub-date> with @date-type="pub" and @publication-format="print" to represent publication date of the print issue.
Articles Published Online and Collected into "Issues" Online Model — Issues here do not need to be named "Issue 1", "Issue 2", etc. These are just collections of articles online. The collecting might be done by dates (Months, Quarters, Years) or by Volume. For this model, each article will have <pub-date> with @date-type="pub" and @publication-format="electronic" to represent its individual publication date and a <pub-date> with @date-type="collection" and @publication-format="electronic" to represent the date of the online collection it belongs in. This date may be a day/month/year, month/year, season/year, or just year.
<pub-date date-type="pub" publication-format="electronic">
<day>1</day>
<month>1</month
<year>2013</year>
</pub-date>
<pub-date date-type="collection" publication-format="electronic">
<month>1</month>
<year>2013</year>
</pub-date>
<pub-date date-type="pub" publication-format="print">
<day>1</day>
<month>1</month>
<year>2013</year>
</pub-date>
attributes:
- date-type—Must be used with @publication-format; suggested values include "pub", "corrected", "retracted", "preprint". Must not be used with @pub-type.
- publication-format—Must be used with @date-type; values include "print", "electronic", or "electronic-print". Must not be used with @pub-type.
1.2
Tag only one publication date per <pub-date> element.
Articles cannot have more than one <pub-date> with the same combination of @date-type and @publication-format.
Any article with a specified @date-type="collection" must also have one <pub-date> with @date-type="pub" and @publication-format="electronic". Epub dates must contain a <day>, <month>, and <year>.
The most common @publication-format values are "electronic" and "print"; the most common @date-type values are "pub" and "collection". When an article is published in more than one medium, there will be more than one <pub-date>. The number and types of tagged <pub-date> elements depends on the publication model of the journal.
There are two basic classes of publication: issue-based publication and article-based publication.
- Issue-based publication is when an entire issue is "published" at one time — in print, online, or both. Issue publication dates and article publication dates coincide, so the issue publication date is all that is needed.
- Article-based publication is when articles are "published" individually or in small groups. They may be published in Issues (e.g. all of the articles published online in June 2005 are in the "June" issue) which may or may not be printed. Even if the articles are not collected in Issues, they are collected in some way - perhaps by random collection dates, by volume, or by year. This "collection" date usually does not coincide with the article publication date.
Here are several examples of publishing models and their corresponding publication dates.
Print-only Model — This is the traditional print model. Articles are collected by the editor, formed into issues, and published an issue-worth at a time. All articles have the same publication date, which coincides with the Issue cover date. For this model, each article will have <pub-date> with @date-type="pub" and @publication-format="print". In this model, the issues may go "online" the same day as the print date or sometime thereafter, but the official publication date is controlled by the Issue cover date.
Print–Online Coincident Model — This is a similar model to the Print-only Model, except there is a little more emphasis on the fact that the online version of the issue is published on the same date. For this model, each article will have <pub-date> with @date-type="pub" and @publication-format="electronic-print".
Print with Electronic Articles Prepublished Model — In this model, some or all of the articles are published (their official publication date) online before the publication date of the print issue. For this model, each prepublished article will have <pub-date> with @pub-type="epub" to represent its individual online publication date, and every article will have a <pub-date> with @date-type="pub" and @publication-format="print" to represent the printed issue date.
Print with Electronic "Preprints" — This is similar to the "Print with Electronic Articles Prepublished Model" where articles from an issue appear online before the publication date of the issue. The difference, however, is that the online versions of the articles are electronic preprints and are not officially published. All of the articles are published on the issue cover date, and they all have the same publication date. For this model, each preprint article will have <pub-date> with @date-type="preprint" and @publication-format="electronic" to represent date it was available online, and every article will have a <pub-date> with @date-type="pub" and @publication-format="print" to represent the printed issue date.
Articles Published Online and Collected into Print Issues Model — For this model, each article will have <pub-date> with @date-type="pub" and @publication-format="electronic" to represent its individual publication date and a <pub-date> with @date-type="pub" and @publication-format="print" to represent publication date of the print issue.
Articles Published Online and Collected into "Issues" Online Model — Issues here do not need to be named "Issue 1", "Issue 2", etc. These are just collections of articles online. The collecting might be done by dates (Months, Quarters, Years) or by Volume. For this model, each article will have <pub-date> with @date-type="pub" and @publication-format="electronic" to represent its individual publication date and a <pub-date> with @date-type="collection" and @publication-format="electronic" to represent the date of the online collection it belongs in. This date may be a day/month/year, month/year, season/year, or just year.
<pub-date date-type="pub" publication-format="electronic">
<day>1</day>
<month>1</month
<year>2013</year>
</pub-date>
<pub-date date-type="collection" publication-format="electronic">
<month>1</month>
<year>2013</year>
</pub-date>
<pub-date date-type="pub" publication-format="print">
<day>1</day>
<month>1</month>
<year>2013</year>
</pub-date>
attributes:
- date-type—Must be used with @publication-format; suggested values include "pub", "corrected", "retracted", "preprint". Must not be used with @pub-type.
- publication-format—Must be used with @date-type; values include "print", "electronic", or "electronic-print". Must not be used with @pub-type.
1.1
Tag only one publication date per <pub-date> element.
Articles cannot have more than one <pub-date> with the same combination of @date-type and @publication-format.
Any article with a specified @date-type="collection" must also have one <pub-date> with @date-type="pub" and @publication-format="electronic". Epub dates must contain a <day>, <month>, and <year>.
The most common @publication-format values are "electronic" and "print"; the most common @date-type values are "pub" and "collection". When an article is published in more than one medium, there will be more than one <pub-date>. The number and types of tagged <pub-date> elements depends on the publication model of the journal.
There are two basic classes of publication: issue-based publication and article-based publication.
- Issue-based publication is when an entire issue is "published" at one time — in print, online, or both. Issue publication dates and article publication dates coincide, so the issue publication date is all that is needed.
- Article-based publication is when articles are "published" individually or in small groups. They may be published in Issues (e.g. all of the articles published online in June 2005 are in the "June" issue) which may or may not be printed. Even if the articles are not collected in Issues, they are collected in some way - perhaps by random collection dates, by volume, or by year. This "collection" date usually does not coincide with the article publication date.
Here are several examples of publishing models and their corresponding publication dates.
Print-only Model — This is the traditional print model. Articles are collected by the editor, formed into issues, and published an issue-worth at a time. All articles have the same publication date, which coincides with the Issue cover date. For this model, each article will have <pub-date> with @date-type="pub" and @publication-format="print". In this model, the issues may go "online" the same day as the print date or sometime thereafter, but the official publication date is controlled by the Issue cover date.
Print–Online Coincident Model — This is a similar model to the Print-only Model, except there is a little more emphasis on the fact that the online version of the issue is published on the same date. For this model, each article will have <pub-date> with @date-type="pub" and @publication-format="electronic-print".
Print with Electronic Articles Prepublished Model — In this model, some or all of the articles are published (their official publication date) online before the publication date of the print issue. For this model, each prepublished article will have <pub-date> with @pub-type="epub" to represent its individual online publication date, and every article will have a <pub-date> with @date-type="pub" and @publication-format="print" to represent the printed issue date.
Print with Electronic "Preprints" — This is similar to the "Print with Electronic Articles Prepublished Model" where articles from an issue appear online before the publication date of the issue. The difference, however, is that the online versions of the articles are electronic preprints and are not officially published. All of the articles are published on the issue cover date, and they all have the same publication date. For this model, each preprint article will have <pub-date> with @date-type="preprint" and @publication-format="electronic" to represent date it was available online, and every article will have a <pub-date> with @date-type="pub" and @publication-format="print" to represent the printed issue date.
Articles Published Online and Collected into Print Issues Model — For this model, each article will have <pub-date> with @date-type="pub" and @publication-format="electronic" to represent its individual publication date and a <pub-date> with @date-type="pub" and @publication-format="print" to represent publication date of the print issue.
Articles Published Online and Collected into "Issues" Online Model — Issues here do not need to be named "Issue 1", "Issue 2", etc. These are just collections of articles online. The collecting might be done by dates (Months, Quarters, Years) or by Volume. For this model, each article will have <pub-date> with @date-type="pub" and @publication-format="electronic" to represent its individual publication date and a <pub-date> with @date-type="collection" and @publication-format="electronic" to represent the date of the online collection it belongs in. This date may be a day/month/year, month/year, season/year, or just year.
<pub-date date-type="pub" publication-format="electronic">
<day>1</day>
<month>1</month
<year>2013</year>
</pub-date>
<pub-date date-type="collection" publication-format="electronic">
<month>1</month>
<year>2013</year>
</pub-date>
<pub-date date-type="pub" publication-format="print">
<day>1</day>
<month>1</month>
<year>2013</year>
</pub-date>
attributes:
- date-type—Must be used with @publication-format; suggested values include "pub", "corrected", "retracted", "preprint". Must not be used with @pub-type.
- publication-format—Must be used with @date-type; values include "print", "electronic", or "electronic-print". Must not be used with @pub-type.
1.0
Tag only one publication date per <pub-date> element.
Articles cannot have more than one <pub-date> with the same combination of @date-type and @publication-format.
Any article with a specified @date-type="collection" must also have one <pub-date> with @date-type="pub" and @publication-format="electronic". Epub dates must contain a <day>, <month>, and <year>.
The most common @publication-format values are "electronic" and "print"; the most common @date-type values are "pub" and "collection". When an article is published in more than one medium, there will be more than one <pub-date>. The number and types of tagged <pub-date> elements depends on the publication model of the journal.
There are two basic classes of publication: issue-based publication and article-based publication.
- Issue-based publication is when an entire issue is "published" at one time — in print, online, or both. Issue publication dates and article publication dates coincide, so the issue publication date is all that is needed.
- Article-based publication is when articles are "published" individually or in small groups. They may be published in Issues (e.g. all of the articles published online in June 2005 are in the "June" issue) which may or may not be printed. Even if the articles are not collected in Issues, they are collected in some way - perhaps by random collection dates, by volume, or by year. This "collection" date usually does not coincide with the article publication date.
Here are several examples of publishing models and their corresponding publication dates.
Print-only Model — This is the traditional print model. Articles are collected by the editor, formed into issues, and published an issue-worth at a time. All articles have the same publication date, which coincides with the Issue cover date. For this model, each article will have <pub-date> with @date-type="pub" and @publication-format="print". In this model, the issues may go "online" the same day as the print date or sometime thereafter, but the official publication date is controlled by the Issue cover date.
Print–Online Coincident Model — This is a similar model to the Print-only Model, except there is a little more emphasis on the fact that the online version of the issue is published on the same date. For this model, each article will have <pub-date> with @date-type="pub" and @publication-format="electronic-print".
Print with Electronic Articles Prepublished Model — In this model, some or all of the articles are published (their official publication date) online before the publication date of the print issue. For this model, each prepublished article will have <pub-date> with @pub-type="epub" to represent its individual online publication date, and every article will have a <pub-date> with @date-type="pub" and @publication-format="print" to represent the printed issue date.
Print with Electronic "Preprints" — This is similar to the "Print with Electronic Articles Prepublished Model" where articles from an issue appear online before the publication date of the issue. The difference, however, is that the online versions of the articles are electronic preprints and are not officially published. All of the articles are published on the issue cover date, and they all have the same publication date. For this model, each preprint article will have <pub-date> with @date-type="preprint" and @publication-format="electronic" to represent date it was available online, and every article will have a <pub-date> with @date-type="pub" and @publication-format="print" to represent the printed issue date.
Articles Published Online and Collected into Print Issues Model — For this model, each article will have <pub-date> with @date-type="pub" and @publication-format="electronic" to represent its individual publication date and a <pub-date> with @date-type="pub" and @publication-format="print" to represent publication date of the print issue.
Articles Published Online and Collected into "Issues" Online Model — Issues here do not need to be named "Issue 1", "Issue 2", etc. These are just collections of articles online. The collecting might be done by dates (Months, Quarters, Years) or by Volume. For this model, each article will have <pub-date> with @date-type="pub" and @publication-format="electronic" to represent its individual publication date and a <pub-date> with @date-type="collection" and @publication-format="electronic" to represent the date of the online collection it belongs in. This date may be a day/month/year, month/year, season/year, or just year.
<pub-date date-type="pub" publication-format="electronic">
<day>1</day>
<month>1</month
<year>2013</year>
</pub-date>
<pub-date date-type="collection" publication-format="electronic">
<month>1</month>
<year>2013</year>
</pub-date>
<pub-date date-type="pub" publication-format="print">
<day>1</day>
<month>1</month>
<year>2013</year>
</pub-date>
attributes:
- date-type—Must be used with @publication-format; suggested values include "pub", "corrected", "retracted", "preprint". Must not be used with @pub-type.
- publication-format—Must be used with @date-type; values include "print", "electronic", or "electronic-print". Must not be used with @pub-type.
3.0
Tag only one publication date per <pub-date> element.
Articles cannot have more than one <pub-date> with the same @pub-type.
Any article with a specified @pub-type="collection" must also have one <pub-date> with @pub-type="epub". Epub dates must contain a <day>, <month>, and <year>.
The most common @pub-type values are "epub", "ppub", "epub-ppub", "epreprint", and "collection". When an article is published in more than one medium, there will be more than one <pub-date>. The number and types of tagged <pub-date> elements depends on the publication model of the journal.
There are two basic classes of publication: issue-based publication and article-based publication.
- Issue-based publication is when an entire issue is "published" at one time — in print, online, or both. Issue publication dates and article publication dates coincide, so the issue publication date is all that is needed.
- Article-based publication is when articles are "published" individually or in small groups. They may be published in Issues (e.g. all of the articles published online in June 2005 are in the "June" issue) which may or may not be printed. Even if the articles are not collected in Issues, they are collected in some way - perhaps by random collection dates, by volume, or by year. This "collection" date usually does not coincide with the article publication date.
Here are several examples of publishing models and their corresponding publication dates.
Print-only Model — This is the traditional print model. Articles are collected by the editor, formed into issues, and published an issue-worth at a time. All articles have the same publication date, which coincides with the Issue cover date. For this model, each article will have <pub-date> with @pub-type="ppub". In this model, the issues may go "online" the same day as the print date or sometime thereafter, but the official publication date is controlled by the Issue cover date.
Print–Online Coincident Model — This is a similar model to the Print-only Model, except there is a little more emphasis on the fact that the online version of the issue is published on the same date. For this model, each article will have <pub-date> with @pub-type="epub-ppub".
Print with Electronic Articles Prepublished Model — In this model, some or all of the articles are published (their official publication date) online before the publication date of the print issue. For this model, each prepublished article will have <pub-date> with @pub-type="epub" to represent its individual online publication date, and every article will have a <pub-date> with @pub-type="ppub" to represent the printed issue date.
Print with Electronic "Preprints" — This is similar to the "Print with Electronic Articles Prepublished Model" where articles from an issue appear online before the publication date of the issue. The difference, however, is that the online versions of the articles are electronic preprints and are not officially published. All of the articles are published on the issue cover date, and they all have the same publication date. For this model, each preprint article will have <pub-date> with @pub-type="epreprint" to represent date it was available online, and every article will have a <pub-date> with @pub-type="ppub" to represent the printed issue date.
Articles Published Online and Collected into Print Issues Model — For this model, each article will have <pub-date> with @pub-type="epub" to represent its individual publication date and a <pub-date> with @pub-type="ppub" to represent publication date of the print issue.
Articles Published Online and Collected into "Issues" Online Model — Issues here do not need to be named "Issue 1", "Issue 2", etc. These are just collections of articles online. The collecting might be done by dates (Months, Quarters, Years) or by Volume. For this model, each article will have <pub-date> with @pub-type="epub" to represent its individual publication date and a <pub-date> with @pub-type="collection" to represent the date of the online collection it belongs in. This date may be a day/month/year, month/year, season/year, or just year.
<pub-date pub-type="epub">
<day>1</day>
<month>1</month>
<year>2013</year>
</pub-date>
<pub-date pub-type="collection">
<month>1</month>
<year>2013</year>
</pub-date>
attributes:
- pub-type—The values depend on the model of publication used. See above for details.
2.3
Tag only one publication date per <pub-date> element.
Articles cannot have more than one <pub-date> with the same @pub-type.
Any article with a specified @pub-type="collection" must also have one <pub-date> with @pub-type="epub". Epub dates must contain a <day>, <month>, and <year>.
The most common @pub-type values are "epub", "ppub", "epub-ppub", "epreprint", and "collection". When an article is published in more than one medium, there will be more than one <pub-date>. The number and types of tagged <pub-date> elements depends on the publication model of the journal.
There are two basic classes of publication: issue-based publication and article-based publication.
- Issue-based publication is when an entire issue is "published" at one time — in print, online, or both. Issue publication dates and article publication dates coincide, so the issue publication date is all that is needed.
- Article-based publication is when articles are "published" individually or in small groups. They may be published in Issues (e.g. all of the articles published online in June 2005 are in the "June" issue) which may or may not be printed. Even if the articles are not collected in Issues, they are collected in some way - perhaps by random collection dates, by volume, or by year. This "collection" date usually does not coincide with the article publication date.
Here are several examples of publishing models and their corresponding publication dates.
Print-only Model — This is the traditional print model. Articles are collected by the editor, formed into issues, and published an issue-worth at a time. All articles have the same publication date, which coincides with the Issue cover date. For this model, each article will have <pub-date> with @pub-type="ppub". In this model, the issues may go "online" the same day as the print date or sometime thereafter, but the official publication date is controlled by the Issue cover date.
Print–Online Coincident Model — This is a similar model to the Print-only Model, except there is a little more emphasis on the fact that the online version of the issue is published on the same date. For this model, each article will have <pub-date> with @pub-type="epub-ppub".
Print with Electronic Articles Prepublished Model — In this model, some or all of the articles are published (their official publication date) online before the publication date of the print issue. For this model, each prepublished article will have <pub-date> with @pub-type="epub" to represent its individual online publication date, and every article will have a <pub-date> with @pub-type="ppub" to represent the printed issue date.
Print with Electronic "Preprints" — This is similar to the "Print with Electronic Articles Prepublished Model" where articles from an issue appear online before the publication date of the issue. The difference, however, is that the online versions of the articles are electronic preprints and are not officially published. All of the articles are published on the issue cover date, and they all have the same publication date. For this model, each preprint article will have <pub-date> with @pub-type="epreprint" to represent date it was available online, and every article will have a <pub-date> with @pub-type="ppub" to represent the printed issue date.
Articles Published Online and Collected into Print Issues Model — For this model, each article will have <pub-date> with @pub-type="epub" to represent its individual publication date and a <pub-date> with @pub-type="ppub" to represent publication date of the print issue.
Articles Published Online and Collected into "Issues" Online Model — Issues here do not need to be named "Issue 1", "Issue 2", etc. These are just collections of articles online. The collecting might be done by dates (Months, Quarters, Years) or by Volume. For this model, each article will have <pub-date> with @pub-type="epub" to represent its individual publication date and a <pub-date> with @pub-type="collection" to represent the date of the online collection it belongs in. This date may be a day/month/year, month/year, season/year, or just year.
<pub-date pub-type="epub">
<day>1</day>
<month>1</month>
<year>2013</year>
</pub-date>
<pub-date pub-type="collection">
<month>1</month>
<year>2013</year>
</pub-date>
attributes:
- pub-type—The values depend on the model of publication used. See above for details.
<ref-list> contains a set of references (<ref>). It may or may not have a title.
1.3
<ref> contains a reference of some kind. It will usually contain a single <mixed-citation> or <element-citation>; however, complex References may contain multiple citations or a combination of text and citations.
See References for details on complex references.
1.2
<ref> contains a reference of some kind. It will usually contain a single <mixed-citation> or <element-citation>; however, complex References may contain multiple citations or a combination of text and citations.
See References for details on complex references.
1.1
<ref> contains a reference of some kind. It will usually contain a single <mixed-citation> or <element-citation>; however, complex References may contain multiple citations or a combination of text and citations.
See References for details on complex references.
1.0
<ref> contains a reference of some kind. It will usually contain a single <mixed-citation> or <element-citation>; however, complex References may contain multiple citations or a combination of text and citations.
See References for details on complex references.
3.0
<ref> contains a reference of some kind. It will usually contain a single <mixed-citation> or <element-citation>; however, complex References may contain multiple citations or a combination of text and citations.
See References for details on complex references.
2.3
<ref> contains a reference of some kind. It will usually contain a single <citation> or <nlm-citation>; however, complex References may contain multiple citations or a combination of text and citations.
See References for details on complex references.
Use to point to another article and to describe the relationship. The element's attribute values specify the related article's citation information so that it can be uniquely identified. The described article must not be the article containing this tag. If the related article has a DOI, it is strongly recommended that the DOI be specified. When specifying a DOI, tag the DOI value in @xlink:href and specify @ext-link-type="doi". The element may be empty.
PMC uses a controlled list of values in @related-article-type, such as "corrected-article" or "letter" to describe the relationships between the article being tagged and the related article. The value of @related-article-type must always describe the type of article being pointed to. For example, a correction notice uses the @related-article-type="corrected-article" to point to the article being corrected.
Note: PMC automatically generates a reciprocal link from the related article to the article containing the <related-article> element for most @related-article-type values, so it isn't necessary to tag a <related-article> in both the article and its related article.
| @related-article-type | Use to: | Notes |
|---|---|---|
| "addended-article" | point from an addendum to the original article | Only allowed when the @article-type is "addendum". |
| "alt-language" | point to the same article published in a different language | |
| "article-reference" | point to an article referenced by the current article | For relationships not categorized by another type and not requiring a reciprocal link. Do not use this for letters or editorials, see commentary-article below. |
| "author-comment" | point to an author comment in response to a peer review report | Use when @article-type is "research-article" or "reviewer-report". |
| "commentary-article" | point from an article-commentary to the article being commented upon | Used for commentaries, editorials, and letters that comment on a specific article. |
| "companion" | point to a companion article | For relationships not categorized by another type and requiring a reciprocal link. |
| "concurrent-pub" | point to the same article published in another title at the same time | |
| "corrected-article" | point from a correction to the original article | Only allowed when the @article-type is "correction". |
| "data-paper" | point to a paper that describes the data in this article | |
| "editor-report" | point to an editor's decision letter | Use when @article-type is "research-article" or "author-comment". |
| "letter" | point from a reply to a letter | Only use when the <article> is a direct reply to the specified letter. |
| "object-of-concern" | point from an expression of concern to the original article | Only allowed when @article-type is "expression-of-concern". |
| "preprint" | point from a published article to a preprint of it | |
| "published-article" | point from a preprint to the published article | |
| "reprinted-article" | point from a reprint to the original article | See Reprints and Republications. |
| "republished-article" | point from a republished article to the original article | See Reprints and Republications. |
| "retracted-article" | point from a retraction to the original article | Only allowed when the @article-type is "retraction". |
| "reviewed-article" | point to the article being peer reviewed, e.g. a research article | Use when @article-type is "reviewer-report", "editor-report", "community-comment", "aggregated-review-documents". |
| "reviewer-report" | point to a peer review report | Use when @article-type is "research-article" or "author-comment". |
| "updated-article" | point from an update to the original article |
Correction notice pointing to the corrected article:
<related-article id="ra1" xlink:href="10.1111/agc.123" ext-link-type="doi"
related-article-type="corrected-article"/>
An article-commentary, letter, or editorial pointing to the article on which it comments:
<related-article id="ls132" journal-id="Front Syst Neurosci" journal-id-type="nlm-ta"
vol="3" page="123" related-article-type="commentary-article"/>
attributes:
- related-article-type—Value describes the type of article being pointed to. Only use a value listed in the table above.(#REQUIRED)
- ext-link-type—Required if @xlink:href is specified. Use "doi" if @xlink:href value is a DOI. Use "pubmed" if @xlink:href value is a PubMed ID. Use "pmcid" if @xlink:href value is a PubMed Central ID.
- journal-id—Identifier for the journal containing the <related-article>
- journal-id-type—Example: "nlm-ta" for PubMed title abbreviation. Required if @journal-id is specified.
- id—(#REQUIRED)
- vol—Specify the volume number of the related article
- issue—Specify the issue number of the related article.
- page—Include only the first page of the related article
- elocation-id—Include when the related article uses <elocation-id> in lieu of <first-page> and <last-page>
- xlink:href—May include target article's identifier (DOI, PubMed ID, PubMed Central ID). If specified, @ext-link-type is required.
1.3
Use this tag to identify related objects. May be used to identify journal articles and Clinical Trials.
Use this element's attributes to identify the target object citation. The following objects must always exist together:
- @source-id and @source-id-type
- @document-id and @document-id-type
- @object-id and @object-id-type
Specify the type of target object for the most specific unit. For example, if the <related-object> is a table in a chapter of a book, the table is the most specific unit so specify @object-type="table". If the <related-object> is a chapter of a book, the most specific unit is the chapter so the correct attribute is @document-type="chapter".
When specifying a journal article, the following attributes must be present:
- @document-id
- @document-id-type: Must be a DOI, a PubMed ID, or a PubMed Central ID
- @document-type: Must be set to "article"
- @id: XML ID of the <related-object> element
- @link-type: Must be an approved value. See the approved values for @related-article-type described in <related-article>.
When specifying Clinical Trials, the following attributes must be present:
- @source-id: The @source-id attribute must be used to identify the clinical trial registry.
- @source-id-type: The value of @source-id-type should be "crossref-doi" or "registry-name", as appropriate.
- @document-id: The @document-id must hold the clinical trial number as provided in the clinical trial registry.
- @document-id-type: The @document-id-type must identify the kind of @document-id. The value must be either "clinical-trial-number" or "doi".
1.2
Use this tag to identify related objects. May be used to identify journal articles and Clinical Trials.
Use this element's attributes to identify the target object citation. The following objects must always exist together:
- @source-id and @source-id-type
- @document-id and @document-id-type
- @object-id and @object-id-type
Specify the type of target object for the most specific unit. For example, if the <related-object> is a table in a chapter of a book, the table is the most specific unit so specify @object-type="table". If the <related-object> is a chapter of a book, the most specific unit is the chapter so the correct attribute is @document-type="chapter".
When specifying a journal article, the following attributes must be present:
- @document-id
- @document-id-type: Must be a DOI, a PubMed ID, or a PubMed Central ID
- @document-type: Must be set to "article"
- @id: XML ID of the <related-object> element
- @link-type: Must be an approved value. See the approved values for @related-article-type described in <related-article>.
When specifying Clinical Trials, the following attributes must be present:
- @source-id: The @source-id attribute must be used to identify the clinical trial registry.
- @source-id-type: The value of @source-id-type should be "crossref-doi" or "registry-name", as appropriate.
- @document-id: The @document-id must hold the clinical trial number as provided in the clinical trial registry.
- @document-id-type: The @document-id-type must identify the kind of @document-id. The value must be either "clinical-trial-number" or "doi".
1.1
Use this tag to identify related objects. May be used to identify journal articles and Clinical Trials.
Use this element's attributes to identify the target object citation. The following objects must always exist together:
- @source-id and @source-id-type
- @document-id and @document-id-type
- @object-id and @object-id-type
Specify the type of target object for the most specific unit. For example, if the <related-object> is a table in a chapter of a book, the table is the most specific unit so specify @object-type="table". If the <related-object> is a chapter of a book, the most specific unit is the chapter so the correct attribute is @document-type="chapter".
When specifying a journal article, the following attributes must be present:
- @document-id
- @document-id-type: Must be a DOI, a PubMed ID, or a PubMed Central ID
- @document-type: Must be set to "article"
- @id: XML ID of the <related-object> element
- @link-type: Must be an approved value. See the approved values for @related-article-type described in <related-article>.
When specifying Clinical Trials, the following attributes must be present:
- @source-id: The @source-id attribute must be used to identify the clinical trial registry.
- @source-id-type: The value of @source-id-type should be "crossref-doi" or "registry-name", as appropriate.
- @document-id: The @document-id must hold the clinical trial number as provided in the clinical trial registry.
- @document-id-type: The @document-id-type must identify the kind of @document-id. The value must be either "clinical-trial-number" or "doi".
1.0
Use this tag to identify related objects. May be used to identify journal articles and Clinical Trials.
Use this element's attributes to identify the target object citation. The following objects must always exist together:
- @source-id and @source-id-type
- @document-id and @document-id-type
- @object-id and @object-id-type
Specify the type of target object for the most specific unit. For example, if the <related-object> is a table in a chapter of a book, the table is the most specific unit so specify @object-type="table". If the <related-object> is a chapter of a book, the most specific unit is the chapter so the correct attribute is @document-type="chapter".
When specifying a journal article, the following attributes must be present:
- @document-id
- @document-id-type: Must be a DOI, a PubMed ID, or a PubMed Central ID
- @document-type: Must be set to "article"
- @id: XML ID of the <related-object> element
- @link-type: Must be an approved value. See the approved values for @related-article-type described in <related-article>.
When specifying Clinical Trials, the following attributes must be present:
- @source-id: The @source-id attribute must be used to identify the clinical trial registry.
- @source-id-type: The value of @source-id-type should be "crossref-doi" or "registry-name", as appropriate.
- @document-id: The @document-id must hold the clinical trial number as provided in the clinical trial registry.
- @document-id-type: The @document-id-type must identify the kind of @document-id. The value must be either "clinical-trial-number" or "doi".
3.0
Use this tag to identify related objects. May be used to identify journal articles and Clinical Trials.
Use this element's attributes to identify the target object citation. The following objects must always exist together:
- @source-id and @source-id-type
- @document-id and @document-id-type
- @object-id and @object-id-type
Specify the type of target object for the most specific unit. For example, if the <related-object> is a table in a chapter of a book, the table is the most specific unit so specify @object-type="table". If the <related-object> is a chapter of a book, the most specific unit is the chapter so the correct attribute is @document-type="chapter".
When specifying a journal article, the following attributes must be present:
- @document-id
- @document-id-type: Must be a DOI, a PubMed ID, or a PubMed Central ID
- @document-type: Must be set to "article"
- @id: XML ID of the <related-object> element
- @link-type: Must be an approved value. See the approved values for @related-article-type described in <related-article>.
When specifying Clinical Trials, the following attributes must be present:
- @source-id: The @source-id attribute must be used to identify the clinical trial registry.
- @source-id-type: The value of @source-id-type should be "crossref-doi" or "registry-name", as appropriate.
- @document-id: The @document-id must hold the clinical trial number as provided in the clinical trial registry.
- @document-id-type: The @document-id-type must identify the kind of @document-id. The value must be either "clinical-trial-number" or "doi".
2.3
Element is not available in this version.
Tag fully, including metadata. Any <journal-meta> or <article-meta> not explicitly tagged in <front> or <front-stub> is inherited from the parent <article>.
attributes:
- id—(#REQUIRED)
- response-type—Values: reply, discussion, addendum(#REQUIRED)
1.3
Tag role information for each contributor in <role>.
<role> can contain:
- Simple text descriptions of contributor roles, or
- Contributor descriptions that follow the CRediT controlled vocabulary (see also: Author Contributions).
The text content of the element will be used for display. This text does not need to match the name of a CRediT term exactly. PMC will not generate a display string for <role> if the element has no content.
Example of a simple text description of a role:
<role>Editor in Chief</role>
Example of a contributor description that follows the CRediT vocabulary:
<role vocab="credit" vocab-identifier="https://credit.niso.org/"
vocab-term="Writing - Original Draft"
vocab-term-identifier="https://credit.niso.org/contributor-roles/writing-original-draft/"
>Writing - Original Draft</role>
Example of a contributor description where display content does not match the CRediT vocabulary term exactly:
<role vocab="credit" vocab-identifier="https://credit.niso.org/"
vocab-term="Investigation"
vocab-term-identifier="https://credit.niso.org/contributor-roles/investigation/"
>Data Collection</role>
attributes:
- vocab—Use to name the vocabulary: "credit".
- vocab-identifier—Use to indicate the URI of the vocabulary: "https://credit.niso.org/".
- vocab-term—Use to indicate the specific CRediT term.
- vocab-term-identifier—Use to indicate the CRediT term URI (see table in Author Contributions).
1.2
Tag role information for each contributor in <role>.
<role> can contain:
- Simple text descriptions of contributor roles, or
- Contributor descriptions that follow the CRediT controlled vocabulary (see also: Author Contributions).
The text content of the element will be used for display. This text does not need to match the name of a CRediT term exactly. PMC will not generate a display string for <role> if the element has no content.
Example of a simple text description of a role:
<role>Editor in Chief</role>
Example of a contributor description that follows the CRediT vocabulary:
<role vocab="credit" vocab-identifier="https://credit.niso.org/"
vocab-term="Writing - Original Draft"
vocab-term-identifier="https://credit.niso.org/contributor-roles/writing-original-draft/"
>Writing - Original Draft</role>
Example of a contributor description where display content does not match the CRediT vocabulary term exactly:
<role vocab="credit" vocab-identifier="https://credit.niso.org/"
vocab-term="Investigation"
vocab-term-identifier="https://credit.niso.org/contributor-roles/investigation/"
>Data Collection</role>
attributes:
- vocab—Use to name the vocabulary: "credit".
- vocab-identifier—Use to indicate the URI of the vocabulary: "https://credit.niso.org/".
- vocab-term—Use to indicate the specific CRediT term.
- vocab-term-identifier—Use to indicate the CRediT term URI (see table in Author Contributions).
1.1
Tag role information for each contributor in <role>.
<role> can contain:
- Simple text descriptions of contributor roles, or
- Contributor descriptions that follow the CRediT controlled vocabulary.
If using the CRediT vocabulary, include the following attribute on <role>:
- @content-type: include the URI to the CRediT term used (see table in Author Contributions).
Example of a simple text description of a role:
<role>Editor in Chief</role>
With provided content intended to display:
<role content-type="https://credit.niso.org/contributor-roles/data-curation/">Data curation</role>
No content intended to display:
<role content-type="https://credit.niso.org/contributor-roles/formal-analysis/"/>
1.0
Tag role information for each contributor in <role>.
<role> can contain:
- Simple text descriptions of contributor roles, or
- Contributor descriptions that follow the CRediT controlled vocabulary.
If using the CRediT vocabulary, include the following attribute on <role>:
- @content-type: include the URI to the CRediT term used (see table in Author Contributions).
Example of a simple text description of a role:
<role>Editor in Chief</role>
With provided content intended to display:
<role content-type="https://credit.niso.org/contributor-roles/data-curation/">Data curation</role>
No content intended to display:
<role content-type="https://credit.niso.org/contributor-roles/formal-analysis/"/>
3.0
Tag role information for each contributor in <role>.
<role> can contain:
- Simple text descriptions of contributor roles, or
- Contributor descriptions that follow the CRediT controlled vocabulary.
If using the CRediT vocabulary, include the following attribute on <role>:
- @content-type: include the URI to the CRediT term used (see table in Author Contributions).
Example of a simple text description of a role:
<role>Editor in Chief</role>
With provided content intended to display:
<role content-type="https://credit.niso.org/contributor-roles/data-curation/">Data curation</role>
No content intended to display:
<role content-type="https://credit.niso.org/contributor-roles/formal-analysis/"/>
2.3
Tag role information for each contributor in <role>.
<role> can contain:
- Simple text descriptions of contributor roles, or
- Contributor descriptions that follow the CRediT controlled vocabulary.
If using the CRediT vocabulary, include the following attribute on <role>:
- @content-type: include the URI to the CRediT term used (see table in Author Contributions).
Example of a simple text description of a role:
<role>Editor in Chief</role>
With provided content intended to display:
<role content-type="https://credit.niso.org/contributor-roles/data-curation/">Data curation</role>
No content intended to display:
<role content-type="https://credit.niso.org/contributor-roles/formal-analysis/"/>
All sections must contain <title>, <label>, or both. If it does not have either, do not tag it as a section.
Used to capture signatures. If multiple signatures appear, capture in a single <sig-block>.
1.3
PMC does not guarantee that the display specified in the attributes will be implemented on the HTML rendering of the article and strongly discourages using this element.
1.2
PMC does not guarantee that the display specified in the attributes will be implemented on the HTML rendering of the article and strongly discourages using this element.
1.1
PMC does not guarantee that the display specified in the attributes will be implemented on the HTML rendering of the article and strongly discourages using this element.
1.0
PMC does not guarantee that the display specified in the attributes will be implemented on the HTML rendering of the article and strongly discourages using this element.
3.0
PMC does not guarantee that the display specified in the attributes will be implemented on the HTML rendering of the article and strongly discourages using this element.
2.3
Element is not available in this version.
Tag fully, including metadata. Any <journal-meta> or <article-meta> not explicitly tagged in <front> or <front-stub> is inherited from the parent <article>.
Peer review documents should be tagged as sub-article elements. See our tagging guidance on Peer Review Documents.
attributes:
- article-type—Must specify. See the Article Types for descriptions of suggested values.
- id—(#REQUIRED)
Defines the subjects of an article within <article-categories>. These are often used to indicate the Table of Contents headings for an article.
Do not include any <xref> within <subject>. Any article-level footnotes that must be referenced should be referenced from the <article-title>.
Do not include formatting elements unless necessary to convey emphasis. See Formatted Text.
Do not use. See <issue>.
Tag <supplementary-material> in a single <sec> with @sec-type value "supplementary-material" at the end of <body>.
attributes:
- content-type—Specify as "local-data"
Tables should be fully tagged, not included as images.
attributes:
- frame—Specify as "hsides"
- rules—Specify as "groups"
Contains all parts of a single table.
See Display Object Groups for information on when to use this element.
This element should not be used to set math unless it is supplied as an alternative representation of an expression. See Alternate Versions of a Single Object for details.
If <tex-math> is supplied as alternate tagging for an expression, make sure:
- That each expression is a complete LaTeX expression, including header.
- That all characters are represented in LaTeX notation and not with Unicode™ characters.
attributes:
- id—(#REQUIRED)
1.3
This holds the <article-title>.
If there is a footnote to the title, put the <xref> (with @ref-type="fn") in the <article-title> or <subtitle> element, and set the <fn> in the <fn-group> in <back>.
If the article is a book review, see Book Reviews and <article-title> for special rules.
1.2
This holds the <article-title>.
If there is a footnote to the title, put the <xref> (with @ref-type="fn") in the <article-title> or <subtitle> element, and set the <fn> in the <fn-group> in <back>.
If the article is a book review, see Book Reviews and <article-title> for special rules.
1.1
This holds the <article-title>.
If there is a footnote to the title, put the <xref> (with @ref-type="fn") in the <article-title> or <subtitle> element, and set the <fn> in the <fn-group> in <back>.
If the article is a book review, see Book Reviews and <article-title> for special rules.
1.0
This holds the <article-title>.
If there is a footnote to the title, put the <xref> (with @ref-type="fn") in the <article-title> or <subtitle> element, and set the <fn> in the <fn-group> in <back>.
If the article is a book review, see Book Reviews and <article-title> for special rules.
3.0
This holds the <article-title>.
If there is a footnote to the title, put the <xref> (with @ref-type="fn") in the <article-title> or <subtitle> element, and set the <fn> in the <fn-group> in <back>.
If the article is a book review, see Book Reviews and <article-title> for special rules.
2.3
This holds the <article-title>.
If there is a footnote to the title, put the <xref> (with @ref-type="fn") in the <article-title> or <subtitle> element, and set the <fn> in the <fn-group> in <back>.
If the article is a book review, see Book Reviews and <article-title> for special rules.
Used to tag the article <abstract> in a language different than that of the parent <article>.
Tag the <title> of the abstract, even if it is equivalent to "Abstract" in the alternate language.
Excerpted from Bull World Health Organ. 2012 December 1; 90(12): 878–886. 10.2471/BLT.12.106419. Used with permission.
<abstract>
<sec><title>Objective</title>
<p>To estimate the population of Peru living in the vicinity of active or former mining
operations that could be exposed to lead from contaminated soil.</p>
</sec>
</abstract>
<trans-abstract xml:lang="fr">
<title>Résumé</title>
<sec>
<title>Objectif</title>
<p>Estimer la population péruvienne vivant à proximité d'une exploitation
minière, ancienne ou active, qui pourrait être exposée au plomb de sols
contaminés.</p>
</sec>
</trans-abstract>
<trans-abstract xml:lang="es">
<title>Resumen</title>
<sec>
<title>Objetivo</title>
<p>Calcular qué parte de la población peruana residente en las inmediaciones
de explotaciones mineras activas o cerradas podría estar expuesta a suelos contaminados
con plomo.</p>
</sec>
</trans-abstract>
attributes:
- xml:lang—(#REQUIRED)
1.3
Contains the <article-title> in a language different than that of the parent article.
1.2
Contains the <article-title> in a language different than that of the parent article.
1.1
Contains the <article-title> in a language different than that of the parent article.
1.0
Contains the <article-title> in a language different than that of the parent article.
3.0
Contains the <article-title> in a language different than that of the parent article.
2.3
Contains the <article-title> in a language different than that of the parent article.
Must include @xml:lang.
1.3
Only tag elements in a single language in the <trans-title-group>. To tag titles in multiple languages, use one <trans-title-group> per language.
Each element contained within the <trans-title-group> must have a corresponding element in the primary language (do not tag <trans-subtitle> if no <subtitle> exists).
1.2
Only tag elements in a single language in the <trans-title-group>. To tag titles in multiple languages, use one <trans-title-group> per language.
Each element contained within the <trans-title-group> must have a corresponding element in the primary language (do not tag <trans-subtitle> if no <subtitle> exists).
1.1
Only tag elements in a single language in the <trans-title-group>. To tag titles in multiple languages, use one <trans-title-group> per language.
Each element contained within the <trans-title-group> must have a corresponding element in the primary language (do not tag <trans-subtitle> if no <subtitle> exists).
1.0
Only tag elements in a single language in the <trans-title-group>. To tag titles in multiple languages, use one <trans-title-group> per language.
Each element contained within the <trans-title-group> must have a corresponding element in the primary language (do not tag <trans-subtitle> if no <subtitle> exists).
3.0
Only tag elements in a single language in the <trans-title-group>. To tag titles in multiple languages, use one <trans-title-group> per language.
Each element contained within the <trans-title-group> must have a corresponding element in the primary language (do not tag <trans-subtitle> if no <subtitle> exists).
2.3
Element is not available in this version.
attributes:
- xml:lang—Use two-letter, lower case language codes as described in RFC 4646. Values may be obtained from the IANA Language Subtag Registry: http://www.iana.org/assignments/language-subtag-registry.(#REQUIRED)
Tag numeric volumes as an integer only. If Roman numerals are used, tag as the Roman numeral only. Do not include the word "volume" or any related abbreviation in the tag.
If the citation is part of a special issue with no specified volume (like "Supplement 2005"), tag "Suppl" in <volume> and "2005" in <year>.
If there is no volume number, do not tag at all.
Do not tag more than one volume in <article-meta> or <front-stub>.
Used for references to objects within the article. When formatting of the cross references is important, include it in the tagging. For ranges or multiple references that include punctuation between them, include that character data within the formatting element.
Do not tag multiple id values in @rid.
Tag lists of cross references by including one <xref> element for each referenced object.
The changes in education level demonstrate the changing attitudes. 1, 2, 5
<p>The changes in education level demonstrate the changing
attitudes.<sup><xref ref-type="bibr" rid="B1">1</xref>,
<xref ref-type="bibr" rid="B2">2</xref>,
<xref ref-type="bibr" rid="B5">5</xref></sup></p>
Tag ranges of cross references by including an <xref> for the first item, an en-dash (–), and an <xref> for the last item. PMC will display the range as tagged.
The changes in education level demonstrate the changing attitudes. 1–3
<p>The changes in education level demonstrate the changing attitudes.
<sup><xref ref-type="bibr" rid="B1">1</xref>–<xref ref-type="bibr"
rid="B3">3</xref></sup></p>
Set the "linked text" inside of the <xref>. PMC will not generate the content of the link based on the @rid.
The @ref-type must match the target object in the XML, regardless of the object's label.
Correct:
<xref ref-type="table" rid="T1">Table 1<xref>
...
<table-wrap id="T1">...</table-wrap>
Incorrect:
<xref ref-type="table" rid="T1">Table 1<xref>
...
<fig id="T1">
<label>Table 1</label>
</fig>
attributes:
- ref-type—The type of object being referenced: "app", "author-notes", "bibr", "boxed-text", "disp-formula", "fig", "fn", "list", "sec", "supplementary-material", "table", "table-fn".(#REQUIRED)
- rid—The @id of the referenced object.(#REQUIRED)
- id—Do not use.