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

room reservation numbers
by Mylonas, Elli 15 Apr '16

15 Apr '16

are listed on the google doc. --elli

1 0

Build failed in Jenkins: Stylesheets #2011
by Victoria TEI Jenkins 15 Apr '16

15 Apr '16

See <http://teijenkins.hcmc.uvic.ca/job/Stylesheets/2011/changes> Changes: [Martin Holmes] Update VERSION ------------------------------------------ [...truncated 2897 lines...] < </define> < <define name="model.lexicalRefinement_sequenceOptional"> < <optional> < <ref name="gramGrp"/> < </optional> < <optional> < <ref name="pos"/> < </optional> < <optional> < <ref name="subc"/> < </optional> < <optional> < <ref name="colloc"/> < </optional> < <optional> < <ref name="usg"/> < </optional> < <optional> < <ref name="lbl"/> < </optional> < </define> < <define name="model.lexicalRefinement_sequenceOptionalRepeatable"> < <zeroOrMore> < <ref name="gramGrp"/> < </zeroOrMore> < <zeroOrMore> < <ref name="pos"/> < </zeroOrMore> < <zeroOrMore> < <ref name="subc"/> < </zeroOrMore> < <zeroOrMore> < <ref name="colloc"/> < </zeroOrMore> < <zeroOrMore> < <ref name="usg"/> < </zeroOrMore> < <zeroOrMore> < <ref name="lbl"/> < </zeroOrMore> < </define> < <define name="model.lexicalRefinement_sequenceRepeatable"> < <oneOrMore> < <ref name="gramGrp"/> < </oneOrMore> < <oneOrMore> < <ref name="pos"/> < </oneOrMore> < <oneOrMore> < <ref name="subc"/> < </oneOrMore> < <oneOrMore> < <ref name="colloc"/> < </oneOrMore> < <oneOrMore> < <ref name="usg"/> < </oneOrMore> < <oneOrMore> < <ref name="lbl"/> < </oneOrMore> < </define> < <define name="model.gramPart"> < <choice> < <ref name="model.morphLike"/> < <ref name="model.lexicalRefinement"/> < </choice> < </define> 9327c8768 < <data type="nonNegativeInteger"/> --- > <ref name="data.count"/> 9385,9387c8826 < <data type="token"> < <param name="pattern">(\p{L}|\p{N}|\p{P}|\p{S})+</param> < </data> --- > <data type="Name"/> 9403,9405c8842 < <data type="token"> < <param name="pattern">(\p{L}|\p{N}|\p{P}|\p{S})+</param> < </data> --- > <ref name="data.enumerated"/> 9412,9414c8849 < <data type="token"> < <param name="pattern">(\p{L}|\p{N}|\p{P}|\p{S})+</param> < </data> --- > <ref name="data.enumerated"/> 9426d8860 < <ref name="att.notated.attributes"/> 9431,9433c8865,8871 < <data type="token"> < <param name="pattern">(\p{L}|\p{N}|\p{P}|\p{S})+</param> < </data> --- > <ref name="data.enumerated"/> > </attribute> > </optional> > <optional> > <attribute name="notation"> > <a:documentation xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0">indicates what notation is used for the pronunciation, if more than one occurs in the machine-readable dictionary.</a:documentation> > <ref name="data.enumerated"/> 9475,9477c8913 < <data type="token"> < <param name="pattern">(\p{L}|\p{N}|\p{P}|\p{S})+</param> < </data> --- > <ref name="data.enumerated"/> 9547,9549c8983 < <data type="token"> < <param name="pattern">(\p{L}|\p{N}|\p{P}|\p{S})+</param> < </data> --- > <ref name="data.enumerated"/> 9623c9057 < <ref name="gramGrp"/> --- > <ref name="model.morphLike"/> 9652,9654c9086 < <data type="token"> < <param name="pattern">(\p{L}|\p{N}|\p{P}|\p{S})+</param> < </data> --- > <ref name="data.enumerated"/> 9669,9671c9101 < <data type="token"> < <param name="pattern">(\p{L}|\p{N}|\p{P}|\p{S})+</param> < </data> --- > <ref name="data.enumerated"/> 9697,9699c9127 < <data type="token"> < <param name="pattern">(\p{L}|\p{N}|\p{P}|\p{S})+</param> < </data> --- > <ref name="data.enumerated"/> 9727,9733c9155 < <zeroOrMore> < <choice> < <text/> < <ref name="model.gLike"/> < <ref name="oRef"/> < </choice> < </zeroOrMore> --- > <empty/> 9737d9158 < <ref name="att.notated.attributes"/> 9742,9744c9163 < <data type="token"> < <param name="pattern">(\p{L}|\p{N}|\p{P}|\p{S})+</param> < </data> --- > <ref name="data.enumerated"/> 9767,9769c9186 < <data type="token"> < <param name="pattern">(\p{L}|\p{N}|\p{P}|\p{S})+</param> < </data> --- > <ref name="data.enumerated"/> 9778,9784c9195 < <zeroOrMore> < <choice> < <text/> < <ref name="model.gLike"/> < <ref name="pRef"/> < </choice> < </zeroOrMore> --- > <empty/> 9788d9198 < <ref name="att.notated.attributes"/> 9805c9215,9220 < <ref name="att.notated.attributes"/> --- > <optional> > <attribute name="notation"> > <a:documentation xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0">indicates what notation is used for the pronunciation, if more than one occurs in the machine-readable dictionary.</a:documentation> > <ref name="data.enumerated"/> > </attribute> > </optional> 9821,9826c9236,9239 < <group> < <ref name="row"/> < <zeroOrMore> < <ref name="model.global"/> < </zeroOrMore> < </group> --- > <ref name="row"/> > <zeroOrMore> > <ref name="model.global"/> > </zeroOrMore> 9829,9839c9242 < <group> < <ref name="model.graphicLike"/> < <zeroOrMore> < <ref name="model.global"/> < </zeroOrMore> < </group> < </oneOrMore> < </choice> < <zeroOrMore> < <group> < <ref name="model.divBottom"/> --- > <ref name="model.graphicLike"/> 9843c9246,9252 < </group> --- > </oneOrMore> > </choice> > <zeroOrMore> > <ref name="model.divBottom"/> > <zeroOrMore> > <ref name="model.global"/> > </zeroOrMore> 9847d9255 < <ref name="att.typed.attributes"/> 9851c9259 < <data type="nonNegativeInteger"/> --- > <ref name="data.count"/> 9857c9265 < <data type="nonNegativeInteger"/> --- > <ref name="data.count"/> 9885c9293,9294 < <a:documentation xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0">contains a mathematical or other formula. [14.2. Formulæ and Mathematical Expressions]</a:documentation> --- > <a:documentation xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0">contains a mathematical or other formula. [14.2. Formulæ and > Mathematical Expressions]</a:documentation> 9894c9303,9308 < <ref name="att.notated.attributes"/> --- > <optional> > <attribute name="notation"> > <a:documentation xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0">names the notation used for the content of the element.</a:documentation> > <ref name="data.enumerated"/> > </attribute> > </optional> 9907d9320 < <ref name="seg"/> make[1]: *** [test.rng] Error 1 make[1]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/Stylesheets/ws/Test'> make: *** [test] Error 2 Build step 'Execute shell' marked build as failure Archiving artifacts

