November 2017 - Tei-council

naming odd4odds when it's in Exemplars/
by Syd Bauman 07 Nov '17

07 Nov '17

In Prague we agreed that odd4odds should be put into Exemplars/ and thus the oXygen framework, and that I should have that ready by the conference (on which I'm giving a talk on it). IIRC we decided to call it "tei_customization.odd" (and thus .rng, .rnc, etc.). I was recently reminding Martin of this schema and the differences between it and tei_odds, and he wondered aloud if we shouldn't think of tei_customization as a schema to use when creating a TEI customization that is a profile of, or subset of, or constraint of the TEI. (I.e., the set of documents that conform to the customized TEI is a proper subset of the set of documents that conform to tei_all.) And that we think of tei_odds as a schema to use when creating a TEI customization that is an extension of the TEI. That might mean renaming them to tei_customization_extension and tei_subset_customization or some such. Thoughts? (Remember that the present problem we are worrying about is how to explain to the oXygen user the difference between the two. If I understand correctly, we only get to present the user with the name of the thing, no pop-up or mouse-over gloss available. However, we do get to put comments in the template. :-)

2 1

dreaded conflicting ID types
by Syd Bauman 06 Nov '17

06 Nov '17

The odd4odds RELAX NG schema (soon to be tei_customization.rng in Exemplars/ unless someone comes up with a better name) is itself invalid when ID/IDREF checking is on (in oXygen), or the '-i' switch is not present (using `jing`). This, of course, would break the build process unless we special-case it. And, as you can see in the documentation for the schema, this has been a well-known situation for this schema for a long time. The current version is not readily available, as I am working on it. The version of the schema[1] and the documentation[2] that I showed in Prague are still easily available. Here are the error messages I'm getting from `jing` (w/o '-i') from that version of the schema, re-written a bit for readability: | 877:16: error: conflicting ID-types for "@xml:id" of <tei:sequence> | 1057:14: error: conflicting ID-types for "@defaultPhase" of <sch:schema> | 1037:14: error: conflicting ID-types for "@defaultPhase" of <sch:schema> | 1085:14: error: conflicting ID-types for "@defaultPhase" of <sch:schema> | 1016:14 error: conflicting ID-types for "@defaultPhase" of <sch:schema> Of course, if we fix the latter 4 messages by making @defaultPhase NCName instead of IDREF, something else crops up instead (@id of <sch:rule>), as the errors are not from the Schematron declarations, really, but rather from our definitions of "anyElement-xenoData", "anyElement-egXML", "anyElement-content", and "anyElement-datatype". (The first error is from the definition of "sch_foreign-element".) Excluding elements from the Schematron and TEI namespaces form all of these macros fixes this problem. But of course, that's not OK. You might very well want TEI elements inside your Schematron assertions, and you might very well want to give example code of Schematron in your <egXML>. Besides, it would require altering the Schematron schema, which rubs me the wrong way. Before I go special-casing this particular schema in the build process (so it is validated w/ '-i', as all should be in my opinion) I wanted to know if there are any other solutions I'm missing. Notes ----- [1] http://www.wwp.neu.edu/outreach/seminars/_current/handouts/ODD_exercise_sup… [2] http://www.wwp.neu.edu/outreach/seminars/_current/handouts/ODD_exercise_sup…

1 0

co-operative stylesheet education session #13, take 2
by Syd Bauman 02 Nov '17

02 Nov '17

[I sent this last night at 22:12Z, but have reports that no one received it.] Ack! Sorry I've fallen down. Actually I didn't fall down, but my entire digital life fell down around me.[1] I believe we are scheduled for tomorrow Thu 11-02 13:00Z, i.e.: * 06:00 PDT * 09:00 EDT * 13:00 BST <== different than last meeting * 14:00 CEST <== different than last meeting Not surprisingly, I did not get a chance to do as much set-up work as I would have hoped. But I did chat w/ Martin and pop a request off to Elisa. So I'm hoping that our main topic will be a discussion led by Elisa of where & how to fix Stylesheets ticket 286, <ref> inside <listRef>.[2] I'm also hoping to devote 5 mins (certainly no more than 10) to the goals and purpose of the group. At last Council conference call a week ago, it was implied that the group is actually a Council sub-group or work-group that goes about fixing Stylesheets tickets. I bristled at this and said on the record that it is not a work-group and is tasked not with fixing problems but rather with providing a framework for co-operative self-education about the Stylesheets and how they work. That said, I'm perfectly happy to morph this into a Stylesheets task force (the words "mission impossible" jump to mind :-) that *is* actually where and how Council works on the Stylesheets. But I *don't* want that to happen by accident; I want us to purposefully decide we're happy with the role change (or not). If that all goes quickly, other tickets we may wish to poke at, in numerical (not intelligent) order: * 219 * 220 * 247 * 281 Notes ----- [1] On Fri night 10-27 my e-mail account was compromised, including all e-mail being "deleted" on arrival. (In quotes because MS365 e-mail system does not really deleted it, just moves it to a folder called "Deleted".) I did not notice until Sun afternoon 10-29. After I noticed something was wrong, but before I did anything about it (other than change my password, of course), we lost power due to the storm. Power was restored yesterday, Tue evening 10-31. I had a lot of post-power failure work to do (setting clocks, going through food in fridge, etc.), and had dinner, so did not get to my e-mail until late last night. When I sat down to work on e-mail I discovered our cable connection (which is both TV and internet at my house) was down. Note that my wife was watching TV while I ate dinner, so it had been up a mere hour or so before. Anyway, I checked the TV and it had a message that implied they would probably have it fixed "shortly", but I did not wait, I just went to bed. When I finally got to my e-mail today there were 693 pieces of e-mail waiting for me to sift through. [2] https://github.com/TEIC/Stylesheets/issues/286

1 0

Stylesheets repo
by Elisa Beshero-Bondar 02 Nov '17

02 Nov '17

Council— In preparing for tomorrow morning’s Stylesheets meeting, I was preparing to commit some changes to odd2odds.xsl on my fork. I noticed my fork had some old commits on it that I didn’t want to send with a pull request (old practice code I wrote, not useful to us), so I decided to destroy my fork and create a new one. The problem was—I went online to do it, thought I was accessing my forked origin to delete—I was on the wrong page. Evidently I deleted the remote origin repo because I can’t access it any more (and presumably no one can). I immediately wrote for help to GitHub support to try to restore our Stylesheets repo as it was at 11:30pm EST on November 1. I’m waiting to hear from them, but in the meantime, I wonder if we have a full copy of the repo with the issues. I am hoping that this is known territory to someone among us, that the good people at GitHub can help, that I haven’t destroyed everything! I am reasonably confident we can put the files back as they were tonight—I have them pulled in locally anyway. I am anxious about the tickets, and extremely upset. Anyway, you all need to know what just happened, and I hope we can repair it. It hardly bears mentioning that I think I have a fix for the issue we’re to discuss tomorrow. We need the Stylesheets repo! Elisa, worried sick and anxiously awaiting word from GitHub. -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8(a)pitt.edu <mailto:ebb8@pitt.edu> Development site: http://newtfire.org <http://newtfire.org/>

1 1

co-operative stylesheet education session #13
by Syd Bauman 01 Nov '17

01 Nov '17

Ack! Sorry I've fallen down. Actually I didn't fall down, but my entire digital life fell down around me.[1] I believe we are scheduled for tomorrow Thu 11-02 13:00Z, i.e.: * 06:00 PDT * 09:00 EDT * 13:00 BST <== different than last meeting * 14:00 CEST <== different than last meeting Not surprisingly, I did not get a chance to do as much set-up work as I would have hoped. But I did chat w/ Martin and pop a request off to Elisa. So I'm hoping that our main topic will be a discussion led by Elisa of where & how to fix Stylesheets ticket 286, <ref> inside <listRef>.[2] I'm also hoping to devote 5 mins (certainly no more than 10) to the goals and purpose of the group. At last Council conference call a week ago, it was implied that the group is actually a Council sub-group or work-group that goes about fixing Stylesheets tickets. I bristled at this and said on the record that it is not a work-group and is tasked not with fixing problems but rather with providing a framework for co-operative self-education about the Stylesheets and how they work. That said, I'm perfectly happy to morph this into a Stylesheets task force (the words "mission impossible" jump to mind :-) that *is* actually where and how Council works on the Stylesheets. But I *don't* want that to happen by accident; I want us to purposefully decide we're happy with the role change (or not). If that all goes quickly, other tickets we may wish to poke at, in numerical (not intelligent) order: * 219 * 220 * 247 * 281 Notes ----- [1] On Fri night 10-27 my e-mail account was compromised, including all e-mail being "deleted" on arrival. (In quotes because MS365 e-mail system does not really deleted it, just moves it to a folder called "Deleted".) I did not notice until Sun afternoon 10-29. After I noticed something was wrong, but before I did anything about it (other than change my password, of course), we lost power due to the storm. Power was restored yesterday, Tue evening 10-31. I had a lot of post-power failure work to do (setting clocks, going through food in fridge, etc.), and had dinner, so did not get to my e-mail until late last night. When I sat down to work on e-mail I discovered our cable connection (which is both TV and internet at my house) was down. Note that my wife was watching TV while I ate dinner, so it had been up a mere hour or so before. Anyway, I checked the TV and it had a message that implied they would probably have it fixed "shortly", but I did not wait, I just went to bed. When I finally got to my e-mail today there were 693 pieces of e-mail waiting for me to sift through. [2] https://github.com/TEIC/Stylesheets/issues/286

1 0