Possible ... but the commit that broke it was during the afternoon of Wednesday during the meeting. The DNS change wasn't until Friday wasn't it? Was there something that changed with the website on Weds?
Many thanks,
James
--
Dr James Cummings, James.Cummings(a)newcastle.ac.uk
School of English Literature, Language, and Linguistics, Newcastle University
________________________________
From: Elisa Beshero-Bondar <ebbondar(a)gmail.com>
Sent: Saturday, May 11, 2019 11:28:45 PM
To: James Cummings
Cc: tei-council(a)lists.tei-c.org
Subject: Re: [Tei-council] Jenkins build failure
Just a guess— could it be related to the DNS change? Do we need to change a line in the stylesheet that generates ePub?
Elisa
Sent from my iPhone
On May 11, 2019, at 3:00 PM, James Cummings <James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk>> wrote:
Does anyone have any suggestions why commit:
https://github.com/TEIC/TEI/commit/672a64aa68080154242a8c27e19644a88afb9e8a
and/or
https://github.com/TEIC/TEI/commit/a5892a7bbbf8212eb3f66137790c5708bb64dd7b
which are changes to the <desc> of <msFrag> seem to have broken Jenkins?
https://jenkins.tei-c.org/job/TEIP5-dev/changes
The errors from that build https://jenkins.tei-c.org/job/TEIP5-dev/242/parsed_console/ all seem to relate to the creation of EPUB and seem to cover every chapter of the Guidelines complaining about fragment identifiers.
I've spent a bit of time investigating it but haven't figured out why EPUB should be affected by this change (or what randomly changed in between this and the last successful build.) :-(
Many thanks,
James
--
Dr James Cummings, James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk>
Senior Lecturer in Late-Medieval Literature and Digital Humanities
School of English, Newcastle University
_______________________________________________
Tei-council mailing list
Tei-council(a)lists.tei-c.org<mailto:Tei-council@lists.tei-c.org>
http://lists.lists.tei-c.org/mailman/listinfo/tei-council
Got it but for some reason marked as spam. :-(
Many thanks,
James
--
Dr James Cummings, James.Cummings(a)newcastle.ac.uk
School of English Literature, Language, and Linguistics, Newcastle University
________________________________
From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at>
Sent: Friday, May 10, 2019 6:57:18 PM
To: Hugh Cayless; TEI Council
Subject: Re: [Tei-council] Testing
Hip - Hip - Hurra
Von meinem Huawei-Mobiltelefon gesendet
-------- Originalnachricht --------
Betreff: Re: [Tei-council] Testing
Von: Hugh Cayless
An: TEI Council
Cc:
Here's to unexpected success!
On Fri, May 10, 2019 at 1:28 PM Raffaele Viglianti <raffaeleviglianti(a)gmail.com<mailto:raffaeleviglianti@gmail.com>> wrote:
Got it!
On Fri, May 10, 2019 at 1:26 PM Hugh Cayless <philomousos(a)gmail.com<mailto:philomousos@gmail.com>> wrote:
Let me know if you get this
_______________________________________________
Tei-council mailing list
Tei-council(a)lists.tei-c.org<mailto:Tei-council@lists.tei-c.org>
http://lists.lists.tei-c.org/mailman/listinfo/tei-council
Thank you, Peter. So sweet. (And I'm not going to *try* to take it
down. Just worried.)
Peter Stadler writes:
> Re question 1)
> There’s also https://roma.tei-c.de/ but that’s pointing at the same
> instance as https://roma2.tei-c.org/. But I think the bottleneck is
> OxGarage which might choke on multiple concurrent requests. So, I
> updated my OxGarage stack (which roma2 uses) to run three instances
> (behind a load balancer) — just for you, Syd :) I’d be happy to get
> some feedback about whether and how you were still(?) able to bring
> it down.
1
0
test
by Scholger, Martina (martina.scholger＠uni-graz.at)
06 Mar '19
I am teaching a class on TEI schemas Fri 03-08 10:00/12:00-05:00.
At the moment
* https://tei-c.org/tools/roma/ does NOT work
* https://roma.tei-c.org/ does NOT work -- bad certificate
* https://roma2.tei-c.org/ does work
Question 1: Are there other instances of Roma runinng that I might
use? Does anyone happen to have one up? (I used to have
one at Brown, but never set it up at Northeastern.)
Question 2 (mostly for Raff): Bad or good idea to show them RomaJS?
Hello Council,
Now that the new release is (mostly) behind us (thanks Elli, Hugh, at al!),
I wanted to give you a quick update about RomaJS and attempt to schedule a
call for the second week of February to discuss development and get started
on planning user testing.
DOODLE for meeting: https://doodle.com/poll/8p7exq3vptpb8g9t
I've just updated the demo at http://mith.us/romajs. Feel free to try it
out and let me know what's broken.
I've been using waffle.io to keep track of GitHub issues and I found it
very helpful to make sure what I do is reflected as much as possible into
GitHub. The board is public and accessible here:
https://waffle.io/TEIC/romajs
If you have permissions on Github for TEIC, you will also be able to do
stuff here if you log in.
All of this is also available on GitHub issues, I just like the kanban
style of waffle.
To get a summary of what I've been working on since mid-December have a
look at the "Done" column on the right. Here's a couple of highlights:
- Create new classes and new elements in custom namespace
- Implement revert to source button
- Update material components web (you'll notice that the UI is pretty much
the same but a little slicker)
- Split updateOdd reducers (huge task with little practical effects, but
that has greatly affected code readability)
Please fill in the doodle and don't hesitate to ask questions here or on
slack (there's a romajs channel).
Thank you!
Raff
Hi all - I have notes that include improvements to tcw22 from the latest
release experience. (The Raven...) Should I go ahead and edit?
what is the protocol? --elli
If I understand Raff's suggestion correctly, then I would support the restrictive approach to only allow users possibilities of making dataTypes that 'Make Sense'. If they want to do something so weird as put an elementRef into the content of a dataSpec then they clearly should understand it well enough to be hand-editing their ODD, and then explain to us why it should be allowed in RomaJS. (But generally, RomaJS doesn't have to do everything that is possible, but only what we recommend people do.)
Many thanks,
James
--
Dr James Cummings, James.Cummings(a)newcastle.ac.uk
Senior Lecturer in Late-Medieval Literature and Digital Humanities
School of English, Newcastle University
________________________________
From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Syd Bauman <s.bauman(a)northeastern.edu>
Sent: 02 February 2019 12:04
To: lou.burnard(a)retired.ox.ac.uk; TEI Council
Subject: Re: [Tei-council] dataSpec content
[Trying to channel Raff, who is probably still asleep.]
1. Actual content model (that Raff was discussing -- i.e., a model
against which all of our current dataSpec/content elements are
valid):
( dataRef* | valList | textNode | aDr | avL | atN )
aDr = element alternate { dataRef* }
avL = element alternate { valList }
atN = element alternate { textNode }
2. No, Raff was not suggesting any change to content models, only to
his user interface in RomaJS.
But now that you point it out, it would probably make sense to
disallow at least <empty>, <anyElement>, <elementRef>, & <classRef>,
and probably even <macroRef> from the <content> of a <dataSpec>.
> Firstly, I dont understand your pseudocode content model. Does it
> mean the same as the following:
>
> <alternate minOccurs="1" maxOccurs="undefined">
> <elementRef key="dataRef"/>
> <elementRef key="valList"/>
> <elementRef key="textNode"/>
> </alternate>
>
>
> Are you proposing to change the current content model of <content>
> or of <dataSpec> ?
>
> In either case, I suggest defining a class model.dataSpecPart might
> help.
>
> Or is it just about how selective your interface should be in what
> it permits, perhaps as a not-so-subtle way of avoiding the
> question?
>
> Current practice in defining dataSpecs is constrained by what was
> done in P4: I re-used the <content> element here because we also
> used it to define the expansion of macroSpecs (i.e parameter
> entities) back in the day, but that's a historical explanation.
> This over-generates, as you rightly say: it's not at all clear what
> it might mean to put e.g. an elementRef into the content of a
> dataSpec!
_______________________________________________
Tei-council mailing list
Tei-council(a)lists.tei-c.org
http://lists.lists.tei-c.org/mailman/listinfo/tei-council
