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

Report on the continuing work of TEI Simple
by James Cummings 30 Jan '15

30 Jan '15

The TEI Simple project has been working and developed things especially over a week in January where Brian Pytlik Zillig came to Oxford to work with Sebastian and Magdalena (and intermittently me). This includes the first draft of TEI Processing Model documentation, with a configuration for TEI Simple and an implementation. See especially http://htmlpreview.github.io/?https://github.com/TEIC/TEI-Simple/blob/maste… for the description of the draft processing model and the <model>, <modelGrp>, and <modelSequence> elements. http://dixit.hypotheses.org/550 is a blog post of Magdalena's explaining some of the work. Upcoming: a) We have a working and advisory group meeting in late March in Berlin to confirm the the processing model proposal b) We’d like the Council to review the PM ODD extensions at its next f2f meeting; though an idea now of whether they are broadly acceptable would be very useful, but we’re not yet asking the Technical Council to consider whether and how they can be implemented (that’s in hand), just whether: 1) the notation conforms to TEI patterns, 2) the re-use of <rendition> is acceptable, and 3) whether the notation is powerful enough _in the circumstances of the Rahtz Rationale_ (this is important). c) We are negotiating now to get a 2nd implementation made of the PM spec (which still has some editing work pending), possibly by the eXist folks (Wolfgang and Adam), to confirm that there no technical barriers. d) We would like to have a hackathon or workshop getting people to test TEI Simple and its PM maybe in the late spring -James == From Sebastian == The following links should help you read about what we have done and are proposing: Documented ODD for Simple:http://htmlpreview.github.io/?https://github.com/TEIC/TEI-Simple/blo… for differences andhttp://htmlpreview.github.io/?https://github.com/TEIC/TEI-Simple/blob/ma… for full version Documented extensions for processing:http://htmlpreview.github.io/?https://github.com/TEIC/TEI-Simple… for differences andhttp://htmlpreview.github.io/?https://github.com/TEIC/TEI-Simple/blob/ma… for full version TEI Simple schema (RELAX NG):https://raw.githubusercontent.com/TEIC/TEI-Simple/master/teisimple.rng Magdalena Turska has done the first implementation for the processing, and has put up some before and after test files for a test file: https://github.com/TEIC/TEI-Simple/blob/master/tests/testsimple.xml (before) andhttp://htmlpreview.github.io/?https://github.com/TEIC/TEI-Simple/blob/ma… (after) Magdalena has also written a nice blog post about work on Simple at http://dixit.hypotheses.org/550 which I commend to everyone. Remember: everything you see today remains a proposal for discussion, and is not fixed in stone. == From Magdalena == The premise of processing model implementation is to generate XSLT stylesheet based solely on TEI Simple ODD file that contains models and renditions that define intended processing for TEI Simple elements. Base TEI Simple ODD can be found athttps://github.com/TEIC/TEI-Simple/blob/master/teisimple.odd Processing model implementation files can be found in polygon subdirectoryhttps://github.com/TEIC/TEI-Simple/tree/master/polygon and this is assumed to be working directory in all examples below. To generate the XSLT stylesheet one can run following command: saxon -xi -s:../teisimple.odd -o:simple.xsl -xsl:simpleoddtoxsl.xsl That will generate simple.xsl file which can be used in turn to transform the TEI Simple documents, eg: saxon -s:../tests/5730.xml -o:../tests/treasureisland.html -xsl:simple.xsl will produce html output for Treasure Island sample file. To change the behaviour of this final transformation one needs to tweak appropriate sections of teisimple.odd and re-run both commands above to 1. regenerate simple.xsl stylesheet and 2. apply it to source document again. There are additional tests at https://github.com/TEIC/TEI-Simple/tree/master/tests == -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford

1 0

Stylesheets in GLs repo?
by Hugh Cayless 30 Jan '15

30 Jan '15

It looks like a copy of the Stylesheets got checked in to the Guidelines repo last month. I presume this was an accident and it's ok to get rid of it? Hugh

8 21

correspDesc
by Peter Stadler 30 Jan '15

30 Jan '15

