Affiliated Projects: <title>Specification of TEI Interface <docnum>TEI &docfile. <date>&docdate. </titlep> <!> </frontm> <!> <body> <h1>Affiliated Projects---Specification of TEI interface <p> The following projects are (so far) identified to be officially affiliated with the TEI: <ul> <li>Tudor Text Base <li>Project Perseus <li>Women's Writer's Project <li>ACL/DCI <li>Vassar/CNRS Dictionary Project <li>ARTFL <li>Georgetown Center for Text and Technology <li>Milton DataBase <li>Network of European Corpora <li>Nietzsche Project <li>British National Corpus </ul> The terms and arrangements of affiliation are proposed to be as follows: <p> Each affiliated project will designate an official contact person for liaison to the TEI. This person's name, address, and e-mail address will remain in the TEI files in order that all TEI correspondance and information be sent to this person. This person shall serve as an interface between the TEI and the affiliated project, passing information from the TEI to the project, and from the project to the TEI. Ideally, this person shall be involved in the TEI, possibly by serving on a working group. <p> Each affiliated project will be assigned a technical contact person within the TEI, who will serve as a similar interface between the TEI and the project. This person will, to the extent possible, have expertise in areas of relevance to the affiliated project, and have knowledge of both the work of the affiliated project and the work within the TEI that is of direct relevance to the project. This person serves as the contact point in order to enable the project to gain information from within the TEI, either by providing this information him/herself or finding the relevant TEI personnel to provide it. (NOTE: a single person within the TEI may serve as liaison to more than one project, where appropriate.) <p> The goal of affiliation is to provide the affiliated project with details and technical assistance concerning the use of the TEI scheme as it is being developed, in order that the project may utilize the scheme during the development period; and on the other side to provide the TEI with information and feed back which may in turn be used to modify and improve the scheme. To this end, it is imagined that each project will agree to encode some text, utilizing some part of the TEI scheme, and that the encoded text (or some sample of that text) and a report on the experience of implementing the TEI scheme will be provided at some point before the end of the second TEI cycle of work. It is expected that in this report the affiliated project will provide detailed information concerning the following: (a) methods and problems of data capture and/or translation into the TEI scheme, depending on the nature of the project and the software used for data capture or translation (if any); and (b) adequacy of the TEI scheme itself, that is to say, the adequacy of the tags themselves, the adequacy of DTDs, etc. During the period of implementation, the TEI expects to provide intensive technical guidance to the affiliated project. This may involve both visits by the TEI technical liaison to the project site, and (TEI funded) visits by the affiliated project liaison or other staff to TEI working group meetings and/or workshops. <p> In general, the plan of interaction is expected to be roughly as follows, although it may vary as the needs of individual projects are taken into account. <ol> <li>1. Devising of a contract between the TEI and the project, outlining the following: <ul> <li>the text or texts to be encoded during the implementation phase; <li>(to the extent possible) the areas within the TEI scheme that will be implemented; <li>the method(s) of data capture or translation to the TEI scheme that will be used within the project; <li>the content of the final report, the extent of the sample texts, and the date when the report is due. </ul> <li>2. Extended (2-3 day?) visit by a TEI technical liaison to the project site, before the implementation is begun, to provide a detailed overview and technical assistance on the TEI scheme. <li>3. Funded attendance by an appropriate project representative at a TEI workshop (--is this redundant?) <li>4.1-3 funded visits by appropriate project staff to meetings of TEI working groups, or other visits as seen to be desirable <li>5. Where desirable, additional visits by TEI technical liaisons to the project site. <li>6. A final debriefing meeting between the affiliated project liaison and the TEI technical liaison, when the final report is delivered. </ol> <!> <h1>Budget for Average Case <ul> <li>1 2-3 day visit by technical liaison to project site <li>1 workshop attendance <li>2 attendances by AP member at working group meetings <li>1 additional technical liaison visit </ul> </body> <!> </gdoc

