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

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

Welcome to our new members!
by Scholger, Martina (martina.scholger＠uni-graz.at) 23 Nov '20

23 Nov '20

Dear all, Welcome to our new Council members Helena and Janelle! Our webmaster Luis Meneses added you to the Council's and Board-Council's mailing lists to give you an opportunity to keep up to date with what is going on before your term starts officially in January. You should also have received an invitation for the Google Drive folder "TEI-Technical-Council" were we collect our meeting minutes, the GitHub repository, the shared Google calendar, and the Slack channel. New Council members will be assigned a mentor to help you get started. If you have any questions please do not hesitate to contact me. Best, Martina Martina Scholger Centre for Information Modeling Austrian Centre for Digital Humanities University of Graz A-8010 Graz | Elisabethstraße 59/III +43 316 380 2291 martina.scholger(a)uni-graz.at<mailto:martina.semlak@uni-graz.at> http://informationsmodellierung.uni-graz.at<http://informationsmodellierung.uni-graz.at/> | http://gams.uni-graz.at<http://gams.uni-graz.at/> Chair of the TEI Technical Council | http://www.tei-c.org/ Institut für Dokumentologie und Editorik e.V. | https://www.i-d-e.de/

1 0

Meeting in 30 minutes
by Scholger, Martina (martina.scholger＠uni-graz.at) 10 Nov '20

10 Nov '20

Hi all, our call starts in 30 minutes: https://docs.google.com/document/d/1P-DFu-mPB9Xhva2Up2oXTG7HY55l-QgR6zOZLKU… Best, Martina

1 0

Next Council meeting: Nov 10
by Scholger, Martina (martina.scholger＠uni-graz.at) 09 Nov '20

09 Nov '20

Dear all, This is the agenda for our meeting tomorrow at EST 09:00, GMT 14:00, CET 15:00 https://docs.google.com/document/d/1P-DFu-mPB9Xhva2Up2oXTG7HY55l-QgR6zOZLKU… The zoom is linked in the google doc. Best, Martina

1 0

Evaluating the "Copia" version of the Guidelines
by Elisa Beshero-Bondar 04 Nov '20

04 Nov '20

Dear Council, After I had to exit early from this morning's Stylesheets meeting I was eager to see how Syd's "Copia" output of the Guidelines turned out. (For those who missed it, Syd found a quick way to output the Guidelines in a way that would prevent suppression of examples in other languages, and this seems mainly to affect the way the Guidelines Spec pages turn out (not the Guidelines chapter examples). I saw in the minutes that we're asked to review Syd's interesting output, named "Copia" (for more copious examples) and report back to the Council list. So started exploring element spec pages a little this evening. Here's what I'm finding: The bibl element is much improved by the Copia output: the examples are far more diverse, but not bewildering in number. I think it is fascinating to see non-English variety: - Copia: https://bauman.zapto.org/~syd/temp/4TEICouncil/html_GLs_all_eg_en/ref-bibl.… - Current: https://tei-c.org/release/doc/tei-p5-doc/en/html/ref-bibl.html The byline element is similarly a lot more interesting now: - Copia: https://bauman.zapto.org/~syd/temp/4TEICouncil/html_GLs_all_eg_en/ref-bylin… - Current: https://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-byline.html The gap element seems similarly improved, though there's a little problem here: - Copia: https://bauman.zapto.org/~syd/temp/4TEICouncil/html_GLs_all_eg_en/ref-gap.h… - Current: https://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html What I noticed right away was, the number of examples did not seem overwhelming, and the variety of languages evident before you had to click "Show All" reflects a good diversity with Asian languages rising to the fore. However(!) the duplicate example jumps out--duplicates in English. Turns out the French exemplum is identical to the English here, and I"m not really sure why. I think I've seen that in other specs as well. Meanwhile, the element p looks a bit more interesting now, and I think it improves on the current output: - Copia: https://bauman.zapto.org/~syd/temp/4TEICouncil/html_GLs_all_eg_en/ref-p.html - Current: https://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-p.html How about ab? Completely boring: no change at all, and it's sadly evident that we don't have enough examples in the first place. (If that isn't a ticket yet, it should be!) - Copia: https://bauman.zapto.org/~syd/temp/4TEICouncil/html_GLs_all_eg_en/ref-ab.ht… - Current: https://tei-c.org/release/doc/tei-p5-doc/en/html/ref-ab.html Okay-that's a start: a review of 5 out of 582 element specs (less than one percent...sigh). But so far I like the Copia version for what it illuminates about our range of exempla, both where it is diverse and where it is lacking. Looking forward to hearing what others think! 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

5 6

Stylesheets meeting Tue 03 Nov 20
by Bauman, Syd 01 Nov '20

01 Nov '20

We are scheduled to hold a Stylesheets meeting this coming Tue 03 Nov 22. Note the time may be different due to recent DST shift in north America: * 06:00 PST * 09:00 EST * 14:00 GMT (and UTC) * 15:00 CET The topic is pre-ordained from the VF2F Council meeting. The goal is to generate a version of the Stylesheets (in a branch, of course) that puts all examples in every language into the Guidelines outputs. Our fearless leader has prepared a GoogleDoc for us, which has the notes from the VF2F and can be used to take notes during the Stylesheets meeting.[1] Is Hangouts still OK for everyone? Note [1] https://docs.google.com/document/d/1uk_6CtLQIM9lrLPDWcFni48sfTqc9CtSk6SWcXl… [https://lh5.googleusercontent.com/oSVfkHOctyKLYcUfUFycQIkOu3kes8AUpXkCTuzR1…]<https://docs.google.com/document/d/1uk_6CtLQIM9lrLPDWcFni48sfTqc9CtSk6SWcXl…> 2020-11-03_StylesheetsGroup<https://docs.google.com/document/d/1uk_6CtLQIM9lrLPDWcFni48sfTqc9CtSk6SWcXl…> Stylesheets 2020-11-03 https://github.com/TEIC/TEI/issues/1934 Subgroup suggests this ticket for consideration by i18N SIG. 2020-10-24: HC: examples are on the agenda for future discussion of i8N group. RV: What would we be asking i18n? Shouldn't Council be doing the mechanism of this work... docs.google.com

1 0

TEI Customizations ODD issues?
by Hugh Cayless 29 Oct '20

29 Oct '20

Hi All, I guess this question is mostly for Syd, but since the customizations ODD is an exemplar, we're all kind of responsible for it. If I have bug reports, should I make GitHub issues for them? Issues I've run into: 1) @role="nonfatal" I think is not understood as a warning, and gets you the usual red underline/error presentation. I feel like warn and/or info might be better. Oxygen's supported role levels seem to be: "warn" or "warning" "error" "fatal" "info" or "information" 2) default values for required attributes are flagged. I can sort of see the logic there, but they're not *really* the same thing. 3) non-"tei:" schemes in @source are discouraged, but what if your source isn't a TEI release? I've got a couple of these, and I'd like to be able to put a URI in there without being yelled at. Hugh

2 2

VF2F meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 23 Oct '20

23 Oct '20

Dear Council, our VF2F meeting starts tomorrow at 9 EDT, 14 BST, 15 CEST Please find the agenda here: https://docs.google.com/document/d/1nIk4x5SDB0_EqSJG-DynzLz-n9WbmR0tjzM7Aax… Best, Martina

1 0