Dear all, I updated the formal specification and added some chapter prose (for the header chapter — thanks to Sabine and Marcel!) at our SIG’s GitHub repository. So, at [1] you will find the specs (the prose there section is more or less outdated, so please skip) and at [2] a draft for some chapter prose to go into the header section at 2.4.6 My implementation plan is straightforward: * add the prose <div> from [2] to HD-Header.xml * create files under P5/Source/Specs for the new elements and classes (while removing our namespace from elementSpecs and egXML) * modify existing elements (add membership to the new classes) So, please have a look at the files and point me at those things I don’t see … I have one issue though: In the elementSpec for correspAction I try to set some suggested values for @type (see l. 716 in [1]). I tried to follow the model at P5/Source/Specs/list.xml but my values never made it to the RelaxNG schema. Is there some issue with the stylesheets or am I missing something? Best Peter [1] https://github.com/TEI-Correspondence-SIG/correspDesc/blob/master/odd/propo… [2] https://github.com/TEI-Correspondence-SIG/correspDesc/blob/master/odd/HD-He…

3 4

oxygen-tei now successfully building on Jenkins
by Martin Holmes 30 Jan '15

30 Jan '15

Hi all, I now have a fresh build script for the TEI Oxygen plugin which builds the plugin package using the latest successful builds of P5 and the Stylesheets. It will build automatically after every successful TEI P5 build (which itself is triggered by any change to P5 source or following a Stylesheets build), and will also build if its own Google Code repository changes. What this means is that we should now have a trunk build of the Oxygen TEI plugin which tracks the other changes in our codebase. Most importantly, we'll know immediately if something the Oxygen guys do in the Google code repo breaks the build, or if we do something to our own codebase which breaks it. The next stage is to set up an update file for these trunk builds, like this one: http://www.tei-c.org/release/oxygen/updateSite.oxygen to which the braver among us could subscribe, so that the plugin would always get tested steadily as we work. I think the build process should create this file, so it will probably end up being on the Jenkins server itself somewhere. If anyone is interested in testing now, the latest build is here: <http://teijenkins.hcmc.uvic.ca/job/oxygen-tei/lastSuccessfulBuild/artifact/…> Our current release of this plugin is called "teioxygen..." rather than "oxygen-tei", but since the Google Code project is oxygen-tei, and there is also a TEI deb package called "tei-oxygen" which has nothing to do with this, I've taken the opportunity to name my distro like this: oxygen-tei-2.7.1a-7.30.0.zip If you think it's a good idea to carry this naming over to the release package, shout; we could modify the build-and-upload script accordingly, along with the update file, and reduce potential confusion. Cheers, Martin

1 0

Please take a look at this bug
by Martin Holmes 30 Jan '15

30 Jan '15

Hi all, Could I ask Council to take a look at this bug? <http://sourceforge.net/p/tei/bugs/704/> I believe the explanation in the final comment is correct, that it's a corrigible error, and that it's fairly egregious (we give an example in the Guidelines of something that isn't actually permitted in standard TEI schemas; we get round this ourselves in the actual Guidelines source by customizing our ODD schemas). I'd like the OK to fix this; I think it should be release-blocking, and it's holding up the work Ron is doing to integrate the JTEI schema into our system. If there are no objections in the next week, I'll assume assent and implement the fix suggested on the ticket. Cheers, Martin

5 7

Tickets for the new Council members?
by Martin Holmes 29 Jan '15

29 Jan '15

