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

Nov/Dec Telecon
by Hugh Cayless 17 Nov '15

17 Nov '15

Dear All, I’ve been remiss in scheduling our next teleconference due to some rather unfortunate family business I won’t bore you with. The end of November is tricky anyway because of Thanksgiving in the U.S.. I’ve created a Doodle poll to try to schedule it here: http://doodle.com/poll/wyuc3qiv9rkx4db6. I’ve also been very slow to say welcome to our new members, Elisa Beshero-Bondar, Elli Mylonas, Martina Scholger, and Magdalena Turska, who I believe are now subscribed to the list. We’re very glad you’re here! We’d be very pleased if you can join in this meeting, though obviously your presence is optional. I’ll be putting together an agenda, but the main business will I think be whether to release v3.0.0 with Pure ODD before the end of the year. We’ll also have to say a sad goodbye to our departing members, Fabio, Stefanie, Martin, and Paul. I expect this will probably be the last meeting of the year, given that most of us will be out for a big chunk of December, so if we have trouble scheduling it, we can push it a bit later. All the best, Hugh

4 4

GitHub tickets and new council members
by Raffaele Viglianti 13 Nov '15

13 Nov '15

Hello, I'd like to start working on tidying up our labeling system on GitHub, as we discussed at the F2F meeting. We thought about involving one of the new members in this process - who should we pick? Should we send an open call? Have the new members already been added and are reading this email? We also talked about mentoring and I think Elli wasn't assigned a mentor because she knows the job well already - though maybe working on this could be a good way of getting her acquainted with our GitHub workflow? Raff

2 1

A decision we have to take on oxygen-tei
by Martin Holmes 11 Nov '15

11 Nov '15

