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

deprecation & release timing: 1737
by Syd Bauman 24 Apr '18

24 Apr '18

For issue 1737 we agreed last face-to-face to remove macroSpec/@type on 2018-10-01 (the same date we are removing all the data.* macros, I guess). I have just put the @validUntil on to make that happen. But the timing concerns me a little -- when is our next release going to be? Unless it is this month, people will have < 5 months to see the red health warning. BTW, we've agreed to deprecate data.* on 2018-10-01, but who is doing that and is there an issue open for it? (I have this nagging feeling all of a sudden that it's me. :-)

2 1

gitQuestion
by Syd Bauman 21 Apr '18

21 Apr '18

I'm looking at Piotr's pull request #1665. There are like 100 commits in 4 different files. (Well, actually only 61 commits.) Is there any (relatively) easy way for me to check out or otherwise create a copy of P5 with those commits applied, so I can just try building the Guidelines locally with Piotr's changes, and look at and test the result? I suppose I want to do something like merge his pull request into a local copy of mine, rather than into GitHub.

2 1

Workshop@TEI conference
by Scholger, Martina (martina.scholger＠uni-graz.at) 17 Apr '18

17 Apr '18

Dear all, in light of the extension of the CFP until friday, I'd like to come back to our idea of proposing a TEI intro/update workshop for Tokyo. Did anyone already submit a TEI workshop? If not, do we want to do a workshop together? Best wishes, Martina

7 13

Re: [tei-council] RomaJS poster
by James Cummings 10 Apr '18

10 Apr '18

