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

Implementation of @selector on <rendition>
by Martin Holmes 08 Jun '15

08 Jun '15

At the FtF I got the go-ahead to implement the feature request described in detail here: <http://wiki.tei-c.org/index.php/Proposal_for_@selector_attribute_on_renditi…> with the proviso that I should once more call it to everyone's attention for any final objections before I go ahead and do it. If I don't hear objections in the next few days I'll make this change. Cheers, Martin

1 0

nvdl validation of Spec files in Oxygen not working
by Martin Holmes 08 Jun '15

08 Jun '15

Lou and I discovered the other day that the current setup by which Oxygen validates Spec files when you're editing them does not work for some reason. That means that when you're editing a Spec file, you have to be extra careful not to screw anything up. We don't know why it's not working; it looks like something changed around the time of the release of Oxygen 16.1. Cheers, Martin

1 0

defaultVal deprecation
by Martin Holmes 08 Jun '15

08 Jun '15

Hi all, I think a couple of messages got lost when the lists went weird last week, so I thought I should summarize something I need feedback on. I was under the impression that I had the go-ahead to remove defaultVals when the Council was convinced it was a good idea, but Syd reminded me that we should actually deprecate things for a couple of years before removing them. However, there is no mechanism for deprecating <defaultVal>; it's not a member of att.deprecated so it can't have @validUntil added to it. So I hereby recommend that <defaultVal> be added to att.deprecated. If I don't hear any shouts of objection within the next couple of days I'll do that. That of course will require that the Guidelines build then do something with @validUntil on <defaultVal>. That will be my next order of business on this ticket. Meanwhile, I've created this wiki page with all the current defaultVals: <http://wiki.tei-c.org/index.php?title=DefaultVal_candidates_for_removal> It turns out that there are no required attributes with defaultVal, so that low-hanging fruit doesn't exist. Cheers, Martin

1 0

New Jenkins build jobs for bleeding-edge and stable plugin
by Martin Holmes 04 Jun '15

04 Jun '15

Hi all, I have what looks like a working setup on my Jenkins box for building two versions of the Oxygen TEI plugin. The original build job, "oxygen-tei", to which some of you may have subscribed, is now replaced by "oxygen-tei-bleeding", to which you can subscribe here: <http://teijenkins.hcmc.uvic.ca/job/oxygen-tei-bleeding/lastSuccessfulBuild/…> while there is also now "oxygen-tei-stable", to which if you want you can subscribe here: <http://teijenkins.hcmc.uvic.ca/job/oxygen-tei-stable/lastSuccessfulBuild/ar…> The idea is that oxygen-tei-bleeding builds with the latest plugin code against the latest trunk builds of P5 and the Stylesheets, enabling us to see if any change to any of these has broken the plugin; oxygen-tei-stable builds with the latest plugin code, but against the current release versions of P5 and the Stylesheets, enabling us to see what a release version of the plugin would look like if either we or Syncro built one right now. The build is now being done with ant, and in addition to these two targets, there's also: ant syncro which builds a version for the Syncro folks using the latest stable P5 and Stylesheets, as they would do when creating a build for a new Oxygen release. Up to now they've been using our original update-and-upload.sh script, and then preventing it from uploading to SourceForge as it tries to do. That script also requires that you _know_ the correct versions of P5 and the Stylesheets, and supply them correctly on the command line; the new ant build script works that information out for itself. Finally, there is: ant stable which is what our release technician would use during a P5 release process, or what we would use to release an official build of our version of the plugin. This builds in the same way as the version above, but also offers to upload the result to SourceForge, and creates a new version of the updateSite.oxygen file which it offers to upload to tei-c.org. This should make releasing a new plugin version much easier, I hope (although it can only truly be tested for real when we come to release a version, so I'd like to be the one who runs it for real the first time in case something goes wrong). I've added the new job configs for Jenkins to SVN, where James can find them for the Oxford Jenkins, when he has the time. This is all brand-new and only gently tested, so let me know if you try anything, and please report any problems with as much detail as you can. Cheers, Martin

3 4

Minutes Doc and scheduling
by Hugh Cayless 04 Jun '15

04 Jun '15

