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

Pre-release
by Hugh Cayless 19 Feb '16

19 Feb '16

Hi All, In advance of next Thursday’s meeting, I’ve been doing some work on tickets, mainly moving fixed, closed tickets into the 3.0.0 milestone (https://github.com/TEIC/TEI/milestones/Guidelines-3.0.0 <https://github.com/TEIC/TEI/milestones/Guidelines-3.0.0>). This looks like a really good way to easily point to what’s been done for a given release! I’ve created a 3.1.0 milestone we can use to capture work that happens towards the following release. I think in the future that as soon as we mark a ticket "Go", we should also give it a milestone. We have 38 tickets in a Green state (https://github.com/TEIC/TEI/issues?q=is%3Aopen+is%3Aissue+label%3A%22Status… <https://github.com/TEIC/TEI/issues?q=is:open+is:issue+label:%22Status:+Go%22>), meaning there should be no obstacles to their implementation. Can I ask you all to have a look through these and ask a) is this really Green? Does it need more discussion or is it blocked? b) if it’s assigned to you, can you do it, or do you need to hand it off? c) If you’re not assigned a ticket, but think you could do it and are sufficiently bored, can you take it over? It would be nice if we could get at least some of these into 3.0.0. Some of them have been around an awful long time. On Thursday, we need to decide if we’re ready to "freeze" for the release, when that release will be, and who will be the release technician. This will be only our second release from GitHub, and the first under our new repo organization scheme, so we’re essentially doing this for the first time. Git Flow, which we’re emulating, recommends something like the following as a release procedure: 1) Create a release branch - Changes made during the run-up to release should be made here, then merged back into dev - Given this separation, there should be no need for an actual freeze on dev, but no big changes should be merged into release. 2) Merge the release branch into master 3) Push master to GitHub. Ideally, this would trigger a test process, à la https://github.com/TEIC/TEI/issues/1411 <https://github.com/TEIC/TEI/issues/1411>, which is not in place yet 4) Assuming tests pass, tag the release 5) Post release, the release branch can be merged into dev and removed. From there on, more or less as in http://www.tei-c.org/Activities/Council/Working/tcw22.xml <http://www.tei-c.org/Activities/Council/Working/tcw22.xml>, which needs some work (which itself is a problem due to the brokenness of the TEI website CMS). Thoughts?

1 0

Build failed in Jenkins: TEIP5-Test #2762
by Victoria TEI Jenkins 19 Feb '16

19 Feb '16

See <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test/2762/changes> Changes: [stefanie.gehrke] rephrasing and addition of a `<gi>` element close #1310 [stefanie.gehrke] addition of msFrag in manuscriptDescription, msDesc, msFrag, msPart [stefanie.gehrke] added msFrag in //specList/specDesc etc. and replaced Amiens BM exemple [stefanie.gehrke] <origin> deleted inside msFrag [martindholmes] Minor edits to the new prose added by Stefanie on issue [stefanie.gehrke] added Peters example from the Weber-Gesamtausgabe to msFrag.xml [stefanie.gehrke] some changes in the prose (english and frensh) [philomousos] Content model fixes. ------------------------------------------ Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Building in workspace <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test/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 -c core.askpass=true 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 bf360896d19bea68c2a79551f57873d62efc35be (refs/remotes/origin/dev) > git config core.sparsecheckout # timeout=10 > git checkout -f bf360896d19bea68c2a79551f57873d62efc35be > git rev-list 267926631ad4e5cdfc7c8da56cbb04e8f58ab2fd # timeout=10 [workspace] $ /bin/bash -xe /tmp/hudson3656605424350548654.sh + cd P5 ++ pwd + make VCS=git INJENKINS=true XSL=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test/ws/P5/../../../Stylesheets/la…> clean validate test (cd Exemplars; make clean) make[1]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test/ws/P5/Exemplars'> mv tei_lite_fr.nvdl tei_lite_fr.nvdl.bak rm -f *.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/ws/P5/Exemplars'> (cd Test; make clean) make[1]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test/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/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/ws/P5/../../../Stylesheets/la…> -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/ws/P5/../../../Stylesheets/la…> for XSL stylesheets [echo] Do ODD processing for p5odds.odd [echo] Do ODD processing for p5odds-examples.odd BUILD SUCCESSFUL Total time: 1 minute 12 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 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/ws/P5/../../../Stylesheets/la…> 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: 31 seconds <Messages> <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'][2]</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) sh graphics.sh BUILD: Check validity with nvdl, first examples with feasible validity, and then the valid ones ./run-onvdl p5.nvdl p5.xml /usr/bin/onvdl <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test/ws/P5/p5.xml>:67929:7: error: element "note" from namespace "http://www.tei-c.org/ns/Examples" not allowed in this context <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test/ws/P5/p5.xml>:67998:31: error: element "note" from namespace "http://www.tei-c.org/ns/Examples" not allowed in this context <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test/ws/P5/p5.xml>:67929:7: error: element "note" from namespace "http://www.tei-c.org/ns/Examples" not allowed in this context <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test/ws/P5/p5.xml>:67998:31: error: element "note" from namespace "http://www.tei-c.org/ns/Examples" not allowed in this context Error: nvdl run found problems make: *** [valid] Error 1 Build step 'Execute shell' marked build as failure

1 1

msFrag
by Hugh Cayless 18 Feb '16

18 Feb '16

Hi All, I'm about to merge the msFrag branch and I'm looking at content models. I seem to remember, but can't find in the minutes, that we thought msPart and msFrag were mutually exclusive. I.e., you wouldn't want to use them together. I can *imagine* a scenario in which I might, but I'm thinking that absent a request for it, we should start conservatively and say you can either have 0-∞ msParts of 0-∞ msFrags, but not both. What do you all think?

2 3

Dear Jenkins maintainers
by Hugh Cayless 18 Feb '16

18 Feb '16

I added a warning message to the transformtei script that tells you if you haven't set a local source, meaning it will download the last released one. This is usually fine, but at times, and particularly now, when our last release doesn't use Pure ODD, it can mean spurious bugs appear. Jenkins doesn't like warnings it hasn't been told about, so I added a rule: https://github.com/TEIC/TEI/commit/267926631ad4e5cdfc7c8da56cbb04e8f58ab2fd This change will need to be applied to Jenkins so that future builds are stable. Thanks, Hugh

1 0

dataRef attr descriptions
by Syd Bauman 18 Feb '16

18 Feb '16

The description of dataRef/@key is "the identifier used for this datatype specification". This is confusing, if not outright nuts: the identifier used for this particular data reference element would be specified on @xml:id. I'm of a mind that the three "what I'm referring to" attributes should have parallel descriptions. Something like: key = The datatype being referred to from the set of provided or custom TEI datatypes, indicated by its identifier (e.g., "teidata.language") name = The datatype being referred to from the datatypes found in _XML Schemas: Part 2: Datatypes_, indicated by its name (e.g., "gYear") ref = The datatype being referred to in an external datatype library, indicated by a URI although I'm sure those can be improved upon. Meanwhile I've discovered that the dataRef.xml/elementSpec/listRef/ptr/@target pointed to the wrong section, and that in that file @ref was defined as a name, not a URI. I have fixed these corrigible errors, but did not want to muck with the wording on my own.

2 1

@restriction doesn't make it to documentation
by Syd Bauman 18 Feb '16

18 Feb '16

Apologies if this has been pointed out before, I'm a bit behind on PureODD. I just realized that although the pattern specified on @restriction of <dataRef> makes it into the .rnc file (and .rng, and I presume .xsd although I couldn't care less), it does not make it into the HTML customized documentation file.