Hi all, Jens Østergaard Petersen just read the CH-LanguagesCharacterSets.xml prefatory chapter: <http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CH.html> and as he often does, took the trouble to report a bunch of minor issues and typos. I was going to trawl through these tonight, but it crossed my mind that they might be useful for the new Council members to do their first Guidelines edits with. Raffaele and Stefan, what do you think? These are the bugs that are straightforward fixes: <http://sourceforge.net/p/tei/bugs/707/> <http://sourceforge.net/p/tei/bugs/708/> <http://sourceforge.net/p/tei/bugs/709/> <http://sourceforge.net/p/tei/bugs/711/> <http://sourceforge.net/p/tei/bugs/712/> <http://sourceforge.net/p/tei/bugs/714/> <http://sourceforge.net/p/tei/bugs/716/> <http://sourceforge.net/p/tei/bugs/717/> There are a few others, but they need at least a look; the final one calls for a complete section to be deleted or revised, and I tend to agree with him, but it'll need some discussion. Raffaele and Stefan, if you think it would be useful to try editing the Guidelines with some straightforward bugs like this, I'd suggest Raffaele take the even-numbered ones and Stefan the odd-numbered ones, so you don't step on each other's feet, and have a go. Below is a copy of the instructions I sent around in December. If you don't think it's of value to do this, just post to the list and I'll make these fixes. --------------------------------------------------------------- 2. EDITING THE GUIDELINES: --------------------------------------------------------------- Most of the actions taken by Council members involve editing the TEI Guidelines source code. The process basically works like this: 1. Check out the source from Subversion on SourceForge. 2. Make changes. 3. Commit them back to the repository. 4. Wait to see whether our Continuous Integration servers successfully rebuild the schemas and documentation. These are the key URLs for learning how to edit the Guidelines: The Sourceforge SVN repository: <http://sourceforge.net/p/tei/code/HEAD/tree/> (If you log into the SF website, you will see the option RW for a read-write checkout; use this option so that you can easily commit changes back to the repository. All Council members are members of the Developer group, with write permissions.) Bug reports and feature requests (tickets) on SourceForge: <http://sourceforge.net/p/tei/_list/tickets> How to Edit the TEI Guidelines: <http://www.tei-c.org/Activities/Council/Working/tcw20.xml> (This is a vital read before attempting to make any changes to the Guidelines source code.) Style Guide for Editing the TEI Guidelines: <http://www.tei-c.org/Activities/Council/Working/tcw24.xml> (Another important document to read before making any edits.) Currently Unresolved Tickets: <http://www.tei-c.org/Activities/Council/Working/tcw17.html> (This is a good way to see what we're currently working on. New members might find a ticket here that they feel confident about implementing, and could volunteer to take it and work on it with the help of their mentor.) --------------------------------------------------------------- Cheers, Martin

7 11

oxygen-tei build and jar signing
by Martin Holmes 29 Jan '15

29 Jan '15

Hi all, As part of ticket 526: https://sourceforge.net/p/tei/feature-requests/526/ I've got a basic build of oxygen-tei running on my Jinks: <http://teijenkins.hcmc.uvic.ca/> However, there's still a lot to do: - It needs a recent oxygen.jar. I tried to use the one which is in /usr/share/lib/oxygen/lib/, but that was too old. Could the TEI packages be updated to include a more recent oxygen.jar? That would save having to provide a more recent version manually for ant to use in the build process. - Right now I'm just using the default ant build. We normally build a full distro using Sebastian's update-and-upload.sh script; I'll have to adapt that script to do the full Jenkins build without doing the upload. - When I do that, I presume I should be using not the current release of the Stylesheets and P5, but the latest builds from Jenkins, so we have a fully-functional version from trunk. Does anyone see any objection to that? - On the ticket, Sebastian says we'll need to sign the jar files before the results will work (and we'll need them to work in order to test the framework). This doesn't seem to be happening, though, in the update-and-upload.sh script. If that's the case, how come the TEI plugin is working for anyone? Cheers, Martin

2 2

ballots distributed for election for chair of Technical Council
by Kevin Hawkins 13 Jan '15

13 Jan '15

Colleagues, I have just set up an election for Council chair using OpaVote and sent ballots to the following addresses: stefanie.gehrke(a)biblissima-condorcet.fr stefan.majewski(a)onb.ac.at stadler(a)edirom.de s.bauman(a)neu.edu raffaeleviglianti(a)gmail.com philomousos(a)gmail.com pfschaffner(a)umich.edu mholmes(a)uvic.ca lou.burnard(a)retired.ox.ac.uk james.cummings(a)it.ox.ac.uk fabio.ciotti(a)uniroma2.it There are two candidates, whose names should be presented on the ballots in random order: Hugh Cayless Lou Burnard You have until 13 January 2015 at 21:43 Central Standard Time (UTC - 6 hours) to cast your vote for one of the two candidates. --Kevin

7 9

Doodle Poll for Council Meeting
by James Cummings 12 Jan '15

12 Jan '15

