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

New test repo
by Hugh Cayless 11 Sep '15

11 Sep '15

https://github.com/TEIC/TEI-TEST <https://github.com/TEIC/TEI-TEST> This replaces the old Guidelines-TEST repo, which has been deleted.

1 0

repo
by Lou Burnard 11 Sep '15

11 Sep '15

Hugh writes > You’ll probably be better off if you grab a new clone of the data rather than trying to merge the old one. For avoidance of doubt, and for the benefit of those still struggling with gittery, could you spell out what that means in terms of command line commands? I assume I need to clone a new version of the repo if I want to change things in the trunk source (e.g. answer a ticket or two), having further assumed that the freeze on source updates is no longer in effect? And lastly (sorry to ask so many stupid questions) do I also need to refresh my current P5-Pure branch repo ?

4 7

repo
by Lou Burnard 11 Sep '15

11 Sep '15

Hugh writes > You’ll probably be better off if you grab a new clone of the data rather than trying to merge the old one. For avoidance of doubt, and for the benefit of those still struggling with gittery, could you spell out what that means in terms of command line commands? I assume I need to clone a new version of the repo if I want to change things in the trunk source (e.g. answer a ticket or two), having further assumed that the freeze on source updates is no longer in effect? And lastly (sorry to ask so many stupid questions) do I also need to refresh my current P5-Pure branch repo ?

1 0

Git Repo Update
by Hugh Cayless 10 Sep '15

10 Sep '15

Dear all, Lou pointed out that his email address was wrong in the commits imported from svn. It must have been wrong in my spreadsheet to being with. I’ve fixed the problem, but that meant a substantial rewrite of the commit history. You’ll probably be better off if you grab a new clone of the data rather than trying to merge the old one. Apologies for the inconvenience. Hugh

1 0

Changelog format
by Hugh Cayless 10 Sep '15

10 Sep '15

Hi all, I’m looking at ways to replace the current changelog generation routine for Git, and have a formatting question. It’s pretty easy to come up with something that’s close, but not identical, to the current format. My question is whether that is good enough, of if there’s some reason to stick with the old format as-is. The old format is: 2015-03-10 Lou Burnard <lou.burnard(a)retired.ox.ac.uk> Changed paths: M /trunk/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml M /trunk/P5/Source/Guidelines/en/USE.xml M /trunk/P5/Source/Specs/TEI.xml clarify structure of TEI element per bug #742 And it would be replaced by: 2015-03-10 Lou Burnard <lou.burnard(a)retirees.ox.ac.uk> 9fc47c4 clarify structure of TEI element per bug #742 M P5/Source/Guidelines/en/DS-DefaultTextStructure.xml M P5/Source/Guidelines/en/USE.xml M P5/Source/Specs/TEI.xml The short-form commit hash above is an optional extra. We didn’t include svn rev numbers before. Another simple alternative is: 2015-03-10 Lou Burnard <lou.burnard(a)retirees.ox.ac.uk> 9fc47c4 clarify structure of TEI element per bug #742 P5/Source/Guidelines/en/DS-DefaultTextStructure.xml | 6 ++++-- P5/Source/Guidelines/en/USE.xml | 6 +++++- P5/Source/Specs/TEI.xml | 41 +++++++++++++++++++++++++++++++++++------ 3 files changed, 44 insertions(+), 9 deletions(-) Which gives more detail about the nature of the changes. Thoughts?

4 3

F2F scheduling in Lyon
by Hugh Cayless 10 Sep '15

10 Sep '15

Dear all, Any objections if our meeting happens on Sunday, Oct. 25, Monday, Oct. 26, and the morning of Wednesday, Oct. 28? Emmanuelle’s trying to make the schedule work out and Tuesday is currently crowded, but there’s a free room Wednesday morning. Please let me know ASAP if this presents a problem. Thanks, Hugh

9 26

Re: [tei-council] Processing Model Documentation for TEI Guidelines
by Lou Burnard 10 Sep '15

10 Sep '15

