> 1. You seemed to me to do very well, especially considering > the inadequate support. Overall, things went very well. > I hope you didn't mind me bringing > Rebecca (aged 8) along. Not at all - I hope her Saturday morning wasn't too boring! > 2. Some papers that I suspect are yours became attached to mine. > I looked for you but did not know where you had gone. I'll > leave them off at the library in the hopes that they were > not needed in the meantime. No rush. Whenever we meet will be fine. > > 3. I hope you can explain that whole discussion that sprang from > LRECL and hierarchical files. No problem - I have it down pretty cold. There are lots of little changes I will need to implement. I also need to double check the SGML code you've previously done, as I found a couple of problems in the English-Language "code (e.g. - the Web pages). > > 4. I will start really settling down with codebook on Monday night. > [Make that Tuesday morning.] Just so things are clear, > > a. Where should I expect to find the latest approved official > versions of the document-structure-descriptions (i.e. the > discursive descriptions that we are converting to SGML)? They will be on the web. I'll try to get to them today. > b. My page holds the latest official version of cb1.dtd and > teicb1.dtd, right? To be precise: > > http://www.sils.umich.edu/~pfs/cb/cb1.dtd > http://www.sils.umich.edu/~pfs/cb/tei/teicb1.dtd Yes - as for as I'm concerned - those are the official versions at the moment. > > c. My first tasks as I see them are (and shout if I'm wrong): > > (1) Clean up the entire dtd to be consistent, accurate, > non-TEI-conflicting, etc. Yep - > (2) Revise it against the revised descriptions. Yes - as soon as I can get them up on the Web. > (3) Annotate it so as to clarify all decisions. As we go along, this needs to be done. I'll probably need to weigh in somewhere (either as comments in the DTD or in a separate documents) about some of the data considerations we made. > > (4) Create a full and accurate list of > > element names > attribute names > entity names Yes - and we'll need to eventually build in some hyper-links to other standards. > (5) Convert the revised cb1.dtd into a revised teicb1.dtd > [i.e., using parameter stand-ins begining with %n. > > (6) Convert the revised elements list into a revised > teigisc2.ent or whatever that file is called. > > (7) Work with John (on his return--he is actually *OUT OF > EMAIL CONTACT!*) to create a functioning, parsing, > dtd named tei-codebook.dtd. [JPW is back and has > a suggestion about the failure to parse, but more > may be going on...] That will be the exicting part. > (8) tag a real live document and parse it under this > functioning dtd. Yep - it would be good to have a tagged document by the IASSIST conference (mid-May)- preferably (but not necessarily) with a functioning DTD. > (9) Only then begin to consider further revisions based > on experience with real live tagging. I imagine we'll be getting feedback in the Spring/Summer. > (10) Document every step on the web page fully. Would be helpful! > > 5. Completely beside the point: I noticed that the machine > at Angel that I was sitting at had what appeared to be > a Windows version of Emacs installed on it. Do you know > anything about this? Seems vaguely familiar. Somebody at HTI or ITD should know. You could email online.consulting@umich.edu to see where it's installed on campus. If it's useful, we could try to get a copy for HTI or DIAD. Thanks again Paul! John Brandt Social Science Data Librarian Email: John.Brandt@umich.edu Harlan Hatcher Graduate Library Phone: 313-936-2932 University of Michigan Fax: 313-764-0259 Ann Arbor, MI 48109-1205 URL: http://www-personal.umich.edu/~jmbrandt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=