An archival sheet carrying fields of its own

A records office's reference, the department it came from, the date until which the document must be kept and its classification, in a PDF/A-3 file. No standard knows what a retention date is, so each field arrives with a description of itself — its type, who it is written for, what it means — which is what makes a checker accept information you invented. The page prints the same list, so what a person reads and what a machine reads cannot drift apart.

PDF/A accepts metadata no standard ever heard of, but not silently. A piece of information from outside the standards has to travel with a description of itself — what it is called, how it is to be read, who it is written for and what it means — or the file is not conformant.

Here a records office writes down its reference, the department it came from, a retention date and a classification, and the library writes both halves: the metadata itself, and its description beside it. The page prints the same fields, from one and the same list, so what a person reads and what a machine reads cannot drift apart.

What this example shows

  • Information of your own invention, inside a PDF/A file.
  • The description that makes a checker accept it.
  • The page and the record written from one list, so they cannot disagree.

The code, in full

The same document is written twice, once in each language. Both files are shown in full, with the code coloured on the server, and can be copied in one click.

The document itself

The same document is written in each of these languages. Open the one you want to look at.

Open the document in English Open the document in French

Read the Rust source Read the Python source

First page of An archival sheet carrying fields of its own

What this document weighs

Before 122,159 bytes
Now 51,905 bytes
Saved 57.5 %

Not one mark on the page changed. See every document measured.

Examples near this one

A sheet that measures what it says

Three rules — centimetres, inches and points — on a page that states it must print at exactly the size it was drawn, and that the reader is to offer nothing else. That second request only exists from PDF 2.0 on, so the file declares 2.0 rather than changing version without you knowing.

A register whose every part says where it came from

Two sittings bound into one file. Each page carries a record of its own — what it is, whose hand wrote it, when — the photograph on the second page carries one too, and each transcription is tied to the page it transcribes rather than to the file at large. Tying an attached file to anything but the whole document only exists from PDF 2.0 on, so the file declares 2.0.

A tagged, accessible document

A document that says what each run of ink stands for, and which runs are only trimmings. Its text and its table describe themselves, a paragraph and a cell at a time. Validates as PDF/A-3a and PDF/UA-1.

A tagged list whose column is a picture

A parts list whose first column is a picture rather than a word. Each picture is marked as one and carries the words a reader hears in its place, so nothing in the list is lost on somebody who cannot see it. Validates as PDF/A-3a and PDF/UA-1.

A slideshow that runs itself

Thirteen slides, each stating the effect it arrives by — all twelve the standard defines — how long that effect takes and how long the slide stands before the next one comes. The file opens full screen, which is the only place a reader reads any of it.

Every example, by subject

Glossary

PDF/A
A PDF made to be readable in twenty years' time. Everything it needs is inside the file — the fonts, the colours, the description of what it is — so nothing it depends on can go missing later. Public bodies and archives ask for it by name.
XMP
The block inside a file that says what the file is: its title, who made it, when, and which rules it follows. Search engines and archives read it; a reader never sees it.