Note: Commentary is italic. The first section should have the heading ‘Visual-Meta Appendix’ in the same font and size as other top level headings in the document. The following first sentence should be the same size as body text and the ‘tiny type’ should be small, as to not take up too much space but be accessible for those who want to scale the page to read it.


Visual-Meta Appendix

> Normal size font:

The information in very small type below allows software to provide rich interactions with this document. See for more information.

> Tiny type, same as the Visual-Meta itself:

This is what we call Visual-Meta. It is an approach to add information about a document to the document itself on the same level of the content. The same as would be necessary on a physically printed page, as opposed to a data layer, since this data layer can be lost and it makes it harder for a user to take advantage of this data. ¶ Important notes are primarily about the encoding of the author information to allow people to cite this document. When listing the names of the authors, they should be in the format ‘last name’, a comma, followed by ‘first name’ then ‘middle name’ whilst delimiting discrete authors with  (‘and’) between author names, like this: Shakespeare, William and Engelbart, Douglas C. ¶ Dates should be ISO 8601 compliant. ¶ The way reader software looks for Visual-Meta in a PDF is to parse it from the end of the document and look for @{visual-meta-end}. If this is found, the software then looks for {@{visual-meta-start} and uses the data found between these marker tags. ¶ It is very important to make clear that Visual-Meta is an approach more than a specific format and that it is based on wrappers. Anyone can make a custom wrapper for custom metadata and append it by specifying what it contains: For example @dublin-core or @rdfs. ¶ This was written Summer 2021. More information is available from or from emailing for as long as we can maintain these domains.