Dear TEIers,

For those attending the TEI 2009 MM in Ann Arbor,
I propose a Tools SIG working meeting Saturday,
November 14, 10 a.m. - 12:00 p.m.
The place will be the Government Documents Center
(room 203), Hatcher Graduate Library North.

If you are interested in what could be discussed
during that Tools meeting, I suggest that you first subscribe
to the TEI-TOOLS-SIG mailing list :
http://listserv.brown.edu/archives/cgi-bin/wa?A0=tei-tools-sig
And then begin discussion on the meeting agenda there.

For the moment, here is a list of possible topics to discuss
just coming from my hat.
This list and its structure is open and not exhaustive
and not mandatory of course.
We should augment it, select it and sort it by priority.
If it grows to much or needs another way of being
synthesized, we could create a page on the TEI wiki
to hold the Tools SIG working meeting agenda.

a- the goals of the Tools SIG
-- better communicate on available software and environments
--- regularly remember people on TEI-L to describe their
software in the wiki
--- better define the relation between the main tei-c web site
and the wiki concerning software description
--- maybe look for alternative technologies to the wiki for
describing available software (see for example :
http://www.projet-plume.org/en)
[the TEI wiki software description template and categorization
system is really nice anyway]
-- what kind of software must be described
-- what kind of users are targeted : beginners, experts, software makers...
-- what kind of usages : digitizing, authoring, processing,
analysis, conservation, transportation, transformation, publication...

b- its relation to the other SIGs : for example with the Education SIG
which could be interested in being helped to make tool tutorials, videos...
for example for :
- Oxygen authoring through CSS
- Oxygen authoring
- Oxygen+XPath
- Oxygen+XQuery
- Roma

c- the relation between XML-TEI aware software and
the TEI Guidelines evolution
-- for example, I have started a thread on the TEI-L list about the
way TEI texts could expose some specific software related
parameters in the TEI Header to help software to process them.
XML Processing Instructions (PI) are a mecanism for XML processing.
But the TEI may define its own specific mecanism for processing also.
This could be related to general software but also to some more
specific processes - like speech corpora specific software or
Natural Language Processing enriched at the word level corpora
oriented software for example.

d- benchmarking corpora : of good quality, interest, size and "free"

e- better share software knowledge and know-how especially
in the open source software domain
-- we could catalog not only software or stylesheets but also scripts,
components, libraries, workflows, most interesting programming languages...
-- are there well known software architectures that we should follow
to share more efficiently code
-- what are the best places to host an open source project (sourceforge,
google code, savannah...)
-- are there interesting hosting services for online prototypes
-- code licensing experience

I would appreciate any comments and ideas about the above items
in the TEI-TOOLS-SIG mailing list or in the TEI Wiki.

Best regards,
Serge

--
Dr. Serge Heiden, [log in to unmask], http://textometrie.ens-lsh.fr
ENS-LSH/CNRS - ICAR UMR5191, Institut de Linguistique Française
15, parvis René Descartes 69342 Lyon BP7000 Cedex, tél. +33(0)622003883