Used to hold a shortened form of the journal title.

There may be more than one abstract in an article. If there is, identify each with an @abstract-type.

<abstract> allows <title>, <p>, and <sec>.

Only set a <title> if a title is something other than "Abstract".

Only use <sec> if the abstract has been divided into sections. Most abstracts can be tagged with just <p>. However, if an abstract is divided into sections, use the <sec>. Do not just set the section titles in <bold> or other formatting.

Do not use @sec-type for sections inside <abstract>.

Do not include Citation Information and/or Copyright Information at the end of the abstract. This information should be included elsewhere in the <article-meta>.

Any keywords should be set in <kwd-group>. Do not include keywords in the <abstract>.

See Sample 1 for examples.

Use @xml:lang for articles with abstracts in multiple languages.

An English article does not need to have an @xml:lang at the <article>. A non-English article title should be tagged as a <trans-title> within <title-group>. A non-English abstract should be tagged as a <trans-abstract> following the <abstract>.

Set the @xml:lang value to the main language of the article on the <article>. Use <trans-title> within <title-group> and <trans-abstract> to set the English translation of the article title and abstract (or for any other language version that is not in the main language of the article.

Set any label or symbol in the <label> element.

Do not add symbols or labels to define the relationship between contributors and affiliations.

Put the rest of the affiliation information into the <aff> as PCDATA. Follow copy for all punctuation.

See Author/Affiliation Relationship for information on how authors and affiliations are "linked".

See Sample 1 and Sample 2 for examples.

If namespace declarations for MathML and XLink are needed in the article, tag them as attributes on the article (see below).

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.

The content of the <subject> may describe the type of article ("Editorial", "Obituary") or the content of the article ("Physical Sciences", "Psychology"). If no subject is available, use "Article".

A set of subjects may have multiple levels, see the Tag Library for more details.

Other <subj-group> with different @subj-group-type may be included.

Contains any unique identifier assigned to the article, such as pii, doi, or PubMed ID.

Each <article-id> can store a single identifier.

See Sample 2 for examples.

<article-id> - contains any unique identifier assigned to the article.

<article-categories> - use tagging supplied under Article Categories or Subjects.

<title-group> - this includes the article title/subtitle

<contrib-group> - contains contributor information. <contrib-group> and <aff> may interleave.

<author-notes> - contains notes with information specific to the author(s).

<pub-date> - holds the publication date of the article.

<license> - contains information about terms of use of the content.

<self-uri> - a link to a different version of the article.

<abstract> - the article's abstract.

<kwd-group> - keywords, if supplied.

<contract-num> - contract number. This should link to/from <contract-sponsor>.

<contract-sponsor> - contract sponsor. This should link to/from <contract-number>.

<counts> - counts of objects in the article.

<custom-meta-wrap> - custom metadata (might not need this one yet).

If the article is a Book Review, use the explicit title found on the article. If no explicit title is present, use the title of the first (or only) book being reviewed. Then, use <product> to include detailed information about the title being reviewed; see Article Title for examples.

See Sample 1 for an example.

Do not set <title>.

<fn-group> should be used to hold all article-level footnotes.

Use <title> for section titles. Do not just set the section titles in <bold> or other formatting.

All named Figures and Tables should be collected in a <sec> in <back>.

Back matter elements, such as <app-group>, <glossary> and <ref-list>, should not appear at the end of <body>.

<citation> can appear within body or <ref-list>. It should include a citation-type attribute.

See Sample PubMed Central Citations for fully-tagged examples.

<contract-sponsor> needs to be set only once, even if there is more than one grant listed. It should be linked to/from at least one <contract-num>.

Any <xref> in the author information should have @ref-type="author-notes" and point to a target <fn> in <author-notes>.

See Author Names for more information.

See Sample 1 and Sample 2 for examples.

The relationships between <contrib>, and <aff> can be complex, but we should be able to simplify things here.

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

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

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

See Sample 1 and Sample 2 for examples.

The contents will usually be the word "Copyright", a copyright symbol, the copyright year, and the name of the copyright holder. The year of copyright should also be tagged in <copyright-year>, whether or not it appears as part of the <copyright-statement>.

Should be contained in <permissions>.

Should be contained in <permissions>.

Set any label or symbol in the <label> element.

Put the address, phone, and fax information into the <corresp> as PCDATA. Follow copy for all punctuation.

Tag any email address as <email>. Do not use <phone> or <fax>.

See Sample 1 for an example.

If more than one article shares the same first page, specify @seq. The first article should have @seq="a", the second @seq="b", etc. See description of Continuous Makeup Articles.

Tag footnotes that apply to the article as a whole in <fn-group> in <back>.

Tag table footnotes in <table-wrap-foot>.

<journal-meta> and <article-meta> are required and detailed later in this document.

Do not use <notes> here in the frontmatter.

See Sample 1 for an example.

See Sample 2 for examples.

Tag "Part" issues as "Pt [integer]". Tag "Supplement" issues as "Suppl [integer]". If the Part or Supplement has no integer, then tag as "Pt" or "Suppl" only.

If there is no issue number, do not tag at all.

Multiple journal-ids may be tagged. Specify type of id in @journal-id-type. If PubMed abbreviation is available, tag with @journal-id-type="nlm-ta".

Requires <issn>, <journal-id>, <journal-title>, and <publisher>.

Contains the complete title of the journal in which the article is published.

Do not include emphasis that encompasses the entire contents.

Should be contained in <permissions>.

A URI to the license description should be captured in the @xlink:href.

See Sample 1 for an example.

<license license-type="open-access" 
   xlink:href="http://creativecommons.org/licenses/by/2.5/">
	<p>This is an open-access article distributed under the terms of the 
	Creative Commons Attribution License, which permits unrestricted use, 
	distribution, and reproduction in any medium, provided the original 
	work is properly cited.</p>
</license>
	

See Sample 1 and Sample 4 for examples.

Do not use <label>.

Do not use to tag single characters.

If you have a month range (January-March), tag it as a <season>.

is used for article-level notes. These often appear at the beginning of the article, the end of the article or after a <table>.

Notes about the author(s) should be placed in <article-notes>.

Article Disclaimers should be tagged as <notes> in the front matter.

Notes in Proof should be tagged as <notes> in the back matter.

Paragraph. Contains text of article.

See Sample 4 for an example.

holds the publication date(s) for the article.

If an article has more than one publication date, create successive <pub-date> tags.

The most common values are "epub", "ppub", "epub-ppub", "epreprint", and "collection". When an article is published in more than one medium, there should be more than one <pub-date>. The number and type of <pub-date> to be set depends on the publication model of the journal. There are two 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 (eg, all of the articles published online in June 2005 are in the "June" issue. This issue may be printed, or it may not. 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.

Hopefully some models will help illustrate:

Print-only Model — This is the traditional print model. Articles are collected by the editor, formed into issues, and published and 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.

See Sample 2 for examples.

See References for details on complex references.

See Sample PubMed Central Citations for fully-tagged examples of <citation> and <nlm-citation>.

See Sample 1 and Sample 5 for examples.

See fully-tagged examples in Response and Sub-Article

Ranges of months are considered seasons.

Do not include the year in <season>.

See fully-tagged examples in Meeting Reports/Abstracts and Response and Sub-Article

Do not include any <xref> within <subject>. Any article-level footnotes that must be referenced should be referenced from the <article-title>.

See Sample 1 and Sample 2 for examples. More fully-tagged tables are available on the DTD website.

It also allows <subtitle>, <trans-title>, <alt-title> and <fn-group>.

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 <article-title> for special rules.

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.

We don't expect to need @ref-type="aff" because the affiliation information should all be supplied with the <contrib> or <contrib-group>.

Do not tag emphasis or style inside or around the <xref>.

When the text contains a list of <xref>s, tag each individually with the corresponding @rid value. When there is a range, tag the first <xref> with the @rid of the beginning of the range and the last <xref> with the @rid with the end of the range. Separate the two with the Unicode en-dash (&#x2013;). Do not tag multiple values in @rid.

Set the "linked text" inside of the <xref>. Do not expect PMC to generate the content of the link based on the id.

See Sample 1 for an example.