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

shooting the messenger : make still broken
by Lou Burnard 03 Jul '19

03 Jul '19

Thinking about this debacle again, it seems to me that the approach taken in issue #370 (oh tei_simpleprint.odd has stopped working: so there must be something wrong with it) is really not defensible. 1. The unmodified tei_simplePrint odd is structured in exactly the same way as countless other ODDs, not excluding the TEI Guidelines. It has free floating globs of specification elements, which are invoked from a single schemaSpec by means of specGrpRefs. 2. The only thing which is slightly different about it is that some objects are declared more than once in multiple specGrps, with @mode=change. This is because the specGrps are organised thematically (for example one contains changes needed to introduce processing models, another contains changes needed to introduce schematron rules). This kind of logical organisation is perfectly reasonable as far as I am aware, indeed why else bother to have specGrps. 3. The only objection I can see to it is that an ODD processor has to decide how to combine two or more @mode=change specs. It's not just a matter of applying one set of changes: there may be a bunch of them. This is kind of the way unification grammars work in NLP: you build up the complete spec one bit at a time. Yes, occasionally you may find contradictions -- one spec adds an attribute x (say) which another one deletes, or gives a different datatype to. But this is not the only place where ODD processing is underspecified and rules of thumb are not hard to imagine (e.g. delete always wins; in the absence of delete, most recent modification always wins; etc.). 4. Moreover, and this is where I am really a bit annoyed, THIS USED TO WORK! So some infrastructural change has made it impossible to run the makefile and impossible to use the simpleprint odd as originally designed. And instead of trying to find what change has caused this, we are shooting the messenger. This my friends is called zealotry. In the immortal words of Michael SpMcQ in another recent context, "please don't".

7 27

feedback on teiCorpus
by Scholger, Martina (martina.scholger＠uni-graz.at) 01 Jul '19

01 Jul '19

Dear Laurent, dear Council, As discussed, we want to send an email to the TEI-L announcing the introduction of nesting TEI elements and asking for feedback on the proposal to deprecate <teiCorpus>. I made a first draft for this email here (https://docs.google.com/document/d/1Jlk0FUHjUKlN-1-WAqhlhYReT2yq_eIbYP66osk…) and ask you to chime in. I suggest to send this on Wednesday. Best wishes, Martina

2 6

nesting TEI
by Syd Bauman 28 Jun '19

28 Jun '19

Hugh -- I have 1. created a 'nest_TEI_deprecate_teiCorpus' branch 2. updated the <desc> for <TEI> (English only) 3. added <TEI> to model.resourceLike 4. begun the process of updating the prose HOWEVER, 1) I can't really test it well, because the build process is broken. But what I can easily test, it seems to be fine. 2) I have run out of time and have not even proofread the changes I made to DS and CC. Over to you ...

2 1

make broken?
by Lou Burnard 27 Jun '19

27 Jun '19

My occasional practice of doing git pull make in my local copy of the dev repo seems to have hit a rock again. ../run-onvdl tei_simplePrint.nvdl tei_simplePrint.odd /usr/bin/onvdl fatal: file not found: /home/lou/Public/TEI/P5/Exemplars/tei_simplePrint.nvdl (No such file or directory) java -jar ../Utilities/lib/trang.jar tei_simplePrint.rng tei_simplePrint.rnc java -jar ../Utilities/lib/trang.jar -o disable-abstract-elements tei_simplePrint.rng tei_simplePrint.xsd /home/lou/Public/TEI/P5/Exemplars/tei_simplePrint.rng:475:61: error: reference to undefined pattern "att.global.rendition.attribute.rendition" Makefile:71: recipe for target 'tei_simplePrint.dtd' failed make[1]: *** [tei_simplePrint.dtd] Error 1 make[1]: Leaving directory '/home/lou/Public/TEI/P5/Exemplars' Makefile:201: recipe for target 'exemplars' failed make: *** [exemplars] Error 2

5 11

Re: [Tei-council] priorities
by James Cummings 25 Jun '19

25 Jun '19

If no one else has time to test this (which I agree with Raff is a priority), I'll do so before Friday afternoon. Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Raffaele Viglianti <raffaeleviglianti(a)gmail.com> Sent: Monday, June 24, 2019 10:44:20 PM To: Bauman, Syd Cc: TEI Council Subject: Re: [Tei-council] priorities Sorry to add fuel to the fire, but I have also just sent a very simple PR to generate different p5subset.json files for each supported languages. If this gets included in the release, the Vault will have all the data needed for Roma (beta). If not, I'll keep pulling data from my server until the next release. I tested locally and got the output I expected, but it would be great to have someone else look it over and merge it into dev. https://github.com/TEIC/TEI/pull/1890 Best, Raff On Sun, Jun 23, 2019 at 5:51 PM Syd Bauman <s.bauman(a)northeastern.edu<mailto:s.bauman@northeastern.edu>> wrote: EBB> For right now, it seems a higher priority to resolve the EBB> release-blocking problems on dev connected with simplePrint.odd EBB> ..., doesn't it? Well, yes, but the question is whether *I* should be tackling the nesting-<TEI> issue (for which I will find the schema changes easy, but the prose changes will take me a long time because I'm slow at that sort of stuff), or the stylesheet problems. (If someone else is already 1/2-way to fixing it, speak up! :-) HC> It would be a bit of a shame to lose it. I could work on it when HC> I’m back home this weekend. Or on the plane on Friday for that HC> matter... Thanks. Might be a good idea. Although to be fair, we would not be losing it, just not tucking it in until next release. (When, honestly, it might make a bit more sense, anyway.) MS> ... my understanding was that we already decided on the nesting MS> TEI element, regardless of the deprecation of teiCorpus. Right; I'm just talking about timing, not whether-or-not. (And in part, timing so we can get feedback from community.) MS> I am aware that we agreed on having LR propose this to the list, MS> but on second thought my feeling is that such a suggestion should MS> better be coming from the Council. I would therefore suggest that MS> I draft an email to the list and circulate it to you. My thought is "go, girl!". But perhaps the right thing to do is for you to write up a draft, and send it to LR as well as to us so that he can chime in, too? EBB> It isn’t looking as if this sent, so I am trying again... I had gotten it just fine. _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org<mailto:Tei-council@lists.tei-c.org> http://lists.lists.tei-c.org/mailman/listinfo/tei-council

