Martina (and all) -- where are we on the big nesting TEI issue? I had planned to spend my TEI time between now and release working on that, so at this release <TEI> would be able to nest, and the documentation would include this possibility (whether we deprecated use of <teiCorpus> now or not). But a) I'm not sure I'm clear to move ahead on that; and b) I'm wondering if I shouldn't be spending time on the Stylesheets issues instead? I realize that means bumping nesting-<TEI> another 6 months (which would make *me* sad), but that may not be a bad thing if we're still waiting for LR's post to TEI-L and the fallout therefrom.
Hi Syd-- Well, we have a week of activity before officially we go into
refrigeration. I'd be in favor of deferring the nesting of TEI elements for
a moment, but others may feel differently. For right now, it seems a higher
priority to resolve the release-blocking problems on dev connected with
simplePrint.odd (re https://github.com/TEIC/TEI/issues/1853 and
https://github.com/TEIC/Stylesheets/issues/370 ), doesn't it?
Among other much tickets I've added from my pile to the 3.6.0 release next
month, I'm (finally!) returning to work on the measurement issue (
https://github.com/TEIC/TEI/issues/1707 ) , and hope I can get this put
together in a way that passes build tests in time to review and merge in to
dev for the release. I think I'm likely to need some help reviewing and
checking everything connected with units and formula conversions here so
expect occasional pips of confusion and shrieks of anguish from me next
week.
Thanks,
Elisa
On Sun, Jun 23, 2019 at 11:15 AM Syd Bauman
Martina (and all) -- where are we on the big nesting TEI issue? I had planned to spend my TEI time between now and release working on that, so at this release <TEI> would be able to nest, and the documentation would include this possibility (whether we deprecated use of <teiCorpus> now or not).
But a) I'm not sure I'm clear to move ahead on that; and b) I'm wondering if I shouldn't be spending time on the Stylesheets issues instead? I realize that means bumping nesting-<TEI> another 6 months (which would make *me* sad), but that may not be a bad thing if we're still waiting for LR's post to TEI-L and the fallout therefrom. _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
It would be a bit of a shame to lose it. I could work on it when I’m back home this weekend. Or on the plane on Friday for that matter...
On Jun 23, 2019, at 16:15, Syd Bauman
wrote: Martina (and all) -- where are we on the big nesting TEI issue? I had planned to spend my TEI time between now and release working on that, so at this release <TEI> would be able to nest, and the documentation would include this possibility (whether we deprecated use of <teiCorpus> now or not).
But a) I'm not sure I'm clear to move ahead on that; and b) I'm wondering if I shouldn't be spending time on the Stylesheets issues instead? I realize that means bumping nesting-<TEI> another 6 months (which would make *me* sad), but that may not be a bad thing if we're still waiting for LR's post to TEI-L and the fallout therefrom. _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
Dear Syd and all,
Although we don't want to make you sad 😊 Syd, I think the release-blocking problem with the Stylesheets must be our priority so close to the release.
As for the nesting TEI: my understanding was that we already decided on the nesting TEI element, regardless of the deprecation of teiCorpus.
I am aware that we agreed on having LR propose this to the list, but on second thought my feeling is that such a suggestion should better be coming from the Council. I would therefore suggest that I draft an email to the list and circulate it to you.
Best,
Martina
-----Ursprüngliche Nachricht-----
Von: Tei-council
On Jun 23, 2019, at 16:15, Syd Bauman
wrote: Martina (and all) -- where are we on the big nesting TEI issue? I had planned to spend my TEI time between now and release working on that, so at this release <TEI> would be able to nest, and the documentation would include this possibility (whether we deprecated use of <teiCorpus> now or not).
But a) I'm not sure I'm clear to move ahead on that; and b) I'm wondering if I shouldn't be spending time on the Stylesheets issues instead? I realize that means bumping nesting-<TEI> another 6 months (which would make *me* sad), but that may not be a bad thing if we're still waiting for LR's post to TEI-L and the fallout therefrom. _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
It isn’t looking as if this sent, so I am trying again... ********* Hi Syd-- Well, we have a week of activity before officially we go into refrigeration. I'd be in favor of deferring the nesting of TEI elements for a moment, but others may feel differently. For right now, it seems a higher priority to resolve the release-blocking problems on dev connected with simplePrint.odd (re https://github.com/TEIC/TEI/issues/1853 and https://github.com/TEIC/Stylesheets/issues/370 ), doesn't it? Among other much tickets I've added from my pile to the 3.6.0 release next month, I'm (finally!) returning to work on the measurement issue (https://github.com/TEIC/TEI/issues/1707 ) , and hope I can get this put together in a way that passes build tests in time to review and merge in to dev for the release. I think I'm likely to need some help reviewing and checking everything connected with units and formula conversions here so expect occasional pips of confusion and shrieks of anguish from me next week. Thanks, Elisa
On Sun, Jun 23, 2019 at 11:15 AM Syd Bauman
wrote: Martina (and all) -- where are we on the big nesting TEI issue? I had planned to spend my TEI time between now and release working on that, so at this release <TEI> would be able to nest, and the documentation would include this possibility (whether we deprecated use of <teiCorpus> now or not). But a) I'm not sure I'm clear to move ahead on that; and b) I'm wondering if I shouldn't be spending time on the Stylesheets issues instead? I realize that means bumping nesting-<TEI> another 6 months (which would make *me* sad), but that may not be a bad thing if we're still waiting for LR's post to TEI-L and the fallout therefrom. _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
EBB> For right now, it seems a higher priority to resolve the EBB> release-blocking problems on dev connected with simplePrint.odd EBB> ..., doesn't it? Well, yes, but the question is whether *I* should be tackling the nesting-<TEI> issue (for which I will find the schema changes easy, but the prose changes will take me a long time because I'm slow at that sort of stuff), or the stylesheet problems. (If someone else is already 1/2-way to fixing it, speak up! :-) HC> It would be a bit of a shame to lose it. I could work on it when HC> I’m back home this weekend. Or on the plane on Friday for that HC> matter... Thanks. Might be a good idea. Although to be fair, we would not be losing it, just not tucking it in until next release. (When, honestly, it might make a bit more sense, anyway.) MS> ... my understanding was that we already decided on the nesting MS> TEI element, regardless of the deprecation of teiCorpus. Right; I'm just talking about timing, not whether-or-not. (And in part, timing so we can get feedback from community.) MS> I am aware that we agreed on having LR propose this to the list, MS> but on second thought my feeling is that such a suggestion should MS> better be coming from the Council. I would therefore suggest that MS> I draft an email to the list and circulate it to you. My thought is "go, girl!". But perhaps the right thing to do is for you to write up a draft, and send it to LR as well as to us so that he can chime in, too? EBB> It isn’t looking as if this sent, so I am trying again... I had gotten it just fine.
Sorry to add fuel to the fire, but I have also just sent a very simple PR
to generate different p5subset.json files for each supported languages. If
this gets included in the release, the Vault will have all the data needed
for Roma (beta). If not, I'll keep pulling data from my server until the
next release.
I tested locally and got the output I expected, but it would be great to
have someone else look it over and merge it into dev.
https://github.com/TEIC/TEI/pull/1890
Best,
Raff
On Sun, Jun 23, 2019 at 5:51 PM Syd Bauman
EBB> For right now, it seems a higher priority to resolve the EBB> release-blocking problems on dev connected with simplePrint.odd EBB> ..., doesn't it?
Well, yes, but the question is whether *I* should be tackling the nesting-<TEI> issue (for which I will find the schema changes easy, but the prose changes will take me a long time because I'm slow at that sort of stuff), or the stylesheet problems. (If someone else is already 1/2-way to fixing it, speak up! :-)
HC> It would be a bit of a shame to lose it. I could work on it when HC> I’m back home this weekend. Or on the plane on Friday for that HC> matter...
Thanks. Might be a good idea. Although to be fair, we would not be losing it, just not tucking it in until next release. (When, honestly, it might make a bit more sense, anyway.)
MS> ... my understanding was that we already decided on the nesting MS> TEI element, regardless of the deprecation of teiCorpus.
Right; I'm just talking about timing, not whether-or-not. (And in part, timing so we can get feedback from community.)
MS> I am aware that we agreed on having LR propose this to the list, MS> but on second thought my feeling is that such a suggestion should MS> better be coming from the Council. I would therefore suggest that MS> I draft an email to the list and circulate it to you.
My thought is "go, girl!". But perhaps the right thing to do is for you to write up a draft, and send it to LR as well as to us so that he can chime in, too?
EBB> It isn’t looking as if this sent, so I am trying again...
I had gotten it just fine. _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
participants (5)
-
Elisa Beshero-Bondar
-
Hugh Cayless
-
Raffaele Viglianti
-
Scholger, Martina (martina.scholger@uni-graz.at)
-
Syd Bauman