Initial Work Topics <title>for the Second Cycle of the Text Encoding Initiative <docnum>TEI &docfile. <date>&docdate. </titlep> </frontm> <!> <body> This paper lists some work topics for the second cycle of the Text Encoding Initiative, to be supplemented as occasion warrants with further topics, either now or later. Most of the topics should be addressed by naming a work group to revise existing proposals or develop new ones; some should be assigned to existing working committees; some may be better addressed in agreements of work with affiliated projects. This paper does not include topics already assigned to committees TD and ML. Proposals for common procedural rules for the work groups are contained in a separate document. <!> <h1>1. Defined Topics <!> Version 1.0 of the Guidelines mentions a variety of topics as requiring further work; some others are commonly acknowledged in TEI planning as being reserved for the second cycle, though perhaps not mentioned in the current draft. These topics are mostly reasonably well defined; for some, proposals exist either in the TEI scheme or elsewhere. Some of these topics may require further splitting at a later date. <p> One working group has been formed for each of these topics. For some topics, we suggest some concrete goals; these are fleshed out further in the formal charge to the group. <ol> <li>character sets (group TR1) (extension to Eastern Europe, non-Latin alphabets, non-alphabetic scripts; revision of WSD; specification with ML of pack/unpack mechanisms; review of interchange recommendations; treatment of multi-byte proposals ŤISO 10646, Unicode, etc.Ů; multidirectional texts; allographs in Arabic and elsewhere) <li>text criticism (group TR2) (work with existing proposals; algorithms for translation among current forms; choice of a preferred form if possible; treatment of tags within variants; electronic versioning; text-critical annotation; recommendations for critical editions not relating to apparatus criticus) <li>hypertext and multimedia (group TR3) (reference schemes; live and blind references; canonical schemes; link annotation; out-of-line links; compatibility with existing hypertext software and current efforts at hypertext standards) <li>formulas, tables, figures, graphics (TR4) (develop more concrete recommendations) <li>newspapers (TR5) <li>corpora (TR6) </ol> <!> <h1>2. Ill-Defined Areas <p> Earlier planning called for the &TEI. to expand its recommendations, during the second cycle, into areas not addressed in the first cycle; experience thus far has also suggested areas into which we should also expand. In several cases, we are not yet in a position to break the area down into workable topics for working parties. That is, further work is needed to determine exactly what further work is needed. We recommend naming working groups to survey these fields and report back with suggestions for topics for working groups and an assessment of what working groups on these topics can be expected to achieve. <ol> <li>linguistics in general (AI1) <li>spoken texts and interview transcripts (AI2) <li>literary scholarship (AI3) <li>historical scholarship (AI4) <li>machine-readable versions of (print) dictionaries (AI5) <li>computational lexica (AI6) <li>non-dictionary reference works (TR7) <li>physical description of the copy text (analytic bibliography, codicology, paleography, history of the book arts) (TR8) </ol> <!> <h1>3. Usability Issues <p> The &TEI. must address usability issues directly if the Guidelines are soon to find wide adoption among the community we are trying to serve; it is not clear whether these are best dealt with by special working parties or as aspects of the TEI's cooperation with affiliated projects. <ol> <li>software assessment and benchmarking for SGML software <li>techniques for using non-SGML-aware software to good effect <li>facilities for implementers (subroutine libraries)? <li>coherence with conventions of major e-text sources (e.g. governments) <li>conventions of existing markup packages </ol> The two latter topics are primarily concerned with promoting convertibility between TEI conformant and other forms of encoded texts. <!> </body> </gdoc

.sr docfile = &sysfnam. ;.sr docversion = 1;.im teigmlp1 .* Document proper begins. Initial Work Topics <title>for the Second Cycle of the Text Encoding Initiative <docnum>TEI &docfile. <date>&docdate. </titlep> </frontm> <!> <body> This paper lists some work topics for the second cycle of the Text Encoding Initiative, to be supplemented as occasion warrants with further topics, either now or later. Most of the topics should be addressed by naming a work group to revise existing proposals or develop new ones; some should be assigned to existing working committees; some may be better addressed in agreements of work with affiliated projects. This paper does not include topics already assigned to committees TD and ML. Proposals for common procedural rules for the work groups are contained in a separate document. <!> <h1>1. Defined Topics <!> Version 1.0 of the Guidelines mentions a variety of topics as requiring further work; some others are commonly acknowledged in TEI planning as being reserved for the second cycle, though perhaps not mentioned in the current draft. These topics are mostly reasonably well defined; for some, proposals exist either in the TEI scheme or elsewhere. Some of these topics may require further splitting at a later date. <p> One working group has been formed for each of these topics. For some topics, we suggest some concrete goals; these are fleshed out further in the formal charge to the group. <ol> <li>character sets (group TR1) (extension to Eastern Europe, non-Latin alphabets, non-alphabetic scripts; revision of WSD; specification with ML of pack/unpack mechanisms; review of interchange recommendations; treatment of multi-byte proposals ŤISO 10646, Unicode, etc.Ů; multidirectional texts; allographs in Arabic and elsewhere) <li>text criticism (group TR2) (work with existing proposals; algorithms for translation among current forms; choice of a preferred form if possible; treatment of tags within variants; electronic versioning; text-critical annotation; recommendations for critical editions not relating to apparatus criticus) <li>hypertext and multimedia (group TR3) (reference schemes; live and blind references; canonical schemes; link annotation; out-of-line links; compatibility with existing hypertext software and current efforts at hypertext standards) <li>formulas, tables, figures, graphics (TR4) (develop more concrete recommendations) <li>newspapers (TR5) <li>corpora (TR6) </ol> <!> <h1>2. Ill-Defined Areas <p> Earlier planning called for the &TEI. to expand its recommendations, during the second cycle, into areas not addressed in the first cycle; experience thus far has also suggested areas into which we should also expand. In several cases, we are not yet in a position to break the area down into workable topics for working parties. That is, further work is needed to determine exactly what further work is needed. We recommend naming working groups to survey these fields and report back with suggestions for topics for working groups and an assessment of what working groups on these topics can be expected to achieve. <ol> <li>linguistics in general (AI1) <li>spoken texts and interview transcripts (AI2) <li>literary scholarship (AI3) <li>historical scholarship (AI4) <li>machine-readable versions of (print) dictionaries (AI5) <li>computational lexica (AI6) <li>non-dictionary reference works (TR7) <li>physical description of the copy text (analytic bibliography, codicology, paleography, history of the book arts) (TR8) </ol> <!> <h1>3. Usability Issues <p> The &TEI. must address usability issues directly if the Guidelines are soon to find wide adoption among the community we are trying to serve; it is not clear whether these are best dealt with by special working parties or as aspects of the TEI's cooperation with affiliated projects. <ol> <li>software assessment and benchmarking for SGML software <li>techniques for using non-SGML-aware software to good effect <li>facilities for implementers (subroutine libraries)? <li>coherence with conventions of major e-text sources (e.g. governments) <li>conventions of existing markup packages </ol> The two latter topics are primarily concerned with promoting convertibility between TEI conformant and other forms of encoded texts. <!> </body> </gdoc