The Unwritten Glossary of the Digital Commons
I found myself this morning, as I often do, chasing a ghost. It was a term from an old technical report, a piece of jargon so specific to a long-defunct municipal project that it returned zero results in any search engine. The project itself is well-documented in the city’s open data portal—budgets, timelines, final outcomes. But the language, the particular texture of how those people spoke to one another, is gone. We have preserved the fossil, but we’ve lost the creature’s breath.
We speak so much of preserving data, of saving the ones and zeros that form the official record. We build archives to house the final reports, the legislation, the spreadsheets of public works. This is the skeleton of our civic body. But what of the muscle and the nerve? What of the slang of the planning department, the acronyms that made engineers chuckle, the shorthand that blossomed in the margins of meeting minutes? This is the unwritten glossary of the digital commons, and it is perhaps the most fragile thing we possess.
This lexicon isn’t official. It is born in hallway conversations, in the subject lines of internal emails, in the shared exasperation of a problem solved. It is the living language of a community at work. It defines a culture more accurately than any mission statement. And when a project concludes, when a department is restructured, or when staff retire, this language evaporates. It is the first thing to be forgotten because it was never formally remembered. The data remains, but its context—the human noise that gave it meaning—fades into silence.
The Whisper in the Machine
This presents a quiet, almost philosophical problem for digital preservation. We are adept at saving the what, but we are only beginning to understand how to save the how and the why. A future historian, looking at a dataset from our time, will see the figures. But will they understand the slight, almost imperceptible shift in terminology that indicated a change in political will? Will they sense the hesitation in a changed project code name?
These nuances are the whisper in the machine. They are not captured in a schema or a metadata field. They reside in the informal web of communication that exists just beside the official record. To preserve them requires a new kind of attentiveness. It means archiving the internal wiki that everyone used but no one thought was important. It means considering the value of the chat log, the project management board, the very doodles on a digitized memo.
It is a call to preserve not just the clean, curated data, but the wonderfully messy human activity that produced it. For the true record of our time is not just in the answers we produced, but in the language we invented to ask the questions. Saving that language is how we ensure the digital commons remains not just a repository of facts, but a living, comprehensible conversation.
Notes & further reading
A few pages I came back to while writing this: