JATS4R — short for JATS for Reuse — is a NISO working group that publishes recommended practices for tagging scholarly journal articles in JATS XML so the resulting files are consistently machine-actionable across publishers, archives, and downstream systems. Where the base JATS XML standard (ANSI/NISO Z39.96) is deliberately permissive — allowing several structurally valid ways to tag the same piece of information — JATS4R narrows that flexibility down to one recommended pattern per element, specifically so that funding statements, data citations, author identifiers, and similar metadata can be extracted programmatically without publisher-by-publisher special-casing. If you are new to JATS XML itself, start with the companion JATS XML dictionary term and the JATS XML Explained guide; this page assumes that baseline and focuses on what JATS4R adds on top of it.
What JATS4R is, and its NISO status
JATS4R began as an independent working group focused on improving the reusability of JATS-tagged scholarly content, and has operated under the auspices of NISO (the National Information Standards Organization) since December 2018. Rather than publishing a single monolithic standard, JATS4R issues a series of individually numbered NISO Recommended Practices (RP), each addressing one specific category of article metadata or content. Confirmed published examples include Authors and Affiliations (RP-48-2024, version 2.0), Accessibility (RP-47-2024, version 1.0), Abstracts (RP-43-2022, version 1.0), and Data Citations (RP-36-2020, version 2.0). Each recommendation goes through NISO’s standard development and public-comment process before publication, giving it the same formal standing as other ANSI/NISO Recommended Practices, while staying narrow enough in scope to be revised independently as practice evolves in that specific area.
The problem JATS4R solves
Base JATS XML is intentionally flexible: its Tag Library documents multiple structurally valid ways to mark up many kinds of content, because JATS has to accommodate archival, publishing, and authoring use cases with different constraints (see the Green/Blue/Pumpkin tag-set split covered in the JATS XML guide). That flexibility works well for JATS as an archival format, but it becomes a problem the moment a downstream system tries to extract one specific piece of information — a funder name, a data availability statement, an ORCID iD — programmatically across many publishers’ output. If several publishers each choose a different, individually valid way to tag the same funding acknowledgment, a funder registry or aggregator cannot reliably parse it without a separate parsing rule per publisher. JATS4R exists to close that gap: for each content type it covers, it recommends exactly one tagging pattern, so a system built against JATS4R’s specification can parse conforming output the same way regardless of which publisher produced it.
What JATS4R recommends, by topic
JATS4R’s recommendations are published individually on jats4r.niso.org and cover a specific, growing set of article metadata and content areas rather than the article as a whole:
- Authors and affiliations (RP-48-2024, v2.0) — how to tag author names, affiliations, and persistent identifiers, including using the
<contrib-id>element for a full-URL-form ORCID iD. - Abstracts (RP-43-2022, v1.0) — consistent tagging for abstracts, including structured and graphical abstract variants.
- Accessibility (RP-47-2024, v1.0) — tagging conventions that support accessible rendering of article content, such as alt text and structural markup that assistive technology can rely on.
- Data citations (RP-36-2020, v2.0) — recommends citing datasets within the article’s main reference list rather than only as informal in-text mentions, so dataset citations are extractable the same way article citations are.
- Data availability statements — structured tagging so a statement about where underlying data can be found is consistently locatable and machine-readable, regardless of which of the common phrasing patterns an author or journal uses.
- Funding — a strict tagging model for funder names, award or grant numbers, and funder identifiers in the article’s front matter, so funding information can be matched against funder registries and deposited with services such as Crossref’s funding data.
- CRediT contributor roles — recommends how the CRediT taxonomy’s contributor roles should be tagged in author metadata so role assignments are machine-parseable rather than visible only as prose in an author-contributions statement.
- Peer review materials, ethics statements, permissions, preprint citations, software citations, and subject/keyword guidelines — additional published NISO recommended practices, each scoped to that one content type.
Not every recommendation carries a citable RP number in every reference to it; where this page cites a specific RP number and version, it reflects what NISO’s own committee page documents as of this writing — check NISO’s JATS4R committee page directly for the current, complete list, since the working group continues to publish and revise recommendations.
JATS4R vs. base JATS XML
| JATS XML (ANSI/NISO Z39.96) | JATS4R | |
|---|---|---|
| What it is | The underlying XML vocabulary (tag suite) for structuring an article’s text and metadata | A set of NISO Recommended Practices that pick one preferred tagging pattern within that vocabulary |
| Scope | The whole article: front matter, body, back matter, across three tag sets (Green, Blue, Pumpkin) | Specific metadata/content categories: authors, funding, data citations, abstracts, accessibility, and more |
| Flexibility | Deliberately permits multiple valid tagging approaches for the same content | Narrows to one recommended approach per covered element, to enable reuse |
| Governance | ANSI/NISO standard (Z39.96), maintained with the Tag Library at jats.nlm.nih.gov | NISO working group since December 2018, publishing individually numbered Recommended Practices |
| Compliance check | Validated against the JATS DTD/schema for the relevant tag set | Checked with JATS4R’s own Schematron-based validator, layered on top of base JATS validity |
The JATS4R validator
JATS4R also publishes a Schematron-based validator that checks whether a given JATS XML file actually conforms to its recommended tagging patterns, rather than only checking that the file is valid against the base JATS schema. This lets a publisher or production vendor test output directly against JATS4R’s recommendations before deposit, rather than discovering a mismatch only when a downstream system — an archive, a funder registry, a data repository — fails to parse the file correctly.
Why this matters for research administration
Most research administrators never touch JATS XML directly — tagging is a publisher and production-vendor concern — but the consistency JATS4R exists to create shows up downstream in things a research office does rely on. Funder confirmations that flow through funder registries and services like Crossref’s funding data depend on funding metadata having been tagged consistently at the source. ORCID auto-updates depend on author identifiers being tagged in the pattern ORCID’s integration expects. And a funder or institutional mandate that a data availability statement be machine-discoverable, not just human-readable, depends on it being tagged as a discrete, structured element rather than left as unstructured prose in the article body — see How to Write a Data Availability Statement for Reproducibility for the authoring side of that same requirement. In each case, JATS4R is the layer that makes the underlying JATS XML file usable by the specific downstream system rather than merely valid.
Frequently asked questions
What does JATS4R stand for?
JATS for Reuse. The name describes its purpose directly: making JATS-tagged content more reliably reusable by downstream systems, not introducing a new tag suite.
Is JATS4R a separate standard from JATS XML?
No. JATS4R does not define new XML elements or a competing schema. It recommends which of the tagging options already permitted within JATS XML (ANSI/NISO Z39.96) to use for a given piece of content, so that different publishers converge on the same pattern.
Is JATS4R conformance required for PubMed Central deposit?
PMC’s own deposit requirements are defined by the JATS Archiving and Interchange tag set itself, not by JATS4R directly. JATS4R’s recommendations are best-practice guidance layered on top of that baseline, aimed at making tagged content more reusable beyond archiving alone (for example, by funders, data repositories, and citation services) — check current requirements directly with PMC or the specific archive or aggregator you are depositing with rather than assuming JATS4R conformance is or is not mandatory.
Who maintains JATS4R?
A NISO working group, operating under NISO’s auspices since December 2018. Recommendations are developed collaboratively with input from publishers, technology vendors, and archives, and go through NISO’s standard development and public-comment process before publication.
Where can I find the current list of JATS4R recommendations?
jats4r.niso.org publishes each recommendation individually, along with the JATS4R validator; NISO’s committee page lists the formally numbered Recommended Practices.