2 1

need input on ticket 1331, dating attributes
by Syd Bauman 15 Feb '16

15 Feb '16

[Insert pun about the attributes required to get a ticket for a medieval match.com here.] [New folks -- e-mail from me should almost always be read with a fixed-width or monospaced font. This one is no exception.] For ticket 1331 (https://github.com/TEIC/TEI/issues/1331) I'm supposed to jigger the prose a bit, and develop a table of the semantics of the various combinations of @from, @to, @notBefore, and @notAfter. I've gotten a very good start on this, but am running into trouble with the table, and am seeking help and advice. Issues, in rough order of importance: 1. There are two combinations of these attributes that I don't know what to do with. As far as I'm concerned, it makes no sense to use the pairs @from & @notBefore or @to & @notAfter. That said, some *might* argue that using three of the four (either @from with @notBefore & @notAfter, or @to with @notBefore & @notAfter) does make sense. (Specifying a duration that starts at @from and ends sometime in the range specified by the other two, or that ends at 3A@to and starts sometime in the range specified by the other two.) So: a) What should I put for the makes-no-sense pairs? b) Should I be writing prose to support the ( (@from|@to), @notBefore, @notAfter ) encoding? Or is that too wild? Or is there some other interpretation we should be considering? 2. Since order of attribute specification is inconsequential, and an attribute may only be specified once, making a full 4x4 table of these attributes results in 4 cells that make no sense because they are for the same attribute twice, and each of the other unique 6 cells is duplicated (for a total of 16 cells). A B C D A XX ba ca da B ba XX cb db C ca cb XX dc D da db dc XX Should we display all 16 cells? Or make an abbreviated chart, e.g.: A B C D A XX -- -- -- B ba XX -- -- C ca cb XX -- D da db dc XX Or, noting that in the above chart row A and column D are useless, make a truncated chart, e.g.: A B C B ba XX -- C ca cb XX D da db dc If you look at the draft of the chapter I have at the moment (http://paramedic.wwp.neu.edu/~syd/temp/TEI_Council/html/ND.html#NDATTSda) you'll see that there several (ugly) versions of this table. Which one should we use? 3. The default HTML styling of <table>, <tr>, and <td> is not good for this purpose, and I see no easy way to special-case this. (Putting @style on <td>, and maybe <tr>, does not work; the attribute does not get propagated to the HTML.) Does anyone know of a way around this, or already know where in the Stylesheets I should be working to get @style working? If you take a look at http://paramedic.wwp.neu.edu/~syd/temp/TEI_Council/test-table-of-attrs-layo…, you'll see a set of tables closer to what I think they should look like.

3 2

versions
by Lou Burnard 13 Feb '16

13 Feb '16

I've been asked to run a workshop on ODD at the Ecole Nationale des Chartes at the start of March, and I'd like to use the latest version of pure ODD, plus Stylesheets that process it. So, remind me chaps, what do I need to do to ensure that workshop participants get the right stuff installed in their oxygens? Or will we really have a release 2.9 out before then? (My workshop is on the 3rd, so this is cutting it fine in any case...)

1 0

odd reminder
by Lou Burnard 09 Feb '16

09 Feb '16

I haven't heard from anyone since I asked Council members to check that their existing ODDs continue to work as expected using the lb42-pureodd branch. So maybe no Council members actually have any ODDs to check, or maybe those who do have all checked and have nothing to report, or maybe they just haven't got round to it yet. I don't know, but just in case it's the 3rd possibility, please could I urge you to give it a go this weekend? If you prefer, you could just bung me a copy of the ODD and I'll test it for you! Why the pressure? Well, mostly that I've just been reminded that we're aiming for a pre-release freeze for the end of the current month, and I'm going to be buried in the French countryside with only intermittent net access until then.

7 20

Re: [tei-council] Testing Pure ODD
by James Cummings 09 Feb '16

09 Feb '16

Well, as I said, mostly this was very very simple relaxng content models in any case. I might mock up some more complex ODD doing something bizarre with datatypes.... when I get some time. -James On 09/02/16 11:41, Lou Burnard wrote: > Thanks James.. V encouraging! > > Sent from my Honor Mobile > > -------- Original Message -------- > Subject: [tei-council] Testing Pure ODD > From: James Cummings > To: TEI Council > CC: > > Hi Lou and Council, > > I've been looking around for a TEI ODD file where I redefined > content models. Mostly I just add/delete > elements/attributes/classes which isn't really changing. Finally > remembered I had changed some content models in my tei_corset > ODD. This was a mass-digitisation ODD for the Stationers' > Register project where the keying company was willing to use any > XML schema but would charge per kilobyte of output. So I renamed > everything to be shorter names, etc. in a tei_corset namespace > which over a lot of text input saved us money and was easy to > convert back. > > Where I used any relax ng in this it was fairly minimal and the > conversion able to be done automatically with no problems: > > a) to rename <TEI> to be <file> and say that its content model > was just <teiHeader> and <body> (both renamed elsewhere) > Old ODD: > https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… > Pure ODD: > https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… > This just changes to two <elementRef>s. > > b) to rename <teiHeader> to be <header> and give it a content > model of <title> followed by zero or more model.pLike > Old ODD: > https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… > Pure ODD: > https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… > This just changes to an <elementRef> followed by a <classRef> > > c) for various reasons some empty elements were changed to allow > text content. For example <gap> was renamed <gp> and had a > content of <rng:text> > Old ODD: > https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… > Pure > ODD:https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_c… > <rng:text> just becomes <textNode/> > > d) exactly the same thing for <space> renamed <spc>: > Old ODD: > https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… > Pure ODD: > https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… > > > The resulting schema validates against the files I had. I did > have to change some other things in the ODD, but these had to do > with the moving of rendition things into att.global.rendition > from att.global. (Since this ODD was 3 or 4 years old.) > > I converted the Pure ODD to HTML and everything worked as expected. > > Clearly not an exhaustive test of all of the functionality of > Pure ODD, but just another confirmation that migrating to Pure > ODD is able to be semi-automated and for most people's low > hanging fruit doesn't introduce any major problems. > > -James > > > -- > Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT > Services, University of Oxford > -- > 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 -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford

2 1

Testing Pure ODD
by James Cummings 09 Feb '16

09 Feb '16

Hi Lou and Council, I've been looking around for a TEI ODD file where I redefined content models. Mostly I just add/delete elements/attributes/classes which isn't really changing. Finally remembered I had changed some content models in my tei_corset ODD. This was a mass-digitisation ODD for the Stationers' Register project where the keying company was willing to use any XML schema but would charge per kilobyte of output. So I renamed everything to be shorter names, etc. in a tei_corset namespace which over a lot of text input saved us money and was easy to convert back. Where I used any relax ng in this it was fairly minimal and the conversion able to be done automatically with no problems: a) to rename <TEI> to be <file> and say that its content model was just <teiHeader> and <body> (both renamed elsewhere) Old ODD: https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… Pure ODD: https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… This just changes to two <elementRef>s. b) to rename <teiHeader> to be <header> and give it a content model of <title> followed by zero or more model.pLike Old ODD: https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… Pure ODD: https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… This just changes to an <elementRef> followed by a <classRef> c) for various reasons some empty elements were changed to allow text content. For example <gap> was renamed <gp> and had a content of <rng:text> Old ODD: https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… Pure ODD:https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_c… <rng:text> just becomes <textNode/> d) exactly the same thing for <space> renamed <spc>: Old ODD: https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… Pure ODD: https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… The resulting schema validates against the files I had. I did have to change some other things in the ODD, but these had to do with the moving of rendition things into att.global.rendition from att.global. (Since this ODD was 3 or 4 years old.) I converted the Pure ODD to HTML and everything worked as expected. Clearly not an exhaustive test of all of the functionality of Pure ODD, but just another confirmation that migrating to Pure ODD is able to be semi-automated and for most people's low hanging fruit doesn't introduce any major problems. -James -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford

2 1

Roma eXist-db down?
by Peter Stadler 08 Feb '16

08 Feb '16

Dear all, at present, I can’t access Roma (I may enter the first pages but Roma is unable to fetch module information etc.) and it seems the eXist-db is down. Looking in the logs at /var/www/vhosts/tei-c.org/opencms_tomcat/lv1/local/tomcat_6.0.14_teicms/webapps/exist/WEB-INF/logs/exist.log states: 2016-02-08 07:01:18,941 [main] INFO (BrokerPool.java [shutdown]:1495) - shutdown complete ! 2016-02-08 07:23:49,589 [http-8040-9] INFO (XQueryServlet.java [init]:135) - form-encoding = UTF-8 2016-02-08 07:23:49,590 [http-8040-9] INFO (XQueryServlet.java [init]:139) - container-encoding = UTF-8 2016-02-08 07:23:49,590 [http-8040-9] INFO (XQueryServlet.java [init]:143) - encoding = UTF-8 2016-02-08 07:23:49,631 [http-8040-9] WARN (Descriptor.java [<init>]:96) - Giving up unable to read descriptor file from /descriptor.xml 2016-02-08 07:23:49,631 [http-8040-9] WARN (Descriptor.java [<init>]:115) - Giving up unable to read descriptor.xml file from classloader in package org.exist.http So, it looks as if the db was shutdown and failed to restart. Does anyone know any details and how to proceed? (I’m unfamiliar with eXist within Tomcat …) Best Peter

4 5

proc mod queries
by Lou Burnard 06 Feb '16

06 Feb '16

I've made a bit more progress on the "processing model" extensions to ODD proposed by the TEI Simpletons a while ago, and now have a version of P5 based on the current dev branch which includes them AND builds correctly. But I havent yet finished hacking the prose into shape, and I have some questions. Here's the first. The @output attribute "the intended output method" (that's clearly wrong though; surely it should be "the intended output target"?) is defined with a closed list of values "web", "print", and "plaintext". a) why is this a closed list? I can think of lots of other possible values e.g. "mobile device", "PDF", "text-to-speech synthesizer" for starters... b) what exactly does "plaintext" mean? And here's the zero'th. To whom if not the Council should I be addressing this query?

3 8

processing model use of CSS
by Lou Burnard 05 Feb '16

05 Feb '16

Decision please. The current description of the processing model tacitly assumes that CSS is used to express output rendition, and it's hard to see how else the job would be done, but the text of the Guidelines is rather vague on the topic. Should we say a) outputRendition *must* be expressed using CSS b) it is *recommended* that CSS be used c) we don't care what you use, but our examples assume you will use CSS If we choose b or c, we will presumably need to add some complexity to the scheme (e.g. to say what has been used instead if it's not CSS)

5 17

weird example
by Lou Burnard 05 Feb '16

05 Feb '16

The spec for <model> currently has a whole slew of examples, some of which need to go elsewhere I think. And one or two of them are entirely mysterious. This one for example: <exemplum xml:lang="en"> <egXML xmlns="http://www.tei-c.org/ns/Examples"> <model predicate="parent::choice and count(parent::*/*) gt 1" behaviour="omit"/> </egXML> </exemplum> Can someone please explain to me what this is meant to achieve? It seems to be saying "if my parent is <choice> and any of my parents has more than one child node, then suppress me". In the immortal words of Manuel, che?

3 4

outputRendition spec
by Lou Burnard 05 Feb '16

05 Feb '16

The <remarks> for this element currently read: "<p>The <gi>outputRendition</gi> element differs from the <gi>rendition</gi> element describes rendering information in one or more possible outputs, usually recorded in the TEI customization file, the latter must only be used to document the original rendition of the source text.</p>" - As far as I know <outputRendition> can only appear inside an ODD file, so why "usually" ? - If @useSourceRendition is true, then the <rendition> element *will* affect the output. I'm proposing the following revision: <p>This component of an element specification describes the rendering or appearance intended for all occurrences of the element in a specified context for a specified type of output. The <rendition> element, by contrast, describes the actual rendering or appearance of all occurrences of the specified element in a source document. The <att>useSourceRendition</att> attribute may however be used to indicate that formatting information provided by a <gi>rendition</gi> element is to be combined with any provided by an <gi>outputRendition</gi> element.</p> <p>It is strongly recommended that the W3C Cascading Stylesheet language (CSS2 or later) be used to express the required formatting information.</p> (The second paragraph modulo whatever we decide to do about the CSS or what debate)

3 2

Proofreading processing model rewrite
by James Cummings 28 Jan '16

28 Jan '16

I'd like to thank Lou again for the rewrite of the draft section for TD that I'd done in the processing-model branch -- it is a substantial rewrite. This is at http://teic.github.io/TEI/TD.html#TDPM or if you prefer the xml https://github.com/TEIC/TEI/blob/lb42-procmod/P5/Source/Guidelines/en/TD-Do… I've given the chapter a quick skim read and my initial suggestions/thoughts are: "22.4.4.4 Processing Models" Should processing models section be a new 22.4.5? It is longer an more substantial than some of its siblings at this level. " In the present implementation, rendition is expressed using the W3C Cascading Stylesheet Language (CSS)" In which implementation? This may be confusing, perhaps just the second half of that sentence? "The intent is that these should be presented in an italic font as inline elements:" maybe: "The intent is that these elements should be presented inline in an italic font" (i.e. They may not be being processed into 'elements', that may be mistaken as suggesting this is only for HTML output or something.) You are right that at the bottom of the Output Rendition section we could say something about 'Why CSS', but this is for the same reason that we suggest elsewhere inside the <rendition> element as a formally declared stylesheet language. This might suggest that we should be having a @scheme attribute like <rendition> with css as a value? In Implementation: "If the useSourceRendition attribute on the model has the value false then any rendition attribute on the source element can be ignored; otherwise its value must be combined with that given in the outputRendition element, if any." Maybe reverse this since it might contradict what was said above in the bit on useSourceRendition? So: "If the @useSourceRendition attribute on the model has the value true then any rendition attribute in the source element must be combined with any given in the outputRendition element, otherwise all rendition attributes in the source should be ignored." -James -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford "

4 10

screwy example (was "Re: [TEI] <lg> and <gap> (#1419)")
by Syd Bauman 25 Jan '16

25 Jan '16

Re: the 4th example in section 3.12.1, "Core Tags for Verse"[1] See file TEI/P5/Source/Guidelines/en/CO-CoreElements.xml and search for "#CO-eg-07". The example doesn't seem to exemplify what the prose is talking about at all. Looks to me like the <stage> is supposed to be a sibling of the <l>s, in between the last two. (Otherwise, the @part attributes are not needed, the last two <l> elements could just be one <l> with a <stage> inside. Which, BTW, is a less-than-optimal encoding in this case, because the stage direction doesn't scan. :-) This seems to me to be a corrigible error, which I have just fixed on my home desktop, but don't plan to push for awhile in case someone wants to object. Notes ----- [1] http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COVE

1 0

Links for this morning's call
by Hugh Cayless 25 Jan '16

25 Jan '16

Agenda: https://docs.google.com/document/d/1sJgb6aQVJUTs0ENyRSIMfZODtrhXeOSyKoPYrM0… Hangout: https://hangouts.google.com/call/hpffrckgslsfz425fyzfby256ia Phone numbers are in the Agenda if you can’t connect to the Hangout.

1 0

Pure ODD
by Hugh Cayless 25 Jan '16

25 Jan '16

Dear All, Now that Lou’s tremendous work on Pure ODD has been merged into dev, we should try to give it a thorough workout. I’ve regenerated the "bleeding edge" Guidelines at http://teic.github.io/TEI/index.html <http://teic.github.io/TEI/index.html>. It would be extremely helpful if you can take the time to look it over for problems and report them as issues. I’ve experimented in that build with rearranging the order in which things are displayed. See, e.g. http://teic.github.io/TEI/ref-witDetail.html <http://teic.github.io/TEI/ref-witDetail.html>. Your reactions (whether positive or not) will be most welcome!

3 3

Chair Elections
by Hugh Cayless 25 Jan '16

25 Jan '16

Dear All, No-one has contacted me about running for chair, and I don’t believe anyone has expressed their willingness to run on-list either. Please correct me if I’m wrong! As I said in our last meeting, I’m willing to serve for another year, particularly if nobody else wants to do it, but I’d encourage you to think about it (for next year even if not this one). I may not even be on Council next year, as my term will be up at year’s end! It’s really not that bad a job, I promise :-). If anyone has questions about it, even if you’d rather wait until next year, do feel free to ask me or James (who was Chair before me) about it. Note that the deliberately vague guidelines for Chair Elections are posted here: http://wiki.tei-c.org/index.php/TEI-Council-FAQ#How_is_the_TEI_Technical_Co… <http://wiki.tei-c.org/index.php/TEI-Council-FAQ#How_is_the_TEI_Technical_Co…> —it’s one of those things I’ve never done before as Chair, and so have gotten it somewhat wrong, but I don’t want to sneak back into the position, so I’ll issue a last call for self-nominations now. My own reasons for wanting to continue are: 1) I think I sort of have it figured out now 2) My job at Duke will allow me to devote the time needed to it 3) I’d like to think things will be easier this year If anyone objects or wants to stand, then we’ll set up an election. All the best, and wishing you all a happy new year, Hugh

6 16

revised TD for procmod
by Lou Burnard 24 Jan '16

24 Jan '16

I've now made a new branch in the repo for my revised version of TD containing the processing model documentation. Some way to go yet, notably in the element specs which still seem occasionally too vague to me, and test files are still missing. But I'd appreciate some reassurance that I haven't totally misunderstood something crucial. The branch is called lb42-procmod and is based on dev as of last night

1 0

modest proposal for simplifying procmod
by Lou Burnard 23 Jan '16

23 Jan '16

The <param> element currently declares its content to be "macro.xpath" -- i.e. it can contain only an XPath. It would be a lot easier to enforce this constraint if the content were supplied as an attribute, e.g. "value" so, eg, instead of <param name="foo">@bar</param> <param name="default">corr</param> <param name="lang">ancestor::*/@xml:lang</param> <param name="place">'foot'</param> I suggest <param name="foo" value="@bar"/> <param name="default" value="corr"/> <param name="lang" value="ancestor::*/@xml:lang"/> <param name="place" value="'foot'"/> Anyone got strong feelings against this change? The @place example looks a bit dodgy, but otherwise it seems a fairly benign enhancement.

5 11

Teleconference 2015-01 - Invitation to edit
by Hugh Cayless (via Google Docs) 20 Jan '16

20 Jan '16

I've shared an item with you: Teleconference 2015-01 https://docs.google.com/document/d/1sJgb6aQVJUTs0ENyRSIMfZODtrhXeOSyKoPYrM0… It's not an attachment -- it's stored online. To open this item, just click the link above. A draft agenda for our meeting on the 25th at 09:00 EST / 14:00 GMT / 15:00 CET is available at https://docs.google.com/document/d/1sJgb6aQVJUTs0ENyRSIMfZODtrhXeOSyKoPYrM0… Please feel free to add agenda items if there's additional stuff you want to talk about.

1 0

Re: [tei-council] Scheduling
by Elisa Beshero-Bondar 11 Jan '16

11 Jan '16

Hi everyone! I was just looking at the Doodle poll for the January Telco, and I saw that on Mon. 1/25 at 9AM EST I'm the only one preventing a meeting of all of us. I changed that to tentatively Yes, though it's awkward for me because I'm heading it to teach my DH class at 10:30 AM. I could go in early to campus to do the telco from my office, which would mean I wouldn't have to bolt from my house before 10am to get to school on time. M W F mornings aren't great for me this semester because they're my heavy teaching days, but I can do the "if need be" option for this one! On the whole I'd be happiest to meet on a weekend. Thanks, and hope this helps! Elisa On Fri, Jan 8, 2016 at 10:33 AM, Mylonas, Elli <elli_mylonas(a)brown.edu> wrote: > I'm fairly flexible both earlier and later. There are some standing > meetings I have to work around. --elli > > [Elli Mylonas > Senior Digital Humanities Librarian > and > Center for Digital Scholarship > University Library > Brown University > library.brown.edu/cds] > > On Fri, Jan 8, 2016 at 5:20 AM, James Cummings <James.Cummings(a)it.ox.ac.uk > > > wrote: > > > Hi all, > > > > In case it helps I'm flexible outside usual work hours so wouldn't have > > any problem with doing telco meetings in evenings or on weekends, but > > suspect there are others that this would not work for. > > > > -James > > > > > > On 08/01/16 01:54, Syd Bauman wrote: > > > >> I don't see more slots in the poll for this months telcon[1], but for > >> the most part (barring an early morning run) could make 08:00 ET or > >> afternoon ET work. (Mon, Tue, Fri much better than Wed, Thu.) > >> > >> I've filled in the added slots on the face-to-face poll.[2] > >> > >> In case folks are having trouble finding it, the monthly telcon poll > >> is at [3]. > >> > >> Notes > >> ----- > >> [1] http://doodle.com/poll/h9c4wu85pqqvbcbe > >> [2] http://doodle.com/poll/cd9n3d47e5ezfkit > >> [3] http://doodle.com/poll/d3nyte4wuiiqt9r4 > >> > > > > > > -- > > Dr James Cummings, James.Cummings(a)it.ox.ac.uk > > Academic IT Services, University of Oxford > > > > > > -- > > 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 > -- Elisa Beshero-Bondar, PhD 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

4 3