- Tei-council - lists.tei-c.org

VF2F meeting: Jan 29 and 30
by Scholger, Martina (martina.scholger＠uni-graz.at) 28 Jan '21

28 Jan '21

Dear all, This is the agenda for our VF2F meeting: https://docs.google.com/document/d/1ditQHz4VXEitKZ7IeWO41tgzKZq_LwF0zclXHJF… I think that we first should work on pull requests (with milestone 4.2.0) and Guidelines issues with the milestone "Guidelines 4.2.0" which are still labeled with "Needs Discussion+Go" or do not have a status yet. For the North American Group - please start with whatever you like and fix issues from either or both of the tables. On Saturday the European group will continue. In the full Council session on Saturday we start with the discussion on ruby glosses. Please have a look at the issue and Martin's proposal on prose. Please feel free to add topics that you would like to discuss. Hugh will send a zoom link for tomorrow's meeting. Best, Martina

1 0

Stylesheets meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 28 Jan '21

28 Jan '21

Dear all, This is the zoom link for our Stylesheets meeting which starts in an hour https://us02web.zoom.us/j/88017340213?pwd=T3NTWmpFUWNrUWFaeU4zWHBBQUVqZz09 Best, Martina

2 1

Stylesheets meeting in 1 week
by Bauman, Syd 28 Jan '21

28 Jan '21

We are scheduled to hold a Stylesheets meeting on Thu 28 Jan 21 from 19:00Z to 20:30Z. That’s * 11:00–12:30 PST * 14:00–15:30 EST * 19:00–20:30 GMT * 20:00–21:30 CET We have not decided yet on a platform (although it seems to be Zoom vs Google Meet), or who will be hosting. Per last week’s Council meeting, our main topic will be Stylesheets #237<https://github.com/TEIC/Stylesheets/issues/237>. I hope to post a bit of a summary and some thoughts on this issue by the beginning of next week, but not guarantees.

4 4

Question on progress with the ruby work
by Martin Holmes 26 Jan '21

26 Jan '21

Hi all, I'm writing to Council because I need to get some clarity on what Council is aiming at with regard to the ruby markup proposal and the upcoming release. My initial understanding, and the work Syd and I have been doing, was based on the idea that we would really like to get a basic implementation of the new elements into the schema, along with a simple section for the prose chapter, in time for this release; that would allow the Japanese users in particular, who initiated the work, to get started with the markup and begin to work out some of the edge cases. However, the work on the ticket and the repo has become increasingly complexified; Duncan has submitted a set of cases that would stretch the initial implementation considerably and require a much-expanded prose section with many more examples, and this could not be ready for the upcoming release. My personal view is that these cases could be submitted as feature requests for further exemplification and expansion of the chapter prose, which we will need to do anyway, after the initial release, but Duncan is quite determined that he doesn't want to do that. There are also various discussions about multiple methods for doing stand-off ruby markup, some of which look quite flaky to me, and which I wouldn't really want to recommend in the Guidelines; but I'm not a content expert and don't have much authority to wield. As always, there is a lot of tension between the need for the Guidelines to provide straightforward, generic recommendations and the desire for people to see their own preferred approaches sanctioned and exemplified. I need to have something ready for the Council meeting on Saturday, so I'd like to get Council's view on what we're aiming to do right now. I think our options are: 1. Add only the new elements to the schema, with full Spec files and basic examples in them, but without any prose section in the Guidelines. 2. Add to #1 a relative short and straightforward introduction in the prose, with some basic worked examples, but no complicated edge cases, at the same time soliciting feature requests for further work. 3. Give up on getting anything into this release, and instead adopt a working-group approach to build a complete solution before we put anything into a release. My personal preference is for #2, but I don't think it's a decision I can make without Council's backing. Cheers, Martin -- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes(a)uvic.ca

3 2

Next Weekend's Council F2F: Timing Question
by Elisa Beshero-Bondar 25 Jan '21

