November 2015 - Tei-council

Telecon and updates
by Hugh Cayless 30 Nov '15

30 Nov '15

Dear All, I’ve made some progress on the Pure ODD XSLT. Please browse around http://teic.github.io/TEI/index.html <http://teic.github.io/TEI/index.html> and be on the lookout for display bugs or things you’d like done differently. Although we had enough for a quorum in the poll for meeting times, we’d either be excluding new members, which I’d rather not do, or current members who really need to be there, so I’ve added some more dates at http://doodle.com/poll/wyuc3qiv9rkx4db6. Please update your availability when you get the chance. Whether we have a year-end release or not, I think we’re getting close to the time when we should go ahead and merge the Pure ODD branch. Thoughts? All the best, Hugh

6 7

Bugfix for Roma available for testing
by Martin Holmes 29 Nov '15

29 Nov '15

Hi all, A new Roma is here: <http://www.tei-c.org/Roma-4.18/> with my minor bugfix for the title element included, along with other things (I know not exactly what) that had been added since the last release found its way onto tei-c in 2013. If you have any experience with Roma at all, please give it a bit of a go to make sure nothing is broken. Cheers, Martin

3 4

Adding processing model to github
by James Cummings 26 Nov '15

26 Nov '15

Hiya, To the 'processing-model' branch, based on the 'lb42-pureodd' branch, I've added the specs of elements needed for the processing model, modified that for elementSpec, and added the draft prose to the TD chapter. Hurrah. (Feel free to edit and improve the prose.) I don't promise I've not broken anything and haven't yet added the cross-references to the guidelines text in the TD chapter. (But that is straightforward and I'll do so soon.) What I *haven't* added so far are the tests that Sebastian had written for the processing model because a) believe it or not I've never actually added tests to the TEI build system and so now ask for help in doing so and b) I'm not sure the tests Sebastian was doing are specifically the tests we want. In this case what we want are tests that test that our schemas are allowing/disallowing the various model* and related elements in the right place and used only in ways that they are allowed. Sebastian's tests actually test the parsing of these processing models and the output they generate. Is that what we want? Remember, what we're doing here is adding the ability for documenting processing models, not adding TEI Simple, or any particular implementation of doing things with that processing model documentation. For example, in the TEI-Simple repository there are two types of test in the build.xml ant file: The 'tests' target: https://github.com/TEIC/TEI-Simple/blob/master/build.xml#L197 validates the TEI Simple ODD against the processing-model schema, and validates various instances of TEI Simple against the TEI Simple schema. That doesn't actually test the processing model elements are used properly. The 'pm' target: https://github.com/TEIC/TEI-Simple/blob/master/build.xml#L259 first creates some TEI simple XSL from the processing model documentation in the TEI Simple ODD, then creates a variant of this from teipm-ms.odd (which was a test variant requested by Council demonstrating using it for Manuscripts), and then runs various test files through both those XSL in order to produce HTML. Again, this seems to be testing the processing of the documentation of processing models, rather than the elements. (e.g. we don't seem to test 'list' or 'person' in this way?). Could someone with more experience with the TEI test system either help me design some new tests or help me migrate some of these into the processing-model branch? Many thanks, -James -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford

1 0

Pure ODD display update
by Hugh Cayless 24 Nov '15

24 Nov '15

Dear all, I’ve been spending my time on getting the Pure ODD display working in the GLs generation. I’m getting closer, I think, though there are still some issues. Can you take a look at http://teic.github.io/TEI/index.html <http://teic.github.io/TEI/index.html> (e.g. http://teic.github.io/TEI/ref-certainty.html <http://teic.github.io/TEI/ref-certainty.html>) and see if the Pure ODD display is what you were hoping for, and what bugs you can find. Issues I’m aware of are: RelaxNG display is displaying the result of evaluating data types rather than a link to the data type definition and "Used by" isn’t getting populated for macros and dataypes. What I’d really like to know is whether I’m on the right track or a different display is needed. This (unsurprisingly) turns out to be way more complicated than I’d hoped, and I haven’t even begun to work out how to alter the display for GLs output beyond HTML. This could take a while.

2 2

GitHub P6 label, anyone?
by Peter Stadler 24 Nov '15

24 Nov '15

I was just going through some tickets and came across #1400 „Remove numbered divisions“, wondering whether we need (or want) a P6 label? That way, we could start collecting issues for the day X. That would not necessarily mean that those changes be implemented in P6, but discussion is postponed until then. So, rather than simply closing the issue, we could label it first (and close it then, so it’s not polluting our issue tracker), making it easy to reopen these issues when the time comes. Cheers Peter

5 5

brett's issues
by Lou Burnard 22 Nov '15

22 Nov '15

Apologies for the delay, but (as originally promised last week) I have now finished working through all of Brett's 24 issues with chapter PH. All but 7 of them involve minor and non-controversial corrections which I have duly made, and closed the tickets. The seven remaining however might benefit from a second look by someone with domain expertise. James? Hugh? They are really very minor points but this is a precariously organized chapter which shouldnt be deconstructed too much.

2 2

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

Peter's head in a lamp and other images
by Syd Bauman 03 Nov '15

03 Nov '15

http://bauman.zapto.org/~syd/temp/TEI_Council_Lyon.tar At that URL you will find a tarball of the few photographs I took at our meeting in Lyon. I have done *no* editing on these at all (not even weeding out the bad ones), except that all these images are 1/16 of the original size (i.e., 1232 x 816 instead of the original 4928 x 3264), and a few have been rotated. All the pictures are copyright 2015 by me, and available under the CC-BY-SA license.[1] I.e., do whatever you want so long as you give me credit and don't lie about the picture. Notes ----- [1] That's the Creative Commons Attribution-ShareAlike 4.0 International license; see http://creativecommons.org/licenses/by-sa/4.0/. Metadata is embedded, so there is no burden on you if you publish them digitally (as long as you don't strip out the metadata :-)

2 4

Two more pages updated
by Martin Holmes 02 Nov '15

02 Nov '15

I've updated these two pages: <http://www.tei-c.org/Guidelines/P5/> <http://www.tei-c.org/Guidelines/P5/get.xml> If anyone has five minutes to give them a read, let me know if you see anything that needs fixing. Kevin, I hope I haven't trodden on your feet there; I figured that while I was doing other stuff involving SF to GitHub, I might as well do these. Both pages, but especially the second, have some very ancient and perhaps now obsolete sections that really need looking at, especially as we're making decisions about what to do with the deb packages. Cheers, Martin

4 8

Mentors
by Hugh Cayless 02 Nov '15

02 Nov '15

Dear All, It was great seeing you all last week. It felt like we got a lot done, and I really appreciate your hard work. I’m writing to ask who among us is willing to serve as a mentor to our new members. We’ll have three people who’ve never been on Council before, and one (Elli) who missed the repo move and may want some guidance on Git/GitHub stuff, so that’s three, maybe four people. I’d be happy to help Elli out if she needs it, since we talk fairly frequently anyway. Hugh

6 5

TEI GitHub RSS feed
by Raffaele Viglianti 02 Nov '15

02 Nov '15

Martin mentioned getting RSS feeds from the repo earlier; Tom Elliot subscribed the other day to the *releases* atom: https://github.com/TEIC/TEI/releases.atom which could still be useful to show on the teic website. Sadly, GitHub doesn't seem to have a RSS feed for issues, but we *could* build one via their API. Raff

3 2