| | 1 | = high level requirements for schema development = |
| | 2 | |
| | 3 | == technical == |
| | 4 | * schema language will be Relax NG |
| | 5 | * compact schema syntax will be used |
| | 6 | * schema will be modularized (cf. HTML schema) |
| | 7 | * trang will be used for conversion |
| | 8 | |
| | 9 | == procedural == |
| | 10 | * schema modules will be maintained with svn |
| | 11 | |
| | 12 | == design & capabilities == |
| | 13 | * compatibility with archimedes will be ensured when possible |
| | 14 | * compatibility with TEI P5 will be maintained in the absence of a reason to depart from TEI P5 |
| | 15 | * full use of XML potentials should be made |
| | 16 | * Dublin Core will be used for metadata |
| | 17 | * RDF will be used to indicate typing for DC metadata |
| | 18 | * use of entities will be minimized or eliminated (where and if possible) |
| | 19 | * vocabularies will be reused when possible |
| | 20 | * e.g. HTML tables; MathML; ChemML; SVG |
| | 21 | |
| | 22 | == modularity == |
| | 23 | * core module will incorporate base transcription mecanism for printed books (through 19th c.) |
| | 24 | * a module for manuscriptology and textual criticism (emendation; conjecture) |
| | 25 | * possibilities for modules for verse, etc. |