1 0

priorities
by Syd Bauman 24 Jun '19

24 Jun '19

Martina (and all) -- where are we on the big nesting TEI issue? I had planned to spend my TEI time between now and release working on that, so at this release <TEI> would be able to nest, and the documentation would include this possibility (whether we deprecated use of <teiCorpus> now or not). But a) I'm not sure I'm clear to move ahead on that; and b) I'm wondering if I shouldn't be spending time on the Stylesheets issues instead? I realize that means bumping nesting-<TEI> another 6 months (which would make *me* sad), but that may not be a bad thing if we're still waiting for LR's post to TEI-L and the fallout therefrom.

5 6

Stylesheets meeting in ~3.5 hours
by Syd Bauman 21 Jun '19

21 Jun '19

We will be holding a Stylesheets group meeting this afternoon: 13:00 PDT 16:00 EDT 21:00 BST 22:00 CEST today. Google Hangouts unless someone says otherwise. Peter won't be able to join us. He wants us to work on getting the build to work. Elli probably won't be there. She wants us to work on ticket 370. The good news is that Martin & I just discovered they are the same thing. We've put some info about how far we got on the ticket, so if you can read up on https://github.com/TEIC/Stylesheets/issues/370 before we start. -- Syd Bauman, NRP (he/him/his) Senior XML Programmer/Analyst Northeastern University Women Writers Project s.bauman(a)northeastern.edu or Syd_Bauman(a)alumni.Brown.edu

1 0

Today’s meeting
by Peter Stadler 21 Jun '19

21 Jun '19

Hi all, I’m most probably on the road tonight and won’t be able to meet with you, sorry :( But it’d be great if you were able to tackle the current build problems :) Best Peter

1 0

release planning
by Scholger, Martina (martina.scholger＠uni-graz.at) 20 Jun '19

20 Jun '19

Dear all, Here is a quick reminder regarding the upcoming release: Refridge: June 30-July 8 Freeze: July 9-13 Create release branch: July 14 Release: July 16 Please have a look at the issues assigned to you and add those which you plan to do before the release to the 3.6.0. milestone. @Luis: currently, there is no place for release techs to login to the server and deploy the new release. Are you available on July 16 in case we need your help with this? Our next Council call is scheduled for July 19, which is after the release. Do we need to meet before that? This might be difficult since some of us are at the DH conference in Utrecht the week before... Best, Martina

1 0

Re: [Tei-council] oxygen plugin
by Scholger, Martina (martina.scholger＠uni-graz.at) 18 Jun '19

18 Jun '19

Excellent! Von: James Cummings <James.Cummings(a)newcastle.ac.uk> Gesendet: Dienstag, 18. Juni 2019 13:40 An: Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at>; TEI Council <tei-council(a)lists.tei-c.org> Betreff: Re: oxygen plugin Doh! It was indeed that. I thought just deleting it from the managed add-ons was enough. I didn't read the instructions well enough. Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk> Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Scholger, Martina (martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at>) <martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at>> Sent: 18 June 2019 12:34 To: James Cummings; TEI Council Subject: AW: oxygen plugin Hi James, Are the new <object...> elements allowed? And it is no longer in the list of "Update Sites URLs" (Options > Preferences > Add-ons)? Best, Martina Von: James Cummings <James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk>> Gesendet: Dienstag, 18. Juni 2019 13:12 An: Scholger, Martina (martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at>) <martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at>>; TEI Council <tei-council(a)lists.tei-c.org<mailto:tei-council@lists.tei-c.org>> Betreff: Re: oxygen plugin Hi Martina, Although documents validate and transformations work, in my 18.1 Oxygen, I still get it looking for updateSite.oxygen at www.tei-c.org<http://www.tei-c.org> even though the add-on is installed from jenkins lastSuccessfulBuild. I removed all extensions, restarted, prior to installing it. See screenshot below. Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk> Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org<mailto:tei-council-bounces@lists.tei-c.org>> on behalf of Scholger, Martina (martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at>) <martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at>> Sent: 18 June 2019 09:54 To: TEI Council Subject: [Tei-council] oxygen plugin Hi all, I tested the oXygen plugin with version 18.1., 19.1, and 20.1. and it works. In version 18.1 and 19.1. I already had the plugin installed, so it did not work when I just replaced the link in options > preferences > add-ons. I had to uninstall it in help > manage add-ons first. In version 20.1 the plugin was not installed before and I just added the link in options > preferences > add-ons. Can anyone confirm case 1? Best, Martina

1 0