September 2017 - Tei-council

co-operative stylesheet education session #12
by Syd Bauman 03 Oct '17

03 Oct '17

I believe we are scheduled for this coming Thu 10-05 13:00Z, i.e.: * 06:00 PDT * 09:00 EDT * 14:00 BST * 15:00 CEST However, there is only a 50% chance I can make that meeting myself. Our homework from the last session was for each of us to come up with a solution and a test file. But we also realized that having a comprehensive idea of what should be happening is a good idea. So it seems to me & Martin that our first step should be deciding what the proper outcome is for each combination of the various flavors of the various constructs involved (e.g., adding a new attribute to a list that is a closed list). To that end we have started developing a comprehensive test file and table of the possible combinations on the ticket.

4 5

RomaJS meetings
by Raffaele Viglianti 03 Oct '17

03 Oct '17

Hello, I would like to set a 1-hour call for sometime next week to kick things off. I said Fridays would be good, but actually I'll be in Charlottesville at the end of this week, so these are times that would work for me (all times are in EDT): Tuesday 3 Oct 9am - 10am Tuesday 3 Oct between 2pm - 5pm Wednesday 4 Oct between 9am - 12pm Please let me know if you're interest in attending, your time preference, or if you're interested but cannot make those times. While it's true that you'll need to know some Javascript to help, there is a fair bit of conceptual work that wouldn't require you to code. For example: what operations should one be able to do with elements? What about defining their content model? What parts of the ODD (and its JSON counterpart) should be queried and how? Coming up with algorithms / strategies together can be as useful as writing the real thing. Also, based on my email from yesterday about p5subset.json, it's now likely that there will be some XSLT work required as well, which most of you can help with. We still need to discuss what changes are needed and why, and I'm hoping we can focus on this during the call. If you want to try helping with JS coding and are not familiar with React/Redux, you could start form these short pieces to get a summary idea: https://reactjs.org/tutorial/tutorial.html#what-is-react http://redux.js.org/docs/introduction/Motivation.html http://redux.js.org/docs/introduction/CoreConcepts.html Because development is underway, there is already a lot of boilerplate code that can be copied to create new places where to hold data, new operations, and new UI components. But you'll still need to figure out how to connect everything together. I am happy to do code walkthroughs. Thanks, Raff

5 5

Re: [tei-council] p5subset.json
by James Cummings 28 Sep '17

28 Sep '17

There were some other people who had built things on top of it.... I don't remember what though. I remember us getting some questions about it at some point though. What are the kinds of changes you want to make? As long as not drastic then I don't see why not. We don't claim it is a perfect serialization to JSON. 😉 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: 28 September 2017 16:16:45 To: tei-council(a)lists.tei-c.org Subject: [tei-council] p5subset.json Hi all, Does anyone know if p5subset.json is used for anything except Byzantium at the moment? In short, can I change the XSLT that generates it as I please? 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

4 3

GitHub Issues: Milestones 3.30
by James Cummings 28 Sep '17

28 Sep '17

As discussed in the meeting I went through and assigned some unassigned tickets. You can always move those to someone else if you can't do it, or ping people to get them to contribute. (Remember, being assigned doesn't mean you necessarily *do* the ticket, just that it is your responsibility to ensure it *gets done*) Some of you may have noticed (and if you didn't, check that you have your github account set to notify you!) that I added the 3.3.0 milestone to many many issues. Basically _most_ of the issues that were open and had Status:Go (with the logic that if they have that status then they should be done by the next release....right? Obviously not all of these will be done by the next release and most of them are not "release-blocking" in any way. You can just _remove_ the milestone, or if you know you will do it before the following release change the milestone to the 3.4.0 release (just added). The benefit of this is when we come to release 3.3.0 we'll go through all these and ask "Hey, this has been around since 2012, why the heck haven't we just *done* it already!" Best wishes, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University

1 0

p5subset.json
by Raffaele Viglianti 28 Sep '17

28 Sep '17

Hi all, Does anyone know if p5subset.json is used for anything except Byzantium at the moment? In short, can I change the XSLT that generates it as I please? Raff

1 0

Re: [tei-council] Reminder, September telecon
by James Cummings 28 Sep '17

28 Sep '17

Just to say I might be slightly late to the meeting as I'll be running back to my office from across campus from another meeting. (But maybe this one I'm in at the moment will end early, who knows.) 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: 28 September 2017 03:18:38 To: tei-council(a)lists.tei-c.org Subject: Re: [tei-council] Reminder, September telecon Hi Hugh and all— Should we take a look at Google Meet, which seems to be a paid-for version of Hangouts with HD video? I’ve been hosting a number of hangouts meetings with DH student-instructor teams at Pitt this month and the lags are predictable and annoying—and I’m nearly (but not quite) ready to spring for a paid upgrade for my own sanity. To get the paid version, I guess you set up a G Suites account for at min, $5 per month—Is that something maybe the TEI can budget for Council? See https://gsuite.google.com/pricing.html?tab_activeEl=tabset-companies <https://gsuite.google.com/pricing.html?tab_activeEl=tabset-companies> —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 Sep 25, 2017, at 4:20 PM, Hugh Cayless <philomousos(a)gmail.com> wrote: > > Sorry to hear that Alex. Safe travels! > > On Mon, Sep 25, 2017 at 4:17 PM, Alejandro Bia <abia(a)umh.es> wrote: > >> Hi All, >> >> On Thursday I'll be on an intercontinental flight from Spain to Uruguay. >> I will not be able to join the meeting this time. Sorry. >> >> Best, >> Alex.- >> >> >> At 17:26 25/09/2017, Hugh Cayless wrote: >> >>> Hi All, >>> >>> We're meeting this Thursday at 09:00 EST / 13:00 UTC / 14:00 BST / 15:00 >>> CEST. Draft agenda is here: >>> https://docs.google.com/document/d/1QIfi1ganpSs5g8TCC4x- >>> aUKo-gs0QHf3nSyssqeDFQc/edit?usp=sharing >>> >>> >>> I'd like to see if we can get some of our "Needs Discussion" backlog >>> turned >>> green, so if you have any you'd like the go-ahead on, please add them to >>> the list. I've just stuck some of the more recent ones in there as a >>> starting point. >>> >>> Elli won't be back from vacation, so I don't think we can use the Brown >>> hangout this time. We could try something different if anyone has any >>> suggestions, or I may just bite the bullet and sign up for a paid Google >>> office suite thing, which will give us up to 25 simultaneous users. >>> >>> Hugh >>> -- >>> 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 >> -- >> 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

