Practical comparison / PMC and JATS
PMC Style Checker and JATS Verify solve different problems
Use current NLM and PMC tools to check PMC tagging requirements. Add package-level preflight when your release question also covers linked files, destination-specific metadata, or changes from an earlier package.
The Online PMC Style Checker reports errors and warnings against the PMC Tagging Guidelines. NLM also publishes a downloadable StyleChecker and an API. JATS Verify does not certify or guarantee PMC acceptance.
Choose by the question you need answered
| Need | Official NLM and PMC tools | JATS Verify |
|---|---|---|
| PMC-specific style feedback | The online checker reports PMC errors and warnings | Not a replacement |
| DTD and PMC style checking | The online and API responses report DTD and style status separately. The downloadable StyleChecker requires a separate DTD validation step | Checks an explicitly configured trusted JATS DTD |
| Missing local figures and supplements | Follow PMC's file specifications and production workflow in addition to XML style checking | Checks local references when an assets ZIP is supplied |
| Broken internal cross-references and duplicate IDs | Checks PMC cross-reference targets and target types. DTD validation handles duplicate XML IDs declared by the DTD | Checks package cross-references and duplicate IDs |
| Journal-specific required metadata | Applies the selected NLM or PMC profile, not a journal's separate instructions | Can apply a configured journal profile |
| Previous-release comparison | No release-baseline workflow is documented for the Style Checker | Can compare a candidate with a supplied previous XML file |
| Saved evidence | Keep the official checker response with the release record | Provides a JSON report and release-package evidence on paid checks |
| Automation | NLM publishes an API and downloadable StyleChecker 5.48 | Offers a paid API and public GitHub Action |
A sensible release sequence
- 01Build the package
Create the JATS XML and collect every locally referenced figure, media file, supplement, and related asset.
- 02Run package QA
Use JATS Verify for structure, assets, internal links, identifiers, journal rules, changes, and retained evidence.
- 03Run the destination checker
Use the current checker supplied by PMC, SciELO, your archive, or the receiving journal.
- 04Keep both results
Retain the destination response and the package evidence with the exact release delivered.
Why pay for another check?
JATS Verify is useful when a production team needs one package record that covers checks outside the selected PMC style profile, such as supplied local assets, a configured journal profile, or a comparison with a previous XML file. If the official NLM and PMC tools fully answer your release question, keep using them.
Official sources
See the package layer
Check one JATS package free.
No account, email, card, or sales call. The free result shows the verdict and up to five findings.