.sr docfile = &sysfnam. ;.sr docversion = 'Draft';.im teigmlp1 .* Document proper begins. TEI Steering Committee Meeting <title>20-21 September 1990, Chicago <title>Tentative Agenda <docnum>TEI &docfile. <date>&docdate. </titlep> </frontm> <!> <body> <ol> <li>Report <ol> <li>Responses from readers <li>Revisions proposed to date <li>Reprinting </ol> <li>Fall Workshops <ol> <li>Arrangements <li>Attendance: committee members, working groups, affiliated projects, others <li>Financing </ol> <li>Future Workshops and Tutorials <ol> <li>ACH-ALLC 91 <li>ACL-91 <li>Commercial sector conferences </ol> <li>Committees and Working Groups <ol> <li>Committee Heads: Johansson: problems with time and with lack of payment from Pisa <li>Plans for DOC and Metalanguage <li>Restructuring TR and AI <ol> <li>TR: critical editions, new character sets, papyri, . . . <li>AI: literary: classic, medieval, modern; history; . . . <li>Topics, WG heads, and suggested members </ol> <li>Establish schedules for deliverables for Committees and Working Groups <li>Proposal for a WG on Historical Sources (AHC) </ol> <li>Affiliated Projects <ol> <li>Review Nancy's proposal <li>Appoint liaison members </ol> <li>Administrative Support <ol> <li>Michael's arrangements at UIC <li>Lou's arrangements at OUCS <li>Role of support people: mail reports; maintain budget and accounting information; record feedback from report; develop DTDs; create examples; other tasks? </ol> <li>Financial Issues <ol> <li>Redirection of funds: Support working group rather than committee meetings, at least for TR and A & I; Support Affiliated Projects <li>Industry solicitation: Encourage participation as well as contributions; Provide tutorials, multiple documentation? <li>ACH <li>EEC <li>Pisa </ol> <li>Usability Issues <ol> <li>User's Manuals / Tutorial Guides / Notes for Implementers <li>Example applications from raw data through software tools to SGMLized files with illustrations of processing capabilities </ol> <li>Software Support <ol> <li>Relate report contents to existing software <li>Acquire and experiment with existing software <li>Motivate development of new software <li>Incorporate software recommendations and specifications into Final Report <li>Establish formal relations with software suppliers: Get reactions and evaluations; Get them to incorporate our guidelines in their products </ol> <li>Publicity <ol> <li>News releases: Contents; schedules; distribution <li>Conference papers and talks <li>Journal articles <li>Tutorials and briefings materials: Standardize on visuals and syllabus materials <li>Working Paper releases <li>Maintaining a log of all these materials </ol> <li>Schedule <ol> <li>September/October 90: Workshops <li>November 90: Committee and Working Group Plans <li>November 90: Comments on First Report due <li>January 91: Response to comments due <li>March 91: Feedback on experience with Guidelines <li>June/July 91: New version of Report? <li>January 92: Final comments on distributed materials <li>March 92: Draft of Final Report <li>June 92: Distribution/Publishing of Final Report </ol> <li>Future Steering Committee Meetings <ol> <li>October 90 (Waterloo)? <li>December 90 with Committee and Working Group Heads (Oxford) <li>March 91 (ALLC/ACH Tempe) <li>June 91 (ACL Berkeley) </ol> <li>Publication and Distribution of Final Report <ol> <li>Commercial publisher: Kluwer, Oxford University Press? <li>Electronic distribution </ol> <li>Rockefeller grant and conference <!> </body></gdoc