Didn't comment on this before submission, but of course I'm happy with this. Raff deserves all the credit, but I see the usefulness of mentioning Council. I don't think the Programming Committee would reasonably object, would it? (Though I strongly disagree with any sentiment that corporations can be people!) 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: 09 April 2018 20:43:47 To: tei-council(a)lists.tei-c.org Subject: Re: [tei-council] RomaJS poster Ok, cool! We may be setting an interesting precedent. I'll submit it that way, we'll see what the PC says. Raff On Mon, Apr 9, 2018 at 1:19 PM, Elisa <ebbondar(a)gmail.com> wrote: > Agreed—to incorporation into a Collective Org. > > 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 | Development site: http://newtfire.org > > Typeset by hand on my iPad > > > On Apr 9, 2018, at 11:21 AM, Hugh Cayless <philomousos(a)gmail.com> wrote: > > > > I like that idea. > > > > On Mon, Apr 9, 2018 at 11:12 AM, Mylonas, Elli <elli_mylonas(a)brown.edu> > > wrote: > > > >> perhaps it can go in as Raff and the TEI Council, instead of Raf and 10 > >> other people. --elli > >> > >> [Elli Mylonas > >> Director, Center for Digital Scholarship > >> University Library > >> Brown University > >> library.brown.edu/cds] > >> > >> On Mon, Apr 9, 2018 at 10:37 AM, Hugh Cayless <philomousos(a)gmail.com> > >> wrote: > >> > >>> I think that's fair. And that we can make sure Raff gets proper credit > >>> while we all support the effort. > >>> > >>> Hugh > >>> > >>> On Mon, Apr 9, 2018 at 10:05 AM, Raffaele Viglianti < > >>> raffaeleviglianti(a)gmail.com> wrote: > >>> > >>>> Hi everyone, > >>>> > >>>> Thank you for the feedback! Ok, I'll go solo. Overall, I'm keen on > >>>> portraying this as a concerted TEI council effort overall, because the > >>> more > >>>> it is decoupled from me as an individual, the more likely it is to be > >>>> associated with council and as something that the council as a body > >>>> maintains into the future (as opposed to me alone). > >>>> > >>>> Best, > >>>> Raff > >>>> > >>>> On Mon, Apr 9, 2018 at 8:16 AM, Scholger, Martina ( > >>>> martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at> wrote: > >>>> > >>>>> Hi Raff! > >>>>> > >>>>> I totally agree with Peter and I like the proposal. > >>>>> > >>>>> Martina > >>>>> > >>>>> -----Ursprüngliche Nachricht----- > >>>>> Von: tei-council-bounces(a)lists.tei-c.org <tei-council-bounces@lists. > >>>>> tei-c.org> Im Auftrag von Mylonas, Elli > >>>>> Gesendet: Montag, 9. April 2018 01:37 > >>>>> An: tei-council(a)lists.tei-c.org > >>>>> Betreff: Re: [tei-council] RomaJS poster > >>>>> > >>>>> Although happy to the actual poster if that would help. --elli > >>>>> > >>>>> [Elli Mylonas > >>>>> Director, Center for Digital Scholarship University Library Brown > >>>>> University library.brown.edu/cds] > >>>>> > >>>>> On Sun, Apr 8, 2018 at 7:07 PM, Mylonas, Elli < > >> elli_mylonas(a)brown.edu> > >>>>> wrote: > >>>>> > >>>>>> Likewise. --elli > >>>>>> > >>>>>> [Elli Mylonas > >>>>>> Director, Center for Digital Scholarship University Library > >> Brown > >>>>>> University library.brown.edu/cds] > >>>>>> > >>>>>> On Sun, Apr 8, 2018 at 5:39 PM, Elisa Beshero-Bondar < > >> ebb8(a)pitt.edu> > >>>>>> wrote: > >>>>>> > >>>>>>> Yeah, I agree with Peter on this. We all advise you and comment, > >> but > >>>>>>> that's what we're *supposed* to do on Council anyway. I'm happy > >> for > >>>>>>> this to be your work solo. > >>>>>>> > >>>>>>> Elisa > >>>>>>> > >>>>>>> On Sun, Apr 8, 2018 at 3:25 PM, Peter Stadler <stadler(a)edirom.de> > >>>>> wrote: > >>>>>>> > >>>>>>>> Raff, > >>>>>>>> > >>>>>>>> it’s very generous that you want us all on the poster, but I > >>> really > >>>>>>> think > >>>>>>>> it’s your work! > >>>>>>>> (= no one ever committed to https://github.com/raffazizzi/ > >> romajs > >>>>>>>> except > >>>>>>>> you) > >>>>>>>> > >>>>>>>> And the poster design will probably your work, as well. So > >> credit > >>>>>>>> where credit is due! > >>>>>>>> > >>>>>>>> Just my 2p > >>>>>>>> Peter > >>>>>>>> > >>>>>>>>> Am 06.04.2018 um 20:54 schrieb Raffaele Viglianti < > >>>>>>>> raffaeleviglianti(a)gmail.com>: > >>>>>>>>> > >>>>>>>>> Dear all, > >>>>>>>>> > >>>>>>>>> As suggested at our last meeting, I prepared an abstract for a > >>>>>>>>> poster describing and demoing RomaJS. You can find and edit it > >>>> here: > >>>>>>>>> https://docs.google.com/document/d/1YIIAIPPy8mVR8UddgU8R- > >>>>>>>>> FuECzdAdD7P2L0eG3TRups/edit# > >>>>>>>>> > >>>>>>>>> Please provide feedback before monday April 9th if you can. > >> I've > >>>>>>>>> added > >>>>>>>> all > >>>>>>>>> of us as authors; feel free to update your title/affiliation. > >>>>>>> Technically > >>>>>>>>> each author should provide a short bio, so feel free to add > >>> that, > >>>>>>>>> but > >>>>>>>> keep > >>>>>>>>> in mind that the "authors" section cannot go over 500 words. > >>>>>>>>> > >>>>>>>>> Of the council members involved in RomaJS, Lou is the only one > >>>>>>>>> who currently isn't a member so I haven't included him. But > >>>>>>>>> perhaps I > >>>>>>> should, > >>>>>>>>> thoughts? > >>>>>>>>> > >>>>>>>>> Thanks! > >>>>>>>>> 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 > >>>>>>>> > >>>>>>>> > >>>>>>>> -- > >>>>>>>> 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 > >>>>>>> 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 <ebb8(a)pitt.edu> Development site: > >>>>>>> http://newtfire.org > >>>>>>> -- > >>>>>>> tei-council mailing list > >>>>>>> tei-council(a)lists.tei-c.org > >>>>>>> http://lists.lists.tei-c.org/mailman/listinfo/tei-council > >>>>>>> > >>>>>>> PLEASE NOTE: postings to this list are publicly archived > >>>>>>> > >>>>>> > >>>>>> > >>>>> -- > >>>>> tei-council mailing list > >>>>> tei-council(a)lists.tei-c.org > >>>>> http://lists.lists.tei-c.org/mailman/listinfo/tei-council > >>>>> > >>>>> PLEASE NOTE: postings to this list are publicly archived > >>>>> -- > >>>>> tei-council mailing list > >>>>> tei-council(a)lists.tei-c.org > >>>>> http://lists.lists.tei-c.org/mailman/listinfo/tei-council > >>>>> > >>>>> PLEASE NOTE: postings to this list are publicly archived > >>>>> > >>>> -- > >>>> tei-council mailing list > >>>> tei-council(a)lists.tei-c.org > >>>> http://lists.lists.tei-c.org/mailman/listinfo/tei-council > >>>> > >>>> PLEASE NOTE: postings to this list are publicly archived > >>>> > >>> -- > >>> tei-council mailing list > >>> tei-council(a)lists.tei-c.org > >>> http://lists.lists.tei-c.org/mailman/listinfo/tei-council > >>> > >>> PLEASE NOTE: postings to this list are publicly archived > >>> > >> -- > >> tei-council mailing list > >> tei-council(a)lists.tei-c.org > >> http://lists.lists.tei-c.org/mailman/listinfo/tei-council > >> > >> PLEASE NOTE: postings to this list are publicly archived > >> > > -- > > 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

RomaJS poster
by Raffaele Viglianti 09 Apr '18

09 Apr '18

Dear all, As suggested at our last meeting, I prepared an abstract for a poster describing and demoing RomaJS. You can find and edit it here: https://docs.google.com/document/d/1YIIAIPPy8mVR8UddgU8R- FuECzdAdD7P2L0eG3TRups/edit# Please provide feedback before monday April 9th if you can. I've added all of us as authors; feel free to update your title/affiliation. Technically each author should provide a short bio, so feel free to add that, but keep in mind that the "authors" section cannot go over 500 words. Of the council members involved in RomaJS, Lou is the only one who currently isn't a member so I haven't included him. But perhaps I should, thoughts? Thanks! Raff

7 12

Removing an inherited class (RomaJS and ODD processing)
by Raffaele Viglianti 04 Apr '18

04 Apr '18

Hi all, (this is based off a conversation James and I just had over the romajs slack channel) I'm implementing a button to remove an inherited attribute class form an element, for example removing att.global.responsibility from abbr, but keeping the other classes it inherits via att.global. I figured it would be enough to generate ODD like this: <elementSpec ident="abbr" mode="change"> <classes mode="change"> <memberOf key="att.global.rendition" mode="delete"/> </classes> </elementSpec> But it doesn't work because abbr is not a direct member of att.global.rendition. Should it work, though? If it did, it would certainly make roma's processing easier, otherwise it will have to generate something like the following, which is easier said than done: <elementSpec ident="abbr" mode="change"> <classes mode="change"> <memberOf key="att.global" mode="delete"/> <memberOf key="att.global.responsibility"/> <memberOf key="att.global.source"/> </classes> </elementSpec>. I appreciate your thoughts! If this sounds more like a bug / feature request I'm happy to move the conversation to a GitHub ticket. Also feel free to chime in on Slack. Ciao, Raff

1 0

Build failed in Jenkins: TEIP5-Test-dev #3539
by Victoria TEI Jenkins 03 Apr '18

03 Apr '18

See <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/3539/display/redirect?pag…> Changes: [elli_mylonas] adding @source attribute to egXML per #1476 ------------------------------------------ [...truncated 3.82 KB...] 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 BUILD FAILED <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/antbuilder.xml>:39: ; SystemID: <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Utilities/expand.xsl;> Line#: 68; Column#: 21 net.sf.saxon.trans.XPathException: org.xml.sax.SAXParseException; systemId: <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Source/Specs/acquis…;> lineNumber: 29; columnNumber: 8; The value of attribute "source" associated with an element type "egXML" must not contain the '<' character. at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:447) at net.sf.saxon.event.Sender.send(Sender.java:138) at net.sf.saxon.functions.DocumentFn.makeDoc(DocumentFn.java:326) at net.sf.saxon.functions.Doc.call(Doc.java:114) at net.sf.saxon.functions.Doc.call(Doc.java:24) at net.sf.saxon.expr.FunctionCall.iterate(FunctionCall.java:547) at net.sf.saxon.expr.Expression.evaluateItem(Expression.java:831) at net.sf.saxon.expr.SimpleStepExpression.iterate(SimpleStepExpression.java:113) at net.sf.saxon.value.Closure.iterate(Closure.java:156) at net.sf.saxon.expr.instruct.ApplyTemplates$ApplyTemplatesPackage.processLeavingTail(ApplyTemplates.java:550) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:432) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:295) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:248) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:337) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:415) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:347) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:502) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:295) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:248) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:337) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:415) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:347) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:502) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:295) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:248) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:337) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:415) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:347) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:502) at net.sf.saxon.expr.instruct.ApplyTemplates$ApplyTemplatesPackage.processLeavingTail(ApplyTemplates.java:553) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:432) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:295) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:248) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:337) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:415) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:347) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:502) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:295) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:248) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:337) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:415) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:347) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:502) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:295) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:248) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:337) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:415) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:347) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:502) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:295) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:248) at net.sf.saxon.expr.instruct.DocumentInstr.evaluateItem(DocumentInstr.java:302) at net.sf.saxon.expr.instruct.DocumentInstr.evaluateItem(DocumentInstr.java:50) at net.sf.saxon.expr.parser.ExpressionTool.evaluate(ExpressionTool.java:325) at net.sf.saxon.expr.LetExpression.eval(LetExpression.java:509) at net.sf.saxon.expr.LetExpression.processLeavingTail(LetExpression.java:690) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:347) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:502) at net.sf.saxon.Controller.transformDocument(Controller.java:2402) at net.sf.saxon.Controller.transform(Controller.java:1970) at net.sf.saxon.s9api.XsltTransformer.transform(XsltTransformer.java:596) at net.sf.saxon.jaxp.TransformerImpl.transform(TransformerImpl.java:73) at org.apache.tools.ant.taskdefs.optional.TraXLiaison.transform(TraXLiaison.java:195) at org.apache.tools.ant.taskdefs.XSLTProcess.process(XSLTProcess.java:876) at org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:414) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:435) at org.apache.tools.ant.Target.performTasks(Target.java:456) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) at org.apache.tools.ant.Project.executeTarget(Project.java:1364) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1248) at org.apache.tools.ant.Main.runBuild(Main.java:851) at org.apache.tools.ant.Main.startAnt(Main.java:235) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109) Caused by: org.xml.sax.SAXParseException; systemId: <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Source/Specs/acquis…;> lineNumber: 29; columnNumber: 8; The value of attribute "source" associated with an element type "egXML" must not contain the '<' character. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source) at org.apache.xerces.impl.XMLScanner.scanAttributeValue(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanAttribute(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:427) ... 81 more --------- org.xml.sax.SAXParseException; systemId: <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Source/Specs/acquis…;> lineNumber: 29; columnNumber: 8; The value of attribute "source" associated with an element type "egXML" must not contain the '<' character. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source) at org.apache.xerces.impl.XMLScanner.scanAttributeValue(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanAttribute(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:427) at net.sf.saxon.event.Sender.send(Sender.java:138) at net.sf.saxon.functions.DocumentFn.makeDoc(DocumentFn.java:326) at net.sf.saxon.functions.Doc.call(Doc.java:114) at net.sf.saxon.functions.Doc.call(Doc.java:24) at net.sf.saxon.expr.FunctionCall.iterate(FunctionCall.java:547) at net.sf.saxon.expr.Expression.evaluateItem(Expression.java:831) at net.sf.saxon.expr.SimpleStepExpression.iterate(SimpleStepExpression.java:113) at net.sf.saxon.value.Closure.iterate(Closure.java:156) at net.sf.saxon.expr.instruct.ApplyTemplates$ApplyTemplatesPackage.processLeavingTail(ApplyTemplates.java:550) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:432) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:295) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:248) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:337) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:415) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:347) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:502) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:295) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:248) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:337) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:415) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:347) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:502) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:295) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:248) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:337) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:415) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:347) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:502) at net.sf.saxon.expr.instruct.ApplyTemplates$ApplyTemplatesPackage.processLeavingTail(ApplyTemplates.java:553) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:432) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:295) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:248) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:337) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:415) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:347) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:502) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:295) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:248) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:337) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:415) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:347) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:502) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:295) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:248) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:337) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:415) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:347) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:502) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:295) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:248) at net.sf.saxon.expr.instruct.DocumentInstr.evaluateItem(DocumentInstr.java:302) at net.sf.saxon.expr.instruct.DocumentInstr.evaluateItem(DocumentInstr.java:50) at net.sf.saxon.expr.parser.ExpressionTool.evaluate(ExpressionTool.java:325) at net.sf.saxon.expr.LetExpression.eval(LetExpression.java:509) at net.sf.saxon.expr.LetExpression.processLeavingTail(LetExpression.java:690) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:347) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:502) at net.sf.saxon.Controller.transformDocument(Controller.java:2402) at net.sf.saxon.Controller.transform(Controller.java:1970) at net.sf.saxon.s9api.XsltTransformer.transform(XsltTransformer.java:596) at net.sf.saxon.jaxp.TransformerImpl.transform(TransformerImpl.java:73) at org.apache.tools.ant.taskdefs.optional.TraXLiaison.transform(TraXLiaison.java:195) at org.apache.tools.ant.taskdefs.XSLTProcess.process(XSLTProcess.java:876) at org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:414) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:435) at org.apache.tools.ant.Target.performTasks(Target.java:456) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) at org.apache.tools.ant.Project.executeTarget(Project.java:1364) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1248) at org.apache.tools.ant.Main.runBuild(Main.java:851) at org.apache.tools.ant.Main.startAnt(Main.java:235) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109) Total time: 5 seconds make: *** [p5.xml] Error 1 Build step 'Execute shell' marked build as failure Not sending mail to unregistered user elli_mylonas(a)brown.edu

1 1

Stylesheets group meeting, Tue 03 Apr 18
by Syd Bauman 02 Apr '18

02 Apr '18

Just a reminder. We are planning to meet this coming Tue 04-03 13:00Z. That's * 06:00 PDT (Martin) * 09:00 EDT (Syd, Elisa, Elli, Raff, Sarah, Hugh) * 14:00 BST (James) * 15:00 CEST (Lou, Peter, Martina, Magdalena?) I _think_ I have those parentheticals correct, but I'm not sure, and I don't know which continent you will be on, Alejandro. As always, I'm hoping someone else will arm wrestle with Mr. Google to get a Hangout up and running. This will be the same sort of meeting as the past few (attack a problem or two as a group, probably coming up with more questions than answers :-), but I'd also like to carve out a few minutes to consider different approaches. E.g., rather than all of us on the same conference call attacking the same issue, perhaps it is, or soon will be, time to divide and conquer. We'd start the same way, but spend the first 5-10 mins dividing up a few problems to sub-groups, then spend 40 mins in sub-groups, then regroup as a whole for 15 mins. Another possibility would be to handle ticket assignment to sub-groups of 2-4 people a few days to a week ahead of our meeting, and then use the group teleconference to report on difficulties, successes, ask questions, etc.

4 3

oXygen 20 not plugging in
by Syd Bauman 01 Apr '18

01 Apr '18

I am running oXygen 20 on Mac OS. I cannot install either the TEI release framework[1] or the TEI bleeding edge framework[2]. In both cases after entering the URL, the information is retrieved, but grayed out, and the "install this one" box cannot be checked. Furthermore, if I check "show only compatible add-ons", the entire line disappears. I am away from home at the moment, so cannot check this on any other systems. 1) Anyone else having this problem? 2) Any way to easily run the jTEI to PDF transformation w/o using oXygen? (Yes, I am desperately working on my jTEI paper. :-) Notes ----- [1] http://www.tei-c.org/release/oxygen/updateSite.oxygen [2] http://teijenkins.hcmc.uvic.ca/job/oxygen-tei-bleeding/lastSuccessfulBuild/…

