write_own_notes.json
The JSON file of the “The notes a program leaves itself” example. A press proof carrying the run on the file, the plate on the page and the ink on the colour bar placed twice. None of it is drawn and no reading software shows it: it is there for the program that wrote it.
This file is a request: an application sends it over the network to the server, which creates the PDF and sends it back. It makes 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.
What this example is for
A press room sends a proof out and gets it back three days later with a pencil note in the margin. To pick the job up again it has to know which run the sheet belongs to, which plate the page was set for, and which ink the colour bar was drawn against — and none of that is anything the person holding the sheet should be shown. So it travels under the document instead of on it: the file carries the run, the page carries its plate, and the colour bar, placed twice on that page, carries the ink it was set against.
What this example shows
- The file carries the run, the page its plate, the drawing the ink it was set against.
- Each packet is filed under the name of the program that left it and stamped with a moment.
- Nothing of it is drawn, and no reading software shows any of it.