I started looking at this, but something seems to have gone wrong in the conversion to doc e.g. * *"*The <model> element is the basis of any processing model documentation. foundation The <model> element is used to document the intended processing model for a particular element in an abstract manner which separates . A required @behaviour attribute which documents the processing function and controls which processing function should be used to present this element in output. * " is gibberish. Personally I would *much* rather edit/comment on the ODD source, which must exist somewhere. On 08/09/15 16:08, James Cummings wrote: > > Hi all, > > I've been taking the documentation in the tei-pm.odd and rewriting it > to be something which could be added to the TEI Guidelines. I've put > it up as a google doc with open editing for those of you who wish to > improve it. This will (of course) be encoded in TEI, it is merely > being placed here for ease of collaborative authorship. I believe > that the appropriate place for it is either 22.4.8 shortly after > http://www.tei-c.org/release/doc/tei-p5-doc/en/html/TD.html#TDENT or > another possibility is as a new 22.5 (pushing the current one down to > 22.6). > > https://docs.google.com/document/d/1C1fw5SCrJBZxT7O7-_HLrkBQJk5YZZJzzDbA-ir… > > > Feel free to improve it, and if you have any questions or comments > please make them here on the TEI Simple mailing list. > > -James > >

2 5

Jenkins build is back to normal : Stylesheets #1967
by mholmes＠uvic.ca 09 Sep '15

09 Sep '15

See <http://teijenkins.hcmc.uvic.ca/job/Stylesheets/1967/changes>

1 0

Jenkins build is back to normal : TEIP5 #2135
by mholmes＠uvic.ca 09 Sep '15

09 Sep '15

See <http://teijenkins.hcmc.uvic.ca/job/TEIP5/2135/>

1 0

September Telecon Poll
by Hugh Cayless 08 Sep '15

08 Sep '15

Please indicate your availability at http://doodle.com/poll/4fbdufgwsyc8ruc3 Reminder: we will freeze on October 1, so in my mind, the earlier we meet before that, the better, but we'll have to see what everyone's availability is. All the best, Hugh

1 0

Processing Model Documentation for TEI Guidelines
by James Cummings 08 Sep '15

08 Sep '15

Hi all, I've been taking the documentation in the tei-pm.odd and rewriting it to be something which could be added to the TEI Guidelines. I've put it up as a google doc with open editing for those of you who wish to improve it. This will (of course) be encoded in TEI, it is merely being placed here for ease of collaborative authorship. I believe that the appropriate place for it is either 22.4.8 shortly after http://www.tei-c.org/release/doc/tei-p5-doc/en/html/TD.html#TDENT or another possibility is as a new 22.5 (pushing the current one down to 22.6). https://docs.google.com/document/d/1C1fw5SCrJBZxT7O7-_HLrkBQJk5YZZJzzDbA-ir… Feel free to improve it, and if you have any questions or comments please make them here on the TEI Simple mailing list: teisimple(a)maillist.ox.ac.uk (or teisimple-subscribe(a)maillist.ox.ac.uk to subscribe). -James -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford

1 0

Are we jumping to GitHub or are we not?
by Martin Holmes 04 Sep '15

04 Sep '15

Hi all, My Jinks is able to build the TEI products from GitHub, thanks to some help from Hugh, and James's will also be switched today as a secondary test. The only wrinkle is that Jinks will not be able to notify committers when a build fails, because GitHub doesn't have a transparent way of automatically associating committer ids with email addresses, but we can handle this by having it notify the Council mailing list instead. I've set that up, and I think it might just work out of the box but if not Kevin will be able to allow it. We now want to start revising those "Editing the Guidelines" and similar documents to point to GitHub, and consider what we're going to do about tickets. Is there anyone at this point who objects to moving the repo to GitHub? If not, then I suggest we start updating documentation. Tickets can stay on SF until we have a comfortable migration path for them. Cheers, Martin

5 6

dtd jabberwock slain?
by Lou Burnard 02 Sep '15

02 Sep '15

I have now successfully run the P5 Makefile to completion in my local copy of the P5-Pure branch. I think an exclamation mark is warranted, so here it is ! Holmes's Cunning Wheeze of post-modifying the p5subset.xml seems to do the trick. And tweaking the ANT scripts both to generate and then to use the doctored version of same was not that hard, as Martin also predicted. However, this has yet to be tried out by anyone else, so I repeat my plea for someone to check out this branch and see if it works for them. I will of course be doing so on another computer myself, but that is not at all the same as a fresh pair of eyes.