Re: [tei-council] Reminder, September telecon
by Alejandro Bia 28 Sep '17

28 Sep '17

Hi All, On Thursday I'll be on an intercontinental flight from Spain to Uruguay. I will not be able to join the meeting this time. Sorry. Best, Alex.- At 17:26 25/09/2017, Hugh Cayless wrote: >Hi All, > >We're meeting this Thursday at 09:00 EST / 13:00 UTC / 14:00 BST / 15:00 >CEST. Draft agenda is here: >https://docs.google.com/document/d/1QIfi1ganpSs5g8TCC4x-aUKo-gs0QHf3nSyssqe… > > >I'd like to see if we can get some of our "Needs Discussion" backlog turned >green, so if you have any you'd like the go-ahead on, please add them to >the list. I've just stuck some of the more recent ones in there as a >starting point. > >Elli won't be back from vacation, so I don't think we can use the Brown >hangout this time. We could try something different if anyone has any >suggestions, or I may just bite the bullet and sign up for a paid Google >office suite thing, which will give us up to 25 simultaneous users. > >Hugh >-- >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

3 2

Dealing with an abbreviation that expands to multiple lines of verse
by Raffaele Viglianti 25 Sep '17

25 Sep '17

Dear List, We're encoding a number of early-modern songs for a pilot project and we are wondering how to deal with a special form of abbreviation and its expansion. An example: image from EEBO <https://eebo.chadwyck.com/search/full_rec?SOURCE=pgimages.cfg&ACTION=ByID&I…> You can see at the bottom of the left page that the last line reads: "But I have vow'd, &c.". The "&c." indicates that the rest of the refrain is to be sung; you can find it underlain in the score above, starting at about a third of the page: "But I have vow'd, and never muſt your baniſh'd ſervant trouble you for if he break you may diſtruſt, the vow he made to love you too.". We would like to encode both the "&c." and the expansion, but since this spans multiple lines, we are not able to use <choice> with <abbr> and <expan>. What should we do instead? <lg type="stanza">  <l>About with him he bears the rage,</l> <l>And in his tainted bloud the fire.</l> <l>But I have vow'd, &c.</l>  </lg> We could link together expansions, but the choice remains somewhat incomplete, as it only wraps the first part of the expansion: <l>But I have vow'd, <choice><abbr>&c.</abbr><expan xml:id="ex1" next="#ex2">and never must</expan></choice></l> <l><expan xml:id="ex2" prev="#ex1" next="#ex3">your banish'd servant trouble you</expan></l> <l><expan xml:id="ex3" prev="#ex2" next="#ex4">for if he break you may distrust,</expan></l> <l><expan xml:id="ex4" prev="#ex3">the vow he made to love you too.</expan></l> Another possibility could be wrapping the refrain in a nested <lg> and give it a subtype, but I'm not too happy about it. It also doesn't indicate clearly what was on the original document and what was expanded because "But I have vow'd," gets bundled with the rest. <l rend="indent1">And in his tainted bloud the fire.</l> <lg type="refrain" subtype="expanded"> <l>But I have vow'd, <choice> <abbr>&c.</abbr> <expan>and never muſt</expan> </choice> </l> <l>your baniſh'd ſervant trouble you</l> <l>for if he break you may diſtruſt,</l> <l><expan>the vow he made to love you too.</expan></l> </lg> </lg> Thanks for any advice you can provide! Raff -- Raffaele Viglianti, PhD Research Programmer Maryland Institute for Technology in the Humanities University of Maryland

1 1

Reminder, September telecon
by Hugh Cayless 25 Sep '17

25 Sep '17

Hi All, We're meeting this Thursday at 09:00 EST / 13:00 UTC / 14:00 BST / 15:00 CEST. Draft agenda is here: https://docs.google.com/document/d/1QIfi1ganpSs5g8TCC4x-aUKo-gs0QHf3nSyssqe… I'd like to see if we can get some of our "Needs Discussion" backlog turned green, so if you have any you'd like the go-ahead on, please add them to the list. I've just stuck some of the more recent ones in there as a starting point. Elli won't be back from vacation, so I don't think we can use the Brown hangout this time. We could try something different if anyone has any suggestions, or I may just bite the bullet and sign up for a paid Google office suite thing, which will give us up to 25 simultaneous users. Hugh

1 0

dates for XML Prague 2018
by Syd Bauman 22 Sep '17

22 Sep '17

XML Prague 2018 will be from Thu 02-08 to Sat 02-10, with preconference workshops Tue 02-06 and Wed 02-07, I think. http://www.xmlprague.cz/

3 5

Re: [tei-council] booking near U Vic
by Martin Holmes 18 Sep '17

18 Sep '17

