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

Re: [tei-council] release plan
by James Cummings 17 Jan '18

17 Jan '18

re: ISO standards, I don't think TEI-C has any special access to them, no. Some have had access in the past through various institutions (I don't currently). 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 Elisa Beshero-Bondar <ebbondar(a)gmail.com> Sent: 15 January 2018 16:33:24 To: tei-council(a)lists.tei-c.org Subject: Re: [tei-council] release plan Hi Peter and all, I took about 30 minutes again reviewing the proposal from issue 1671 (the ticket with all the discussion is 1670:https://github.com/TEIC/TEI/issues/1670 <https://github.com/TEIC/TEI/issues/1670> ). I think the @join attribute is fine as proposed because it’s already an ISO standard, and exemplified in 1670 as well as in Maik Stührenberg’s 2012 article in JTEI: “The TEI and Current Standards for Structuring Linguistic Data”: http://journals.openedition.org/jtei/523 <http://journals.openedition.org/jtei/523> (search for “join” to zoom to the example). If we don’t have issues with this example, presumably we’re okay with Piotr’s pull request here? In our minutes from the Victoria F2f, we asked "We think @join is fine but wonder if a different name could be used, or is that exactly what this is called in ISO 24611?” I looked it up, and the ISO standard referenced here is from 2012: ISO 24611:2012 (en) and the section with the join attribute is B3.2. (https://www.iso.org/obp/ui/#iso:std:iso:24611:ed-1:v1:en <https://www.iso.org/obp/ui/#iso:std:iso:24611:ed-1:v1:en> ) A sidenote and a rookie question: Because ISO standards are often relevant to our work, it seems like we ought to be able to access them fully—but this one doesn’t come free. Does TEI have some special mode of access to ISO standards, such as an ANSI membership? Cheers, 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 15, 2018, at 10:41 AM, Peter Stadler <stadler(a)edirom.de> wrote: > > Dear all, > > the build seems to be broken right now (or am I wrong)? > Can we fix this before refrigerating? > > Additionally, I’d like to please Piotr and accept his PR https://github.com/TEIC/TEI/pull/1671 concerning issue https://github.com/TEIC/TEI/issues/1670. > IMHO, the only question for us is whether anyone feels strong to come up with a more general application (and name) for the proposed attribute @join? Otherwise, I’ll merge … > > Best > Peter > > >> Am 15.01.2018 um 15:25 schrieb Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)UNI-GRAZ.AT>: >> >> Refrigerate: Thu 18 - Wed 24 January. In this period no major changes which could possibly break the schema should be done any more. Minor changes (prose, typos) are fine until the 24th. > > -- > 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

2 1

Re: [tei-council] POSTPONED - RomaJS meeting
by James Cummings 17 Jan '18

17 Jan '18

Dear Raff, Oh no! Get well soon! Lots of fluids and bed rest! 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 Raffaele Viglianti <raffaeleviglianti(a)gmail.com> Sent: 17 January 2018 11:52:02 To: tei-council(a)lists.tei-c.org Subject: [tei-council] POSTPONED - RomaJS meeting All, I came down with a nasty stomach bug and I'm running a high fever. I'm afraid we're going to have to postpone the meeting. Apologies! Raff -- 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

2 1

POSTPONED - RomaJS meeting
by Raffaele Viglianti 17 Jan '18

17 Jan '18

All, I came down with a nasty stomach bug and I'm running a high fever. I'm afraid we're going to have to postpone the meeting. Apologies! Raff

4 3

Re: [tei-council] POSTPONED - RomaJS meeting
by Alejandro Bia 17 Jan '18

17 Jan '18

Hope you get better. Take care! Best, Alex.- At 12:52 17/01/2018, you wrote: >All, > >I came down with a nasty stomach bug and I'm running a high fever. I'm >afraid we're going to have to postpone the meeting. Apologies! > >Raff >-- >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 --------------------------------------------------------- ALEJANDRO BIA e-mail: abia(a)umh.es CIO - DEMI Centro de Investigación Operativa Departamento de Estadística, Matemáticas e Informática Área de Lenguajes y Sistemas Informáticos Universidad Miguel Hernández Ed. Torretamarit, Av. Universidad s/n, CP:03202, Elche, ESPAÑA Web: http://dhw.umh.es/alex-bia/ Tel: +34 966658973 Móvil: +34 644447008 Skype: alex-bia Twitter: @alex_bia --------------------------------------------------------- --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

1 0

standOff conf call
by Peter Stadler 17 Jan '18

17 Jan '18

Dear all, during yesterdays Council conf call I forwarded Laurent’s proposal to discuss the current status/issues of the pending standOff proposal with us. That’s probably much better than me being an intermediary, so here’s the poll: https://doodle.com/poll/uhdfph5pc95fatky I already pointed Council at https://github.com/laurentromary/stdfSpec/tree/AnnArbor/Scenarios for a first draft of Stand-off use cases as envisioned by Laurent. All the best Peter

2 4

any comments on issue 1729?
by Mylonas, Elli 16 Jan '18

16 Jan '18

I'll fix by Th. am if no complaints. This is one of the things that came up as Syd and I are working through the unclassed attributes. https://github.com/TEIC/TEI/issues/1729 --elli

1 0

Agenda for RomaJS meeting tomorrow at 15:00 UTC
by Raffaele Viglianti 16 Jan '18

16 Jan '18

Dear all, Here's the agenda for tomorrow's meeting: https://docs.google.com/document/d/1SiWIZyNa3uHjzBLN1YQw5_CrlZbFUAz-53gN0I2… If you wanted to have a look at the new stuff, here's what you can do (these instructions are on the agenda doc also): Latest iteration: http://mith.us/romajs - Click on “(TEST: SKIP OXGARAGE)”, it will load TEI Bare - Add ‘ab’ and click on it OR - Search for ‘div’ and click on it See you tomorrow! I'll send a hangout link 15 or 10 minutes before the meeting. All best, Raff

1 0

Is there a meeting now?
by Alejandro Bia 16 Jan '18

16 Jan '18

Hi all, Is there a Stylesheets-group meeting now? How can I connect? Best, Alex.- --------------------------------------------------------- ALEJANDRO BIA e-mail: abia(a)umh.es CIO - DEMI Centro de Investigación Operativa Departamento de Estadística, Matemáticas e Informática Área de Lenguajes y Sistemas Informáticos Universidad Miguel Hernández Ed. Torretamarit, Av. Universidad s/n, CP:03202, Elche, ESPAÑA Web: http://dhw.umh.es/alex-bia/ Tel: +34 966658973 Móvil: +34 644447008 Skype: alex-bia Twitter: @alex_bia --------------------------------------------------------- --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 2

Stylesheets group meeting, Tue 16 Jan 18
by Syd Bauman 16 Jan '18

16 Jan '18

For this coming meeting, we are hoping to talk about ticket 296, possibly shifting focus from how to fix this tiny problem (no space between attr value and gloss thereof) to how to properly format a suggested values include list. If we actually finish with that in under an hour, we can talk about ticket 303, which turns out to be not nearly as simple as I thought when I originally posted the ticket.

3 2

Re: [tei-council] CHANGED: RomaJS meeting Wednesday at 15:00 UTC
by James Cummings 15 Jan '18

15 Jan '18

The teiconsortium(a)gmail.com user could share its calendar with the google accounts of all Board and Council giving us all write access to it. (Individuals could choose to receive notifications from it or not.) So I'm confused about when the RomaJS meeting is now happening? 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 Elisa Beshero-Bondar <ebbondar(a)gmail.com> Sent: 15 January 2018 15:40:14 To: tei-council(a)lists.tei-c.org Subject: Re: [tei-council] CHANGED: RomaJS meeting Wednesday at 15:00 UTC Apologies that I won’t be able to make the Wednesday meeting, but I definitely like the idea of a shared calendar—a Google Calendar would make scheduling for us much easier, since you can input times in your own time zone and translate them into UTC and other time zones. 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 15, 2018, at 10:31 AM, Raffaele Viglianti <raffaeleviglianti(a)gmail.com> wrote: > > Ugh sorry, obviously I confused time zones. We're meeting tomorrow for the > stylesheets at 2pm UTC, but I read it as 2pm EST. We really need a shared > calendar, maybe this is something to talk about at the F2F. > > Elisa, I don't like very much the idea of following the stylesheets meeting > with another meeting. Personally, that would take too much time from my > work day's schedule. Likewise, I'd rather not have both meetings on the > same day, regardless of time conflict. > > So let's keep the changed time as indicated in this email's subject: > Wednesday January 17th at 15:00 UTC / 10:00 EST. > > Raff > > On Mon, Jan 15, 2018 at 10:21 AM, Elisa Beshero-Bondar <ebbondar(a)gmail.com <mailto:ebbondar@gmail.com>> > wrote: > >> I was about to write the same thing—Raff, I wonder if more of us might be >> able to attend if you held your meeting tomorrow immediately to follow the >> Stylesheets meeting? >> >> 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> <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu>> >> Development site: http://newtfire.org <http://newtfire.org/> <http://newtfire.org/ <http://newtfire.org/>> >> >> >> >> >> >> >>> On Jan 15, 2018, at 10:20 AM, Syd Bauman <s.bauman(a)northeastern.edu> >> wrote: >>> >>> This must be some new definition of "conflict" of which I was >>> formerly unaware. The Stylesheets meeting is at 09:00 EDT, so neither >>> your original 15:00 suggestion nor the 10:00 is theorhetically in >>> conflict. >>> >>>> Never mind, just realized this conflicts with the Stylesheets meeting. >>>> Sorry! >>>> >>>> The second best meeting from the poll is this Wednesday Jan 17 at 10:00 >> EDT >>>> / 15:00 UTC, so let's go with that. >>>> >>>> Sorry again for the confusion! >>> -- >>> 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 <mailto:tei-council@lists.tei-c.org> >> http://lists.lists.tei-c.org/mailman/listinfo/tei-council <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 <mailto:tei-council@lists.tei-c.org> > http://lists.lists.tei-c.org/mailman/listinfo/tei-council <http://lists.lists.tei-c.org/mailman/listinfo/tei-council> > > PLEASE NOTE: postings to this list are publicly archived

2 1

release plan
by Scholger, Martina (martina.scholger＠uni-graz.at) 15 Jan '18

15 Jan '18

Dear all, this is a summary of our release plan: Refrigerate: Thu 18 - Wed 24 January. In this period no major changes which could possibly break the schema should be done any more. Minor changes (prose, typos) are fine until the 24th. Release branch: Thu 25 January. Freeze: Thu 25 - Tue 30 January. No more changes should be done. If it is really inevitable, changes for the release can only be done in the release branch (is that right?). Release: Wed 31 January. Please have a look at issues you are assigned to. Especially at those which are labelled with "Guidelines 3.3.0" (https://github.com/TEIC/TEI/milestone/4) If you are not able to manage them for the upcoming release, please remove the milestone. Our next teleconference will be on Thu 25 January (13UTC). Best wishes, Martina Martina Scholger Centre for Information Modelling Austrian Centre for Digital Humanities University of Graz Elisabethstraße 59/III 8010 Graz

3 2

CHANGED: RomaJS meeting Wednesday at 15:00 UTC
by Raffaele Viglianti 15 Jan '18

15 Jan '18

Never mind, just realized this conflicts with the Stylesheets meeting. Sorry! The second best meeting from the poll is this Wednesday Jan 17 at 10:00 EDT / 15:00 UTC, so let's go with that. Sorry again for the confusion! Raff On Mon, Jan 15, 2018 at 10:13 AM, Raffaele Viglianti < raffaeleviglianti(a)gmail.com> wrote: > Dear all, > > Thanks for filling in the Doodle poll! We'll be meeting tomorrow Tuesday > January 16 at 15:00 EDT / 20:00 UTC. I'll start the hangout and send a link > 15 minutes before the meeting. > > All best, > Raff >

3 5

RomaJS meeting tomorrow (Tuesday) at 20:00 UTC
by Raffaele Viglianti 15 Jan '18

15 Jan '18

Dear all, Thanks for filling in the Doodle poll! We'll be meeting tomorrow Tuesday January 16 at 15:00 EDT / 20:00 UTC. I'll start the hangout and send a link 15 minutes before the meeting. All best, Raff

1 0

F2F agenda Cologne
by Scholger, Martina (martina.scholger＠uni-graz.at) 14 Jan '18

14 Jan '18

Dear all, I set up a very basic agenda for the F2F meeting in Cologne (February 24-26 2018). https://docs.google.com/document/d/1CgyTW1lRTy-_32TbVJVJpmg9399bgWnjteiExC2… Please add topics you want to discuss. I provided some travel and accommodation information from the conference website. I will delete them from the minutes at the beginning of our F2F meeting. Both of our meeting rooms are at the University of Cologne. @Peter, if you have further recommendations for travel & accommodation, please add them. Best wishes, Martina Martina Scholger Centre for Information Modelling Austrian Centre for Digital Humanities University of Graz Elisabethstraße 59/III 8010 Graz

1 0

Stylesheets group, general
by Syd Bauman 13 Jan '18

13 Jan '18

So for the moment our plan is to meet the Tue immediately following a TEI Council meeting at 09:00 ET. (That will be slightly different UTC and other times, depending on DST.) Thus: Tue 2018-01-16 14:00Z Tue 2018-01-30 14:00Z Tue 2018-02-27 14:00Z (we may decide to cancel, as just after F2F) Tue 2018-04-03 13:00Z Tue 2018-05-01 13:00Z Tue 2018-06-05 13:00Z Tue 2018-07-03 13:00Z Tue 2018-07-31 13:00Z Tue 2018-09-04 13:00Z Tue 2018-10-02 13:00Z Tue 2018-10-30 13:00Z Tue 2018-12-04 14:00Z Tue 2019-01-01 14:00Z (we may decide to cancel, as it's a holiday) Our meetings are technically scheduled to be 1 hour long, but I am personally trying to block out an hour and half for each, as they seem to go over pretty frequently. So far we've been using Google Hangouts, and that has worked OK. We haven't run into any limitation problems, I don't think. So unless someone objects, I think we'll just continue to do that, eh?

1 0

git policy
by Syd Bauman 13 Jan '18

13 Jan '18

Dear Hugh and other gitExperts -- Once we've decided it's OK to merge in a pull request, do we merge, squash, or rebase? (Martin & I were looking at https://github.com/TEIC/Stylesheets/pull/292, but were not sure how to merge it in.)

1 0

WG: Reimbursement Victoria
by Scholger, Martina (martina.scholger＠uni-graz.at) 12 Jan '18

12 Jan '18

Hi all, this is the answer from John about the travel reimbursement for Victoria. Please let me know as soon as you receive your payment. Best, Martina Von: John Unsworth [mailto:john.m.unsworth@gmail.com] Gesendet: Freitag, 12. Jänner 2018 05:08 An: Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at> Cc: Tim Naughton <tnaughton(a)virtualmgmt.com> Betreff: Re: Reimbursement Victoria Hi Martina, TEI has recently hired a management services company, Virtual Inc., that works with open source, non-profit, and association-based organizations like ours. The arrangement should give us much better continuity and reliability in our business operations, over time. The Victoria reimbursements are the first payments that Virtual are doing, and doing anything for the first time takes a little longer, but I believe anyone who has submitted requests for reimbursements up to now will have received payment in the next week, or two at the latest. I’ve cc’d Tim Naughton, who is our representative from Virtual: if there are specific questions about cases or process, he can answer those. John 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>> Date: Thursday, January 11, 2018 at 4:01 PM To: John Unsworth <john.m.unsworth(a)gmail.com<mailto:john.m.unsworth@gmail.com>> Subject: Reimbursement Victoria Dear John, today, we had our first Technical Council meeting of the year and as the new Chair it's now my job to ask questions :-) We were talking about reimbursement for the F2F meeting in Victoria. I just wanted to ask when the Council members (excluded me, since I only sent you my receipt this week) can expect the reimbursement, since for some of us it was a bigger expense and we are already planning our next meeting for the end of February in Cologne. Thank you for the information and your effort! Best wishes, Martina Martina Scholger Centre for Information Modelling Austrian Centre for Digital Humanities University of Graz Elisabethstraße 59/III 8010 Graz

1 0

RomaJS meeting
by Raffaele Viglianti 11 Jan '18

11 Jan '18

Hello, Here's a doodle poll for a RomaJS meeting: https://doodle.com/poll/bbebdwf6zpinshew I quickly wanted to add that in case upgrading OxGarage or writing something new won't work out, it *is* possible to rewrite the odd2json XSLT in XSLT2, it's just not very convenient and more error prone. Validation would remain an issue, however. Raff

1 0

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