5 13

P5Pure: the next frontier
by Lou Burnard 02 Sep '15

02 Sep '15

If you try the html-web make target, you will see that &winita; -- the stylesheets concerned don't know anything about dataRef and the content model is (curiously) still displayed in RelaxNG. Sigh.

4 9

ANTifying build process
by Peter Stadler 02 Sep '15

02 Sep '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear all, I wanted to support Martin in his endeavor to move to ANT for our build process(es) and started working on a build.xml file in the P5 directory (within my new peterstadler-antify branch). Second reason, I want to become more familiar with the build process itself… It looks like a straightforward thing to do, the only things I'd like to change are: * create a directory "build" where all the built files go (rather than polluting the P5 directory * create a directory "release" where the zipped archives go Both directories then can easily be discarded when cleaning the working copy before commiting ;) Does that make sense? Is anyone already working on this by chance? Best Peter -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJV5hLZAAoJEJclm6G69Xq24gIH/34ez/QmIDAKbQ2sw3/PEzRK ERJyVdOWNCqv4m5lES6PDjVicVgpzjiOhR7l4sc57h/oPM6t1rxFKcftc6NBFkYl x//JmHNuCPM1BWV2wVN2jrGh+k6uXlov8rJoKMPFdzpFqdl9Yh+nebVuptDSOLxC GOSUjcJsXNgHYgXNNYFTodceRLUi/JDxL7zkFHMEvUtGSpQOEq7maeTnFpHPyfGG ASHOW35DGJXTzHFm8D72D7Ep3l35Vugm6nyGWURfSmQSfF7myaGDKGWjBsB/o9Kn TKrB+u1qC4Y2NwPeiUisGFk2L+ZCNtqEGBXlSvBa9uvUuaW5yk2w1adiVv/w/ZA= =Ja1L -----END PGP SIGNATURE-----

3 2

Lyon meeting hotel
by Lou Burnard 01 Sep '15

01 Sep '15

Following Hugh's comments on the call, I have checked in at the "special rate" at the Mama Shelter from Saturday 25th for 8 nights. According to the conference website, "special TEI discount rate" of 106 euro per night is available, but only until 2 september, i.e. tomorrow. However, the hotel's own website doesn't seem to know anything about this, and offered me 79 euros for some nights of my stay and 115 for others. Oh well. It looks dead posh anyway.

1 0

Update on build problems with P5
by Martin Holmes 01 Sep '15

01 Sep '15

HI all, Hugh and I have been wrestling with the very puzzling results of the P5 build on Jenkins: while TEIP5-Documentation works as expected, generating Guidelines based on the git version, TEIP5 seems to know nothing of git, and behaves as if we're still using svn. I think I've figured out the cause. The Makefile* includes targets "debversion" and "deb" (the latter depends on the former), and the latter seems to be shot through with explicit references to svn: @echo BUILD: make Debian tei-p5-database package (cd debian-tei-p5-database; debclean;debuild -eXSL=${XSL} -eINJENKINS=${INJENKINS} --no-lintian -nc -b -i.svn -I.svn -uc -us) The Documentation build does not try to build the deb packages, but the full P5 build calls: make* VCS=git clean deb dist and in the process of that happening, VCS is set back to svn somehow. If I call make* VCS=git clean dist everything works OK. I know nothing about building debian packages, so this is a mystery to me. I don't mind learning about it, and people assure me that it's not complicated, but it might be more than I can do in a couple of weeks, at least with any confidence. Does anyone else have familiarity with building deb packages? *I hate make. Cheers, Martin

4 9

GitHub Repo import
by Hugh Cayless 31 Aug '15

31 Aug '15

Finally finished and available at https://github.com/TEIC/Guidelines Took about a week to run, with one interruption over the weekend due to some network glitch. Given the degree of pain involved, if we think this looks good, I think we should run with it. So let's: a) stop committing to SF (at least for now, maybe forever). Maybe I should actually restrict commit access to it lest anyone not on this list push an update. b) Check the above repo over for warts/see if anything's missing. There are a couple of branches that are artifacts of the CVS -> SVN migration that weren't visible on Sourceforge. We can probably get rid of them, but I haven't yet. There's also an sf/trunk branch, which I think is just a copy of master. Thoughts?

