Skip to content

Don't Touch My SGML

· Balisage Series on Markup Technologies · Vol 31 · 0 citations

TL;DR

This paper starts off from a use case involving three separate SGML vocabularies that had to be supported going forwards, including adding other SGML vocabularies when needed, to take advantage of modern XML technologies for authoring and publishing.

Abstract

SGML used to be the future of documentation. It still is, because no matter how much we push for XML, we still need SGML. Entire business models rely on it, and if we want to use our newfound technologies (hey, XML is only 28 as I write this), we'd better make sure we can include the old. Author in XML? Yes, sure. Publish the XML? Yes, absolutely. But don't touch my SGML This paper starts off from a use case involving three separate SGML vocabularies that had to be supported going forwards, no matter what. That use case evolved into a more general approach to converting SGML to XML, including adding other SGML vocabularies when needed, to take advantage of modern XML technologies for authoring and publishing, including publishing back to SGML when needed. The resulting set of scripts and resources has been made freely available in the hope that it can help others looking for a way to manage SGML.

View source

Similar papers

Open access Sep 2026

<!--Does This Affect the Interpretation of What Follows?-->

It is argued that the fact that the subjects have ultimate authority over the interpretation of XML documents renders the documents hermeneutically unstable – an instability that even the inclusion of a comment specifying a principle for handling known and unknown information shifts rather than definitively resolves.

T. Tambassi · 0 citations
Review Aug 2026

Beyond the Editing Canvas: Evidence Divergence in OOXML-to-LLM Ingestion

This work systematically traverse and mine the OOXML specification and confirms 21 evidence forks across Excel, Word, and PowerPoint, spanning six dimensions of view construction, which show that exposure is shaped upstream of the model by the ingestion path and extractor configuration.

Side Liu, Jiang-Wen Liu, Jingqiang Xin et al. · 0 citations
Preprint Sep 2026

Is there a future for models in the LLM era?

In an era where software development is deeply tied with Large Language Models, does Model Driven Engineering (MDE) still make sense? This raises the question of the extent to which MDE can be successfully combined with an LLM approach to address the downsides of each approach separately. In this paper, we try to answe...

Marco Calamo, Massimo Mecella, Monique Snoeck · 0 citations
Review Open access Sep 2026

LLM-ASSISTED MARKUP OF ENTITIES IN TEI: A CASE STUDY

This paper presents a case study of marking up TEI (Text Encoding Initiative) documents using large language models. We detail our experiments using LLMs for named entity recognition and entity linkage in a corpus of TEI documents. The corpus consists of four journals co-edited by the Swiss-German theologian, Karl Bart...

Jonah Causin, Morgan Fuksa, Arne Käfer et al. · 0 citations
Review Aug 2026

Passages

Richard P. Gabriel's Patterns of Software: Tales from the Software Community is the kind of book that Passages, as a column, aspires to bring back to the attention of the software community. I am fairly sure this book, from 1996, is largely forgotten, but I think it deserves a wide audience, to this day, because it has...

Alex Groce · 0 citations
#artificial intelligence Preprint Aug 2026

Redakto - The Incognito Tab for LLMs

Large Language Models (LLMs) are being increasingly used in everyday applications. A major challenge in the context of LLMs or Artificial Intelligence (AI) in general is to ensure privacy when using them, meaning that personally identifiable information (PII) is removed from any text that enters an LLM. These challenge...

S. K. Saha, Tom Röhr, F. Biessmann · 0 citations

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.