November 2015 - Tei-council

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