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

F2F Minutes Frozen
by Hugh Cayless 10 Jun '15

10 Jun '15

I’m getting ready to publish the minutes from Ann Arbor, so I have frozen the Google Doc. If you have any remaining changes you want to put in, you should let me know immediately. Thanks, Hugh /** * Hugh A. Cayless, Ph.D * Chair, TEI Technical Council * Duke Collaboratory for Classics Computing (DC3) * hugh.cayless(a)duke.edu * http://blogs.library.duke.edu/dcthree/ **/

1 0

Re: [tei-council] dataypes: the never ending story
by Syd Bauman 09 Jun '15

09 Jun '15

I understand completely that conversion to Pure ODD is a big deal, but is converting <datatype> to <dataSpec> going to have a much larger impact than using <elementRef> instead of <rng:ref>, etc.? My point is that conversion to Pure ODD is a big deal either way, no? I think you're right, project management, and maybe even some money, is in our future. (And I can already hear Hugh muttering "git-fork" under his breath. :-) > my heart slightly fails me when I start thinking about the side > effects of dropping <datatype> and converting all the Guidelines to > <dataSpec>. The existing .odd files out there stop working > (potentially), Roma stops working, as does its little cousin > Byzantium, the documentation of the Guidelines probably gets hosed, > a small myriad of utilities fall over. > > I hate to say it, but changes of this scale need a bit of project > management. > > else you need a team of dedicated people fixing things on the fly.

2 1

dataypes: the never ending story
by Lou Burnard 09 Jun '15

09 Jun '15

If we are to abide by Martin's eminently suggestion of permitting the new pure odd dataRef to coexist with the current <dataype> mechanism, I can't see any way out of doing the following a) make a set of new <dataSpec> elements corresponding with the existing <macroSpec type="dt">s b) since @ident values are supposed to be unique, these new things will all have to have different names (I suggest teidata.foo rather than data.foo) c) the current section 1.4.2 on datatype macros (#DTYPES, in #ST) will also need to be cloned, or substantially revised, since this is where the pesky things are actually defined Anyone got any better ideas?

3 11

unencoded words that maybe should be
by Syd Bauman 09 Jun '15

09 Jun '15

I'm going over the minutes, and strolled across bug 740. It lists an instance where a few words that should have been encoded as <gi> were not. I wondered about others. So I created http://bauman.zapto.org/~syd/temp/4TEICouncil/list-of-PCDATA-idents.html In principle, it is probably a useful task for someone to go through this set and find the few that really should be encoded as <gi> or <ident> and fix them. In fact, it's obviously a huge task that would take multi-person coordination and lots of time for little benefit.

1 0

iso schemaron syntax
by Lou Burnard 08 Jun '15

08 Jun '15

Does this look vaguely right <sch:assert test="name(parent(.))='dataSpec' and not(contains(dataRef))">An alternate element inside a dataSpec may contain only dataRef children </sch:assert> ? #tooLazyToLookItUp

2 2

oxygen-tei plugin
by Martin Holmes 08 Jun '15

08 Jun '15

Hi all, Sebastian released a new version of the Stylesheets yesterday, prompting a new version of the oxygen-tei plugin, so I've taken the opportunity of this release to enact some changes we agreed on a while ago: The new version number of the plugin is 3.0.0; this disentangles its version numbering from P5 releases. The new location and file name for the plugin is: http://sourceforge.net/projects/tei/files/oxygen-tei/oxygen-tei-3.0.0.zip The file is now named oxygen-tei-x.x.x.zip to match the actual project name and to distinguish it from the debian package, and it's in a new folder called "oxygen-tei". I've left the old "tei-oxygen" folder on SF in place for the moment, just in case, so right now there's additional potential confusion, but if all is well after a couple of days I'll do two things: 1. Move the last couple of releases with the old filenames into the new folder and give them new filenames, adjusting the updateSite.oxygen file accordingly. 2. Remove the old folder and the rest of the old versions. Please yell if you don't think I should do either of those things. Cheers, Martin

2 2

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