Hope that by now everyone’s made it home safely. Can we all look over the minutes doc while the meeting is still fresh in our memories and correct/add anything that’s missing? I will plan to freeze the document on Friday June 5th and convert the minutes over for the website. Re scheduling the next telecon: Do we want to try to stick with Fridays at 09:00 or 10:00 EDT? That’s 06:00/07:00 PDT, 14:00/15:00 BST, 15:00/16:00 CEST. I’m flexible as to day of the week during the summer—when I’m not actually away, of course. Fridays in June/July look particularly difficult. I’ll either be on vacation or away on business for several of them. Doodle poll for June telecon: http://doodle.com/q5ixp76erdceeydk <http://doodle.com/q5ixp76erdceeydk> Doodle poll for July telecon: http://doodle.com/xy2hqrpk9swnzhzd <http://doodle.com/xy2hqrpk9swnzhzd> Doodle poll for August telecon: http://doodle.com/txi5p2cn3mhmfizr <http://doodle.com/txi5p2cn3mhmfizr> Thanks to all of you for your hard work last week. It felt to me like we covered a lot of ground. All the best, Hugh

8 10

defaultVals for removal
by Martin Holmes 03 Jun '15

03 Jun '15

Hi all, Re this ticket: <https://sourceforge.net/p/tei/feature-requests/546/?page=1> I was under the impression from our discussion at the FtF that my job was to present the case for removing defaultVals one by one, and then remove them if Council did not object. However, Syd points out that this should be done through deprecation, so I've now added @validUntil on <defaultVal> on att.fragmentable/@part. We'll see what shows up in the Guidelines build as a result -- I'm not sure whether there's adequate handling in the Stylesheets for it. Meanwhile, I've generated a complete list of atts with defaultVal here: <http://wiki.tei-c.org/index.php/DefaultVal_candidates_for_removal> since that seems to be what Syd was expecting. He was tasked with removing those which are on required attributes, but there don't seem to be any of those. Cheers, Martin

1 1

Re: [tei-council] [tei:feature-requests] #546 <defaultVal> should be removed from all specs
by Syd Bauman 02 Jun '15

02 Jun '15

Martin -- We'll talk tomorrow, I'm sure, but I'm not sure this is OK. I know you hate default values, as do I, and we want to get rid of them. But I'm not sure it's acceptable to yank them out w/o warning. DTD users might be upset. Besides, changing the semantics of a value like that is the sort of thing users need warning about. Those who actually have part="N" explicitly expressed may well be using it to say "I can't tell if this is a fragment or not". MH> att.fragmentable's @part now has no defaultVal, and the "N" value MH> now actually means "no", as it should. Rev 13232.

2 6

dataSpec content
by Lou Burnard 31 May '15

31 May '15

I'm still poking away at my datatype replacement ticket ... We agreed that <dataSpec> should be used to fully specify a TEI-defined datatype and also noted in passing that its existing <content> child needed additional constraints (e.g, it shouldnt allow you to supply elementRefs) In fact it seems to me that the "content" of a dataSpoe should be much more restrictive: I'd like for it to contain just <alternate>, <sequence>, <valList>, or <dataRef>, with the additional constraint that <alternate> and <sequence>s it contains can contain only one or more <dataRef>s If no-one has any counterproposal that's what i am planning to try to implement anyway.

2 1

Fast-track a simple ticket
by Martin Holmes 31 May '15

31 May '15

Hi all, This ticket: <https://sourceforge.net/p/tei/feature-requests/561/> arose out of our re-working yesterday of Laurent's standoff proposal. I'd like to fast-track it if we can; it seems straightforward to me, and doesn't involve any Birnbaum issues. While I get around to figuring out the actual change to the Spec file, could you all check to see if you have any objections to it in principle? Cheers, Martin

6 7

rng:group but no rng:choice
by Peter Stadler 31 May '15

31 May '15

I just stumbled across the content model of climate (and there are more …) which looks like <content> <rng:group> <rng:zeroOrMore> <rng:ref name="model.headLike"/> </rng:zeroOrMore> <rng:choice> <rng:group> <rng:oneOrMore> <rng:ref name="model.pLike"/> </rng:oneOrMore> </rng:group> <rng:group> <rng:oneOrMore> <rng:ref name="model.labelLike"/> </rng:oneOrMore> </rng:group> </rng:choice> <rng:zeroOrMore> <rng:choice> <rng:ref name="model.noteLike"/> <rng:ref name="model.biblLike"/> </rng:choice> </rng:zeroOrMore> <rng:zeroOrMore> <rng:ref name="climate"/> </rng:zeroOrMore> </rng:group> </content> My question is: is there some magic to the surrounding rng:group or could that be deleted? (I don’t intend to do so but was just wondering …) Best Peter

2 2