<?xml version="1.0" standalone="yes"?>
<Paper uid="W01-1503">
  <Title>The TELRI tool catalogue: structure and prospects</Title>
  <Section position="11" start_page="0" end_page="0" type="concl">
    <SectionTitle>
5 Conclusions
</SectionTitle>
    <Paragraph position="0"> The paper reported on the set-up of the TELRI corpus-tool catalogue, concentrating on the technical issues involved in its creation (form interface), storage (DocBook) and display (XSLT). At present, the input form is operational and the catalogue contains a few sample entries and has a preliminary (default) rendering of its contents. The current version of the catalogue and templates is available at http://nl.ijs.si/telri/ In the future, we hope to flesh out the catalogue with more tools, and enlist the services of TELRI experts in providing user support for them. The catalogue will, where license permits, also archive a copy of the software, and will continue with a proactive adoption of the GNU license and open standards.</Paragraph>
    <Paragraph position="1"> The open (non-profit) nature of the tools we attempt to identify lends them well for pedagocial purposes at the graduate and undergraduate courses in natural language processing, corpus linguistics and language engineering.</Paragraph>
    <Paragraph position="2"> The tool catalogue, as well as TRACTOR, could also be made a part of the Open Language Archives Community mentioned in the introduction. To join OLAC a number of changes and mappings would have to be defined, say from the on-line form onto Dublin Core and the OLAC Metadata Set. The choices currently listed in the template could also be changed into a controlled vocabulary to facilitate searching.</Paragraph>
    <Paragraph position="3"> The process of catalogue updates is currently manual. To automate the production of the on-line version of the catalogue directly from new form entries would be relatively easy, given sufficient volume to justify this. More challenging would be (semi)automatic tracking of new tools that become available via various (OLAC) archives and announcements.</Paragraph>
  </Section>
class="xml-element"></Paper>