25 Jan '21

Greetings, Council! Next Saturday, January 30, do we have any plans to meet after the times we posted in our minutes, namely: 06:00–10:00 PST 09:00–13:00 EST 15:00–19:00 CET ? I'm pretty sure not, but wanted to double-check as I'm trying to schedule something. Thanks, Elisa -- Elisa Beshero-Bondar, PhD Program Chair of Digital Media, Arts, and Technology | Professor of Digital Humanities | Director of the Digital Humanities Lab at Penn State Erie, The Behrend College Development site: https://newtfire.org

2 1

GitHub PRs
by Bauman, Syd 22 Jan '21

22 Jan '21

Inspired by Nick’s tei_current_assignments.py<https://github.com/npcole/teiutils>, a program that leverages the gitHub API to summarize gitHub issue assignments, I have just spent the entire day trying to write an XSLT program to summarize pull requests. At this point, I have to (at least temporarily) give up. I simply cannot figure out how to get the list of reviewers (those who have been asked to be reviewers, those who have accepted the request to be a reviewer, and those who have submitted reviews) without, at least sometimes, including the OP in that list. (That is, I have yet to figure out an XPath that will select the reviewers without the OP from the JSON-converted-to-XML returned by the “reviews” API call.) If anybody feels like helping me out, I think we would find this a useful utility. To prove the point, I generated one possible useful output (an HTML table) using my current mildly broken code, and went through and fixed the output by hand. (Sigh.) See https://bauman.zapto.org/~syd/temp/4TEICouncil/GHPRs.html. Talk to y’all tomorrow.

3 4

shift of validation need deprecation?
by Bauman, Syd 19 Jan '21

19 Jan '21

I am hoping to close several tickets, including #2062<https://github.com/TEIC/TEI/issues/2062> very soon. This one “needs discussion”, IMHO, only on the issue of whether or not deprecation is required. Could folks weigh in on the ticket, please? Issue: the @key attribute of <specDesc> is optional in the schema, but required by the Stylesheets. The request is to require it in the schema, too. Decision (unilateral, by me): yes, we should make @key of <specDesc> required by the schema. Question: Do we have to provide deprecation for this change? Discussion 1: The <specDesc> element “indicates that a description of the specified element or class should be included at this point within a document”. The @key attribute is the only mechanism by which the element or class you want to be included can be indicated. Therefore a <specDesc> without a @key is not doing what it is supposed to do. Currently, a <specDesc> without a @key passes validation, but then when processed by the Stylesheets the message “ERROR: no key attribute on specDesc” is generated (by Stylesheets/common/common_tagdocs.xsl); processing continues, and the spot where the @keyless <specDesc> occurred is simply blank in the output HTML. Discussion 2: We have decided in the past that, in general, changes that break backward compatibility should be deprecated. (I.e., users should get a warning, not an error, for 6 months to 2 years before the feature is changed to an error.) My opinion (on the question “Do we have to provide deprecation for this change?”): Emphatically not, this is a corrigible error. The change only effects when the user gets an error message, not if. One of the main reasons to have schema validation is to catch errors before you get to the processing stage. Discussion 3: One (especially a new member of Council) may well ask, why did I even bother raising this question? The answer is an abundance of caution. The question of whether or not a change need be deprecated is often an issue with disagreement within Council. I have a (well deserved) reputation for having a high threshold for requiring deprecation; others (including Peter and Martin) have a reputation for a much lower threshold. Thus it makes sense to make sure that I am not the only one who thinks this does not need deprecation.

4 3

tei_customization the shunned step child
by Bauman, Syd 18 Jan '21

18 Jan '21

Is there a reason that tei_customization.rn[cg] are not showing up in https://jenkins.tei-c.org/job/TEIP5-dev/lastSuccessfulBuild/artifact/P5/rel… Am I looking in the wrong place? BTW, where in the lastSuccessfulBuild hierarchy does one look for the .isosch files?

2 3