Hi all, I think the Council meetings are going to be held downtown; Hugh and Michelle have been handling the room booking. We figured that would be more convenient because most people will be staying downtown (we assumed), although with AirBnB that's no longer a given, of course. The conference will be on campus. We do have a room booked on campus just in case, but it's not ideal; it has a glass wall facing a common area in the Library. My experience from my years on Council was that day three was always a bit fragmentary, with some people leaving during the day because they needed to catch planes, and others working all day and leaving in the evening or the day after. Cheers, Martin On 2017-09-16 04:30 PM, Beshero-Bondar, Elisa Eileen wrote: > Hi Council people (cc: Martin) -- I located an AirBNB room very close to > the U Vic campus (and the owners even offer to collect me at the > airport). I booked to arrive Sat. Nov 11 and depart Sat. Nov 18--though > I haven't booked flights yet. Questions: > 1) I understand Council is meeting after the conference. Did I predict > correctly that we'll be meeting on the U Vic campus? (If we are meeting > downtown I will reconsider my lodging.) > 2) Do we need the full day Saturday 11/18 for Council work? (I hope not, > and that that can be a travel day--it is usually a long red-eye flight > for me to return home and I want to be back teaching my classes on Mon. > 11/20). > > If we're going to be on campus for that week, I recommend others try > AirBNB and set the map search around the ring road that surrounds the > campus--you may be able to avoid having to take a bus in from the city > that way! > > Cheers, > Elisa > > -- > Elisa Beshero-Bondar, PhD > Director, Center for the Digital Text > Associate Professor of English > University of Pittsburgh at Greensburg > 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/> > > Typeset by hand on my iPad

3 3

Re: [tei-council] Fwd: Proposal for creation of a TEI SIG “Indic Texts”
by James Cummings 15 Sep '17

15 Sep '17

Sounds good to me. Follows naturally on from the East Asian/Japanese one. 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: 14 September 2017 15:37:22 To: tei-council(a)lists.tei-c.org Subject: Re: [tei-council] Fwd: Proposal for creation of a TEI SIG “Indic Texts” Very interesting! I could also imagine a TEI-backed customization coming out of this. Raff On Thu, Sep 14, 2017 at 10:22 AM, Hugh Cayless <philomousos(a)gmail.com> wrote: > Dear All, > > A new SIG proposal. Sounds interesting. Any thoughts? > > > ---------- Forwarded message ---------- > From: Patrick McAllister <patrick.mcallister(a)oeaw.ac.at> > Subject: Proposal for creation of a TEI SIG “Indic Texts” > > > Dear Hugh Cayless, > > I'm writing to you, the director of the TEI technical council, because > Andrew Ollett (see CC) and I would like to start a TEI Special Interest > Group focused on Indic texts. > > Our plan for this SIG is as follows: > > ########## > > The proposed SIG “Indic Texts” aims to coordinate scholars engaged in > the study of Indic texts so as to establish a consensus on best > practices for using the TEI’s Guidelines to analyze these kinds of > texts. > > There are several respects in which the applicability of the TEI guidelines > to these texts is less than obvious. These relate to distinctive features > of Indic textuality, including: the use of syllabic scripts, and the > non-coincidence of grapheme- (syllable-) and word-boundaries; the > application of phonotactic rules (sandhi) that further obscures the > boundaries between words; extensive compounding; the use of distinctive > media and writing supports (such as birch bark, palm leaves, and copper > plates); distinctive metrical patterns with different types of caesuras; > the prominence of the commentary as a genre, and the depth of intertextual > relations this implies; the frequent reuse of texts in other texts, which > requires careful and deliberate application of the "quoteLike" module. > > The expected outcome of the SIG’s work is a practical guide, which could > perhaps be added to the TEI Guidelines, that analyzes common cases in > the markup of Indic texts and proposes ways in which the analytical > tools provided by the TEI Guidelines might best be used in these cases, > discussing benefits and drawbacks of the solutions possible. > > ########## > > The SIG coordinators should be Andrew Ollett and I. > > We would like to add that we have already spoken to quite a few > colleagues specialized in various areas of our field who are eager to > join this group and would welcome its creation. We hope that the > proposal, though quite general, will be accepted. Please let us know if > you need anything more to decide on this. > > With best wishes, > > -- > Patrick McAllister > > Email: patrick.mcallister(a)oeaw.ac.at > Phone: + 43 1 51581 6423 > > Institute for the Cultural and Intellectual History of Asia (IKGA) > Austrian Academy of Sciences > Hollandstraße 11-13, 2nd floor > 1020 Vienna, Austria > > http://www.ikga.oeaw.ac.at/ > -- > 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

Fwd: Proposal for creation of a TEI SIG “Indic Texts”
by Hugh Cayless 14 Sep '17

14 Sep '17