4 3

Re: [tei-council] F2F Tokyo
by Alejandro Bia 31 Mar '18

31 Mar '18

Hi Martina, I'm in favour of d) or b), in this order. I would be glad to take part in joint council activities. Maybe a workshop. Best, Alex.- At 10:53 26/03/2018, you wrote: >Hi Martina, > > >I favour a) or b) in that list. > > >I'm planning on submitting something >individually but would also be willing to take >part in joint council activities if we want to do something. > > >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 Scholger, Martina >(martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at> >Sent: 25 March 2018 18:13:15 >To: tei-council(a)lists.tei-c.org >Subject: [tei-council] F2F Tokyo > >Hi all, > >sorry for being so quiet since our F2F in >Cologne. As most of you already know, I >successully defended my dissertation and the >thundercloud above my head has disappeared... > >I'm in contact with Susan and Kyionori about the >F2F meeting in Tokyo. The TEI conference (Sun >9th - Thu 13th) takes place in conjunction with >the JADH conference (Sun 9th - Tue 11th). >The TEI workshops are on Sunday (full day) and >Monday morning. Magda, you said that you want to >do a workshop - do you plan full-day or >half-day? Is anyone else planning a workshop? I >think we could ask the program committee to >schedule workshops from Council members according to our request. >The Board meeting is planned for Monday morning (Hugh and I have to be there). > >I think our options - assuming that Kiyonori can >arrange rooms accordingly - are: >a) Thu 6th - Sat 8th >b) Fri 7th - Sun 9th (in case nobody want's to >do a full-day workshop and half-day workshops are scheduled for monday) >c) Thu 13th afternoon - Sat 15th (but that would >mean only 2,5 days - and no excursion) >d) Fri 14th - Sun 16th >e) to split our meeting (I'm not in favour) > >Please let me know your preferences concerning our meeting. > >The program committee (resp. Susan Schreibman) >would be very pleased about numerous >contributions from the Council. Who is planning >to submit something? Should we think of doing a workshop / a panel together? > >Best wishes, >Martina > > >Martina Scholger >Zentrum für Informationsmodellierung - Austrian Centre for Digital Humanities >Elisabethstraße 59/III >8010 Graz >Austria >martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at> >https://informationsmodellierung.uni-graz.at | https://gams.uni.graz.at > >Chair of the TEI Technical Council >Institut für Dokumentologie und Editorik e.V. https://i-d-e.de > > > >-- >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 --------------------------------------------------------- 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 Skype: alex-bia Twitter: @alex_bia --------------------------------------------------------- --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

1 0

Reimbursement F2F Victoria
by Scholger, Martina (martina.scholger＠uni-graz.at) 30 Mar '18

30 Mar '18

Hi, I wanted to make sure that everyone got their reimbursement for the Victoria F2F meeting. Please let me (or Hugh) know in case it is still missing. Best wishes, Martina

2 1

Re: [tei-council] Stylesheets group meeting, Tue 03 Apr 18
by James Cummings 30 Mar '18

30 Mar '18

Hi All, I'm going to have to send my apologies for this Stylesheets meeting -- though like Syd's second possibility. Perhaps we should assign some stylesheets tickets each to multiple assignees in advance, they work on it as a group however they like, then report back on it. (i.e. "We tried this and it didn't work, anyone have any ideas why?"). That just sounds more productive since we all work at different rates and in different ways. (For example the work windows desktop machine I'm at for teleconferences does not have the software/etc on it that I use for doing TEI work.) Apologies that I can't be there, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: tei-council-bounces(a)lists.tei-c.org <tei-council-bounces(a)lists.tei-c.org> on behalf of Syd Bauman <s.bauman(a)northeastern.edu> Sent: 29 March 2018 15:27:46 To: TEI Council; Lou Burnard; Martin Holmes Subject: [tei-council] Stylesheets group meeting, Tue 03 Apr 18 Just a reminder. We are planning to meet this coming Tue 04-03 13:00Z. That's * 06:00 PDT (Martin) * 09:00 EDT (Syd, Elisa, Elli, Raff, Sarah, Hugh) * 14:00 BST (James) * 15:00 CEST (Lou, Peter, Martina, Magdalena?) I _think_ I have those parentheticals correct, but I'm not sure, and I don't know which continent you will be on, Alejandro. As always, I'm hoping someone else will arm wrestle with Mr. Google to get a Hangout up and running. This will be the same sort of meeting as the past few (attack a problem or two as a group, probably coming up with more questions than answers :-), but I'd also like to carve out a few minutes to consider different approaches. E.g., rather than all of us on the same conference call attacking the same issue, perhaps it is, or soon will be, time to divide and conquer. We'd start the same way, but spend the first 5-10 mins dividing up a few problems to sub-groups, then spend 40 mins in sub-groups, then regroup as a whole for 15 mins. Another possibility would be to handle ticket assignment to sub-groups of 2-4 people a few days to a week ahead of our meeting, and then use the group teleconference to report on difficulties, successes, ask questions, etc. -- tei-council mailing list tei-council(a)lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council PLEASE NOTE: postings to this list are publicly archived

2 1

ODD compilation
by Lou Burnard 30 Mar '18

30 Mar '18

I've just discovered something which is definitely a bug, though I'm not sure whether it's in my understanding of how ODD processors ought to behave or in the current incarnation of odd2odd. As you will recall, this stylesheet is supposed to "compile" an ODD into a form which can then be re-used by other ODDs. It looks to me as if it ignores anything other than deletions. For example, suppose my base ODD changes att.global.rendition by removing one of the attributes it supplies, changes the content model of some element, and supplies a valList for some attribute which didn't have one before. The first change is reflected in the compiled ODD generated by odd2odd, but neither the second nor the third is. This is quite a shock (if it's not just a bug in the code) as it considerably reduces the usefulness of odd chaining as a technique. Anyone else noticed it?

2 2

Agenda for Thursday
by Scholger, Martina (martina.scholger＠uni-graz.at) 29 Mar '18

29 Mar '18

Hi all, our next teleconference is scheduled for Thursday 29th (08:00 EDT, 13:00 BST, 14:00 CEST). Here is the agenda - please add your topics: https://docs.google.com/document/d/1Syd6J93GQ0dAElsKAzqoEVYmOuu0s2JBxUi610H… Hugh shared a Google calendar - thanks for that! I hope you can see the registered dates in your time zone? Elli, can we use the Brown Hangout again? Best wishes, Martina Martina Scholger Zentrum für Informationsmodellierung - Austrian Centre for Digital Humanities Elisabethstraße 59/III 8010 Graz Austria martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at> https://informationsmodellierung.uni-graz.at | https://gams.uni.graz.at Chair of the TEI Technical Council Institut für Dokumentologie und Editorik e.V. https://i-d-e.de

3 3

Modifying the content model of the event element
by James Cummings 28 Mar '18

28 Mar '18

Hi Council, (Martin Holmes CC'd) I've made proposal on https://github.com/TEIC/TEI/issues/1756 and wonder if council members have a moment whether they could give it a read, comment there, vote on which you prefer, etc. It is a fairly small change (adding idno to the content model of event, and ptr to event/person/place/org) that would have numerous benefits for many projects dealing with named entities (of which I consider event something that is much of a named entity as person/place/org). Since 2012 council has agreed a desire to rationalise the content models of person/place/org (and I would add 'event' to that list of entities): c.f. https://github.com/TEIC/TEI/issues/367 my suggestions on this ticket work under the principle that any proposed smaller changes that bring the content models of named entities into greater cohesion of content models and doesn't preclude later rationalisation are probably a good ideas. We shouldn't need to wait for the perfect solution to implement smaller ones. Best wishes, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University

1 0

F2F Tokyo
by Scholger, Martina (martina.scholger＠uni-graz.at) 27 Mar '18

27 Mar '18

Hi all, sorry for being so quiet since our F2F in Cologne. As most of you already know, I successully defended my dissertation and the thundercloud above my head has disappeared... I'm in contact with Susan and Kyionori about the F2F meeting in Tokyo. The TEI conference (Sun 9th - Thu 13th) takes place in conjunction with the JADH conference (Sun 9th - Tue 11th). The TEI workshops are on Sunday (full day) and Monday morning. Magda, you said that you want to do a workshop - do you plan full-day or half-day? Is anyone else planning a workshop? I think we could ask the program committee to schedule workshops from Council members according to our request. The Board meeting is planned for Monday morning (Hugh and I have to be there). I think our options - assuming that Kiyonori can arrange rooms accordingly - are: a) Thu 6th - Sat 8th b) Fri 7th - Sun 9th (in case nobody want's to do a full-day workshop and half-day workshops are scheduled for monday) c) Thu 13th afternoon - Sat 15th (but that would mean only 2,5 days - and no excursion) d) Fri 14th - Sun 16th e) to split our meeting (I'm not in favour) Please let me know your preferences concerning our meeting. The program committee (resp. Susan Schreibman) would be very pleased about numerous contributions from the Council. Who is planning to submit something? Should we think of doing a workshop / a panel together? Best wishes, Martina Martina Scholger Zentrum für Informationsmodellierung - Austrian Centre for Digital Humanities Elisabethstraße 59/III 8010 Graz Austria martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at> https://informationsmodellierung.uni-graz.at | https://gams.uni.graz.at Chair of the TEI Technical Council Institut für Dokumentologie und Editorik e.V. https://i-d-e.de

3 2

Re: [tei-council] F2F Tokyo
by James Cummings 26 Mar '18

26 Mar '18

Hi Martina, I favour a) or b) in that list. I'm planning on submitting something individually but would also be willing to take part in joint council activities if we want to do something. 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 Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at> Sent: 25 March 2018 18:13:15 To: tei-council(a)lists.tei-c.org Subject: [tei-council] F2F Tokyo Hi all, sorry for being so quiet since our F2F in Cologne. As most of you already know, I successully defended my dissertation and the thundercloud above my head has disappeared... I'm in contact with Susan and Kyionori about the F2F meeting in Tokyo. The TEI conference (Sun 9th - Thu 13th) takes place in conjunction with the JADH conference (Sun 9th - Tue 11th). The TEI workshops are on Sunday (full day) and Monday morning. Magda, you said that you want to do a workshop - do you plan full-day or half-day? Is anyone else planning a workshop? I think we could ask the program committee to schedule workshops from Council members according to our request. The Board meeting is planned for Monday morning (Hugh and I have to be there). I think our options - assuming that Kiyonori can arrange rooms accordingly - are: a) Thu 6th - Sat 8th b) Fri 7th - Sun 9th (in case nobody want's to do a full-day workshop and half-day workshops are scheduled for monday) c) Thu 13th afternoon - Sat 15th (but that would mean only 2,5 days - and no excursion) d) Fri 14th - Sun 16th e) to split our meeting (I'm not in favour) Please let me know your preferences concerning our meeting. The program committee (resp. Susan Schreibman) would be very pleased about numerous contributions from the Council. Who is planning to submit something? Should we think of doing a workshop / a panel together? Best wishes, Martina Martina Scholger Zentrum für Informationsmodellierung - Austrian Centre for Digital Humanities Elisabethstraße 59/III 8010 Graz Austria martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at> https://informationsmodellierung.uni-graz.at | https://gams.uni.graz.at Chair of the TEI Technical Council Institut für Dokumentologie und Editorik e.V. https://i-d-e.de -- 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