Meeting in 25 minutes
by Scholger, Martina (martina.scholger＠uni-graz.at) 14 Jan '21

14 Jan '21

Von: Scholger, Martina (martina.scholger(a)uni-graz.at) Gesendet: Montag, 11. Jänner 2021 23:25 An: tei-council(a)lists.tei-c.org Betreff: Next Council meeting: Jan 14 Dear all, This is the agenda for our next meeting on Thursday, Jan 14 at 11am-12:30pm PST/2pm-3:30pm EST/7pm-8:30pm GMT/8pm-9:30pm CET (please double check the meeting times in the google calendar): https://docs.google.com/document/d/1ofn0oIgmP5yyuCCfu4NF0Jw8lmNRMN44FN8gwsc…<https://docs.google.com/document/d/1ofn0oIgmP5yyuCCfu4NF0Jw8lmNRMN44FN8gwsc…> Please add topic that you would like to discuss. The zoom link is in the google doc. Best, Martina

3 2

Next Council meeting: Jan 14
by Scholger, Martina (martina.scholger＠uni-graz.at) 11 Jan '21

11 Jan '21

Dear all, This is the agenda for our next meeting on Thursday, Jan 14 at 11am-12:30pm PST/2pm-3:30pm EST/7pm-8:30pm GMT/8pm-9:30pm CET (please double check the meeting times in the google calendar): https://docs.google.com/document/d/1ofn0oIgmP5yyuCCfu4NF0Jw8lmNRMN44FN8gwsc… Please add topic that you would like to discuss. The zoom link is in the google doc. Best, Martina

1 0

Stylesheets - new meeting times
by Scholger, Martina (martina.scholger＠uni-graz.at) 04 Jan '21

04 Jan '21

Dear all, The cooperative Stylesheets meeting takes place every fourth Thursday of the month (two weeks after the regular Council meeting) from 11am-12:30pm PST/2pm-3:30pm EST/8pm-9:30pm CET. The first meeting will be on Thursday, January 28. Please cross-check the meeting times in the Google Calendar. With best wishes for 2021! Martina

1 0

Dec 20 ticket assignments
by Bauman, Syd 03 Jan '21

03 Jan '21

Finally got to it, sorry. Let me know if you are interested in my litany of excuses … 🙂 I left TEI #2073 and Stylesheets #480 unassigned, as they are blocked by another ticket. (They are the 2nd and 3rd parts of the 3 step sequence for the examples: change the content model (#2072), change the processing (#480), actually change the use of the element (#2073).) Number of tickets of current and recent Council members, loosely defined (TEI then Stylesheets): Syd Bauman = sydb 42 14 Elisa Beshero-Bondar = ebeshero 23 06 Vanessa Bigot_Juloux = vbigot-juloux 02 00 Meaghan Brown = MegJBrown 10 01 Loub Burnard = lb42 01 00 Hugh Cayless = hcayless 21 12 Nicholas Cole = npcole 13 07 James Cummings = jamescummings 05 03 Martin Holmes = martindholmes 08 13 Janelle Jenstad = JanelleJenstad 02 00 Jessica_H. Lu = lujessica 10 03 Elli Mylonas = emylonas 02 01 Helena Bermúdez_Sabel = HelanaSabel 02 00 Martina Scholger = martinascholger 18 03 Peter Stadler = peterstadler 17 09 Sarah Stanley = scstanley7 00 00 Magdalena Turska = tuurma 18 02 Raffaele Viglianti = raffazizzi 18 03 BTW, if you want to quickly see how many tickets are assigned to each GitHub user that has tickets assigned, try out Nick’s clever new tool. See https://github.com/npcole/teiutils. If you have Python 3.8 installed you can just issue python3.8 teiutils/bin/tei_current_assignments.py, and presto! P.S. HelenaSabel is now a member of TEIC on GitHub. I only auto-added her to the TEI Council group. Can she add herself to other teams as she wants, or does an owner or team member have to do that for her?

