A "text" is an abstraction, created by or for a community of readers. Markup encodes and makes concrete such abstractions.
Only that which is explicit can be reliably processed
Now, imagine your budget has been halved. Repeat the exercise!
What is markup for?
Schema languages vary in the amount of validation they support
There are a variety of schema languages
All have different tool kits, different syntaxes, and different methods of doing things
The TEI was designed to support multiple views of the same resource
Module name | Chapter |
analysis | Simple Analytic Mechanisms |
certainty | Certainty and Responsibility |
core | Elements Available in All TEI Documents |
corpus | Language Corpora |
dictionaries | Dictionaries |
drama | Performance Texts |
figures | Tables, Formulae, and Graphics |
gaiji | Representation of Non-standard Characters and Glyphs |
header | The TEI Header |
iso-fs | Feature Structures |
linking | Linking, Segmentation, and Alignment |
msdescription | Manuscript Description |
namesdates | Names, Dates, People, and Places |
nets | Graphs, Networks, and Trees |
spoken | Transcriptions of Speech |
tagdocs | Documentation Elements |
tei | The TEI Infrastructure |
textcrit | Critical Apparatus |
textstructure | Default Text Structure |
transcr | Representation of Primary Sources |
verse | Verse |
att.naming
inherit from it attributes key and
ref; all members of att.typed
inherit from it type
and subtypeatt.typed
class, rather than define those attributes
explicitly.What tools do we need?
Now we've got a resource…
* we have not addressed these today.