TEI Council 2002-06-24 Conference Call Notes
Names are copied-and-pasted from TEI website, so don't blame me for misspellings :-).
Initialis Used for People
Contents
Call commenced at ~ 12:01-00 with GR, SB, FJ, PW, MP, LB, SR, JU, DB; MD joined a bit later; CW & TE never joined (nor did DD nor LR, but that was expected).
CW & TE, it turns out, were the victims of mistaken timezone.
committee reports
Training
GR explained the training committee had written 1 general and 2 specific (for Chicago 2002-10, and for GA 2003) RFPs for training courses. Suggested that within a few weeks all 3 would be edited & posted. SB said the programme committee for the Oct member's meeting would like that specific RFP out ASAP, preferably shortly after MMs return. GR thinks that's reasonable (he will be talking to MM on phone circa 06-28).
Thanks to the training committee for this work.
Lou recommends that the three RFPs be combined into one; general agreement, there should be one RFP, with an appendix that gives particulars for upcoming events that require specific proposals.
GR notes that, esp. for proposals for training at the Oct member's meeting, they do not have to be full-blown proposals. SB points out that programme committee is expecting a 1-day training on Thu 2002-10-10.
Although questions about an RFP may (or should) be sent to the training committee, and questions about the venue, etc., may (or should) be sent to the local organizer, the Proposals themselves should be sent to JU, who will forward them to the Council for [dis]approval.
Motion that amended (as discussed) RFPs be accepted; passed.
certification
Software certification discussion: we're leaning towards encouraging reviews of software (cull form TEI-L?) (certify reviewers? certify reviews?)
P5
core tags and schema
Discussion of SR's proposal notes for conference call on 24th 2002-06-24 00:25+01-- SB thinks timescale aggresive, but SR & JU think it's reasonable (better to have too aggresive a deadline than none at all).
SB agrees strongly that TSD become an additional tagset, and that P5 be written in (possibly extended) TSD.
SR suggests Son of Odd report for members meeting 2002-10; SB suggests [dis]approval by Council in 2003-01; SR recommends including discussions of manuscript, char sets, standoff to that 2003-01 council meeting; MP reports manuscript should be ready.
Within the discussion there was concensus that it's important to change from DTD notation to some other notation inside <elemDecl>s (whether a pre-existing schema or our own is still an open question), and to allow multiple schema output from odds (i.e., to give TEI users choice in which schema language they use to validate their TEI documents).
Motion to accept SR's timetable as a framework approved.
character encoding WG update
LB reports on char sets WG progress -- lots of discussion via e-mail, mostly centered on how much of the world's problems Unicode solves. Face-to-face WG meeting planned for 2002-07-23/24 in Tübingen (in conjunction with ALLC/ACH 2002). Both SB & plan to be present. WG is working on detailed proposals for a replacement to WSD mechanism which LB (& SB) expect will be discussed at WG meeting in Tübingen. CW doing good job keeping it going w/o domination by a particular person or constituency.
Council agreed that requirement for 1.5 days of meeting in order to obtain TEI reimbursement be waved, if needed, for this WG meeting. It was suggested that council need not vote, that chair could just do this unilaterally.
stand-off markup, xlink, xpointer WG
Council wanted assurance that an editor would be available for each call; SB & LB do not think this will be a problem.
Someone voiced concern as to whether or not council should be worried about lack of progress — [preliminary or draft? -- SB] report is due [2002-08-01 or 2002-10-11? -- SB]. SB said no need to worry yet, but should recheck after [2 or 3] of the planned conference calls (and then become concerned if little or no progress).
medieval MSS description
While MP may not be at member's meeting (snif! What's wrong with a TEI meeting as a honeymoon? Well, congratulations in any case), she is still hopeful that she and MD can get together this summer to hammer out differences in manuscript description stuff.
next meeting, assignments, future business
Future meetings: We like conference calls; SB suggests one roughly every 3 months.
SR points out we need to have firm deadlines before 2003-01 face-to-face, as it's expensive.