TEI/MEP DTDs
This page provides pointers to the document-type definition files for the TEI / MEP encoding scheme.
For a full description of the derivation of the DTD, see the document “TEI/MEP Encoding Scheme”. For documentation, see the “Reference manual”.
XML DTDs
The simplest way to use the TEI/MEP encoding scheme is to use one of the pre-compiled ‘single-file’ DTDs. They are derived mechanically from the TEI extension files listed below, using the driver files also listed below. The extension files and driver files are available for situations where they are more helpful than the pre-compiled DTDs.
Pre-compiled DTDs
There are several pre-compiled DTDs, matching different levels of encoding, as described in “Markup Guidelines for Documentary Editions”:
- meptei1x.dtd
- The pre-compiled DTD for level-1 encoding.
- meptei2x.dtd
- The pre-compiled DTD for level-2 encoding.
- meptei3x.dtd
- The pre-compiled DTD for level-3 encoding. Most documents on the MEP web site are currently encoded using this DTD.
- mepteix.dtd
- The pre-compiled DTD for the archival-form encoding.
TEI extension files
The TEI Guidelines (TEI P3) define a method for customizing the TEI DTD that requires the following two DTD fragments.
- mep.dtd
- The declaration of new and modified elements, for the archival form.
- mep.ent
- Modified parameter-entity declarations, for the archival form.
- mepdc.dtd
- The declaration of new and modified elements, for the data-capture form.
- mepdc.ent
- Modified parameter-entity declarations, for the data-capture form.
DTD driver files
The following ‘driver’ files invoke the TEI DTDs and the extension files listed above; they are used in generating the pre-compiled DTDs.
- mep-drvx.dtd
- Driver file for the archival form.
- mep-drv1x.dtd
- Driver file for level one of the data-capture form.
- mep-drv2x.dtd
- Driver file for level two of the data-capture form.
- mep-drv3x.dtd
- Driver file for level three of the data-capture form.
SGML DTDs
The simplest way to use the TEI/MEP encoding scheme is to use one of the pre-compiled ‘single-file’ DTDs. They are derived mechanically from the TEI extension files listed below, using the driver files also listed below. The extension files and driver files are available for situations where they are more helpful than the pre-compiled DTDs.
Pre-compiled DTDs
There are several pre-compiled DTDs, matching different levels of encoding, as described in “Markup Guidelines for Documentary Editions”:
- meptei1.dtd
- The pre-compiled DTD for level-1 encoding.
- meptei2.dtd
- The pre-compiled DTD for level-2 encoding.
- meptei3.dtd
- The pre-compiled DTD for level-3 encoding. Most documents on the MEP web site are currently encoded using the XML version of this DTD.
- meptei.dtd
- The pre-compiled DTD for the archival-form encoding.
TEI extension files
The TEI Guidelines (TEI P3) define a method for customizing the TEI DTD that requires the following two DTD fragments.
- mep.dtd
- The declaration of new and modified elements, for the archival form.
- mep.ent
- Modified parameter-entity declarations, for the archival form.
- mepdc.dtd
- The declaration of new and modified elements, for the data-capture form.
- mepdc.ent
- Modified parameter-entity declarations, for the data-capture form.
DTD driver files
The following ‘driver’ files invoke the TEI DTDs and the extension files listed above; they are used in generating the pre-compiled DTDs.
- mep-drv.dtd
- Driver file for the archival form.
- mep-drv1.dtd
- Driver file for level one of the data-capture form.
- mep-drv2.dtd
- Driver file for level two of the data-capture form.
- mep-drv3.dtd
- Driver file for level three of the data-capture form.