Hi all, I've put up a doodle poll to schedule our next meeting. I've suggested 2pm (GMT) or 3pm start (for an hour or more meeting) on any of the weekdays the week of Monday 19 January. Timezone support is on so it _should_ show you the time in your own timezone but feel free to double check this with www.timeandate.com. Please select any date/time you can make. If you might *usually* be able to make one of these on another month (or if it would be only mildly inconvenient) then select (yes) (ifneedbe) and/or leave a comment. http://doodle.com/mmqpzigxa5p6zqyz -James Chair Emeritus -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford

3 6

minor problem in PDF table of contents
by Lou Burnard 08 Jan '15

08 Jan '15

An eagle-eyed reader of the PDF version of the Guidelines points out that the links from the table of contents page are not quite right. The problem seems to be that a link to section "n" in the PDF doesn't include information about whether it's going to section "n" in the front, body, or back, and always goes to the first one that's available. The links in the HTML version are fine, so this must be something going wrong in the LaTeX, or more likely in the generated PDF. On 07/01/15 22:23, Keith Handley wrote: > > The PDF has the table of contents as bookmarks. If you click on "1 The > TEI Infrastructure", you go to the spot labeled "1 Releases of the TEI > Guidelines". If you click on "2 The TEI Header" you get "2 Dedication". > > You get similar stuff for the top-level bookmarks for chapters 3 > through 6, as well (which have corresponding numbered chapters in the > front matter). > > The same thing happens with sub-chapters, when there is a sub-chapter > with the same number in the front matter. So "4.1 Divisions of the > Body" points to 4.1 in the front matter. 4.2 and 4.3 behave similarly, > but 4.4 works correctly--I assume because there is no chapter 4.4 in > the front matter. >

2 1

Council Chair Elections and Teleconferences
by James Cummings 06 Jan '15

06 Jan '15

Hi Council! Happy New Year! We have two things to sort out before the Council can get down to business this year: 1) Elections: Lou and Hugh put themselves forward for election to the glorious position of Council chair. I've asked someone if they will act as the returning officer and am just awaiting their response. All current council members get a vote and so you may wish to refresh your minds as to Lou and Hugh's candidate statements for getting elected to the Council: http://www.tei-c.org/Membership/Meetings/2014/mm70.xml#burnard http://www.tei-c.org/Membership/Meetings/2014/mm70.xml#cayless 2) Teleconferences: I'm about to set up a doodle poll for a set of date/time combinations that we can then use as a template to schedule meetings for the rest of the year. I'll send the link to that in a separate email later this evening. Apologies for the delay with both of these. -James -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford

1 0

oops -- please check xlsxtotei
by Syd Bauman 04 Jan '15

04 Jan '15

I *thought* I was pushing a stylesheet bug fix to GitHub for review by Sebastian et al. But it seems (probably because, quite reasonably, I have the necessary privileges) that my change was committed w/o review. Could Sebastian, James, Martin, Hugh, and anyone else who stands a chance of understanding the code check that it makes sense? See https://github.com/TEIC/Stylesheets/commit/b3cd09986637ea3339f22dfe503a0d63… You'll find there are hundreds of changes, but they're all white-space changes except lines 277-280 (search for "Syd"). Could anyone who has an Excel spreadsheet that has intra-cell changes in style (like typeface or italics) test this? Would make me feel a lot better about this change if we had more than 1 case in which the new code was an improvement. :-) Thanks. P.S. How do I send mail to the GitHub list for Stylesheets?

2 1

simple/minimal
by Lou Burnard 04 Jan '15

04 Jan '15

I just noticed that the current oxygen framework offers a menu of available TEI document types which includes items called "Simple", "Simple with Internationalisation", etc. (see attached graphic, if this list permits it) These are of course nothing to do with the "TEI Simple" schema currently used for EEBO TCP texts. The corresponding schema files are not so named, obviously but it seems a source of needless confusion to retain the name "simple" here rather than say "minimal". Where are these names defined, and is it not in the council's remit to correct them?

2 3

How about a translate-a-thon at the Members Meeting?
by Martin Holmes 30 Dec '14

30 Dec '14

Hi all, I have a vague memory of this idea being raised at some point, but I can't find any evidence of it, so maybe it was all in my head. After three attempts to get translation projects going have failed almost at the starting gate, it seems to me that we need an alternative strategy. Since the Members Meeting will be in France next year, how about organizing a one-day "translate-a-thon" to update the French translation? We could provide food, organization and guidance, and try to get a large enough group of interested French speakers to storm through as much of the French translation job as can be done in a day. We might get it all done. Even if we don't, I bet we could get far enough with it that the job would get finished over the following weeks. What do you think? Cheers, Martin