1 3

some changes got lost :(
by Peter Stadler 07 Apr '16

07 Apr '16

Dear all, I’m sorry to say that obviously some commits to the TEIC/TEI dev branch got erroneously overwritten by subsequent commits. I just realized when I looked at the current header chapter and found the modifications I made to the correspDesc section missing. There were a bunch of changes (for a list see issue #1350) and obviously they got lost during the "merge branch 'dev' of github.com:TEIC/TEI into dev“ by some hcayless (Jan 9, commit 6bc49d05f1b0d9385c10563e843c3baeed557591). It’s not clear to me how that happened, especially since Syd’s commit (c5e0adb713042c024bf64d93a8bf4291ed4f875f) came between mine and Hugh’s while his changes to the header chapter were added correctly (and didn’t overwrite mine)?! Peter

3 3

Jenkins working group
by Hugh Cayless 06 Apr '16

06 Apr '16

Dear All, Some of us have been chatting about setting up a working group to get our Jenkins testing protocols properly sorted out and to make it easier to set up new TEI Jenkins environments. Is there anyone who's not in on the current discussion (Martin, James, Peter, Elisa, and Syd) who'd like to join in on such a thing? Hugh

3 6

Re: [tei-council] msItemStuct / filiation
by Lou Burnard 06 Apr '16

06 Apr '16

Hi Matija This seems to be the result of a cut and paste error several years ago: the mistake has been there since a change to the content model which I made at the end of October 2012. I've fixed it now, so it will appear in the next release. Lou On 06/04/16 14:22, Matija Ogrin wrote: > Dear colleagues, > > I wished to ask why the <filiation> element doesn't seem to be valid > within <msItemStruct> any more? > > The related division of the Guidelines > http://www.tei-c.org/release/doc/tei-p5-doc/en/html/MS.html#mscoit > admits <filiation> in both <msItem> and <msItemStruct> (as was the > practice earlier), but the specific table on <filiation> element > http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-filiation.html > actually says what also a recently generated schema does: that > <filiation> may be contained by <msItem> only. > > Thanks for any comments. Best, > Matija >

1 0

Simple Analytic Mechanisms and quotation markup
by Elisa Beshero-Bondar 02 Apr '16

02 Apr '16

Council-- I have a feeling this has probably come up before, but I thought I'd ask here if there's a quick answer. Some of my students have decided to upconvert a project to TEI and to apply `<s>` and `<w>` to do some grammatical markup. And they're trying to figure out how to deal with quoted phrases: Before they'd started the grammatical adventure, they'd been orienting themselves to the various ways to mark quotation (`<said>`, `<mentioned>`, `<q>`, etc.) and had worked out a good system for working with <q>. Now that they're working inside `<s>` elements, though, they discovered the hard way that they can't nest `<q>` inside `<s>`. Before letting them go and rewrite the rules to make it valid for their project for <q> sit in <s>, I found myself cautioning them that there may be a better way. Here's what I wrote: - You've noticed that the TEI content model for the <s> element is restrictive and does not permit the <q> element inside. True. And that may seem "fubared", except that *none* of the elements used for structuring "simple analytic mechanisms" (neither <s> nor its cousin <cl>, and nor the somewhat more permissive <phr>) allow for <q> inside. That exclusion appears to be deliberate, and I think it is because the <s>, <cl>, <phr>, and <w> are a special set of elements that could *by themselves with attributes* convey the information you're wanting to deliver with <q>. Here's what I'd recommend then: Instead of <q>, find its equivalent in an element native to Simple Analytic Mechanisms: I expect that is <phr> for phrase, and add an @type and/or and @rend to indicate you're signalling quotation marks. Work with Ch. 17 a while and I think you'll see why this seems the wiser course. I'm a little troubled by my own response, though, since `<mentioned>` is permitted both inside and outside `<phr>`, so now I'm wondering why the others aren't: I discover `<q>` isn't permitted inside `<phr>` for example. I'll go digging for the history of this, but if anyone here has perspective, I'd be grateful--I imagine this must come up and probably has a lot on the main TEI list. Thanks, 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 about.me/ebbondar

1 0

April F2F logistics
by Mylonas, Elli 01 Apr '16

01 Apr '16

Hi all - i've made a google doc with information in it. Please check and fill out. If you don't have a flight confirmed but are pretty sure of dates, just put them in and say so in the note. I'm trying to finalize hotel reservations at the Hampton Inn. I have made a google doc where you can enter information. This is viewable to anyone with the link, https://docs.google.com/document/d/1lTfB34MS8lbdvO53bsyLsJbXCyan7MWGWJS2MnW… thanks, --elli

5 6

TEI Simple customization
by Magdalena Turska 31 Mar '16

31 Mar '16

Hi all, I've started a tei-simple branch with ODD, template and test file for TEI Simple customization. Magdalena

1 1

Fwd: Reminder: Monthly telecon tomorrow
by Hugh Cayless 31 Mar '16

31 Mar '16

---------- Forwarded message ---------- From: Martin Holmes <mholmes(a)uvic.ca> Date: Thu, Mar 31, 2016 at 12:25 AM Subject: Re: Reminder: Monthly telecon tomorrow To: Hugh Cayless <philomousos(a)gmail.com> Hi Hugh, I've rabbited on at annoying length in the attached text file about release stuff. Please feel free to distribute it or not, or pull some points out if you agree with them for discussion tomorrow. See you in the morning, Martin On 16-03-30 06:08 PM, Hugh Cayless wrote: > Great! We usually add in the phone conference too. Lou probably can't make > it, so we may not go over anyway. It may just be logistics--difficulty > getting sustained attention for more than a day, but in general I agree > with you. > > Sent from my phone. > > On Mar 30, 2016, at 15:49, Martin Holmes <mholmes(a)uvic.ca> wrote: >> >> Hi Hugh, >> >> I'd be happy to sit in if it's not intrusive. Won't it push you over the >> 10-user limit for Hangouts, though? If it's simpler I can just send you >> some thoughts on what's missing from scripts and so on. I think the process >> could be spread out over a week and be less exhausting; I'm not sure why >> it's necessary to have the date of the build match the date of the >> release-to-the-public -- do you? >> >> Cheers, >> Martin >> >> On 2016-03-30 11:00 AM, Hugh Cayless wrote: >>> Martin, would you have any interest in sitting in on the release >>> debrief? Or if not, do you have anything you'd like us to consider? >>> >>> Thanks, >>> Hugh >>> >>> Sent from my phone. >>> >>> Begin forwarded message: >>> >>> *From:* Hugh Cayless <philomousos(a)gmail.com >>>> <mailto:philomousos@gmail.com>> >>>> *Date:* March 30, 2016 at 13:26:07 EDT >>>> *To:* tei-council(a)lists.tei-c.org <mailto:tei-council@lists.tei-c.org> >>>> *Subject:* *Reminder: Monthly telecon tomorrow* >>>> >>>> Hi All, >>>> >>>> Sorry for the late reminder on this. I was rather embroiled in the >>>> release. We will meet tomorrow at 09:00 EST / 14:00 BST / 15:00 CEST. >>>> I’ve put up a preliminary agenda at: >>>> >>>> >>>> https://docs.google.com/document/d/1irjJ8YukC1ro0nyQOYj6DxcZgaUp06FPZQx5nxI… >>>> >>>> Please add items you’d like to discuss. >>>> >>>> All the best, >>>> Hugh >>>> >>>> >>>>

1 0

release branch naming scheme
by Peter Stadler 31 Mar '16

31 Mar '16

Is there any benefit in naming the release branches (both Guidelines and Stylesheets) „release-x.x.x“ rather than just „release“? If it was just „release“ we could have proper jenkins jobs for these branches [1] and wouldn’t need to update the config files for every release. (I guess we will be deleting those „release-x.x.x“ branches after the release but a „release“ branch could simply persist.) What do you think? Peter [1] along with documentation/archival at https://github.com/TEIC/TEI/tree/dev/Documents/Editing/Jenkins/jobs

6 13