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

Next meeting: July 14
by Scholger, Martina (martina.scholger＠uni-graz.at) 10 Jul '20

10 Jul '20

Dear all, Our next Council meeting is on Tuesday, July 14 at EST 09:00-10:30 / GMT 14:00-15:30 / CEST 15:00-16:30. Please add issues to the agenda that you want to discuss on Tuesday: https://docs.google.com/document/d/1ffGOmKq_EY_ZFBNMfoR59VlX6QfaHBuwCpmvOvH… The Zoom-link is in the google doc. Best, Martina

1 0

Stylesheets coop meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 06 Jul '20

06 Jul '20

Dear all, I've set up a zoom meeting for our cooperative Stylesheets meeting tomorrow at 6:00 PDT / 9:00 EDT / 14:00 BST / 15:00 CEST: https://us02web.zoom.us/j/83142838842?pwd=NUFSS05UNXVEWnlTQkpzUDBmVDdndz09 Best, Martina

1 0

ack! bad Syd, bad!
by Syd Bauman 04 Jul '20

04 Jul '20

I just went to see from whom I am taking over as ticket triage person only to find that I screwed up, I was the ticket triage person for June, not July. Elisa -- you are the ticket triage person for July. I plan to make a run through the tickets tomorrow, and will hand the baton over to you shortly thereafter, OK? Sorry, y'all.

3 4

Git branch naming
by Hugh Cayless 03 Jul '20

03 Jul '20

Hi All, Some of you may have come across the recent move toward changing the default branch name in Git away from "master" to (probably) "main". My understanding is that GitHub is working on this, and that it will probably happen in Git as well. I'm aware of a number of projects that are moving ahead immediately on renaming their master branches. On the one hand, I'm generally in favor of this. The "master" terminology probably came from BitKeeper, which had "master" and "slave" repositories (rather than branches). I had always assumed it was meant in the sense of "master copy", like in sound recordings. But see also https://twitter.com/xpasky/status/1271477451756056577 from the person responsible for the name (not a native English speaker). On the other hand, I'm slightly cynical about this sort of thing, as it's the kind of change one can make and feel righteous about without being *actually* significantly anti-racist. It's a bit performative, but sometimes it's important to set an example. So I think we should consider going through the renaming process for TEI repos. There are probably some implications to doing that, broken links being the first one that comes to mind. What do you all think? Hugh

10 20

Re: [Tei-council] WG: A new tool for the TEI!
by Raffaele Viglianti 30 Jun '20

30 Jun '20

