Public, reproducible package evidence.

Public package check / 16 August 2026

Valid-looking XML. Broken package handoff.

We checked one openly licensed PubMed Central article version together with every object distributed under its public AWS prefix. The XML pointed to a PDF filename that the package did not contain.

The decision

Block until the PDF reference and delivered filename agree.

This does not mean the article content is invalid or that PMC failed to ingest it. It means a consumer treating the public prefix as one portable package cannot resolve two local self-uri references.

2Unresolved asset references
4Referenced table images verified
32References inspected
1Reproducible canonical hash

What we checked

The sample is article version PMC10009402.1, distributed by the National Library of Medicine through the public PMC Article Datasets bucket. Its metadata marks the article as open access under CC BY.

XMLPMC10009402.1.xml

ObjectsPublic package listing

MethodPMC dataset documentation

The exact mismatch

The XML contains two local references to S0033291721002701a.pdf. The public prefix contains a PDF named PMC10009402.1.pdf, but not the filename declared by those XML references.

ERROR asset.unresolved

/article/front/article-meta/self-uri[1] local asset 'S0033291721002701a.pdf': asset does not exist

ERROR asset.unresolved

/article/front/article-meta/self-uri[2] local asset 'S0033291721002701a.pdf': asset does not exist

Why schema validation is not enough

A schema can allow a self-uri and accept its filename. It cannot prove that the named file is present in the package a customer receives. That requires checking the XML and the delivered files together.

  • Every local XML reference resolves inside the package.
  • Filename case matches exactly.
  • Cross-references resolve to unique XML IDs.
  • Assets receive size, MIME type, and SHA-256 evidence.
  • The XML receives a canonical hash for repeatable comparison.

Reproduce the result

Download the objects listed under the public prefix, place them in one directory, and run the local gate without a destination-specific profile.

jats-gate PMC10009402.1.xml \
  --assets . \
  --format json

Download the complete deterministic evidence JSON

Scope note: this check did not submit the article to PMC, verify editorial content, or claim destination rejection. It tested whether the files exposed as one public article version form a self-consistent local package.

Use your own evidence

Check the package you are about to deliver.

One diagnostic is free. No card, no account, and no sales call.

Check one package free