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

Agenda and Hangout
by Hugh Cayless 03 Dec '15

03 Dec '15

Hi all, Sorry for the delay. Moving offices is a headache. Agenda: https://docs.google.com/document/d/1f27Q0VLFN26oDNKgJ8hIXg97MF_9LeYavb1Wd9h… Hangout: https://talkgadget.google.com/hangouts/_/x3ri7iimwlh5ogr3t265zhe6n4a See you in 15 minutes!

1 0

LearnGit at Codecademy
by Raffaele Viglianti 02 Dec '15

02 Dec '15

Codecademy has just released a free interactive course for learning Git. Some council members may find it useful! It cleared some things up for me as well. (Also interesting how it has you write literature rather than code) https://www.codecademy.com/learn/learn-git Best, Raff

1 0

Telecon and updates
by Hugh Cayless 30 Nov '15

30 Nov '15

Dear All, I’ve made some progress on the Pure ODD XSLT. Please browse around http://teic.github.io/TEI/index.html <http://teic.github.io/TEI/index.html> and be on the lookout for display bugs or things you’d like done differently. Although we had enough for a quorum in the poll for meeting times, we’d either be excluding new members, which I’d rather not do, or current members who really need to be there, so I’ve added some more dates at http://doodle.com/poll/wyuc3qiv9rkx4db6. Please update your availability when you get the chance. Whether we have a year-end release or not, I think we’re getting close to the time when we should go ahead and merge the Pure ODD branch. Thoughts? All the best, Hugh

6 7

Bugfix for Roma available for testing
by Martin Holmes 29 Nov '15

29 Nov '15

Hi all, A new Roma is here: <http://www.tei-c.org/Roma-4.18/> with my minor bugfix for the title element included, along with other things (I know not exactly what) that had been added since the last release found its way onto tei-c in 2013. If you have any experience with Roma at all, please give it a bit of a go to make sure nothing is broken. Cheers, Martin

3 4

Adding processing model to github
by James Cummings 26 Nov '15

26 Nov '15

Hiya, To the 'processing-model' branch, based on the 'lb42-pureodd' branch, I've added the specs of elements needed for the processing model, modified that for elementSpec, and added the draft prose to the TD chapter. Hurrah. (Feel free to edit and improve the prose.) I don't promise I've not broken anything and haven't yet added the cross-references to the guidelines text in the TD chapter. (But that is straightforward and I'll do so soon.) What I *haven't* added so far are the tests that Sebastian had written for the processing model because a) believe it or not I've never actually added tests to the TEI build system and so now ask for help in doing so and b) I'm not sure the tests Sebastian was doing are specifically the tests we want. In this case what we want are tests that test that our schemas are allowing/disallowing the various model* and related elements in the right place and used only in ways that they are allowed. Sebastian's tests actually test the parsing of these processing models and the output they generate. Is that what we want? Remember, what we're doing here is adding the ability for documenting processing models, not adding TEI Simple, or any particular implementation of doing things with that processing model documentation. For example, in the TEI-Simple repository there are two types of test in the build.xml ant file: The 'tests' target: https://github.com/TEIC/TEI-Simple/blob/master/build.xml#L197 validates the TEI Simple ODD against the processing-model schema, and validates various instances of TEI Simple against the TEI Simple schema. That doesn't actually test the processing model elements are used properly. The 'pm' target: https://github.com/TEIC/TEI-Simple/blob/master/build.xml#L259 first creates some TEI simple XSL from the processing model documentation in the TEI Simple ODD, then creates a variant of this from teipm-ms.odd (which was a test variant requested by Council demonstrating using it for Manuscripts), and then runs various test files through both those XSL in order to produce HTML. Again, this seems to be testing the processing of the documentation of processing models, rather than the elements. (e.g. we don't seem to test 'list' or 'person' in this way?). Could someone with more experience with the TEI test system either help me design some new tests or help me migrate some of these into the processing-model branch? Many thanks, -James -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford

1 0

Pure ODD display update
by Hugh Cayless 24 Nov '15

24 Nov '15

Dear all, I’ve been spending my time on getting the Pure ODD display working in the GLs generation. I’m getting closer, I think, though there are still some issues. Can you take a look at http://teic.github.io/TEI/index.html <http://teic.github.io/TEI/index.html> (e.g. http://teic.github.io/TEI/ref-certainty.html <http://teic.github.io/TEI/ref-certainty.html>) and see if the Pure ODD display is what you were hoping for, and what bugs you can find. Issues I’m aware of are: RelaxNG display is displaying the result of evaluating data types rather than a link to the data type definition and "Used by" isn’t getting populated for macros and dataypes. What I’d really like to know is whether I’m on the right track or a different display is needed. This (unsurprisingly) turns out to be way more complicated than I’d hoped, and I haven’t even begun to work out how to alter the display for GLs output beyond HTML. This could take a while.

2 2

GitHub P6 label, anyone?
by Peter Stadler 24 Nov '15

24 Nov '15

I was just going through some tickets and came across #1400 „Remove numbered divisions“, wondering whether we need (or want) a P6 label? That way, we could start collecting issues for the day X. That would not necessarily mean that those changes be implemented in P6, but discussion is postponed until then. So, rather than simply closing the issue, we could label it first (and close it then, so it’s not polluting our issue tracker), making it easy to reopen these issues when the time comes. Cheers Peter

5 5

brett's issues
by Lou Burnard 22 Nov '15

22 Nov '15

Apologies for the delay, but (as originally promised last week) I have now finished working through all of Brett's 24 issues with chapter PH. All but 7 of them involve minor and non-controversial corrections which I have duly made, and closed the tickets. The seven remaining however might benefit from a second look by someone with domain expertise. James? Hugh? They are really very minor points but this is a precariously organized chapter which shouldnt be deconstructed too much.

2 2

Nov/Dec Telecon
by Hugh Cayless 17 Nov '15

17 Nov '15

Dear All, I’ve been remiss in scheduling our next teleconference due to some rather unfortunate family business I won’t bore you with. The end of November is tricky anyway because of Thanksgiving in the U.S.. I’ve created a Doodle poll to try to schedule it here: http://doodle.com/poll/wyuc3qiv9rkx4db6. I’ve also been very slow to say welcome to our new members, Elisa Beshero-Bondar, Elli Mylonas, Martina Scholger, and Magdalena Turska, who I believe are now subscribed to the list. We’re very glad you’re here! We’d be very pleased if you can join in this meeting, though obviously your presence is optional. I’ll be putting together an agenda, but the main business will I think be whether to release v3.0.0 with Pure ODD before the end of the year. We’ll also have to say a sad goodbye to our departing members, Fabio, Stefanie, Martin, and Paul. I expect this will probably be the last meeting of the year, given that most of us will be out for a big chunk of December, so if we have trouble scheduling it, we can push it a bit later. All the best, Hugh

4 4

GitHub tickets and new council members
by Raffaele Viglianti 13 Nov '15

13 Nov '15

Hello, I'd like to start working on tidying up our labeling system on GitHub, as we discussed at the F2F meeting. We thought about involving one of the new members in this process - who should we pick? Should we send an open call? Have the new members already been added and are reading this email? We also talked about mentoring and I think Elli wasn't assigned a mentor because she knows the job well already - though maybe working on this could be a good way of getting her acquainted with our GitHub workflow? Raff

2 1