Foundation
SGML — Structured Content Foundation Standard
Overview
What is SGML?
SGML (Standard Generalized Markup Language) is a standard for defining generalized markup languages for documents. As the ancestor of both HTML and XML, SGML provides the theoretical foundation for all modern structured content systems.
Key Features
- Document Type Definitions (DTD): define structure and content models
- SGML Declaration: character set and syntax rules
- Content models: define what elements can contain
- Entity management: handle special characters and external references
- Foundation for XML: understanding SGML illuminates modern markup
Also written as: Standard Generalized Markup Language · ISO 8879
Who SGML Applies To
SGML is an ISO standard and the ancestor of both HTML and XML. Almost nobody starts a new project in it. It matters because large legacy technical libraries are held in it — particularly in defense and aerospace, where content produced under earlier standards has outlived the tooling that created it — and someone has to be able to read those.
Where SGML Programs Go Wrong
- Assuming an SGML library converts cleanly to XML. Minimization, custom declarations and entity handling all need decisions, and the exceptions are where the effort lives.
- Losing the DTD. Content without the document type that defined it is significantly harder to interpret, and separated DTDs go missing more often than the content does.
- Deferring migration until the toolchain fails. Options narrow sharply once nothing can open the source.
How It Relates to Other Standards
SGML Questions
What is SGML?
An ISO standard for defining markup languages — the framework from which HTML and XML both descend. It introduced the ideas modern structured content still runs on: document type definitions, content models that constrain what may appear where, and entity management.
We have legacy SGML content. What now?
Establish what defined it before you plan to move it: the DTD, any custom SGML declaration, and the entity set. Conversion to XML is well-trodden but the cost sits in the exceptions rather than the bulk, and it rises the longer the source is left with no tooling that can read it.
What does SGML stand for?
Standard Generalized Markup Language. It is standardized as ISO 8879, published in 1986, and it is the framework from which both HTML and XML descend — HTML began as an SGML application, and XML is a simplified profile of SGML designed for the web.
What is the difference between SGML and XML?
XML is SGML with the flexibility removed. SGML permits minimization — omitted tags, abbreviated markup — and lets each document set its own syntax rules through an SGML declaration; XML fixes the syntax, requires every element to be explicitly closed, and makes documents parseable without their DTD. That strictness is why XML tooling is universal and SGML tooling is scarce, and it is also why converting SGML to XML involves real decisions rather than a mechanical translation.
Is SGML still used?
Rarely for new work, but substantially in legacy libraries — defense and aerospace programs produced decades of technical manuals in SGML under standards whose current revisions have since moved to XML. Those libraries still have to be read, revised, and eventually converted, which is why SGML capability remains a practical requirement rather than a historical one.
Where to Get SGML
SGML is standardized as ISO 8879, sold by ISO. For most teams the standard itself is less useful than the DTD and declaration that defined their legacy content — recover those from the original program before buying anything.
All standardsTechnical publications servicesTalk to us about SGML
Get In Touch
Let's Talk
Planning, building, or migrating SGML-compliant technical content? We can help.