teip5-dkclarin-schema
author: Lene Offersgaard
language: en
availability: This template file is freely available and you are hereby authorised to copy, modify, and redistribute it in any way without further reference or permissions. When making such modifications, you are strongly recommended to change the present text to include an accurate statement of the licencing conditions applicable to your modified text.

TEI Complete

of the TEI (P5) modules. This is a very useful starting place for manually creating your own customizations — it is much easier to delete the modules you do not want than to add the modules you do. Furthermore this customization often proves helpful for testing TEI software.This TEI customization describes a schema that includes all of the TEI (P5) modules. This is a very useful starting place for manually creating your own customizations — it is much easier to delete the modules you do not want than to add the modules you do. Furthermore this customization often proves helpful for testing TEI software.all of the TEI (P5) modules. This is a very useful starting place for manually creating your own customizations — it is much easier to delete the modules you do not want than to add the modules you do. Furthermore this customization often proves helpful for testing TEI software.This TEI customization describes a schema that includes all of the TEI (P5) modules. This is a very useful starting place for manually creating your own customizations — it is much easier to delete the modules you do not want than to add the modules you do. Furthermore this customization often proves helpful for testing TEI software.

However, this particular TEI customization is not recommended for actual use for encoding documents. It produces schemas and reference documentation that will be much larger, and include many more elements, than almost anyone could conceivably ever need. Tempting though it may be simply to have absolutely everything, and just ignore elements not required, experience has shown that their presence makes the documentation harder to read and use, and makes a schema that is far more lax than desired.

<titleStmt>

<publicationStmt>

<fileDesc>