write_pdfa3a.json
The JSON file of the “A Tagged PDF/A-3a Schedule of Charges” example. A schedule a screen reader follows and a program reads from the table attached inside it: the third part of the archival standard at its highest level.
This file is a request: an application sends it over the network to the server, which creates the PDF and sends it back. It creates the same page as the Rust and Python versions of this example. A request names every file it uses, never its content; the call carries the request and the files together. A font the server already holds, such as DejaVuSans, is named with nothing attached. Send the request to the address the API page gives.
This request names files it does not carry: schedule. Each one travels beside the request, in the same call, as a supplied part named exactly as the request names it here — the description says which name plays which role, so you name your files as you like. A request naming a file the call carries nothing of is refused.
What This Example Is For
A schedule of charges is read by customers, some of them through software that reads aloud, and by the billing system that applies it. Writing it twice — a page for people, a file for the system — is how the two end up quoting different prices.
What This Example Shows
- Three charges for the second half of 2026, stated on the page.
- The heading, the paragraphs and the decoration named, for software reading aloud.
- The same charges attached inside the file as a table a program opens.