We're faced with a rather difficult decision with regard to the oxygen-tei plugin. The Oxygen guys have introduced a lot of new features, especially relating to CSS usage in Author mode (as far as I understand it), and they've made a point of using jTEI as one of their examples. However, their new stuff only works on Oxygen 17.1. They've put it in a branch on oxygen-tei: <https://github.com/TEIC/oxygen-tei/tree/update_oxygen_17_1> Our plugin currently works on versions going back to 15.2. If we merge these exciting new changes, then people using older versions of Oxygen will suddenly get an update that breaks or won't install (I don't know exactly what will happen). However, if we don't update, we'll be in the rather odd situation that Oxygen's release will always be more advanced than our version of our plugin, which makes our plugin sort of pointless, since the main reason for it is to exist is to enable users to get a more up-to-the-minute version of the plugin. I'm tempted to say that it might be time to retire our "official" TEI release of the plugin entirely. We could offer a bleeding-edge preview release of the plugin, based on our dev branches, which we would us for testing and would encourage savvy users with a need to get the absolute latest-and-greatest to install; but otherwise we would just rely on Oxygen's steady release cycle to keep the majority of our users up to date. That would mean a brief lag between the time that we do a major release and Oxygen does, when users of Oxygen would have no easy way to get the latest-and-greatest P5 and Stylesheets. But it would make our lives simpler. Cheers, Martin

4 16

2.9.0 in Vault
by Hugh Cayless 09 Nov '15

09 Nov '15

Can everyone who’s able take a look at http://www.tei-c.org/Vault/P5/2.9.0/doc/tei-p5-doc/en/html/ <http://www.tei-c.org/Vault/P5/2.9.0/doc/tei-p5-doc/en/html/> It looks ok to me… Need to step away while I go pick the kids up, but should be able to resume in an hour if I don’t hear screams from anyone.

8 24

Fwd: [tei-board] submitting expenses
by Hugh Cayless 05 Nov '15

05 Nov '15

> Begin forwarded message: > > From: John Unsworth <unsworth(a)brandeis.edu> > Date: November 4, 2015 at 21:11:19 EST > To: tei-board(a)lists.tei-c.org > Cc: TEI Council <tei-council(a)lists.village.virginia.edu> > Subject: [tei-board] submitting expenses > > Hi folks, > > Here’s an updated form for submitting expenses. Kevin, could you use this to replace what’s at: > > http://www.tei-c.org/Admin/TEI_travel_form.pdf <http://www.tei-c.org/Admin/TEI_travel_form.pdf> > > Thanks, and let me know if you have questions. > > John > > > > _______________________________________________ > tei-board mailing list > tei-board(a)lists.tei-c.org > http://lists.lists.tei-c.org/mailman/listinfo/tei-board

1 0

reimbursement for TEI Council in Lyon
by Syd Bauman 05 Nov '15

05 Nov '15

Am I correct that TEI-C will be reimbursing us for * travel to & from Lyon * meals from Sat 10-24 to lunch on Wed 10-28 (which we got from the conference folks, anyway) * hotel for Sat, Sun, Mon, Tue nights but not the rest of our expenses?

3 2

reminder
by Lou Burnard 04 Nov '15

04 Nov '15

Can someone remind me how I find out whether my local repo is up to date with the dev master? git status tells me if I am ahead of it, but not if I am behind. I can find out by doing a pull and seeing if something has changed, but of course by then it's too late.

2 2

Bretts comments
by Lou Burnard 04 Nov '15

04 Nov '15

I've just collected all the issues raised by Brett into a single document, and will work through it over the next day or two, applying all those (the majority) which seem to me uncontroversial typo corrections as a single modification. And will then close the related tickets.

1 0

Re: [tei-council] Oddity in RNG generation with new @cert datatype
by Lou Burnard 03 Nov '15

03 Nov '15

We define a new data spec which is the alternation of the two and use tha. See teidata.probcert.xml in P5pure branch Sent from my Samsung Galaxy Tab®|PRO -------- Original message -------- From: Raffaele Viglianti Date:11/03/2015 21:00 (GMT+00:00) To: tei-council(a)lists.tei-c.org Subject: Re: [tei-council] Oddity in RNG generation with new @cert datatype If we don't allow composite datatypes in pure ODD, how are we going to convert this specific class? R On Tue, Nov 3, 2015 at 3:56 PM, Lou Burnard <lou.burnard(a)retired.ox.ac.uk> wrote: > This shouldn't happen in pure odd of course because we don't allow > composite datatypes > > > > > Sent from my Samsung Galaxy Tab®|PRO > > > -------- Original message -------- > From: Martin Holmes > Date:11/03/2015 20:42 (GMT+00:00) > To: tei-council(a)lists.tei-c.org > Subject: Re: [tei-council] Oddity in RNG generation with new @cert datatype > > Hi Hugh, > > On 15-11-03 11:52 AM, Hugh Cayless wrote: > > Yeah, All works, but I think what’s happening is that in your ODD, > > the content model is being set to empty because the data.certainty > > and data.probability macros have been stripped, > > How have they been stripped? That's what I don't really understand; I'm > not doing anything to strip them (any more than teiall.odd is doing > anything to include them). > > > and that because > > they’re only getting included via the att.global.responsibility > > reference, in which, because the datatype is a choice between two > > datatypes, the references aren’t resolved, meaning the macros aren’t > > included. This does seem like a bug, doesn’t it? I’ll just go ahead > > and fix it... > > Thanks for that. > > Cheers, > Martin > > >> On Nov 3, 2015, at 14:42 , Hugh Cayless <philomousos(a)gmail.com> > >> wrote: > >> > >> My guess would be that it’s getting in another way with tei_all. > >> Will check though. > >> > >>> On Nov 3, 2015, at 14:40 , Martin Holmes <mholmes(a)uvic.ca> > >>> wrote: > >>> > >>> What I don't understand, then, is why teiall.odd in the tests > >>> generates a correct teiall.rng. If you run make test, then look > >>> at the generated Test/teiall.rng, do you see a broken content > >>> model? > >>> > >>> Cheers, Martin > >>> > >>> On 15-11-03 11:35 AM, Hugh Cayless wrote: > >>>> I’ve tracked it down, but I’m not 100% sure whether it’s > >>>> actually a bug or whether we’re doing it wrong. The odd2odd.xsl > >>>> checks to see if you have an rng:ref that’s the *child* of a > >>>> <datatype>, but here we have a datatype that’s a choice between > >>>> two datatypes (it’s the grandchild of <datatype>). The > >>>> assumption seems to have been that datatypes couldn’t be > >>>> defined by composition. Was that a conscious choice or just an > >>>> oversight? If the latter, then I’ll check in a fix to the > >>>> Stylesheets. If the former, then we need to define > >>>> att.global.responsibility differently… > >>>> > >>>> Thoughts? > >>>> > >>>>> On Nov 3, 2015, at 12:59 , Martin Holmes <mholmes(a)uvic.ca> > >>>>> wrote: > >>>>> > >>>>> I bet Lou and Syd would be able to tell us why. It's got me > >>>>> completely stumped. > >>>>> > >>>>> Cheers, Martin > >>>>> > >>>>> On 15-11-03 09:07 AM, Hugh Cayless wrote: > >>>>>> Yeah, I see the same thing... > >>>>>> > >>>>>> Sent from my phone. > >>>>>> > >>>>>>> On Nov 3, 2015, at 11:49, Martin Holmes > >>>>>>> <mholmes(a)uvic.ca> wrote: > >>>>>>> > >>>>>>> I'm very puzzled by this. Could someone else generate an > >>>>>>> RNG from this ODD: > >>>>>>> > >>>>>>> <http://web.uvic.ca/~mholmes/mariage.odd> > >>>>>>> > >>>>>>> using the dev P5 and Stylesheets, and see if they get the > >>>>>>> same empty content model for @cert? > >>>>>>> > >>>>>>> Can anyone suggest why this might be happening? It > >>>>>>> doesn't happen in the regular P5 build using teiall.xml > >>>>>>> in Test. > >>>>>>> > >>>>>>> Cheers, Martin > >>>>>>> > >>>>>>>> On 15-11-03 07:56 AM, Martin Holmes wrote: Hi Raff, > >>>>>>>> > >>>>>>>> No, this is freshly-generated from an existing ODD, > >>>>>>>> using the latest bleeding-edge Oxygen plugin, meaning > >>>>>>>> that it's the current stylesheets and the current P5 > >>>>>>>> from dev. > >>>>>>>> > >>>>>>>> To build P5, you usually have to point it at the > >>>>>>>> location of your stylesheet checkout: > >>>>>>>> > >>>>>>>> XSL=/home/rviglian/Projects/tei-code/TEI/Stylesheets > >>>>>>>> > >>>>>>>> or whatever. > >>>>>>>> > >>>>>>>> Cheers, Martin > >>>>>>>> > >>>>>>>>> On 15-11-03 07:13 AM, Raffaele Viglianti wrote: Hi > >>>>>>>>> Martin, > >>>>>>>>> > >>>>>>>>> When I first made that change, I mistakenly pointed > >>>>>>>>> the ref to att.certainty and att.probability instead > >>>>>>>>> of data.certainty and data.probability. I fixed this > >>>>>>>>> after jenkins complained, but I imagine that the rng > >>>>>>>>> still got created and it might have looked like the > >>>>>>>>> one you included in your email. > >>>>>>>>> > >>>>>>>>> Is it possible that you're looking at an older RNG > >>>>>>>>> and/or need to rebuild? > >>>>>>>>> > >>>>>>>>> Also I've been trying to build locally to replicate > >>>>>>>>> your problem, but when I `make` in P5 I get this > >>>>>>>>> error: > >>>>>>>>> /home/rviglian/Projects/tei-code/TEI/P5/antbuilder.xml:186: > >>>>>>>>> > >>>>>>>>> > stylesheet > >>>>>>>>> /home/rviglian/Projects/tei-code/TEI/P5/p5odds.isosch.xsl > >>>>>>>>> > >>>>>>>>> > doesn't exist. Have I missed a step? > >>>>>>>>> > >>>>>>>>> Raff > >>>>>>>>> > >>>>>>>>>> On Mon, Nov 2, 2015 at 6:19 PM, Martin Holmes > >>>>>>>>>> <mholmes(a)uvic.ca> wrote: > >>>>>>>>>> > >>>>>>>>>> Hi all, > >>>>>>>>>> > >>>>>>>>>> The @cert in att.global.responsibility now has a > >>>>>>>>>> janus value (att.certainty or att.probability). > >>>>>>>>>> However, when I process one of my existing ODDs > >>>>>>>>>> using the current dev tree, I get an empty value in > >>>>>>>>>> my RNG: > >>>>>>>>>> > >>>>>>>>>> <define > >>>>>>>>>> name="att.global.responsibility.attributes"> <ref > >>>>>>>>>> name="att.global.responsibility.attribute.cert"/> > >>>>>>>>>> <ref > >>>>>>>>>> name="att.global.responsibility.attribute.resp"/> > >>>>>>>>>> </define> <define > >>>>>>>>>> name="att.global.responsibility.attribute.cert"> > >>>>>>>>>> <optional> <attribute name="cert"> > >>>>>>>>>> <a:documentation xmlns:a=" > >>>>>>>>>> http://relaxng.org/ns/compatibility/annotations/1.0 > ">(certainty) > >>>>>>>>>> > >>>>>>>>>> > >>> > >>>>>>>>>> > signifies the degree of certainty associated with the intervention or > >>>>>>>>>> interpretation.</a:documentation> <empty/> > >>>>>>>>>> </attribute> </optional> </define> <define > >>>>>>>>>> name="att.global.responsibility.attribute.resp"> > >>>>>>>>>> <optional> <attribute name="resp"> > >>>>>>>>>> <a:documentation xmlns:a=" > >>>>>>>>>> http://relaxng.org/ns/compatibility/annotations/1.0 > ">(responsible > >>>>>>>>>> > >>>>>>>>>> > party) indicates the agency responsible for the > >>>>>>>>>> intervention or interpretation, for example an > >>>>>>>>>> editor or transcriber.</a:documentation> <list> > >>>>>>>>>> <oneOrMore> <ref name="data.pointer"/> </oneOrMore> > >>>>>>>>>> </list> </attribute> </optional> </define> > >>>>>>>>>> > >>>>>>>>>> Any idea why this might be happening? > >>>>>>>>>> > >>>>>>>>>> Cheers, Martin -- tei-council mailing list > >>>>>>>>>> tei-council(a)lists.tei-c.org > >>>>>>>>>> http://lists.lists.tei-c.org/mailman/listinfo/tei-council > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>> > >>>>>>>>>> > PLEASE NOTE: postings to this list are publicly archived > >>>>>>> -- tei-council mailing list tei-council(a)lists.tei-c.org > >>>>>>> http://lists.lists.tei-c.org/mailman/listinfo/tei-council > >>>>>>> > >>>>>>> > >>>>>>> > PLEASE NOTE: postings to this list are publicly archived > >>>>> -- tei-council mailing list tei-council(a)lists.tei-c.org > >>>>> http://lists.lists.tei-c.org/mailman/listinfo/tei-council > >>>>> > >>>>> PLEASE NOTE: postings to this list are publicly archived > >>>> > >>> -- tei-council mailing list tei-council(a)lists.tei-c.org > >>> http://lists.lists.tei-c.org/mailman/listinfo/tei-council > >>> > >>> PLEASE NOTE: postings to this list are publicly archived > >> > > > -- > tei-council mailing list > tei-council(a)lists.tei-c.org > http://lists.lists.tei-c.org/mailman/listinfo/tei-council > > PLEASE NOTE: postings to this list are publicly archived > -- > tei-council mailing list > tei-council(a)lists.tei-c.org > http://lists.lists.tei-c.org/mailman/listinfo/tei-council > > PLEASE NOTE: postings to this list are publicly archived > -- tei-council mailing list tei-council(a)lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council PLEASE NOTE: postings to this list are publicly archived

1 0

Oddity in RNG generation with new @cert datatype
by Martin Holmes 03 Nov '15

03 Nov '15

Hi all, The @cert in att.global.responsibility now has a janus value (att.certainty or att.probability). However, when I process one of my existing ODDs using the current dev tree, I get an empty value in my RNG: <define name="att.global.responsibility.attributes"> <ref name="att.global.responsibility.attribute.cert"/> <ref name="att.global.responsibility.attribute.resp"/> </define> <define name="att.global.responsibility.attribute.cert"> <optional> <attribute name="cert"> <a:documentation xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0">(certainty) signifies the degree of certainty associated with the intervention or interpretation.</a:documentation> <empty/> </attribute> </optional> </define> <define name="att.global.responsibility.attribute.resp"> <optional> <attribute name="resp"> <a:documentation xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0">(responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.</a:documentation> <list> <oneOrMore> <ref name="data.pointer"/> </oneOrMore> </list> </attribute> </optional> </define> Any idea why this might be happening? Cheers, Martin

4 16