[tei-council] open issues and planning

[Christian Wittern]

Sebastian Rahtz wrote:
> Wittern Christian wrote:
>>      (1) * chapter review, including review of examples
>>      (2) * decision on module dependency architecture made, and if yes
>> implemented
>>      (3) * remove instructions on how to invoke TEI DTD from each chapter
>>      (4) * New user needs to have an easy way to generate customization
>> ODD and generate schemas
>>      (5) * text of prose matches specs
>>      (6) * *Specs frozen! :-)
>>      (7) * Dictionary rewrite completed
>>      (8) * Modification and Conformance chapters rewritten
>>
>> I was wondering where we stand on these issues and how much work needs
>> to be done.  Since there is some dependency on this, it seems to me that
>> we should see how much is needed to achieve (6).  
> One absolute requirement here is to assess all outstanding bug reports
> and feature
> requests in SF, and deal with them one way or another. If, for example,
> Dan is
> going to raise issues about <choice>, that needs a quick agreement.
> 

The editors are supposed to take care of the SF requests, we expect
updates on this in our telcon.

> With my I18N hat on, there are now five groups translating
> descriptions of specs with a delivery date of the autumn
> at latest. I am taking it on trust therefore that the specs _are_
> frozen to all intents and purposes.

In an ideal world, the specs would have the approval from the Council
before being handed for translation.  I realize that reality has
overtaken us here, but it still is a situation that worries me.  Maybe
we need a status flag on the specs that indicates its state ("proposed",
"implemented", "tested", "approved") to track its status?


> The PERS activity will likely need some Specs adding. and dictionaries
> of course.

For P5 as a whole "frozen" should mean the statement "we have all we
need and it looks like we want it" is true for every individual spec.
Whereas for every individual spec itself, it would suffice to be true
for this one spec to be counted as frozen. So in that sense, I think
(hope!) we should be able to say that more tahn 95% of the specs are
frozen.

>> We also need a better way to track the progress -- Maybe we should start
>> a Wiki page for this?
>>   
> I did wonder about running trac (http://trac.edgewall.org/) as an aide.

Do you have experience with this?  It certainly looks good, but we can't
throw too much ressources on getting this up and running.

>> * infrastructure for examples (LB, SB)
>>   
> In my opinion, we have no resources to
> deal with this. I think its a distraction this year.

BUt we still need to be sure that it fits in our overall infrastructure
and leave a place where this can live.

Christian


-- 

 Christian Wittern
 Institute for Research in Humanities, Kyoto University
 47 Higashiogura-cho, Kitashirakawa, Sakyo-ku, Kyoto 606-8265, JAPAN