February 2020 - Tei-council

change in date of next Stylesheets meeting
by Syd Bauman 04 Feb '20

04 Feb '20

100% of the people at today's Stylehseets meeting cannot make the next scheduled date, Tue 03 Mar 20. Thus we would like to move it to Tue 17 Mar 20 (St. Patrick's Day). I have already changed it on the Google Calendar. (Didn't know I had that power! :-) But if there are objections ...

1 0

Stylesheets meeting?
by Raffaele Viglianti 04 Feb '20

04 Feb '20

Hi all, I see on the calendar that there's a stylesheets meeting tomorrow (Tues) at 9am EST, but haven't heard any concrete plans yet. Is it happening? Raff

4 4

time to merge in <standOff>, eh?
by Syd Bauman 03 Feb '20

03 Feb '20

With great thanks to Peter, Martin, and Martina the changes have been reviewed. I've addressed almost all the issues mentioned (still hoping someone can come up with better wording than "makes explicit the multiplicity of the collection"). Mr. Jenkins is happy with the sydb-standOff branch, and it builds fine locally on my machine here. (Not perfectly, but no worse than the dev branch.)-: So I think perhaps it is time to wrap in the sydb-standOff branch into dev, yes? Any objections?

3 2

F2F meeting location
by Scholger, Martina (martina.scholger＠uni-graz.at) 03 Feb '20

03 Feb '20

Dear all, We have three magnificent options for our F2F meeting and need to make a decision. Peter offered to host us in Paderborn, Nicolas in Oxford, and Magdalena in Warsaw. Thanks to all of you for your willingness to host us! Please fill in the (anonymous) doodle poll by Monday, Feb 3: https://doodle.com/poll/vpncpziivf4fcfn6 Best, Martina

1 1

Internationalization working group proposal
by Scholger, Martina (martina.scholger＠uni-graz.at) 03 Feb '20

03 Feb '20

Dear all, as discussed in our last call, we (the group who met at the Scholarly Communication Institute in Chapel Hill to discuss "TEI and internationalization") want to establish a working group on "Internationalization (I18n)". Please find our proposal in this google doc: https://docs.google.com/document/d/1EyAWLkKF5oBeueSoNaES3NGeA2f_AGLtn8Kx9hb… It would be great if we could get a "go ahead" from the Council members this week. In case of your approval, is there any other formality that we have to observe or could we consider it as an official charge then? Best, Martina

1 0

upcoming Stylesheets meeting
by Syd Bauman 03 Feb '20

03 Feb '20

We are planning to meet this coming Tue 04 Feb 14:00Z.[1] I am betting we will use the same Google Hangouts we have been for awhile,[2] but Martina will tell us. (Right, Martina?) Agenda ------ * anything required for release? * next meeting * ticket 403 * tickets 266 & 267 * ticket 370 Notes ----- [1] That's 06:00 PST 09:00 EST 14:00 GMT 15:00 CET Am I missing anyone's time zone? [2] https://hangouts.google.com/group/MCM1LEBUz2Kj9osA9

1 0

checking out <standOff>
by Syd Bauman 02 Feb '20

02 Feb '20

Stuff that's been done: * changed model.resourceLike to model.resource, and removed <TEI> from it * added new model.describedResource, which contains only <TEI> and <teiCorpus> * changed content models of <TEI> and <teiHeader> as discussed * created new <standOff> and model.standOffPart (to SA) * tweaked various bits of prose, e.g. the <remarks> for <settingDesc>, to talk about new <standOff> * updated the beginning of DS * changed prose and an example or two in CC where it talks about major structures for corpora to allow for nested <TEI> * tweaked prose in FS where free-standing <fsdDecl> is mentioned * tweaked prose in MS where <person> is discussed * changed an example in CO to show <standOff> * added a paragraph to DR about using <standOff> for a <castList> * changed prose and an example or two in ND to accommodate <standOff> * tweaked prose in PH to mention that <listTranspose> could be in <standOff> * tweaked beginning of SA, and added an entire new subsection later on, to discuss <standOff> - NOTE: left a stub "Placement of Stand-off Markup and Contextual Information" section that I haven't figured out if it should be kept or deleted, pr new subsection should be moved into it, or what * tweaked TS to remove implication that <listPerson> must be in <particDesc> (although for typical transcriptions of speech it may well be) What I think should be done next is each member of Council should pick one changed chapter and do a quick comparison of it between branch sydb-standOff and dev, reading the changed portions to see if they're OK.[1] In addition, a few people should read the <standOff> tagdoc and play with the schemas. So here is a checklist: https://docs.google.com/document/d/17S_W5vHzJZ_vCQw-Ze6SbOebqfz5KHq0xR9wauB… Please sign up for at least 1 chapter. Note that each chapter or tagdoc name is a link to the sydb-standOff version thereof. It would be good if all the reviews could be done by early Fri morning 24 Jan my time (EST). Notes ----- [1] For me the easiest way to do this is to put the dev and sydb-standOff versions of the HTML in two tabs in one window and pop back and forth between them. But to each his or her own. (But do note that there have been whitespace changes to some of the source files, so GitHub's compare functionality may not be ideal.)

3 3