Re: [tei-council] Release followup

Thanks James. In the absence of any screams of "NO DON’T!!", I’m going to go ahead with the point release and then fixing the Stylesheets build. Please don’t push to the TEI or Stylesheets repos while 2.9.1 is in progress.

On Oct 15, 2015, at 11:25 , James Cummings wrote:

I don't think I have any objections. You are right that the content model looks icky.

-James

On 15/10/15 13:12, Hugh Cayless wrote:

...

I’m not panicked, but I would like to stabilize the 2.9.0 release, and the Stylesheets build. The latter can currently *only* be done via a new release, so I would like to do a 9.4.1 release today, and then we can plan to do a nicer fix in the next release (which you’ll remember we planned to do before year’s end). https://github.com/TEIC/TEI/blob/18fe150c5cc7d46c871e2dfd32c98faad74ca55c/P5... https://github.com/TEIC/TEI/blob/18fe150c5cc7d46c871e2dfd32c98faad74ca55c/P5...<https://github.com/TEIC/TEI/blob/18fe150c5cc7d46c871e2dfd32c98faad74ca55c/P5... https://github.com/TEIC/TEI/blob/18fe150c5cc7d46c871e2dfd32c98faad74ca55c/P5...>, is, I’ll freely admit, hideous, but it does the job of permitting everything currently permitted inside <app> except <app>. I’d like to run with this, fix the release and the Stylesheets, and get everything back on track. Any objections?

...

On Oct 15, 2015, at 6:18 , Lou Burnard wrote:

I have opened a ticket, err, issue (#1345) which I think addresses the underlying problem here.

It's often the case that when something breaks one or other of our processors it's because of an underlying problem which he haven't correctly identified yet. I think that's the case here. We started out down this particular road because we wanted to address concerns about the content model of <app>'s children, and in so doing have uncovered another related issue.

So let's try to do the job properly, rather than get panicked into ad hoc short term fixes. Although I originally argued against Hugh's proposed solution #1 (fix the content model of <app>), like our esteemed shadow chancellor I have now changed my mind. (OBSCURE BRITISH POLITICAL REFERENCE NEVER MIND)

On 15/10/15 03:54, Syd Bauman wrote:

...

I'm still trying to grok this all, but Hugh, could you explain why the need for a fix is urgent? This only breaks XSD, and only XSD that uses <app>, right? (All those epigraphers and manuscripters who want <app> are smart enough to use RNG, aren't they?)

I'm not suggesting that we purposefully dally, but I'm wondering if we truly need to be stressed.

...

Yeah, I think it’s a fixable bug, but we ought to do due diligence before whacking it. The need for a fix is urgent though, so I will implement something like model.appLike in a way that we can easily yank it back out if we decide on #1. -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

-- Dr James Cummings, James.Cummings@it.ox.ac.uk mailto:James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford -- tei-council mailing list tei-council@lists.tei-c.org mailto:tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived