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

No meeting Thursday
by Hugh Cayless 08 Dec '17

08 Dec '17

Hi All, Given that we just had our face-to-face, I don't think there's any need for a telecon this month, unless anyone objects strongly? I've had no expressions of interest in taking over the Chair position, so also a gentle reminder about that... Hugh

5 4

stylesheets attack group meeting
by Syd Bauman 07 Dec '17

07 Dec '17

I'm planning on keeping the Stylesheets group in the mode of using work on stylesheets as a self-educational methodology (as opposed to the mission of actually working on stylesheets) for our Dec meeting this coming Thu 12-07. As mentioned at the Council F2F, we would like to re-schedule to Tuesdays at the same time (09:00 ET which is either 13:00Z or 14:00Z) starting with our Jan (or maybe Feb) meeting, and we'll switch our focus then. (Not that it will really mean much. :-) In any case, we are scheduled to meet this Thu 12-07 at 14:00Z (note: time is different than last meeting), i.e.: * 06:00 PST * 09:00 EST * 14:00 GMT <== different than last meeting * 15:00 CET <== different than last meeting I thought it would be useful to try to attack ticket 293 "error showing author etc". Peter will lead us through his suggested fix of 11-10 (which I'm reasonably sure will, in fact, work). Discussion to include the difference between signatures of xs:string, xs:string*, text(), text()*, node(), and node()*. And for extra credit I'll ask what's wrong with the XPath in common/functions.xsl on line 739. :-) Hope all the Americans had a great Thanksgiving, and that everyone else had a great non-holiday Thu 23 Nov. :-)

2 2

Re: [tei-council] stylesheets attack group meeting
by James Cummings 07 Dec '17

07 Dec '17

Just to say I'll either have to miss or be late to this meeting since I've got a meeting at 14:00. If you are still going when I get back to my office, I'll join in. Peter's suggested fix looks like it might work to me but I've always been slightly wary about xsl:sequence in any case. As to what is wrong with https://github.com/TEIC/Stylesheets/blob/dev/common/functions.xsl#L739, oh, oh, I know! Is it that it is testing something which isn't (and has never been) valid TEI P5? 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 Syd Bauman <s.bauman(a)northeastern.edu> Sent: 02 December 2017 21:49:53 To: TEI Council; Lou Burnard; Martin Holmes Subject: [tei-council] stylesheets attack group meeting I'm planning on keeping the Stylesheets group in the mode of using work on stylesheets as a self-educational methodology (as opposed to the mission of actually working on stylesheets) for our Dec meeting this coming Thu 12-07. As mentioned at the Council F2F, we would like to re-schedule to Tuesdays at the same time (09:00 ET which is either 13:00Z or 14:00Z) starting with our Jan (or maybe Feb) meeting, and we'll switch our focus then. (Not that it will really mean much. :-) In any case, we are scheduled to meet this Thu 12-07 at 14:00Z (note: time is different than last meeting), i.e.: * 06:00 PST * 09:00 EST * 14:00 GMT <== different than last meeting * 15:00 CET <== different than last meeting I thought it would be useful to try to attack ticket 293 "error showing author etc". Peter will lead us through his suggested fix of 11-10 (which I'm reasonably sure will, in fact, work). Discussion to include the difference between signatures of xs:string, xs:string*, text(), text()*, node(), and node()*. And for extra credit I'll ask what's wrong with the XPath in common/functions.xsl on line 739. :-) Hope all the Americans had a great Thanksgiving, and that everyone else had a great non-holiday Thu 23 Nov. :-) -- 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

4 3

Reimbursement and Per Diem rates for Victoria
by Hugh Cayless 05 Dec '17

05 Dec '17

The Meals and Incidentals rate for Victoria is $123 (from https://aoprals.state.gov/web920/per_diem_action.asp?MenuHide=1&CountryCode…), of which we can (now) claim 75%, so $92.25. That breaks down like so: #Meals Breakfast: $18.45 Lunch: $25.83 Dinner: $29.52 #Incidentals Morning: $4.62 Afternoon: $6.45 Evening: $7.38 Reimbursement procedures are discussed at https://wiki.tei-c.org/index.php/Travel_Reimbursement_Procedures_for_Counci… and the form is at http://www.tei-c.org/Admin/TEI_travel_form.pdf. We are asked to submit our reimbursement requests within 30 days of travel. Hugh

2 2

Quick question on zone/@points
by Martin Holmes 04 Dec '17

04 Dec '17

Hi all, I'm working on this ticket: <https://github.com/TEIC/TEI/issues/1453> where I've been tasked with implementing the new @path attribute for att.coordinated. I have a couple of questions which I've put on the ticket, which really need Council decisions. Could you take a look and add any comments you have? I'll hold off on implementing anything based on the decisions for a week. I'm working in a branch: <https://github.com/TEIC/TEI/tree/mdh_path_1453> Cheers, Martin

1 0

Saxon versions
by Syd Bauman 22 Nov '17

22 Nov '17

As part of our investigation in to how far back oXygen will support the new @override-extension-function attr over the @override attr, I was charged (by me) with testing different versions of Saxon. We are hoping somebody will go through the various releases of oXygen to find out what versions of Saxon they are associated with.[1] The oldest version of Saxon 9 I could easily find on Sourceforge was "Saxon-HE 9.2.0.6J from Saxonica". I chose to test by 0.2 increments: 9.2, 9.4, 9.6, and 9.8. If we need the odd decimal increments I'll be happy to do so, but I'm just hoping we don't. For each version of Saxon I tried it with two stylesheets: one in XSLT 2.0 (in which @override is the name of the attr) and one in XSLT 3.0 (in which @override-extension-function is the name of the attr). Each stylesheet defines two <xsl:function>s, one using each attribute. Anyway, here are the results. Not entirely expected, and somewhat disappointing. # --------- saxon version 9.2 using XSLT 2.0 --------- java -jar ~/Downloads/Saxon9.2/saxon9he.jar -s:xslt_attr_test_2.xslt -xsl:xslt_attr_test_2.xslt Error at xsl:function on line 17 column 70 of xslt_attr_test_2.xslt: XTSE0090: Attribute @override-extension-function is not allowed on element <xsl:function> Error at xsl:function on line 17 column 70 of xslt_attr_test_2.xslt: XTSE0090: Attribute @override-extension-function is not allowed on element <xsl:function> Failed to compile stylesheet. 2 errors detected. # --------- saxon version 9.2 using XSLT 3.0 --------- <?xml version="1.0" encoding="UTF-8"?>tst3o tst3oef # --------- saxon version 9.4 using XSLT 2.0 --------- Error at xsl:function on line 17 column 70 of xslt_attr_test_2.xslt: XTSE0090: Attribute @override-extension-function is not allowed on element <xsl:function> Error at xsl:function on line 17 column 70 of xslt_attr_test_2.xslt: XTSE0090: Attribute @override-extension-function is not allowed on element <xsl:function> Failed to compile stylesheet. 2 errors detected. # --------- saxon version 9.4 using XSLT 3.0 --------- Transformation failed: Requested feature (XSLT 3.0) requires Saxon-PE # --------- saxon version 9.6 using XSLT 2.0 --------- Error at xsl:function on line 17 column 70 of xslt_attr_test_2.xslt: XTSE0090: Attribute @override-extension-function is not allowed on element <xsl:function> Error at xsl:function on line 17 column 70 of xslt_attr_test_2.xslt: XTSE0090: Attribute @override-extension-function is not allowed on element <xsl:function> Stylesheet compilation failed: 2 errors reported # --------- saxon version 9.6 using XSLT 3.0 --------- Warning: at xsl:function on line 13 column 49 of xslt_attr_test_3.xslt: SXWN9014: The xsl:function/@override attribute is deprecated; use override-extension-function Warning: at xsl:function on line 13 column 49 of xslt_attr_test_3.xslt: SXWN9014: The xsl:function/@override attribute is deprecated; use override-extension-function <?xml version="1.0" encoding="UTF-8"?>tst3o tst3oef # --------- saxon version 9.8 using XSLT 2.0 --------- Warning at xsl:function on line 13 column 49 of xslt_attr_test_2.xslt: SXWN9014: The xsl:function/@override attribute is deprecated; use override-extension-function <?xml version="1.0" encoding="UTF-8"?>tst2o tst2oef # --------- saxon version 9.8 using XSLT 3.0 --------- Warning at xsl:function on line 13 column 49 of xslt_attr_test_3.xslt: SXWN9014: The xsl:function/@override attribute is deprecated; use override-extension-function <?xml version="1.0" encoding="UTF-8"?>tst3o tst3oef appendix: XSLT program (change '%' to either '2' or '3') -------- ---- ------- ------- --- -- ------ --- -- ---- | <?xml version="1.0" encoding="UTF-8"?> | <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" | xmlns:xs="http://www.w3.org/2001/XMLSchema" | exclude-result-prefixes="xs" | xmlns:syd="http://www.example.org/syd/ns" | version="%.0"> | | <xsl:template match="/"> | <xsl:value-of select="syd:tst%o()"/> | <xsl:value-of select="syd:tst%oef()"/> | </xsl:template> | | <xsl:function name="syd:tst%o" override="yes"> | <xsl:value-of select="'tst%0'"/> | </xsl:function> | | <xsl:function name="syd:tst%oef" override-extension-function="yes"> | <xsl:value-of select="' tst%oef'"/> | </xsl:function> | | </xsl:stylesheet> [1] I don't know if we can just look this up on the oXygen web site, can post on the oXygen-users mailing list, or need to actually find old versions to check. (In the "Libraries" tab of the "About oXygen" menu.)

1 0

return trip fail
by Syd Bauman 22 Nov '17

22 Nov '17

I was scheduled to depart YVH on a lovely floatplane Sun 19 Nov 10:00, have some long and dreary layovers, and finally land in PVD Mon 20 Nov 01:25, which is a mere 12:25 later. (James scoffs! Magdelena harrumphs! The Scholgers start to sneer, but quickly suppress it; Peter is too hung over and jet-lagged to notice that 12.5 hours is a bit excessive[1].) Floatplane was canceled due to high winds in Seattle. I spent a panicky hour at my AirB&B searching around, and found a flight that would get me into PVD Mon 20 Nov 11:49 (I think it was) for only ~$550. But 2 minutes later, when I went to buy it, Travelocity announced the price had gone up. It was now $1002! So I looked some more, and found another @ ~$560 that got me in Mon 20 Nov 13:56. That's > 2 hours worse (they left YYJ at the same time), but certainly the difference did not seem worth $500 of TEI's money. So I took it. I then went and had lunch at a diner (Pluto's on Cook -- I recommend it), and then took busses (the 14 to the 72 to the 88) to the airport, arriving almost 2 hours after I left the diner. After being grilled quite thoroughly by security (why are you asking me for the 3rd time if I packed my own bag?), the flight from YYJ to SEA was largely uneventful. (Pilot predicted landing a few mins early despite departing a few mins late, but we had to circle around due to reports of bad downdrafts near the runway, so ended up a few mins late. No problem.) After an ~5 hour layover, the red-eye flight from SEA to ORD was no problem, although I got almost no sleep. Flight from ORD to IAD boarded exactly on time. Then we sat there for almost an hour due to same maintenance documentation delay. Given that I had only an ~50 min layover in IAD to get from one terminal to another, there was no chance of making the connecting flight to PVD. So I was re-booked to a later flight,[2] and had another ~6 hour layover. I was scheduled to (and did) arrive in PVD at ~19:00, ~17.6 hours late, missing a (minor) medical appointment. I then had to take busses to get to my car (which was at the repair shop), and got home at ~20:40, which was over 3.5 hours late for my EMS shift. And, of course, I was completely exhausted after essentially doing nothing but traveling or planning travel since Sun 19 Nov 08:30 (11:30 ET), i.e. ~33 hours. Sigh. (BTW, that "nothing" included almost no sleep, but at least lots of work on tickets. :-) I got to bed circa 22:45 and slept for nearly 13 hours. Notes ----- [1] The usual is around ~11 hours; I've done it in as little as ~7.6, and as long as ~13.9. [2] One thing I will say that United did well in this, is that on landing at IAD I went to the customer service desk, and they had already re-booked me on the next available flight out, and printed up a boarding pass. They just had to print my (measly $10) meal voucher and hand them to me. Very efficient, although I would have preferred the efficiency be applied to getting that maintenance report to the flight crew.

2 1

Re: [tei-council] Elections history
by Magdalena Turska 20 Nov '17

20 Nov '17

Sure 20.11.2017 19:21 "Hugh Cayless" <philomousos(a)gmail.com> napisał(a): Magdalena, Are you ok with me sharing this with the Board? Thanks, Hugh On Thu, Nov 16, 2017 at 10:03 PM, Syd Bauman <s.bauman(a)northeastern.edu> wrote: > Impressive work, Magdalena! > -- > 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

Elections history
by Magdalena Turska 20 Nov '17

20 Nov '17

Some results from digging in TEI archives http://admin.exist-db.org:44455/exist/apps/tei-elections/index.html

3 2

draft post to TEI-L re 299
by Syd Bauman 20 Nov '17

20 Nov '17

Here is draft language for your review before it is posted to TEI-L. Comments welcome. --------- The TEI Technical Council plans to remove the following attributes: atLeast=, atMost=, confidence=, extent=, max=, min=, precision=, quantity=, scope=, and unit= from the following elements: <affiliation>, <am>, <birth>, <climate>, <corr>, <date>, <death>, <education>, <event>, <expan>, <faith>, <floruit>, <geogName>, <langKnowledge>, <langKnown>, <location>, <name>, <nationality>, <occupation>, <org>, <orgName>, <origDate>, <origPlace>, <origin>, <persName>, <person>, <persona>, <place>, <placeName>, <reg>, <relation>, <residence>, <sex>, <socecStatus>, <terrain>, and <time> These attributes (which are used for expressing a measurement or statistical information about a set) should never have been on these elements in the first place. Thus their presence is considered a corrigible error, and their removal is scheduled to take place at the next release (likely in Jan or Feb 2018) without a 2-year "deprecation" period, during which use of these attributes on these elements would cause a warning to occur. If anyone is actually using one of these attributes on one of these elements, and its removal in future releases might be a hardship, please let us know by posting here or to the issue (https://github.com/TEIC/TEI/issues/299). Thank you. ---------

2 4