.sr docfile = &sysfnam. ;.sr docversion = 'Draft';.im teigmlp1 .* Document proper begins. Affiliated Projects: <title>Specification of TEI Interface <docnum>TEI &docfile. <date>&docdate. </titlep> <!> </frontm> <!> <body> <h1>Affiliated Projects---Specification of TEI interface <p> The following projects are (so far) identified to be officially affiliated with the TEI: <ul> <li>Tudor Text Base <li>Project Perseus <li>Women's Writer's Project <li>ACL/DCI <li>Vassar/CNRS Dictionary Project <li>ARTFL <li>Georgetown Center for Text and Technology <li>Milton DataBase <li>Network of European Corpora <li>Nietzsche Project <li>British National Corpus </ul> The terms and arrangements of affiliation are proposed to be as follows: <p> Each affiliated project will designate an official contact person for liaison to the TEI. This person's name, address, and e-mail address will remain in the TEI files in order that all TEI correspondance and information be sent to this person. This person shall serve as an interface between the TEI and the affiliated project, passing information from the TEI to the project, and from the project to the TEI. Ideally, this person shall be involved in the TEI, possibly by serving on a working group. <p> Each affiliated project will be assigned a technical contact person within the TEI, who will serve as a similar interface between the TEI and the project. This person will, to the extent possible, have expertise in areas of relevance to the affiliated project, and have knowledge of both the work of the affiliated project and the work within the TEI that is of direct relevance to the project. This person serves as the contact point in order to enable the project to gain information from within the TEI, either by providing this information him/herself or finding the relevant TEI personnel to provide it. (NOTE: a single person within the TEI may serve as liaison to more than one project, where appropriate.) <p> The goal of affiliation is to provide the affiliated project with details and technical assistance concerning the use of the TEI scheme as it is being developed, in order that the project may utilize the scheme during the development period; and on the other side to provide the TEI with information and feed back which may in turn be used to modify and improve the scheme. To this end, it is imagined that each project will agree to encode some text, utilizing some part of the TEI scheme, and that the encoded text (or some sample of that text) and a report on the experience of implementing the TEI scheme will be provided at some point before the end of the second TEI cycle of work. It is expected that in this report the affiliated project will provide detailed information concerning the following: (a) methods and problems of data capture and/or translation into the TEI scheme, depending on the nature of the project and the software used for data capture or translation (if any); and (b) adequacy of the TEI scheme itself, that is to say, the adequacy of the tags themselves, the adequacy of DTDs, etc. During the period of implementation, the TEI expects to provide intensive technical guidance to the affiliated project. This may involve both visits by the TEI technical liaison to the project site, and (TEI funded) visits by the affiliated project liaison or other staff to TEI working group meetings and/or workshops. <p> In general, the plan of interaction is expected to be roughly as follows, although it may vary as the needs of individual projects are taken into account. <ol> <li>1. Devising of a contract between the TEI and the project, outlining the following: <ul> <li>the text or texts to be encoded during the implementation phase; <li>(to the extent possible) the areas within the TEI scheme that will be implemented; <li>the method(s) of data capture or translation to the TEI scheme that will be used within the project; <li>the content of the final report, the extent of the sample texts, and the date when the report is due. </ul> <li>2. Extended (2-3 day?) visit by a TEI technical liaison to the project site, before the implementation is begun, to provide a detailed overview and technical assistance on the TEI scheme. <li>3. Funded attendance by an appropriate project representative at a TEI workshop (--is this redundant?) <li>4.1-3 funded visits by appropriate project staff to meetings of TEI working groups, or other visits as seen to be desirable <li>5. Where desirable, additional visits by TEI technical liaisons to the project site. <li>6. A final debriefing meeting between the affiliated project liaison and the TEI technical liaison, when the final report is delivered. </ol> <!> <h1>Budget for Average Case <ul> <li>1 2-3 day visit by technical liaison to project site <li>1 workshop attendance <li>2 attendances by AP member at working group meetings <li>1 additional technical liaison visit </ul> </body> <!> </gdoc