Addition/change of TEI@Paderborn addresses
by Peter Stadler 26 Mar '18

26 Mar '18

Dear Ian, may I ask you (on behalf of the TEI Council) to change the current DNS record for jenkins-paderborn.tei-c.org to point at 193.175.67.218? Additionally, I’ve set up an OxGarage instance there so it’d be great if you could add oxgarage-paderborn.tei-c.org as a subdomain and point it at the same IP?! Many thanks in advance Peter -- Peter Stadler Musikwissenschaftliches Seminar Detmold/Paderborn Hornsche Str. 39 D-32756 Detmold Tel. +49 5231 975-676 Fax: +49 5231 975-668 pstadler at mail.uni-paderborn.de http://muwi-detmold-paderborn.de

2 5

P5/ReleaseNotes/ChangeLog
by Peter Stadler 24 Mar '18

24 Mar '18

Hi Council, Martina discovered during last release that the write_changelog script didn’t clean up properly after running. I promised to fix this (which I just did in https://github.com/TEIC/TEI/commit/e9206ef7dcb689334be51d55734f3f5315ff78ae) but came across a bigger issue. I.e., the script didn’t write proper changelog information sind release 3.0.0 because of an additional blank line which fools the `head -1`. Anyway, I wonder whether anyone ever looks into P5/ReleaseNotes/ChangeLog which is a mere copy of the history you can view from GitHub (or any other git client). So, I think that might have served some purpose back in the old (subversion) days but couldn’t we simply remove that file (along with the script and the build step) now? Best Peter

2 2

oxgarage.euryanthe.de
by Peter Stadler 17 Mar '18

17 Mar '18

Dear all, I’ve set up a new OxGarage instance at oxgarage.euryanthe.de and would like to get some feedback from you heavy users. It’s actually two OxGarage docker containers (created from https://hub.docker.com/r/teic/oxgarage/) running behind a load balancer on a Rancher platform (http://rancher.com) served via HTTPS. The URL is not supposed to be stable forever, at present it’s for testing only – when everything works out fine I hope we can turn it into something like oxgarage-paderborn.tei-c.org … Best Peter

2 4

Balisage symposium
by Syd Bauman 17 Mar '18

17 Mar '18

Anyone else interested in trying to put together a panel of short papers for the Balisage Symposium?

2 1

teibare slightly broken
by Lou Burnard 08 Mar '18

08 Mar '18

I've just been alerted (thanks Peter) to a problem in the teibare.odd which appears in the current TEI/exemplars directory (and is part of the oxygen TEI framework, updated at each release). According to the text of the ODD "Finally three of the TEI attribute classes are simplified. The attributes xml:space, rend, and xml:base are removed from the att.global class, so that this now makes available to all elements only the following attributes: <att>xml:id</att>, <att>n</att>, and <att>xml:lang</att>. " But of course this is no longer true, because @rend is now supplied by att.global.rendition rather than by att.global (along with a lot of other weird attributes which weren't there before). One solution might be to tie this ODD explicitly to a much earlier release of the Guidelines by means of a @source parameter. That would test whether all the tools in the processing chain Do The Right Thing in such a case. Another might be to bring the ODD up to date, e.g. by deleting the att.global.rendition class. That would probably be less upsetting for existing tools. Or we could just leave well alone, and be prepared to shrug when people complain that TEI Bare is really not as bare as it claims to be...

1 0

reimbursement for Cologne
by Syd Bauman 07 Mar '18

07 Mar '18

Following https://wiki.tei-c.org/index.php/Travel_Reimbursement_Procedures_for_Counci… .. The U.S. Dept. of State rates for Cologne are: Maximum Lodging rate = 241 Meals & Incidental Expenses rate = 132 Thus the TEI-C rates are: maximum lodging rate = 180.75 meals & incidental expenses rate = 99.00 ----- --- ---- ---- - ------ total per diem rate = 279.75 incidentals, morning = 13.99 incidentals, afternoon = 19.58 incidentals, evening = 22.38 meals, morning = 55.95 meals, afternoon = 78.33 meals, evening = 89.52 TEI-C separately reimburses for airfare, travel to & from the airport, and lodging at conference hotel rate or less. Travel to & from the meetings themselves are covered by the incidentals expense rate (unless > 20 USD). Group meals already covered ----- ----- ------- ------- Fri 02-23 22:12 group dinner @ maca-ronni [1] Sat 02-24 14:47 group lunch @ Palpine [2] Sat 02-24 ~22:00 group dinner @ Pinnochio [3] Sun 02-25 ~14:00 group lunch @ Cafe Krümel [4] Sun 02-25 22:21 group dinner @ Brauhaus KAPütz [5] Mon 02-26 20:20 group dinner @ Brauhaus KAPütz [6] Councilors present ---------- ------- [1] SB, EB, HC, JC, EM, MS, SS, MT, RV [2] SB, EB, HC, JC, EM, MS, PS, SS, MT, RV [3] SB, EB, HC, JC, EM, MS, PS, SS, RV [4] (Idunno exactly -- paid for by MT.) [5] SB, EB, HC, JC, EM, MS, PS, SS, MT, RV [6] SB, HC, EM, PS, SS,

2 3

lunch Sun 02-25
by Syd Bauman 05 Mar '18

05 Mar '18

Who paid for lunch on Sun? (And where did we go?)

4 3

teidata.point
by Syd Bauman 27 Feb '18

27 Feb '18

Hope y'all are having uneventful trips back home. If you look at the "Schematron" section of http://jenkins2.tei-c.org/job/TEIP5-dev/lastSuccessfulBuild/artifact/P5/rel… or equivalent, you will see that the comments I left in the tagdoc file, intended more for Council than end users, has been copied over to the output. This is not a bug in the stylesheets, IMHO it is a feature -- if I really want the comment not to show up in the output I just move it to be a sibling of <constraint> instead of a child of <constraint>. No big deal. But I forgot about that, and so we have a big ugly comment showing up. But taking a look at it, I wonder whether it should be left there for users or not? Also, just so y'all know, I am planning to add a <remarks> indicating exactly what is deprecated.

2 1