Comparison of TEI customizations and exemplars
Jump to navigation
Jump to search
This table provides an overview of the TEI Guidelines and some commonly confused customizations and exemplars of the TEI Guidelines. Keep in mind that in the interest of brevity, nuance is often lost. For more on any of the markup languages described, please see the documentation of that markup language.
| Markup language | Purpose | Designed for | Prescriptivism: how much freedom is offered in the way you encode a phenomenon? | Designed to be customized? | Other uses | includes a header? | ||
|---|---|---|---|---|---|---|---|---|
| TEI P5 | represent documents for machine processing | scholars, those developing customizations | often more than one | yes | ODD language can be used to specify other markup languages | yes | ||
| TEI P5 customizations | TEI Lite | learn to represent documents for machine processing | beginners | no | yes | |||
| Best Practices for TEI in Libraries | represent documents digitized at scale in a format suitable for digital curation | libraries, those thinking about digitization workflows | usually a single way is recommended | no (sort of) | yes | |||
| TEI Tite | provide specification for digitization vendors that does not require any expert knowledge of the content | digitization vendors | one (with a few exceptions) | no | no | |||
| TEI Simple | tagging subset | eliminating ambiguity for the encoder (much like TEI Tite) | publishers (in the broadest sense) of encoded texts | no | yes (but doesn't constraint as it does the body) | |||
| processing rules | providing default mechanism for processing and ability to customize the processing rules | yes | can be applied to other markup languages | n/a | ||||