4 12

Stylesheets 7.28.0
by Sebastian Rahtz 29 Dec '14

29 Dec '14

In order to complete my term on Council in typically chaotic way, I have taken the opportunity to make a final release of the TEI Stylesheets for the year. Inter alia, this fixes a serious bug in PDF generation of the Guidelines which Lou spotted (looked at the content model for an element in the reference material in the last release); but mostly it represents a lot of fooling around with TCP conversion and rendering, of which more on Jan 1st. I have _not_ updated the oXygen TEI P5+XSL package, as I don’t want to interfere with work to automate that. So a happy holiday to you all, assuming you all do have some of winter solstice break around now, and farewell from me to the TEI Council -- Sebastian Rahtz Director (Research) of Academic IT University of Oxford IT Services 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431 Não sou nada. Nunca serei nada. Não posso querer ser nada. À parte isso, tenho em mim todos os sonhos do mundo.

3 12

Enrich: (was Re: they come to bite us: biblScope/@type fallout
by Lou Burnard 21 Dec '14

21 Dec '14

I'm not sure I agree with that. There is quite a lot of data out there in the real world using Enrich and we wont win any friends by breaking it all for no good reason. I think it would be better to add @type as an explicit locally-defined attribute in the enrich ODD. There is also, I suspect, software which we really don't want to force people to modify., especially since we are no longer in touch with its developers. On 19/12/14 12:55, Sebastian Rahtz wrote: >> On 19 Dec 2014, at 12:50, Martin Holmes <mholmes(a)uvic.ca> wrote: >> >> Hi all, >> >> Following the removal of biblScope/@type, P5-Test and P5-Documentation >> built OK, but the main build failed because of the ENRICH schema, which >> I know nothing about. I guess we have two options: customize the ENRICH >> schema to add back @type on <biblScope>, or modify ENRICH so that it >> uses @unit instead. >> >> Since ENRICH seems to be an interchange format, the former seems the >> better option, so I'll proceed on that basis; if you know differently, >> please shout. It looks like Lou was heavily involved in ENRICH: >> >> <http://projects.oucs.ox.ac.uk/ENRICH/Deliverables/referenceManual_en.html> >> >> If the project is still very active, and has some method of discussing >> and propagating change, we could suggest that they incorporate this >> change into their schema through whatever mechanisms they usually use. > Lou, James and I all worked on ENRICH. No, it doesn’t have an active group > any more. > > I’d be inclined to the "modify ENRICH so that it uses @unit instead” method, > as I don’t want ENRICH to be something other than a subset of TEI. > but I’d like to hear what James and Lou think before you do anything. > -- > Sebastian Rahtz > Director (Research) of Academic IT > University of Oxford IT Services > 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431 > > Não sou nada. > Nunca serei nada. > Não posso querer ser nada. > À parte isso, tenho em mim todos os sonhos do mundo. >

5 10

building P5 pdf locally
by Lou Burnard 20 Dec '14

20 Dec '14

On 18/12/14 14:39, Hugh Cayless wrote: > Sorting out the details of the build system would be nice. I can't myself > do a full buildâ€”it fails somewhere around PDF generation, possibly because > I don't have all the right fonts. But it's not at all clear to me what > those are or how to get them. I've never dug into it because I can generate > the HTML GLs just fine. Is there documentation about the details anywhere? If you run "make dependencies" it should list the packages that need to be installed under debian. These include msttcorefonts, and a bunch of other more exotic (but freely available) font packages, some of which have changed their names since the Makefile was last updated There is also a "make fonttest", but sfaics all this does is check to see whether you have Minion or Myriad fonts installed, and warn you that it will fall back to using yucky Computer modern roman if you don't. By default the Makefile doesn't try to build PDF, or Epub, or Mobi formats for the Guidelines, unless I am missing something. Is this something anyone would want to do when just testing their local mods? It's quite a big deal.

1 0

First message
by James Cummings 12 Dec '14

12 Dec '14

Just sending a first message to the tei-council(a)lists.tei-c.org mailing list. Partly so there can be something in the archives to test their availability. ;-) First post! -James -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford

1 0