5 31

TEI Simple vs TEI Minimal
by Martin Holmes 31 Aug '15

31 Aug '15

If you click on File / New in Oxygen, and look at the TEI P5 options, you'll see a bunch of templates called: Minimal Minimal with Internationalization Minimal with Math and so on. I believe that having TEI Simple alongside TEI Minimal (not to mention TEI Lite and TEI Tite as well) is going to be mighty confusing. I suggest that before we integrate Simple into this ecosystem we might want to reconsider whether we want these Minimal schemas or not. Cheers, Martin

2 2

Agenda and Hangout info
by Hugh Cayless 31 Aug '15

31 Aug '15

Agenda is here: https://docs.google.com/document/d/16XMTZsjq09GnwBRiLCpzXbXTyd5R9dAVhKS3ZH2… The Google Hangout link is in the agenda. Do feel free to add items!

1 0

let me share my pain
by Lou Burnard 30 Aug '15

30 Aug '15

You may be wondering how Pure ODD is progressing... Well, all over the place, there are bits of content model like this (expressed in pure ODD) <sequence minOccurs="0" maxOccurs="unbounded"> <classRef key="model.divBottomPart" /> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> i.e. there may be nothing here at all, or there may be at least one member of the model.divBottomPart class possibly followed by some model.globals. This makes perfect sense when transformed to RelaxNG or even in XSD, but the DTD fragment we get for it is: (%model.divBottomPart;,(%model.global;)*)* which is not syntactically correct in DTD language. It needs to be ((%model.divBottomPart;),(%model.global;)*)* Alas, using the current oddtodtd, those extra parens only appear if the bare class reference is inside either a sequence or an alternation. But we have a schematron rule that says (reasonably enough) that a <sequence> must have two or more children. (We don't see this problem in the impure ODD, of course, because RelaxNG doesn't mind <group>s containing just a single pattern) This is not an isolated problem, either.... it's a favourite trick in our content models. Having spent most of today on this, I am reluctantly coming to one of the following conclusions: a) we should just abandon DTDs b) I could write a dirty hack to detect these things and post process the DTDs c) we should quietly drop the schematron rule d) someone (not me) should rewrite odd to dtd either to deal with these things properly or (more radically) to expand all parameter entities e) there is another silver bullet somewhere but i am too stupid to see it Any opinions? Recommendations?

4 22

constraintSpec
by Lou Burnard 30 Aug '15

30 Aug '15

The content model of <constraintSpec> is currently <rng:zeroOrMore> <rng:choice> <rng:ref name="model.glossLike"/> <rng:ref name="model.descLike"/> </rng:choice> </rng:zeroOrMore> <rng:optional> </rng:optional> or, in pure ODD, <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.glossLike"/> <classRef key="model.descLike"/> </alternate> <elementRef key="constraint" minOccurs="0"/> The fact that this gives rise to an invalid DTD content model (there needs to be a <rng:group> or <sequence> round te whole shebang) isn't really my question though. This is my question: What on earth is the point of a <constraintSpec> that doesn't contain a <constraint>? Or if the idea was to permit just documentation (but not a specification) for one, why isn't the model just <rng:zeroOrMore> <rng:choice> <rng:ref name="model.glossLike"/> <rng:ref name="model.descLike"/> <rng:ref name="constraint"/> </rng:choice> </rng:zeroOrMore> ? I think this is a corrigible error, and the <rng:optional>ity of <constraint> should be removed.

3 3

Abstract Model Enforcement
by Hugh Cayless 30 Aug '15

30 Aug '15

