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

Stylesheets meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 11 Jan '18

11 Jan '18

Hi! I've moved my course to another day. So, Tuesday is fine for me too. Best, Martina Mag. Martina Scholger Zentrum für Informationsmodellierung Austrian Centre for Digital Humanities Universität Graz A-8010 Graz | Elisabethstraße 59/III Tel: +43 316 380 2291 eMail: martina.scholger(a)uni-graz.at<mailto:martina.semlak@uni-graz.at> Web: http://informationsmodellierung.uni-graz.at<http://informationsmodellierung.uni-graz.at/> | http://gams.uni-graz.at<http://gams.uni-graz.at/>

1 0

Agenda for Thursday
by Hugh Cayless 10 Jan '18

10 Jan '18

As (almost) my last act as Chair, here's the agenda for tomorrow's meeting: https://docs.google.com/document/d/154wLaN-5a-HB94DuwUI6ts7aUcKDfPvIK3OVAkm… Elli, can we use the Hangout you previously set up? Thanks, Hugh

1 0

rub-a-new-namespace
by Syd Bauman 06 Jan '18

06 Jan '18

Three things I'd like to change in the Stylesheets: 1) Use xpath-default-namespace="http://www.tei-c.org/ns/1.0", and stop using "tei:" all over.[1] 2) Change the prefix for our examples namespace[2] from "teix:" to "xmp:" or something similar. 3) Change the namespace used for functions and temporary elements to something other than "http://www.tei-c.org/ns/1.0". I'm thinking of xmlns:tp="http://www.tei-c.org/ns/programming" or some such. (1) and (2) are just conveniences, but the very kind of thing that a rub-a-dub-dub should clean up. (3), on the other hand, is needed because using the same namespace for functions in our XSLT as we do for elements in conformant documents is just plain wrong. The name "tei:duck" means something very different when it is the name of tei:duck(), an XSLT function, vs <tei:duck>, an element for manuscript description. Since they are different things, they should have different names. Not that we have any collisions at the moment, but namespaces were designed specifically to help avoid such collisions. So I think this is an important change, but want input as to what the namespace (and its prefix) should be. Notes ----- [1] Actually, I've already done this in odd2odds.xsl. [2] http://www.tei-c.org/ns/Examples

5 6

Re: [tei-council] meetings in Jan
by James Cummings 05 Jan '18

05 Jan '18