1 0

Martina for Chair!
by Bauman, Syd 03 Jan '21

03 Jan '21

Re: https://tei-c.org/activities/council/ So, first a question: who are you? I realize I am not sure who the webmaster is recently. Anyway, on the Council page the “Term January 2019 through December 2020” section should now be deleted, and the “Chair 2020” after Martina’s name should be changed to “Chair 2021” (or perhaps just “Chair”?). Thank you! P.S. Personally, I am still in favor of having a list of people who have served on the Council in the past, either on this page or pointed to by this page. But I have been saying that for years …

1 0

Reminder: Doodle: Stylesheets meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 29 Dec '20

29 Dec '20

Dear all, This is a reminder to fill in the doodle for the monthly Stylesheets meeting: https://doodle.com/poll/6nvai7q622sunhx5?utm_source=poll&utm_medium=link Options: * 1 week before the Council meeting* (same timeslot), * 1 week after the Council meeting* (same timeslot), * 2 weeks after the Council meeting* (same timeslot), or * some other time (please leave a comment if this is the case) * The regular Council meeting will be held every second Thursday of the month from 11am-12:30pm PST/2pm-3:30pm EST/8pm-9:30pm CET. Best, Martina

1 0

Happy holidays
by Scholger, Martina (martina.scholger＠uni-graz.at) 24 Dec '20

24 Dec '20

Dear Council, Thanks for a strange but still very productive year. Happy holidays and a good start into the new year in which we can hopefully meet face to face again at some point. Best, Martina

1 0

virtual short F2F meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 22 Dec '20

22 Dec '20

Dear all, We have a date for the virtual short F2F meeting. It is January 29 to 30. This is how it works: The North Americans start on Friday afternoon at 12am PST / 3pm EST The Europeans continue on Saturday morning at 10am CET The full Council meets on Saturday morning for US/CA, afternoon for Europeans. The original plan would mean 6am PST / 9am EST / 3pm CET. I'd suggest moving this back an hour or two since that seems very early for Janelle. Let's discuss this during our next call on January 14. Unfortunately Meaghan will not be able to join us on those dates, but there was no doodle option which suited everyone. Best, Martina

1 0

Doodle: Stylesheets meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 18 Dec '20

18 Dec '20

Dear all, Here is another doodle for the monthly Stylesheets meeting: https://doodle.com/poll/6nvai7q622sunhx5?utm_source=poll&utm_medium=link Options: * 1 week before the Council meeting (same timeslot), * 1 week after the Council meeting (same timeslot), * 2 weeks after the Council meeting (same timeslot), or * some other time (please leave a comment if this is the case) Best, Martina

3 2

monthly call: new meeting times
by Scholger, Martina (martina.scholger＠uni-graz.at) 18 Dec '20

18 Dec '20

Dear all, We have a decision for the new meeting times for the monthly Council call in 2021. The meeting will be held every second Thursday of the month from 11am-12:30pm PST/2pm-3:30pm EST/8pm-9:30pm CET. The first meeting will be on Thursday, January 14. Please check the Google calendar for the meeting times (Janelle and Helena - you should have access to the calendar). As always I will send the agenda and the zoom link a few days in advance. Best, Martina

2 1

ticket assignments and mentors
by Bauman, Syd 15 Dec '20

15 Dec '20

[Janelle and Helena — every month 1 person from Council is the “ticket triage” person. This person pays attention to new or otherwise unassigned tickets (actually called “issues”) on GitHub, and assigns them to one or more Council members; might also assign labels and milestone to each. This month I am the ticket triager.] IIRC at our last meeting we did not decide on mentors for our new members, instead deferring that decision to January. Does that mean I should not assign tickets to Janelle and Helena, either? My instinct is that I should go ahead and assign tickets to our new members now (so as to avoid forgetting or having unassigned tickets; besides, one of them requires a native Spanish speaker :-), with the understanding that until they have each gone through some orientation with their mentor next month, there is no expectation of actually tackling the tickets yet. As soon as they are ready, the tickets would be waiting for them, though. Any objections?

