Note: For sample code you may have to scroll horizontally in the blocks since it is entered as perforated text
Visual-Meta
This is what we call Visual-Meta. It is an approach to add information about a document to the document on the same level of the content, same as would be necessary on a physically printed page, as opposed to as a data layer since this data layer can be lost and it makes it harder for a user to take advantage of this data. The core data is information about the document to allow users to cite the document. It in the same format at the BibTeX citation for the document. The minimum information is ‘Citation Visual-Meta’ Which is 100% BibTeX for that document as the publisher designed it, which means it will be parsed by others according to their rules. This also includes a Visual-Meta ID which is used to help software know what documents are on the user’s system. It starts with data and time (in UTC) the document was ‘created’ then 11 characters from title, using random characters if title is shorter. This can also include the document’s ‘Reference Section’ which includes the BibTeX the publishers used to create the References in the document. ‘Extended Visual-Meta’ includes headings, Endnotes, Glossary, Notes, Errata and so on. 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 is. For example @dublin-core or @rdfs could wrap the content formatted according to those standards. Feel free to add your own tags but please describe them in this introduction section in order for others to derive value from them now and in the future. This was written Sumer 2021. More information is available from https://visual-meta.info or from emailing frode@hegland.com for as long as we can maintain these domains.
@{visual-meta-start}
@visual-meta{ version = {1.1},
generator = {ACM/Sheridan Production System Name},
organisation = {ACM},
vm-id = {2021-7-17T18:00:00:00Z;kitromeioliso}
}
@{citation-visual-meta-start}
@inproceedings{10.1145/3372923.3404798,
author = {Kitromili, Sofia and Jordan, James and Millard, David E.},
title = {What Authors Think about Hypertext Authoring},
year = {2020},
isbn = {9781450370981},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/3372923.3404798},
doi = {10.1145/3372923.3404798},
abstract = {Despite significant research into authoring tools for interactive narratives and a number of established authoring platforms, there is still a lack of understanding around the authoring process itself, and the challenges that authors face when writing hypertext and other forms of interactive narratives. This has led to a monolithic view of authoring, which has hindered tool design, resulting in tools that can lack focus, or ignore important parts of the creative process.},
booktitle = {Proceedings of the 31st ACM Conference on Hypertext and Social Media},
numpages = {10},
keywords = {authors, digital interactive narratives, hypertext fiction, digital interactive storytelling, authoring tools, authoring, interactive fiction},
location = {Virtual Event, USA},
series = {HT '20},
vm-id = {2021-7-17T18:00:00:00Z;kitromeioliso}
}
@{citation-visual-meta-end}
@{extended-visual-meta-start}
@{references-start}
@inproceedings{inproceedings,
author = {Nakasone, Arturo and Ishizuka, Mitsuru},
year = {1970},
month = {01},
pages = {127-138},
title = {SRST: A Storytelling Model Using Rhetorical Relations},
volume = {4326},
isbn = {978-3-540-49934-3},
doi = {10.1007/11944577_13}
}
@inproceedings{Riedl2009IncorporatingAI,
title={Incorporating Authorial Intent into Generative Narrative Systems},
author={Mark O. Riedl},
booktitle={AAAI Spring Symposium: Intelligent Narrative Technologies II},
year={2009}
}
@{references-end}
@{document-headings-start}
@{document-headings-start}
@heading{
name = {ABSTRACT},
level = {level1}
}
@heading{
name = {Nick Montfort},
level = {level2}
author = {Nick Montfort}
}
@heading{
name = {KEYWORDS},
level = {level1}
}
@{document-headings-end}
@{document-headings-end}
@{extended-visual-meta-end}
@{visual-meta-end}