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

[GitHub] Please reset your password
by GitHub 24 Aug '15

24 Aug '15

We heard that you lost your GitHub password. Sorry about that! But don’t worry! You can use the following link within the next day to reset your password: https://github.com/password_reset/00d3e5078f85464a1ac91e3975609ef5c77315e27… If you don’t use this link within 24 hours, it will expire. To get a new password reset link, visit https://github.com/password_reset Thanks, Your friends at GitHub

1 0

Re: [tei-council] [TEI-L] <relation> w/in <placeList>
by Syd Bauman 21 Aug '15

21 Aug '15

Re: discussion Gabby & Martin are having on TEI-L I think this is evidence in support for a linked data block element that is a child of <text> but not in <front>, <body>, or <back> that is specifically for this kind of stuff (<relation>s).

1 0

[GitHub] Please verify your email address.
by GitHub 21 Aug '15

21 Aug '15

Hey, we want to verify that you are indeed "TEITechnicalCouncil". Verifying this address (tei-council(a)lists.tei-c.org) will let you receive notifications and password resets from GitHub. If you wish to continue, please follow the link below: https://github.com/users/TEITechnicalCouncil/emails/16451158/confirm_verifi… If you’re not TEITechnicalCouncil or didn’t request verification, you can ignore this email.

4 4

Validating Specs
by James Cummings 21 Aug '15

21 Aug '15