4 4

new meeting times
by Scholger, Martina (martina.scholger＠uni-graz.at) 09 Dec '20

09 Dec '20

Dear all, I've set up a doodle to coordinate the meeting times for the monthly Council meetings in 2021. I suggest to stick with the second week of each month (2nd Mon/2nd Tue etc.). In the doodle I have put in the January dates as an example. Please fill in the doodle by 2020-12-14: https://doodle.com/poll/486ypeh2nkzgtp9v?utm_source=poll&utm_medium=link Best, Martina

1 0

Next meeting: Dec 8
by Scholger, Martina (martina.scholger＠uni-graz.at) 04 Dec '20

04 Dec '20

Dear all, This is the agenda for our next meeting on Tuesday, Dec 8 at 6:00-7:30 PST, EST 09:00-10:30, GMT 14:00-15:30, CET 15:00-16:30: https://docs.google.com/document/d/1sToQJklZ9ZdXSE5nMXpxN9P1yZho9IVYvXW--u1… Please find the zoom link in the google doc. Best, Martina

1 0

virtual short F2F meeting January/February
by Scholger, Martina (martina.scholger＠uni-graz.at) 04 Dec '20

04 Dec '20

Dear Council, During the three days virtual F2F meeting in October we agreed on a VSF2F (virtual short face-to-face meeting) in late January or early February: * US/CA meet Friday afternoon / evening (~3 hours) * Europeans meet Saturday morning (~3 hours) * Council convenes as a whole on Saturday (morning for US/CA, afternoon for Europeans) (~4 hours) Please fill in the doodle: https://doodle.com/poll/8958wr5fqecfqxne?utm_source=poll&utm_medium=link For our new members: In addition to the monthly meetings we have in person meetings twice a year for three days (one in spring and one before or after the TEI Conference). This year we had two very successful meetings, but it is not possible to meet online for full three days, also because of the time difference. Since we do not expect in person meetings in 2021 (at least not in the first half of the year) we agreed to hold an additional meeting in January/February. Best, Martina

1 0

Stylesheets meeting addendum
by Bauman, Syd 03 Dec '20

03 Dec '20

Attn: Meaghan Brown, Martin Holmes, Martina Scholger, Elisa Beshero-Bondar, and Raff Viglianti Please see 2nd page of today’s notes<https://docs.google.com/document/d/11aTpKoEaXfYuHTbtCd7Vh6rxdeM-QVxcCp8Ej7V…>; if in a rush skip down to last section, “Current State of Play”.

4 7

Stylesheets meeting, Tue 01 Dec
by Bauman, Syd 01 Dec '20

01 Dec '20

We are scheduled to hold a Stylesheets meeting this coming Tue 01 Dec 20, 14:00Z, which is: * 06:00 PST (Victoria) * 09:00 EST (New York) * 14:00 GMT (London) * 15:00 CET (Berlin) I do not know on which platform we will meet, or who will be hosting. (I suppose as chair of this group I am supposed to figure that out, but so far y’all have pretty cleverly kept me out of the communication technology end of things.) Is Google Hangouts still viable? Anyway, topics include (but are not limited to): * ticket #471<https://github.com/TEIC/Stylesheets/issues/471>: Add permalink for examples * language processing; see https://wiki.tei-c.org/index.php?title=Mapping_language_processing * and, if we have ample time left over, we could re-tackle ticket #399<https://github.com/TEIC/Stylesheets/issues/399>: <code> in <desc> gets dropped in rng

4 3

run XSLT 1 from ant?
by Bauman, Syd 29 Nov '20

29 Nov '20

How do we run XSLT 1 from ant? (In particular, from P5/antbuilder.xml. I tried "trax", but get a fatal “XSLT 1.0 compatibility mode is not available in this configuration”.)

3 5