Didn't hit reply all. See below On Tue, Jun 30, 2020, 12:12 PM Raffaele Viglianti < raffaeleviglianti(a)gmail.com> wrote: > Hi Martina, > > Overall, it seems pretty fast to me, and I like how it's simple to create > a TEI file from a template and that elements and attributes are suggested > as you type. > Here are a few comments from testing on Ubuntu 18.04.4 LTS. > > These things should be there to make it truly useful in a teaching context: > - validation doesn't seem to trigger automatically, one needs to click > "Parse Buffer" to initiate it. This isn't bad per se, but it took me too > long to figure it out. I would recommend making the button more visible > (icon?) and call it something more descriptive (e.g. "Parse and Validate") > - show <a:documentation> values from the RNG when scrolling through > possible elements and attributes. This is the easiest way to know whether > an element is appropriate or not; I rely on it as a training device > - attribute values from closed or semi lists should be shown and documented > > Desiderata (besides the ones already mentioned by them): > - I'm not a jEdit user, but when the plugin is activated, all its > components appear in tiny floating windows that need to be docked. It's a > one-off operation, but frustrating, and I suspect younger students will not > be familiar with this kind of UI. It's possible that nothing can be done > about this, unless jEdit's API allows for a plugin to start "docked". > - it would be great to have a wrap element button or shortcut (Oygen's > Ctrl+e) > > Best, > Raff > > On Mon, Jun 29, 2020 at 8:12 AM Scholger, Martina ( > martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at> wrote: > >> Dear Council, >> >> >> >> Marjorie Burghart and Conal Tuohy have released their TEI plugin for the >> open source editor in jEdit. They would like to invite us for testing the >> tool and sending them feedback. >> >> Please see Marjorie’s email with all the details below. >> >> >> >> Best, >> >> Martina >> >> >> >> *Von:* Marjorie Burghart <marjorie.burghart(a)gmail.com> >> *Gesendet:* Montag, 22. Juni 2020 16:51 >> *An:* Scholger, Martina (martina.scholger(a)uni-graz.at) < >> martina.scholger(a)uni-graz.at>; James Cummings < >> James.Cummings(a)newcastle.ac.uk>; louburnard <lou.burnard(a)gmail.com> >> *Cc:* Conal Tuohy <conal.tuohy(a)gmail.com> >> *Betreff:* A new tool for the TEI! >> >> >> >> Dear Martina, Lou, Hugh and James, >> >> >> >> Conal and I are very pleased to let you know that a TEI plugin for the >> open source editor jEdit has been officially released: >> >> >> >> http://plugins.jedit.org/plugins/?TEI >> >> The plugin is slowly propagating through the mirrors of jEdit's Plugin >> Central, if you don't see it there yet it should appear shortly. >> >> >> >> Before making an official announcement, we would appreciate getting >> feedback from "power users" of the TEI :) We thought of you (and through >> Martina, of all Council members). If you have the time to give it a try, we >> would very much appreciate your feedback on potential bugs, ergonomy >> issues, etc. Conal thinks those first bugs could be fixed in a new release >> in a couple of weeks. >> >> >> >> Conal is hosting the source code on his github, where you could report >> issues: >> >> https://github.com/Conal-Tuohy/jEdit-TEIPlugin/issues >> >> and he has created a wiki page: >> >> https://github.com/Conal-Tuohy/jEdit-TEIPlugin/wiki >> >> >> >> How to proceed: >> >> - Install the latest version of jEdit http://www.jedit.org/ >> >> - Through the plugin manager (Plugins > Plugin Manager...), search the >> "TEI" plugin and install it with all its dependencies >> >> NOTA BENE: if you already had jEdit with the XML plugin installed, you >> will also need to update the XML plugin to the latest version. >> >> >> >> What it does: well, not everything :) The aim is NOT to replace Oxygen >> entirely, but to offer the community a viable free alternative, especially >> for teaching workshops and users with basic needs. We tried to cover the >> needs listed here (basic, and even some some deemed superfluous) : >> >> https://wiki.tei-c.org/index.php?title=Editor_for_teaching_TEI_-_features >> >> >> Conal is currently working on two other improvements: >> >> - schematron support >> >> - a mechanism akin to Oxygen's validation scenarios. >> >> >> >> The plugin has been developed by Conal, and the first steps in its >> development funded by a small grant I obtained from DARIAH - but Conal has >> done much more work "pro bono", and is kindly continuing development to >> enhance the features. If the community sees some use in this first step, I >> am planning to do my best to get further developments funded. >> >> >> >> Best wishes, >> >> Marjorie >> >> >> >> >> _______________________________________________ >> Tei-council mailing list >> Tei-council(a)lists.tei-c.org >> http://lists.lists.tei-c.org/mailman/listinfo/tei-council >> >

1 0

TCW30
by Scholger, Martina (martina.scholger＠uni-graz.at) 30 Jun '20

30 Jun '20

Dear Council, I've published the "Workload and Guidelines for Resignation" as TCW30: http://teic.github.io/TCW/tcw30.html Best, Martina

2 1

WG: A new tool for the TEI!
by Scholger, Martina (martina.scholger＠uni-graz.at) 29 Jun '20

29 Jun '20

Dear Council, Marjorie Burghart and Conal Tuohy have released their TEI plugin for the open source editor in jEdit. They would like to invite us for testing the tool and sending them feedback. Please see Marjorie’s email with all the details below. Best, Martina Von: Marjorie Burghart <marjorie.burghart(a)gmail.com> Gesendet: Montag, 22. Juni 2020 16:51 An: Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at>; James Cummings <James.Cummings(a)newcastle.ac.uk>; louburnard <lou.burnard(a)gmail.com> Cc: Conal Tuohy <conal.tuohy(a)gmail.com> Betreff: A new tool for the TEI! Dear Martina, Lou, Hugh and James, Conal and I are very pleased to let you know that a TEI plugin for the open source editor jEdit has been officially released: http://plugins.jedit.org/plugins/?TEI The plugin is slowly propagating through the mirrors of jEdit's Plugin Central, if you don't see it there yet it should appear shortly. Before making an official announcement, we would appreciate getting feedback from "power users" of the TEI :) We thought of you (and through Martina, of all Council members). If you have the time to give it a try, we would very much appreciate your feedback on potential bugs, ergonomy issues, etc. Conal thinks those first bugs could be fixed in a new release in a couple of weeks. Conal is hosting the source code on his github, where you could report issues: https://github.com/Conal-Tuohy/jEdit-TEIPlugin/issues and he has created a wiki page: https://github.com/Conal-Tuohy/jEdit-TEIPlugin/wiki How to proceed: - Install the latest version of jEdit http://www.jedit.org/ - Through the plugin manager (Plugins > Plugin Manager...), search the "TEI" plugin and install it with all its dependencies NOTA BENE: if you already had jEdit with the XML plugin installed, you will also need to update the XML plugin to the latest version. What it does: well, not everything :) The aim is NOT to replace Oxygen entirely, but to offer the community a viable free alternative, especially for teaching workshops and users with basic needs. We tried to cover the needs listed here (basic, and even some some deemed superfluous) : https://wiki.tei-c.org/index.php?title=Editor_for_teaching_TEI_-_features Conal is currently working on two other improvements: - schematron support - a mechanism akin to Oxygen's validation scenarios. The plugin has been developed by Conal, and the first steps in its development funded by a small grant I obtained from DARIAH - but Conal has done much more work "pro bono", and is kindly continuing development to enhance the features. If the community sees some use in this first step, I am planning to do my best to get further developments funded. Best wishes, Marjorie

1 0

circular build headache suggestion
by Syd Bauman 16 Jun '20

16 Jun '20

The circularity of the P5 and Stylesheets builds depending on each other has bitten us once again. (Ouch!) We have a situation now where the Stylesheets tests can succeed only against either the release branch of P5 or the dev branch of P5, but not both simultaneously. This sucks. Right now Stylesheets dev branch is successfully building against P5 release[1], but failing against P5 dev branch[2]. We believe that the reverse would make a lot more sense. While it is desirable that it build against both branches, it is frequently impossible. So we have to pick one, and we (Martin & Syd) think we should pick them as follows: * P5 release branch should be built with the P5 release Stylesheets * P5 dev branch should be built with the P5 dev Stylesheets * Stylesheets release should be built against P5 release branch * Stylesheets dev should be built against P5 release dev as a general rule. This means we would have to always release a new Stylesheets the same day we release P5 every time. It also means that if we ever had a reason we needed to do an interim release of either, we would have to fight with the circularity problem (probably by trying to make sure both branches work against each other, or temporarily suppressing some finicky tests). But the advantage is that "normal" releases and updates would work properly. So what we would like to do is: * Update Stylesheets deb branch tests so that they work against P5 deb (which will break them against P5 release branch) * Have Peter & Martin agree on a consistent set of explicit job names in Jenkins that perform the 4 builds listed above. Notes ----- [1] E.g. on jenkins.tei-c job "Stylesheets-dev" and jenkins2.tei-c job "Stylesheets-dev-against-P5-release". [2] E.g. on jenkins.tei-c job "Stylesheets-dev-against-TEIP5-dev" and jenkins2.tei-c job "Stylesheets-dev-against-TEIP5-dev".

3 8

off topic: new ODD based non-TEI schema
by Peter Stadler 16 Jun '20

16 Jun '20

Dear all, here I want to bring to your attention a project of a colleague called "Music Performance Markup" (MPM): https://axelberndt.github.io/MPM/ I want to share this with you because it’s a great example of an ODD based non-TEI schema, and it features a nice rendering of the documentation. If we ever wanted to redesign our Spec pages, this might give us some ideas :) Have fun Peter

1 0

Another thought on <annotation>
by Hugh Cayless 12 Jun '20

12 Jun '20

Had a bit of a brainstorm this morning, and I came up with another idea re representing WADM annotations. See #9 at https://docs.google.com/document/d/15lPVs89ehDNpQQ3Qf79kfRAECSN-MT_SpBlQpHU…. I'd be grateful for your opinions. Hugh

1 0