Hiya, I'm starting to look at creating individual spec files for the processing model documentation additions to the Guidelines and when I loaded up some random spec files (e.g. in SF svn: P5/Source/Specs/affiliation.xml) to use as a model I notice it didn't validate. We added an xml-model of: <?xml-model href="http://tei.it.ox.ac.uk/jenkins/job/TEIP5/lastSuccessfulBuild/artifact/relea…" type="application/xml" schematypens="http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0"?> to these some time back. (And part of me wants to point out that maybe this should be http://bits.nsms.ox.ac.uk:8080/ or we should set up jenkins really to run on tei.it rather than use some URL rewrites...) However, the error message I'm getting in oXygen is: "Attribute @xsl:dummy-for-xmlns is not allowed on element <xsl:stylesheet>" I can't find where this is being caused. It doesn't seem to be in our p5odds.rng or p5odds.isosch files. Any suggestions? -James -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford

2 2

SVN Users
by Hugh Cayless 20 Aug '15

20 Aug '15

Looks like we can achieve a happier SVN to Git conversion if we supply Git with a mapping between SourceForge usernames and proper names + email addresses in the form hcayless = Hugh Cayless <philomousos(a)gmail.com> I’ve started a spreadsheet with usernames who’ve committed to our repo at https://docs.google.com/spreadsheets/d/1N8hIBphezGsNB0SvEx7wSamyshNrszeNrlm… <https://docs.google.com/spreadsheets/d/1N8hIBphezGsNB0SvEx7wSamyshNrszeNrlm…> Can you all please pitch in to help fill it out? Thanks, Hugh

5 19

Fwd: Re: editing the TEI stylesheets
by James Cummings 19 Aug '15

19 Aug '15

Forwarding this reminder to tei-council to remind them that they need to keep a watching eye on such pull requests. (Once set up, we should get notifications sent to tei-council if possible) -James -------- Forwarded Message -------- Subject: Re: editing the TEI stylesheets Date: Wed, 19 Aug 2015 09:43:31 +1200 From: Stuart A. Yeates <syeates(a)gmail.com> To: James.Cummings(a)it.ox.ac.uk <James.Cummings(a)it.ox.ac.uk> CC: Sebastian Rahtz <sebastian.rahtz(a)it.ox.ac.uk> OK, so I sent a pull request almost a week ago https://github.com/TEIC/Stylesheets/pull/114 Do I need to notify someone? Or has feedback gone somewhere I'm missing... cheers stuart -- ...let us be heard from red core to black sky On Wed, Aug 12, 2015 at 10:01 PM, James Cummings <James.Cummings(a)it.ox.ac.uk <mailto:James.Cummings@it.ox.ac.uk>> wrote: Hi Stuart, The TEI Technical Council is currently reviewing how it uses GitHub as part of examining whether it is a suitable replacement for SourceForge in moving Guidelines development there. As you know, it moved the Stylesheets (and other software) building there some time ago. Although you (and various others) are members of the Stylesheets repository I believe the correct github etiquette is to fork, then issue a pull request. However, I think as long as you are flagging that you are making the change (or open an issue and then make the change as a result of that) it should probably be fine. (Though when you say 'regularise the display of attribute values' I'd be interested to know what you mean by regularise. There are some options and logic already in there.) The change in your forked version won't get looked at by Jenkins. We're also looking at whether some of the GitHub hosted alternative continuous integration systems might replace Jenkins. So, to be honest, you could do either, but fork+change+pull-request will ensure that it gets other eyes on it before going into the system. Jenkins uses the most up-to-date stylesheets when next building the Guidelines. I know it used to email when doing commits to the Guidelines SF SVN repository that broke something (or more accurately when someone committing around the same time as you broke something ;-) ) and I'm assuming that is still the case. I don't think it emailed just when it was running a job based on your commits...just when that job failed and your commit was one of those possible causes. That is my understanding at least, some of our council github gurus may correct me. -James On 12/08/15 10:26, Stuart A. Yeates wrote: I've got a change I'd like to make to the stylesheets used to generate the HTML version of the standard (a minor change to regularise the display of attribute values), but I'm not quite sure how to go about it. Do I just push a change request to https://github.com/TEIC/Stylesheets ? Or fork it? Does that get tested by jenkins? Jenkins used to send me emails when it ran a job based on my commits, but I've not seen one for a couple of recent commits, is that because I'm not on the council any more? cheers stuart -- ...let us be heard from red core to black sky -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk <mailto:James.Cummings@it.ox.ac.uk> Academic IT Services, University of Oxford -- Dr James Cummings, Academic IT Services, University of Oxford TEI Consultations: tei(a)it.ox.ac.uk

4 12

Validation errors in the Guidelines HTML output
by Martin Holmes 14 Aug '15

14 Aug '15

Hi all, I just discovered the VNU HTML validator, and I'm using it on another project; just for fun I ran it on a clean Guidelines build, and there seem to be about 150 errors, mostly minor and easily fixable. But it caused me to wonder why our build process didn't catch them, and I'm going to look into that. Validating modern HTML is notoriously difficult, but we should do the best we can, I think. Cheers, Martin

2 2

langUsage content model
by Lou Burnard 11 Aug '15

11 Aug '15

The process of TEI content models proceeds apace and (as might be expected) is turning up a few oddities in some unfrequented corners. For example, the content model of <langUsage> is currently (in the source) <content> <oneOrMore xmlns="http://relaxng.org/ns/structure/1.0"> <choice>  <ref name="language"/> </choice> </oneOrMore> </content> Now, this is clearly nonsense : you can't have an alternation with just one option. But did we really want to remove the possibility for having a purely documentary <langUsage> such as <p>Contains various unrecognised Polynesian languages</p>? Can anyone remember why we made this change ? I would have expected to see something like <choice> <oneOrMore> <rng:ref name="model.pLike"/> </oneOrMore> <oneOrMore> <rng:ref name="language"/> </oneOrMore> myself.

4 5

pure odd update
by Lou Burnard 10 Aug '15

10 Aug '15

I've now managed to get the P5-Pure branch of the P5 source up to date with the rest of the world, and have successfully run the P5 test suite (almost) to completion. *It would be very helpful if someone else could check this branch out and confirm that it works for them too!* The main difference is that all datatypes are now expressed using the new dataSpec and dataRef elements we discussed approx 3 million years ago. This in turn means that the old data.foo macroSpecs are now redundant, (we now use dataSpecs called teidata.foo). I have however left the old macroSpecs in the build, since their absence obviously causes existing ODDs that reference them to fall over. It's a pain however, and I would really like to get data.foo deprecated as soon as possible. Only a few (like 2 ore 3) of our test ODDs actually refer to them, but I've no way of telling how many ODDs out there in the wild do, nor how upsetting their maintainers would find it to be told to turn <rng:ref name="data.foo"/> into <dataRef key="teidata.foo"/> passim et seriatim (If you're wondering, the "(almost)" above means that my poor little laptop gave up trying to compile the massive tei_allPlus.odd.processed into tei_allPlus.rng ... probably the heat.)

4 35

more daft alternates
by Lou Burnard 10 Aug '15

10 Aug '15

Something similar occurs in <fvLib> which currently has a model <zeroOrMore xmlns="http://relaxng.org/ns/structure/1.0"> <choice> <ref name="model.featureVal"/> </choice> </zeroOrMore> and in <classes> which currently is <choice xmlns="http://relaxng.org/ns/structure/1.0"> <zeroOrMore> <ref name="memberOf"/> </zeroOrMore> </choice> I'm regarding both of these as corrigible errors in the main P5 source and correcting them. But would appreciate feedback on the <langUsage> case.

1 0