In my own copy of the Guidelines, which I’ll probably switch to a branch in the main repo soon, I’ve been playing with the new app. crit. capabilities. As you probably remember, we decided that allowing larger structures inside <lem> and <rdg> made sense, as long as there wasn’t any violation of the abstract model (e.g. using <rdg> to put a inside a ). I’ve been experimenting with adding Schematron rules that enforce abstract model concepts, such as: "no inside or <ab>", "no <div> inside " etc. These are general rules, nothing to do with the critical apparatus changes per se, but they should help. The commit with the changes is https://github.com/hcayless/TEI-Guidelines/commit/66d11fab1be737c0f17ad4521… <https://github.com/hcayless/TEI-Guidelines/commit/66d11fab1be737c0f17ad4521…> and you can experiment by grabbing a copy of https://github.com/hcayless/TEI-Guidelines/blob/appcrit/AppCrit/examples/Pr… <https://github.com/hcayless/TEI-Guidelines/blob/appcrit/AppCrit/examples/Pr…> and trying to cheat by putting, say, inside a <rdg> inside an <l>. If you do this in Oxygen, it should fuss at you and identify the problem at the correct spot. There are changes to prose that still need to be made, and there are probably more Schematron rules we could add, but I think this is workable. Thoughts?

2 1

gnuify-changelog.pl problem in Roma source may apply to P5
by Martin Holmes 30 Aug '15

30 Aug '15

Hi all, I did a quick bugfix for this ticket: <http://sourceforge.net/p/tei/bugs/724/> back in July, but I'm now dealing with the ramifications of getting it onto tei-c.org, and in the process, noticing that the project was moved from SF to GitHub without some key code changes being made to handle the changelog; I think the same issues will apply to P5, so I think we could use Roma as a good testcase for handling the change. When you run "make dist" or "make install" in the Roma source, one of the things that should happen is that the latest changes are added to the ChangeLog file. That's done by calling a PERL script called gnuify-changelog, which seems to be fairly widely used; but it is explicitly customized for the project and its contributors, all of whom are listed explicitly. What it does is to call svn log to get the latest commits, then converts them into a GNU-style changelog by substituting more detailed user info for user names. There are four problems with this: 1. gnuify-changelog.pl no longer exists in the Roma source, since it's been pulled out of the P5 tree. 2. We're now using git, not svn, so the log info is differently formatted. 3. The script requires a hard-coded list of contributors to be maintained. However, git log seems to be more friendly than svn log, in that it includes user name and email: --------------- $> git log -n 1 --name-status commit 18cc86ddcd79b409a9bfa406426fe4685c37fa8a Author: martindholmes <mholmes(a)uvic.ca> Date: Mon Jul 27 14:05:29 2015 -0700 Fix for http://sourceforge.net/p/tei/bugs/724/. I'm doing a string-replace which catches the specific bug reported (double quotes) in the title and author fields, but doesn't make any attempt to do more comprehensive escaping, since that would need a significant rewrite of large blocks of the code, I think. M VERSION M roma/romadom.php --------------- git log can also be massaged to output stuff in XML, by defining an XML format. So I'd like to suggest the following, to be piloted and tested with Roma, but then implemented for P5 (and any other projects which happen to be using gnuify-changelog.pl in our setup: Replace that call with an ant task which reads the existing XML log file (if it exists), calls git log to output anything subsequent to the last entry in XML, calls Saxon to XSLT it to whatever we want and insert it into the existing XML log file, then calls Saxon again to XSLT the now-updated XML log file into the GNU-preferred text format. Alternatively, if those of you who love PERL would like to simply update gnuify-changelog.pl so that it can use the git log output format, you're welcome to do that; it's a bit urgent because I don't think a build will work properly otherwise. Another option is to rely (for P5 builds) on having an svn checkout which can generate an svn log in the expected format, and using that; and then re-inserting gnuify-changelog.pl into the Roma tree, changing the Makefile to point to it, and doing other updates (adding and removing potential contributors) to both PERL files. I think the ant/XSLT solution is better in the long term, and removes one more PERL dependency, but I suspect I'm in a minority there. Cheers, Martin

2 2

Next Telecon
by Hugh Cayless 28 Aug '15

28 Aug '15

Hi all, A reminder that the Doodle poll for our August telecon needs your input, if you haven't already filled it out: http://doodle.com/5ks6ma5f3fez838c Right now, August 31 looks like the best date. I expect the agenda will focus mainly on the migration and on the logistics of a Fall release. It would be really nice to be able to discuss some tickets too though! All the best, Hugh

7 20