7AAVIN01 Chap.4 Electronic Markup, from SGML to TEI
Electronic Markup, from SGML to TEI
Electronic Markup, from SGML to TEI explains what markup is and where it came from. It starts with the dictionary senses of markup and the idea of metainformation, with four conditions a markup system must meet. It distinguishes presentational, procedural and descriptive markup and shows why italics can hide several meanings.
It then follows generic coding from 1967, SGML as an international standard in 1986, the relationship between HTML and XML, the range of XML vocabularies, the principle of single source and multiple outputs, and the Text Encoding Initiative. The history explains rules you will apply in Oxygen.
The committee that followed generic coding concluded that no closed set of tags could describe every document, that markup should describe rather than instruct, that it should follow the hierarchy of a document, and that it should be precise enough for people and machines alike.
SGML turned those ideas into a grammar for building vocabularies, and XML simplified it in 1998 with strong input from the digital humanities community. Because descriptive XML keeps content apart from presentation, one source can feed many outputs, which is the strongest argument for markup in a project report.
A worked example converts three italic passages into descriptive tags, and practice items check the difference between a metalanguage and a vocabulary and the order in which the standards arrived.
What this chapter covers
- 01
Dictionary senses of markup
- 02
Metainformation and its conditions
- 03
Presentational, procedural and descriptive markup
- 04
Generic coding and GenCode
- 05
SGML as a metalanguage
- 06
HTML, XML and XHTML
- 07
Single source, multiple outputs
- 08
The Text Encoding Initiative
Worked example · free
Classify three kinds of markup
- 1(a) Presentational: it controls only how the text looks.
- 1(b) Descriptive: it names what the text is and leaves appearance to a separate process.
- 1(c) Procedural: it gives formatting instructions to a particular output.
Key terms
- Descriptive markup
- Markup that names the logical or semantic structure of a text and leaves presentation to a separate process.
- Metalanguage
- A grammar for creating markup vocabularies, as SGML is, rather than a fixed set of tags.
- Text Encoding Initiative
- A consortium and its XML-based guidelines for representing texts in digital form.
- Single sourcing
- Keeping one marked-up source from which web, print and other outputs are generated.
- Generic coding
- The 1967 proposal to separate a text's content from its formatting instructions, developed as GenCode.
Electronic Markup, from SGML to TEI FAQ
What is the difference between presentational and descriptive markup?
Presentational markup controls how text looks, as a WYSIWYG editor does. Descriptive markup records what each part of a text is, such as a title or a foreign phrase, and lets a separate process decide its appearance.
Why is SGML called a metalanguage?
It does not supply one fixed set of tags. Instead it defines rules for creating useful vocabularies, which is why many different document types could be built on it and later on XML.
How many elements does TEI contain?
The lecture describes TEI as containing about 500 elements, highly customisable and always a work in progress, maintained by a consortium whose guidelines libraries, museums, publishers and scholars have used since 1994.
How is HTML related to XML?
Both descend from SGML. HTML grew separately through the browser wars and was rationalised by the World Wide Web Consortium from 1996; XML arrived in 1998 as a simplified SGML, XHTML wrote HTML in XML, and HTML5 need not follow XML rules.
Why does the lecture show XML for trains, chemistry and music?
The examples show that XML is a grammar, not one vocabulary. Railway timetables, molecules, business documents, geographic coordinates and musical notation all use the same syntax with different element names, which is why TEI can serve texts while other schemes serve other domains.
What conditions must a markup system meet?
The lecture lists four. It must represent every character of a text, mark the text's structure, offer a place for information that is not part of the text, such as documentation or file details, and be applied consistently throughout.
Assessment move
Take a page of any printed book and list every visual signal on it: italics, headings, indentation, footnote numbers. For each, write the descriptive element you would use instead. Then explain in two sentences why that conversion matters for search. Revisit the four committee conclusions until you can state them without notes. Practise the history as a chain of reasons: each standard solved a problem left by the one before.
Finally, write a three-sentence answer to the core reading's question about when you would choose XML over HTML, JSON or Markdown, and test it on a friend.