Dear All, A new SIG proposal. Sounds interesting. Any thoughts? ---------- Forwarded message ---------- From: Patrick McAllister <patrick.mcallister(a)oeaw.ac.at> Subject: Proposal for creation of a TEI SIG “Indic Texts” Dear Hugh Cayless, I'm writing to you, the director of the TEI technical council, because Andrew Ollett (see CC) and I would like to start a TEI Special Interest Group focused on Indic texts. Our plan for this SIG is as follows: ########## The proposed SIG “Indic Texts” aims to coordinate scholars engaged in the study of Indic texts so as to establish a consensus on best practices for using the TEI’s Guidelines to analyze these kinds of texts. There are several respects in which the applicability of the TEI guidelines to these texts is less than obvious. These relate to distinctive features of Indic textuality, including: the use of syllabic scripts, and the non-coincidence of grapheme- (syllable-) and word-boundaries; the application of phonotactic rules (sandhi) that further obscures the boundaries between words; extensive compounding; the use of distinctive media and writing supports (such as birch bark, palm leaves, and copper plates); distinctive metrical patterns with different types of caesuras; the prominence of the commentary as a genre, and the depth of intertextual relations this implies; the frequent reuse of texts in other texts, which requires careful and deliberate application of the "quoteLike" module. The expected outcome of the SIG’s work is a practical guide, which could perhaps be added to the TEI Guidelines, that analyzes common cases in the markup of Indic texts and proposes ways in which the analytical tools provided by the TEI Guidelines might best be used in these cases, discussing benefits and drawbacks of the solutions possible. ########## The SIG coordinators should be Andrew Ollett and I. We would like to add that we have already spoken to quite a few colleagues specialized in various areas of our field who are eager to join this group and would welcome its creation. We hope that the proposal, though quite general, will be accepted. Please let us know if you need anything more to decide on this. With best wishes, -- Patrick McAllister Email: patrick.mcallister(a)oeaw.ac.at Phone: + 43 1 51581 6423 Institute for the Cultural and Intellectual History of Asia (IKGA) Austrian Academy of Sciences Hollandstraße 11-13, 2nd floor 1020 Vienna, Austria http://www.ikga.oeaw.ac.at/

2 1

minutes & mentors
by Syd Bauman 12 Sep '17

12 Sep '17

I wanted to look up who our mentors were, so I went to look at the minutes from our 2016-09 meeting in Vienna. I did not find what I was looking for (who is currently mentoring whom?), but I did discover that we have no minutes up on http://www.tei-c.org/Activities/Council/Meetings/index.xml since 2016. I.e., we are ~8 months behind. I realize there's trouble with getting stuff up on the website what with the changeover and all, but I'm hoping, Hugh, that we can at least assemble a list of pointers to the notes we have taken during our meetings and conference calls and post it here or on our wiki so that at least we, if not the public can readily find 'em. (Or have we already done this?) It also occurs to me that the numbering system for Council minutes does not scale well, given that we now have 2 face-to-face and over 1/2 dozen conference calls a year. My first thought is to change the system so that the filename incorporates the date (e.g., tcm_2017-09-10.xml), and record whether it is a face-to-face or conference call somewhere in the header. (Use the date of the first day of the meeting for multi-day meetings.)

4 5

IIIF meeting at DH2017
by Mylonas, Elli 11 Sep '17

11 Sep '17

Hi all - I went to the IIIF meeting at DH in Montréal. It consisted of a few people who want to work with IIIF and TEI, continuing the discussion that was started on the list. Two with most experience were Ben Brumfield and Nick Laiacona, there were some others there as well. One of the other members of the group is very interested in referencing zones on an image for ex. and felt stymied by TEI recommnedations as he needed something that matched IIIF notation for zones to work. Ben and Nick have offered to develop some example implementations of IIIF and TEI. Nick's already made progress on TEI client that displays images using IIIF, while I've been working on IIIF manifests that render text using TEI. As i understand it, we have two approaches - 1 is to encode using a TEI document, and use IIIF to display images or zones, and 2. is to start from IIIF and use TEI to display tex. (please tell me if I am wrong) So, if we continue this discussion we may be trying to learn enough to write recommendations for how to get your TEI to interact with IIIF, and also to think about how/if to make sure that TEI provides whatever IIIF might need to talk TEI. Does Council want to give them the go ahead and commit to consider the mechanics of this pairing? Thanks, --elli

1 1

Re: [tei-council] co-operative stylesheet education session #11
by Lou Burnard 07 Sep '17

07 Sep '17

Nor will I -- apologies for having forgotten about this when booking my train. L On 07/09/17 08:33, James Cummings wrote: > Apologies, I won't be able to make this one. > > James > > -- > Dr James Cummings, 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:* Thursday, September 7, 2017 12:48:26 AM > *To:* TEI Council; Martin Holmes; Lou Burnard > *Subject:* [tei-council] co-operative stylesheet education session #11 > We are scheduled for tomorrow morning, Thu 09-07 at 13:00Z. I.e.: > * 06:00 PDT > * 09:00 EDT > * 14:00 BST > * 15:00 CEST > > Martin & I thought it might be a good exercise to try to tackle at > least the "where and what exactly is the problem" underlying ticket > 272 (https://github.com/TEIC/Stylesheets/issues/272). > > Martin & I have each developed a test ODD to exercise this problem, > and Martin has posted his (which is better commented than mine) to > the ticket. We suspect the problem lies in the "odd2odd-copy" mode > templates of odd2odd.xsl, but don't have much more sense than that. > > As before, we will plan to meet on Google Hangouts. I don't think we > actually need someone to be in charge of establishing the conference > call, but if we do, it should not be me. > > Looking forward! > -- > 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 1

Re: [tei-council] co-operative stylesheet education session #11
by James Cummings 07 Sep '17

07 Sep '17

Apologies, I won't be able to make this one. James -- Dr James Cummings, 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: Thursday, September 7, 2017 12:48:26 AM To: TEI Council; Martin Holmes; Lou Burnard Subject: [tei-council] co-operative stylesheet education session #11 We are scheduled for tomorrow morning, Thu 09-07 at 13:00Z. I.e.: * 06:00 PDT * 09:00 EDT * 14:00 BST * 15:00 CEST Martin & I thought it might be a good exercise to try to tackle at least the "where and what exactly is the problem" underlying ticket 272 (https://github.com/TEIC/Stylesheets/issues/272). Martin & I have each developed a test ODD to exercise this problem, and Martin has posted his (which is better commented than mine) to the ticket. We suspect the problem lies in the "odd2odd-copy" mode templates of odd2odd.xsl, but don't have much more sense than that. As before, we will plan to meet on Google Hangouts. I don't think we actually need someone to be in charge of establishing the conference call, but if we do, it should not be me. Looking forward! -- 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

