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

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

31 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 31 Aug '15

31 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 31 Aug '15

31 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

[GitHub] Your password has changed
by GitHub 24 Aug '15

24 Aug '15

Hello TEITechnicalCouncil, We wanted to let you know that your GitHub password was changed. If you did not perform this action, you can recover access by entering tei-council(a)lists.tei-c.org into the form at https://github.com/password_reset. To see this and other security events for your account, visit https://github.com/settings/security. If you run into problems, please contact support by visiting https://github.com/contact or replying to this email.

5 7

[GitHub] Your password has changed
by GitHub 24 Aug '15

24 Aug '15

Hello TEITechnicalCouncil, We wanted to let you know that your GitHub password was changed. If you did not perform this action, you can recover access by entering james+teitechnicalcouncil(a)blushingbunny.net into the form at https://github.com/password_reset. To see this and other security events for your account, visit https://github.com/settings/security. If you run into problems, please contact support by visiting https://github.com/contact or replying to this email.

1 0

[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