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

Re: [tei-council] Development version of oxygen-tei plugin available
by Martin Holmes 03 Feb '15

03 Feb '15

Hi there, On 15-02-03 09:44 AM, Sebastian Rahtz wrote: > happy to set up the job on oxjenkins, shall I do that now or wait a > bit? Go for it. I just tested some of my normal stuff using the new plugin, and it seems to work a treat so far. You'll find the config.xml file for Jenkins in the usual place. The job has to be called "oxygen-tei" (there are some paths in the build-for-jenkins.sh script that depend on that). If you read that script, you'll see it's heavily based on your update-and-upload.sh script, but there are some nifty shenanigans around making the updateSite.oxygen script permanently available at the same URL, while behind the scenes it's shifting its location and has to be regenerated every time based on the previous version. But as far as I know, if you just install the config.xml in a job called oxygen-tei, it'll work. I'm keeping ten versions of the plugin, because we need to let people roll back when things go wrong, and because it gets built often (due to changes in itself, the Stylesheets, or P5). I know your Jinks occasionally has space issues, so that might be something to watch out for, but it's not huge. > the work monitoring oxjenkins is fairly small, so leave that with me > for now. OK. >> The next step is to create some tests we can run in Oxygen to check >> core functionality of the add-on. I envisage this as an Oxygen >> project with a bunch of sample files that are transformed or >> otherwise manipulated and the results checked. > > do you know how to drive oxygen from the command line, then? cool. No, I was planning to write some ant tasks that would be run by a user in the Oxygen interface. Along the lines of: - Create sample file based on template X. - Transform using Stylesheets transformation Y. - Validate result with schema Z. That sort of thing. Not very sophisticated, but the idea would be that when we're about to release a new version of the plugin, someone subscribed to the latest Jinks build would run the tests and confirm nothing is wildly broken, then we'd go ahead and build/upload to the release location. It would be nicer to have automated testing happening as part of the build, of course. If I can learn how to do that, I'll have a go at it. But I don't know where to start right now. Cheers, Martin > > -- Sebastian Rahtz Chief Data Architect University of Oxford IT > Services 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431 > > >

1 0

Spring F2F Poll
by Hugh Cayless 02 Feb '15

02 Feb '15

Hi all, I've set up a poll at http://doodle.com/2qzywq8c379atu87 in the window April 13–May 15. Let's see what we can do, and I'll adjust as needed.

7 11

re corresp oddity
by Lou Burnard 01 Feb '15

01 Feb '15

I note the following things in the definition for <correspAction> in the corresp ODD 1) you should not use @mode="add" together with @module on an <elementSpec> -- it's meaningless, since you are not allowed to add new things to existing TEI modules 2) if you want your valList to appear in the schema you must put @type="closed" on it. otherwise your suggested values appear in the schema only as comments 3) since you are replacing the existing (vacuous) declaration for the possible values of @type, you must put @mode="replace" on your valList With these changes, things work as expected for elements in the TEI namespace. I am still puzzling over why they don't for non-TEI namespaced elements, but have to go out now.

3 2

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