co-operative stylesheet education session #11
by Syd Bauman 07 Sep '17

07 Sep '17

We are scheduled for tomorrow morning, Thu 09-07 at 13:00Z. I.e.: * 06:00 PDT * 09:00 EDT * 14:00 BST * 15:00 CEST Martin & I thought it might be a good exercise to try to tackle at least the "where and what exactly is the problem" underlying ticket 272 (https://github.com/TEIC/Stylesheets/issues/272). Martin & I have each developed a test ODD to exercise this problem, and Martin has posted his (which is better commented than mine) to the ticket. We suspect the problem lies in the "odd2odd-copy" mode templates of odd2odd.xsl, but don't have much more sense than that. As before, we will plan to meet on Google Hangouts. I don't think we actually need someone to be in charge of establishing the conference call, but if we do, it should not be me. Looking forward!

1 0

BTW, I was reimbursed
by Syd Bauman 02 Sep '17

02 Sep '17

Some folks on our recent call expressed doubt as to whether or not TEI-C had reimbursed them for Vienna and Prague yet. I just checked: I have received both my reimbursements in full: Vienna on 2016-12-15 or so, and Prague on 2017-05-11.

1 0

Build failed in Jenkins: TEIP5-Test-dev #3419
by Victoria TEI Jenkins 01 Sep '17

01 Sep '17

See <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/3419/display/redirect?pag…> Changes: [ron.vandenbranden] refined checks for notes and punctuation (cf. Chicago Manual of Style ------------------------------------------ Started by an SCM change Building in workspace <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/TEIC/TEI.git # timeout=10 Fetching upstream changes from https://github.com/TEIC/TEI.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/TEIC/TEI.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/dev^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/dev^{commit} # timeout=10 Checking out Revision ff506f85518200fc7a8ed0f710f0f76878a88a31 (refs/remotes/origin/dev) > git config core.sparsecheckout # timeout=10 > git checkout -f ff506f85518200fc7a8ed0f710f0f76878a88a31 > git rev-list 2c1829d3bb6a248411c055d07d725836d87683c3 # timeout=10 [workspace] $ /bin/bash -xe /tmp/jenkins2322665904575764617.sh + cd P5 ++ pwd + make VCS=git INJENKINS=true XSL=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/../../../Stylesheet…> clean validate test (cd Exemplars; make clean) make[1]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Exemplars'> mv tei_lite_fr.nvdl tei_lite_fr.nvdl.bak rm -f *.processed *.xsd *.dtd *.doc.* *.rnc tei*.xsl tei*.rng *.compiled* *~ *.xi *.isosch *.epub *.pdf *.html *.nvdl *-teix* mv tei_lite_fr.nvdl.bak tei_lite_fr.nvdl rm -f exnames.xml rm -f enrich.rng isofs.rng rm -f names.xml *properties rm -f [A-Z]*xml make[1]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Exemplars'> (cd Test; make clean) make[1]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Test'> rm -f test*.doc.xml test*.rnc test*.dtd test*.compiled.* test*.xsd test*.rnc test*.rng test*.xsl test*.isosch rm -rf LOG *~ *.xsd Schema RomaResults DTD rm -rf *.doc.* rm -f detest.log detest.log.all rm -f *-examples.rng *-examples.rnc *test*.nvdl *-ex.odd rm -f detest.rnc detest.rng detest.dtd detest.isosch make[1]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Test'> rm -rf release Guidelines Guidelines-web Schema DTD dtd Split rm -rf Guidelines.??? Guidelines-* rm -f *.isosch.xsl rm -f *.stamp rm -f *.xsd rm -f Exemplars/stdout rm -f Test/*.isosch rm -f Test/detest.dtd Test/detest.rnc Test/detest.rng Test/detest.xsl rm -f Test/stdout rm -f Utilities/guidelines.xsl rm -f anything buildweb.xml rm -f p5.sch p5.isosch p5.xml p5subset.xml p5subset.json p5subset.js rm -f p5attlist.txt rm -f p5odds-examples.rng p5odds-examples.rnc p5odds.rng p5odds.rnc p5odds.isosch rm -f pdfbuild.log rm -f stripspace.xsl.model rm -f tei-*.zip rm -f tei-p5-*_*build rm -f tei-p5-*_*changes rm -f tei-p5-*_*deb rm -f teiwebsiteguidelines.zip rm -rf FASC-* rm -rf catalogue.* modList rm -rf valid v.xml ValidatorLog.xml Utilities/pointerattributes.xsl graphics.sh missfont.log v.body v.header Schematron1.xml Schematron2.xml Checking you have running XML tools and Perl before trying to run transform... Ant:/usr/bin/ant Perl:/usr/bin/perl Java:/usr/bin/java xmllint:/usr/bin/xmllint touch check.stamp get latest date: VCS is git if [ "git" = "svn" ] ; \ then \ if [ true = "true" ] ; \ then svn info --xml svn://svn.code.sf.net/p/tei/code/trunk/P5 ; \ else svn info --xml ; \ fi > repodate.xml ; \ fi if [ git = "git" ] ; \ then \ git log --max-count=1 --pretty=format:"<info type=\"git\"><entry><commit revision=\"%h\"><date>%ai</date></commit></entry></info>" > repodate.xml ; \ fi BUILD: Generate modular DTDs, Schemas, Schematron and miscellaneous outputs ANT_OPTS="-Xss2m -Xmx752m -Djava.awt.headless=true" ant -q -lib Utilities/lib/jing.jar:Utilities/lib/saxon9he.jar -f antbuilder.xml -DXSL=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/../../../Stylesheet…> -DDRIVER=Source/guidelines-en.xml base subset outputs [echo] make modular DTDs, RELAXNG schemas, json, odd schemas, schematron files [echo] Using <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/../../../Stylesheet…> for XSL stylesheets [echo] Do ODD processing for p5odds.odd [echo] Do ODD processing for p5odds-examples.odd BUILD SUCCESSFUL Total time: 2 minutes 4 seconds BUILD: Generate modular RELAX NG (compact) schemas using trang (cd Schema; for i in *rng; do java -jar ../Utilities/lib/trang.jar $i `basename $i .rng`.rnc;done) touch schemas.stamp BUILD: Check validity with rnv (https://github.com/dtolpin/RNV) if we have it command -v rnv && rnv -v p5odds.rnc p5.xml /usr/local/bin/rnv rnv version 1.7.10 p5.xml BUILD: Check validity with special-purpose XSL code, looking for bad links etc ANT_OPTS="-Xss2m -Xmx752m -Djava.awt.headless=true" ant -q -lib Utilities/lib/saxon9he.jar -f antbuilder.xml -DXSL=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/../../../Stylesheet…> validators [echo] Run Schematron script (normal part of Guidelines) [echo] Run Schematron script (Examples in Guidelines marked as valid) [echo] Run ad hoc XSLT validators BUILD SUCCESSFUL Total time: 1 minute 1 second <Messages> <WARNING>Schematron warning: This defaultVal of status construct becomes outdated on 2017-09-05 [Test: @validUntil cast as xs:date ge (current-date() + (60*xs:dayTimeDuration('P1D')))] Location: /TEI[1]/text[1]/body[1]/div[2]/div[2]/div[4]/specGrp[1]/elementSpec[5]/attList[1]/attDef[1]/defaultVal[1]</WARNING> <WARNING>Schematron warning: This defaultVal of status construct becomes outdated on 2017-09-05 [Test: @validUntil cast as xs:date ge (current-date() + (60*xs:dayTimeDuration('P1D')))] Location: /TEI[1]/text[1]/body[1]/div[2]/div[3]/div[3]/specGrp[1]/elementSpec[2]/attList[1]/attDef[1]/defaultVal[1]</WARNING> <WARNING>Schematron warning: This defaultVal of aloud construct becomes outdated on 2017-09-05 [Test: @validUntil cast as xs:date ge (current-date() + (60*xs:dayTimeDuration('P1D')))] Location: /TEI[1]/text[1]/body[1]/div[3]/div[3]/div[3]/specGrp[1]/elementSpec[1]/attList[1]/attDef[1]/defaultVal[1]</WARNING> <WARNING>Schematron warning: This defaultVal of discrete construct becomes outdated on 2017-09-05 [Test: @validUntil cast as xs:date ge (current-date() + (60*xs:dayTimeDuration('P1D')))] Location: /TEI[1]/text[1]/body[1]/div[7]/div[3]/div[1]/specGrp[1]/elementSpec[3]/attList[1]/attDef[2]/defaultVal[1]</WARNING> <ERROR>Schematron error: The oVar construct is outdated (as of 2017-08-24); ODD processors may ignore it, and its use is no longer supported [Test: @validUntil cast as xs:date ge current-date()] Location: /TEI[1]/text[1]/body[1]/div[9]/div[4]/specGrp[2]/elementSpec[2]</ERROR> <WARNING>Schematron warning: The oVar construct becomes outdated on 2017-08-24 [Test: @validUntil cast as xs:date ge (current-date() + (60*xs:dayTimeDuration('P1D')))] Location: /TEI[1]/text[1]/body[1]/div[9]/div[4]/specGrp[2]/elementSpec[2]</WARNING> <ERROR>Schematron error: The pVar construct is outdated (as of 2017-08-24); ODD processors may ignore it, and its use is no longer supported [Test: @validUntil cast as xs:date ge current-date()] Location: /TEI[1]/text[1]/body[1]/div[9]/div[4]/specGrp[2]/elementSpec[4]</ERROR> <WARNING>Schematron warning: The pVar construct becomes outdated on 2017-08-24 [Test: @validUntil cast as xs:date ge (current-date() + (60*xs:dayTimeDuration('P1D')))] Location: /TEI[1]/text[1]/body[1]/div[9]/div[4]/specGrp[2]/elementSpec[4]</WARNING> <WARNING>Schematron warning: This defaultVal of defective construct becomes outdated on 2017-09-05 [Test: @validUntil cast as xs:date ge (current-date() + (60*xs:dayTimeDuration('P1D')))] Location: /TEI[1]/text[1]/body[1]/div[10]/div[6]/div[6]/specGrp[2]/classSpec[1]/attList[1]/attDef[1]/defaultVal[1]</WARNING> <WARNING>Schematron warning: WARNING: deprecated use of element — The catchwords element will not be allowed outside of msDesc as of 2018-10-01. [Test: ancestor::tei:msDesc] Location: /TEI[1]/text[1]/body[1]/div[10]/div[3]/div[7]/p[1]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/catchwords[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> <WARNING>Schematron warning: WARNING: deprecated use of element — The catchwords element will not be allowed outside of msDesc as of 2018-10-01. [Test: ancestor::tei:msDesc] Location: /TEI[1]/text[1]/body[1]/div[10]/div[3]/div[7]/p[1]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][2]/catchwords[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> <WARNING>Schematron warning: WARNING: deprecated use of element — The catchwords element will not be allowed outside of msDesc as of 2018-10-01. [Test: ancestor::tei:msDesc] Location: /TEI[1]/text[1]/body[1]/div[10]/div[3]/div[8]/specGrp[1]/elementSpec[1]/exemplum[1]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/catchwords[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> <WARNING>Schematron warning: WARNING: deprecated use of element — The catchwords element will not be allowed outside of msDesc as of 2018-10-01. [Test: ancestor::tei:msDesc] Location: /TEI[1]/text[1]/body[1]/div[10]/div[7]/div[3]/div[3]/specGrp[1]/elementSpec[5]/exemplum[3]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/collation[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/p[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/catchwords[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> <WARNING>Schematron warning: WARNING: deprecated use of element — The catchwords element will not be allowed outside of msDesc as of 2018-10-01. [Test: ancestor::tei:msDesc] Location: /TEI[1]/text[1]/body[1]/div[10]/div[7]/div[3]/div[3]/specGrp[1]/elementSpec[5]/exemplum[6]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/collation[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/p[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/catchwords[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> <WARNING>Schematron warning: WARNING: deprecated use of element — The secFol element will not be allowed outside of msDesc as of 2018-10-01. [Test: ancestor::tei:msDesc] Location: /TEI[1]/text[1]/body[1]/div[10]/div[3]/div[7]/p[4]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/secFol[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> <WARNING>Schematron warning: WARNING: deprecated use of element — The secFol element will not be allowed outside of msDesc as of 2018-10-01. [Test: ancestor::tei:msDesc] Location: /TEI[1]/text[1]/body[1]/div[10]/div[3]/div[8]/specGrp[1]/elementSpec[14]/exemplum[1]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/secFol[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> <WARNING>Schematron warning: WARNING: deprecated use of element — The secFol element will not be allowed outside of msDesc as of 2018-10-01. [Test: ancestor::tei:msDesc] Location: /TEI[1]/text[1]/body[1]/div[10]/div[3]/div[8]/specGrp[1]/elementSpec[14]/exemplum[2]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/secFol[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> <WARNING>Schematron warning: WARNING: deprecated use of element — The secFol element will not be allowed outside of msDesc as of 2018-10-01. [Test: ancestor::tei:msDesc] Location: /TEI[1]/text[1]/body[1]/div[10]/div[3]/div[8]/specGrp[1]/elementSpec[14]/exemplum[3]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/secFol[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> <WARNING>Schematron warning: WARNING: deprecated use of element — The signatures element will not be allowed outside of msDesc as of 2018-10-01. [Test: ancestor::tei:msDesc] Location: /TEI[1]/text[1]/body[1]/div[10]/div[3]/div[7]/p[2]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/signatures[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> <WARNING>Schematron warning: WARNING: deprecated use of element — The signatures element will not be allowed outside of msDesc as of 2018-10-01. [Test: ancestor::tei:msDesc] Location: /TEI[1]/text[1]/body[1]/div[10]/div[3]/div[7]/p[3]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/signatures[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> <WARNING>Schematron warning: WARNING: deprecated use of element — The signatures element will not be allowed outside of msDesc as of 2018-10-01. [Test: ancestor::tei:msDesc] Location: /TEI[1]/text[1]/body[1]/div[10]/div[3]/div[8]/specGrp[1]/elementSpec[15]/exemplum[1]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/signatures[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> <WARNING>Schematron warning: WARNING: deprecated use of element — The signatures element will not be allowed outside of msDesc as of 2018-10-01. [Test: ancestor::tei:msDesc] Location: /TEI[1]/text[1]/body[1]/div[10]/div[3]/div[8]/specGrp[1]/elementSpec[15]/exemplum[2]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/signatures[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> <WARNING>Schematron warning: WARNING: deprecated use of element — The signatures element will not be allowed outside of msDesc as of 2018-10-01. [Test: ancestor::tei:msDesc] Location: /TEI[1]/text[1]/body[1]/div[10]/div[3]/div[8]/specGrp[1]/elementSpec[15]/exemplum[3]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/signatures[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> </Messages> (grep -q "<ERROR>" ValidatorLog.xml;if [ $? -ne 1 ] ; then echo "Oh dear me. ERROR found";diff ValidatorLog.xml expected-results/ValidatorLog.xml;false; fi) Oh dear me. ERROR found 2,12d1 < <WARNING>Schematron warning: This defaultVal of status construct becomes outdated on 2017-09-05 [Test: @validUntil cast as xs:date ge (current-date() + (60*xs:dayTimeDuration('P1D')))] Location: /TEI[1]/text[1]/body[1]/div[2]/div[2]/div[4]/specGrp[1]/elementSpec[5]/attList[1]/attDef[1]/defaultVal[1]</WARNING> < <WARNING>Schematron warning: This defaultVal of status construct becomes outdated on 2017-09-05 [Test: @validUntil cast as xs:date ge (current-date() + (60*xs:dayTimeDuration('P1D')))] Location: /TEI[1]/text[1]/body[1]/div[2]/div[3]/div[3]/specGrp[1]/elementSpec[2]/attList[1]/attDef[1]/defaultVal[1]</WARNING> < <WARNING>Schematron warning: This defaultVal of aloud construct becomes outdated on 2017-09-05 [Test: @validUntil cast as xs:date ge (current-date() + (60*xs:dayTimeDuration('P1D')))] Location: /TEI[1]/text[1]/body[1]/div[3]/div[3]/div[3]/specGrp[1]/elementSpec[1]/attList[1]/attDef[1]/defaultVal[1]</WARNING> < <WARNING>Schematron warning: This defaultVal of discrete construct becomes outdated on 2017-09-05 [Test: @validUntil cast as xs:date ge (current-date() + (60*xs:dayTimeDuration('P1D')))] Location: /TEI[1]/text[1]/body[1]/div[7]/div[3]/div[1]/specGrp[1]/elementSpec[3]/attList[1]/attDef[2]/defaultVal[1]</WARNING> < <ERROR>Schematron error: The oVar < construct is outdated (as of 2017-08-24); ODD processors may ignore it, and its use is no longer supported [Test: @validUntil cast as xs:date ge current-date()] Location: /TEI[1]/text[1]/body[1]/div[9]/div[4]/specGrp[2]/elementSpec[2]</ERROR> < <WARNING>Schematron warning: The oVar construct becomes outdated on 2017-08-24 [Test: @validUntil cast as xs:date ge (current-date() + (60*xs:dayTimeDuration('P1D')))] Location: /TEI[1]/text[1]/body[1]/div[9]/div[4]/specGrp[2]/elementSpec[2]</WARNING> < <ERROR>Schematron error: The pVar < construct is outdated (as of 2017-08-24); ODD processors may ignore it, and its use is no longer supported [Test: @validUntil cast as xs:date ge current-date()] Location: /TEI[1]/text[1]/body[1]/div[9]/div[4]/specGrp[2]/elementSpec[4]</ERROR> < <WARNING>Schematron warning: The pVar construct becomes outdated on 2017-08-24 [Test: @validUntil cast as xs:date ge (current-date() + (60*xs:dayTimeDuration('P1D')))] Location: /TEI[1]/text[1]/body[1]/div[9]/div[4]/specGrp[2]/elementSpec[4]</WARNING> < <WARNING>Schematron warning: This defaultVal of defective construct becomes outdated on 2017-09-05 [Test: @validUntil cast as xs:date ge (current-date() + (60*xs:dayTimeDuration('P1D')))] Location: /TEI[1]/text[1]/body[1]/div[10]/div[6]/div[6]/specGrp[2]/classSpec[1]/attList[1]/attDef[1]/defaultVal[1]</WARNING> 26a16,28 > <WARNING>Schematron warning: WARNING: use of deprecated method — the use of the altIdentifier element as a direct child of the msPart element will be removed from the TEI on 2016-09-09 [Test: child::tei:altIdentifier] Location: /TEI[1]/text[1]/body[1]/div[10]/div[10]/specGrp[1]/elementSpec[1]/exemplum[2]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/msDesc[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/msPart[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> > <WARNING>Schematron warning: WARNING: use of deprecated attribute — @degree of the precision element will be removed from the TEI on 2015-11-12. > [Test: @degree] Location: /TEI[1]/text[1]/body[1]/div[21]/div[1]/div[2]/div[4]/specGrp[1]/elementSpec[1]/exemplum[1]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/precision[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> > <WARNING>Schematron warning: WARNING: use of deprecated attribute — @degree of the precision element will be removed from the TEI on 2015-11-12. > [Test: @degree] Location: /TEI[1]/text[1]/body[1]/div[21]/div[1]/div[2]/div[4]/specGrp[1]/elementSpec[1]/exemplum[1]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/precision[namespace-uri()='http://www.tei-c.org/ns/Examples'][2]</WARNING> > <WARNING>Schematron warning: WARNING: use of deprecated attribute — @degree of the precision element will be removed from the TEI on 2015-11-12. > [Test: @degree] Location: /TEI[1]/text[1]/body[1]/div[21]/div[2]/p[5]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/precision[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> > <WARNING>Schematron warning: WARNING: use of deprecated attribute — @degree of the precision element will be removed from the TEI on 2015-11-12. > [Test: @degree] Location: /TEI[1]/text[1]/body[1]/div[21]/div[2]/p[5]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/precision[namespace-uri()='http://www.tei-c.org/ns/Examples'][2]</WARNING> > <WARNING>Schematron warning: WARNING: use of deprecated attribute — @degree of the precision element will be removed from the TEI on 2015-11-12. > [Test: @degree] Location: /TEI[1]/text[1]/body[1]/div[21]/div[2]/p[6]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/residence[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/precision[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> > <WARNING>Schematron warning: WARNING: use of deprecated attribute — @degree of the precision element will be removed from the TEI on 2015-11-12. > [Test: @degree] Location: /TEI[1]/text[1]/body[1]/div[21]/div[2]/p[7]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/precision[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> make: *** [valid] Error 1 Build step 'Execute shell' marked build as failure Not sending mail to unregistered user ron.vandenbranden(a)kantl.be

1 4

how to add values to a list
by Syd Bauman 01 Sep '17

01 Sep '17

I want my customization to add a few possible values to the list P5 provides for a semi-closed attribute list. E.g., the @type of <idno>. P5 says it has "ISBN", "ISSN", "DOI", "URI", "VIAF", "ESTC", and "OCLC". We'd like our customization to add "LC" and "LCCN" to that list. None of the expected combinations of values of @mode ("add" and "change") that I've tried have worked. Two of the more obvious combinations: --------- A --------- <elementSpec module="header" ident="idno" mode="change"> <gloss>JUST A TEST GLOSS to make sure <val>change</val> is working</gloss> <attList> <attDef ident="type" mode="change"> <valList type="semi"> <valItem ident="LC" mode="add"> <gloss>U.S. Library of Congress call number</gloss> </valItem> <valItem ident="LCCN" mode="add"> <gloss>Library of Congress control number</gloss> </valItem> </valList> </attDef> </attList> </elementSpec> --------- B --------- Same, but added @mode of "add" to <valList> For (A), nothing was added -- the list I ended up with was the same as P5. For (B) the 2 new values replaced the existing ones, so I had only those, and none of the 7 from P5. Any thoughts?

2 2