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