I should be able to do Thursday 11th at 2pm GMT. (I know ppl hate them but shouldn't we use things like doodle polls for this kind of thing rather than bouncing emails back and forth?) Best wishes, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: tei-council-bounces(a)lists.tei-c.org <tei-council-bounces(a)lists.tei-c.org> on behalf of Hugh Cayless <philomousos(a)gmail.com> Sent: 04 January 2018 13:08:24 To: TEI Council Subject: Re: [tei-council] meetings in Jan Can we plan on Thursday, January 11 at 09:00 EST / 14:00 GMT / 15:00 CET then? Agenda will be handing over the Chair responsibilities to Martina, and nailing down the release plan. Hugh On Thu, Jan 4, 2018 at 5:20 AM, Peter Stadler <stadler(a)edirom.de> wrote: > Tuesdays don’t work for me, Thursdays are great :) > > Best > Peter > > > Am 02.01.2018 um 22:14 schrieb Elisa Beshero-Bondar <ebbondar(a)GMAIL.COM > >: > > > > I’ve been reserving Thurs. mornings in my EST timezone from teaching at > my campus on TEI Council business generally. Tues. AMs, too. —Elisa > > -- > > Elisa Beshero-Bondar, PhD > > Director, Center for the Digital Text | Associate Professor of English > > University of Pittsburgh at Greensburg | Humanities Division > > 150 Finoli Drive > > Greensburg, PA 15601 USA > > E-mail: ebb8(a)pitt.edu <mailto:ebb8@pitt.edu> > > Development site: http://newtfire.org <http://newtfire.org/> > > > > > > > > > > > > > >> On Jan 2, 2018, at 4:04 PM, Raffaele Viglianti < > raffaeleviglianti(a)gmail.com> wrote: > >> > >> Happy new year! > >> > >> Thursdays work for me. FYI, if we're meeting thisThursday at 9:00 EST, > I'll > >> need to leave sharply at 10. > >> > >> Raff > >> > >> On Tue, Jan 2, 2018 at 3:45 PM, Sarah S <scstanley7(a)gmail.com> wrote: > >> > >>> Happy New Year all, > >>> > >>> Apologies for not being on top of this thread! I am free every Thursday > >>> morning this month, and I could try to make myself available on Tuesday > >>> mornings. > >>> > >>> Best, > >>> Sarah > >>> > >>> Sarah Stanley > >>> Office of Digital Research and Scholarship > >>> Strozier Library, Florida State University > >>> https://www.lib.fsu.edu/drs/ > >>> Twitter: https://twitter.com/sarcathtic > >>> > >>> > >>> On Tue, Jan 2, 2018 at 8:18 AM, Syd Bauman <s.bauman(a)northeastern.edu> > >>> wrote: > >>> > >>>> Re: next Stylesheets meeting > >>>> > >>>> Since Council has not decided yet when Council will be meeting in > >>>> Jan, we don't really know when would be (in)convenient for us to > >>>> meet. Since I didn't previously announce that we *would* be meeting > >>>> today, and because I couldn't make it if we did (Doctor appt), I am > >>>> simply declaring we are not meeting today. > >>>> -- > >>>> 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

3 2

please verify stylesheet error
by Syd Bauman 04 Jan '18

04 Jan '18

I discovered yesterday that I had not been thoroughly testing the stylesheets in between each change I made to the "sydb-rub" branch. (Embarrassing mis-communication between me & Martin; my fault, don't ask. :-) So last night I decided to a) write an ant build that would flex them more thoroughly[1] b) run it using the "dev" branch and the "sydb-rub" branch c) IF the output is the same, great, I haven't screwed anything up d) IF the output is different THEN e) run the test on each commit I made to "sydb-rub" to find the error f) FOR EACH error fix it (in the current "sydb-rub") I've done (a), but when I tried (b), I found to my shock that if I 1) switch to "dev" branch 2) run $ saxon odds/odd2odd.xsl Test/base.odd localsource=/path/to/p5subset.xml lang=en 3) I get the error | odds/odd2odd.xsl:487:34: Fatal Error! An empty sequence is not | allowed as the second argument of | fn:resolve-uri() 4) switch to "release" branch 5) run same cmd 6) I get the error | odds/odd2odd.xsl:424: Fatal Error! An empty sequence is not | allowed as the second argument of | resolve-uri() Despite the line number difference (and the weird fact that Saxon can figure out the column number in one case, but not in the other), it is the same error at the same spot in the code: the point in the resolution of <specGrpRef> where we are testing to see if the @target (which is not a local bare name identifier type pointer) is available. The problem (I think) is that the call to base-uri() should be with the argument '/', not the argument "/tei:TEI", as the input document might not actually start with a <TEI> element, it might legally start with a <teiCorpus> element or, as in this case, illegally start with a <schemaSpec>. But what I don't understand is how come our build process hasn't caught this in the past? Can someone try this on their own and double-check that you get the same error? And if so, either someone should dive into our build process and figure out how this was slipping past, or we should cross our fingers until Martin has finished the Test2/ work, and perhaps help him expedite that. Note ---- [1] Since I don't know how to do much in ant, for now the ant build file I wrote just runs odds/odd2odd.xsl on each of the ODD files in Test/.

1 0

meetings in Jan
by Syd Bauman 04 Jan '18

04 Jan '18

Hugh (and Martina) -- Can we straighten out the meetings in Jan soon (i.e., today)? If the Stylesheets group is going to meet at its new "usual" time, and if we decide that is 2 days before the Council meeting (as opposed to 5 days after the Council meeting), and we decide the Council will meet Thu 01-04, then the Stylesheets group would be meeting in < 48 hours.

7 9

Stylesheets bug, or Syd missing something?
by Syd Bauman 02 Jan '18

02 Jan '18

In odds/odd2odd.xsl (in the dev branch) we find several keys into the <*Spec> elements (e.g., "odd2odd-CHANGE") which use as their key (i.e., their @use) the value of tei:uniqueName(). That function (defined on line 279 of the same file) returns the @ident of the node passed to it, with the namespace in which the thing being specified is declared iff said namespace is not the TEI namespace. BUT, a few of the calls to those keys use @ident, not tei:uniqueName(). In particular, those in the mode "pass0" template for *Spec elements in mode "change" (which starts on line 510) and those in the mode "pass1" template for *Spec elements in mode "delete" (which starts on line 587). I don't see how these would ever work if the base ODD being customized is not a TEI ODD. In which case, isn't this a bug? I wonder, does this work for MEI at all?

2 1