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

processing the processing model
by Lou Burnard 29 Feb '16

29 Feb '16

The next step in getting procmod into the Guidelines ought to be to produce some test files. However, as James mentioned earlier, this is not entirely straightforward. I can dream up sample ODDs which include <model> elements no problem, and can then validate them against the schemas generated from the current source. I can also re-use the ones in the Polygon directory in the original tei-simple repo, written by Magdalena. (why is it called "Polygon" btw?) However, should we not also be producing a test implementation or two showing the actual output generated with the aid of those models? That would require adding, presumably into the Stylesheets tree, some version of Magda's pilot version of a stylesheet for transforming <model>s into XSL. Or is that already there somewhere? Or are we just planning to keep quiet about the whole thing?

2 18

pure odd doc
by Lou Burnard 26 Feb '16

26 Feb '16

As promised, I've now updated my little tutorial on pure ODD. A PDF version is attached, and you can find the source in the repo at https://github.com/TEIC/TEI/blob/dev/Documents/pureODD/pureODDtutorial.xml : I am wondering if it needs a section on "how to convert your existing odd", which would however be much easier to write with input from some early adopters... (that's you chaps) If you sniff around in that bit of the repo, you'll also find a more ambitious document by Sebastian called "The TEI Customisation Handbook" ( https://github.com/TEIC/TEI/blob/dev/Documents/oddmanual/oddmanual.xml) This was written some time ago and doesn't therefore discuss pure odd. I haven't yet had the heart to bring it up to date.

3 6

Brown all set for April meeting
by Mylonas, Elli 24 Feb '16

24 Feb '16

Hi all - i just got a green light for the council meeting at Brown. Details to be arranged. I'll send you all travel information later today so you can work on tickets. However, if you can hold off a bit, it would be great if we could plan some activities around this event. Who has a talk in them, wants to spend an extra day on either end or consult with people or? thanks, --elli [Elli Mylonas Senior Digital Humanities Librarian and Center for Digital Scholarship University Library Brown University library.brown.edu/cds]

5 6

proc mod queries
by Lou Burnard 06 Feb '16

06 Feb '16

I've made a bit more progress on the "processing model" extensions to ODD proposed by the TEI Simpletons a while ago, and now have a version of P5 based on the current dev branch which includes them AND builds correctly. But I havent yet finished hacking the prose into shape, and I have some questions. Here's the first. The @output attribute "the intended output method" (that's clearly wrong though; surely it should be "the intended output target"?) is defined with a closed list of values "web", "print", and "plaintext". a) why is this a closed list? I can think of lots of other possible values e.g. "mobile device", "PDF", "text-to-speech synthesizer" for starters... b) what exactly does "plaintext" mean? And here's the zero'th. To whom if not the Council should I be addressing this query?

3 8

Proofreading processing model rewrite
by James Cummings 28 Jan '16

28 Jan '16

I'd like to thank Lou again for the rewrite of the draft section for TD that I'd done in the processing-model branch -- it is a substantial rewrite. This is at http://teic.github.io/TEI/TD.html#TDPM or if you prefer the xml https://github.com/TEIC/TEI/blob/lb42-procmod/P5/Source/Guidelines/en/TD-Do… I've given the chapter a quick skim read and my initial suggestions/thoughts are: "22.4.4.4 Processing Models" Should processing models section be a new 22.4.5? It is longer an more substantial than some of its siblings at this level. " In the present implementation, rendition is expressed using the W3C Cascading Stylesheet Language (CSS)" In which implementation? This may be confusing, perhaps just the second half of that sentence? "The intent is that these should be presented in an italic font as inline elements:" maybe: "The intent is that these elements should be presented inline in an italic font" (i.e. They may not be being processed into 'elements', that may be mistaken as suggesting this is only for HTML output or something.) You are right that at the bottom of the Output Rendition section we could say something about 'Why CSS', but this is for the same reason that we suggest elsewhere inside the <rendition> element as a formally declared stylesheet language. This might suggest that we should be having a @scheme attribute like <rendition> with css as a value? In Implementation: "If the useSourceRendition attribute on the model has the value false then any rendition attribute on the source element can be ignored; otherwise its value must be combined with that given in the outputRendition element, if any." Maybe reverse this since it might contradict what was said above in the bit on useSourceRendition? So: "If the @useSourceRendition attribute on the model has the value true then any rendition attribute in the source element must be combined with any given in the outputRendition element, otherwise all rendition attributes in the source should be ignored." -James -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford "

4 10

screwy example (was "Re: [TEI] <lg> and <gap> (#1419)")
by Syd Bauman 25 Jan '16

25 Jan '16

Re: the 4th example in section 3.12.1, "Core Tags for Verse"[1] See file TEI/P5/Source/Guidelines/en/CO-CoreElements.xml and search for "#CO-eg-07". The example doesn't seem to exemplify what the prose is talking about at all. Looks to me like the <stage> is supposed to be a sibling of the <l>s, in between the last two. (Otherwise, the @part attributes are not needed, the last two <l> elements could just be one <l> with a <stage> inside. Which, BTW, is a less-than-optimal encoding in this case, because the stage direction doesn't scan. :-) This seems to me to be a corrigible error, which I have just fixed on my home desktop, but don't plan to push for awhile in case someone wants to object. Notes ----- [1] http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COVE

1 0

Links for this morning's call
by Hugh Cayless 25 Jan '16

25 Jan '16

Agenda: https://docs.google.com/document/d/1sJgb6aQVJUTs0ENyRSIMfZODtrhXeOSyKoPYrM0… Hangout: https://hangouts.google.com/call/hpffrckgslsfz425fyzfby256ia Phone numbers are in the Agenda if you can’t connect to the Hangout.

1 0

Pure ODD
by Hugh Cayless 25 Jan '16

25 Jan '16

Dear All, Now that Lou’s tremendous work on Pure ODD has been merged into dev, we should try to give it a thorough workout. I’ve regenerated the "bleeding edge" Guidelines at http://teic.github.io/TEI/index.html <http://teic.github.io/TEI/index.html>. It would be extremely helpful if you can take the time to look it over for problems and report them as issues. I’ve experimented in that build with rearranging the order in which things are displayed. See, e.g. http://teic.github.io/TEI/ref-witDetail.html <http://teic.github.io/TEI/ref-witDetail.html>. Your reactions (whether positive or not) will be most welcome!

3 3

Chair Elections
by Hugh Cayless 25 Jan '16

25 Jan '16

Dear All, No-one has contacted me about running for chair, and I don’t believe anyone has expressed their willingness to run on-list either. Please correct me if I’m wrong! As I said in our last meeting, I’m willing to serve for another year, particularly if nobody else wants to do it, but I’d encourage you to think about it (for next year even if not this one). I may not even be on Council next year, as my term will be up at year’s end! It’s really not that bad a job, I promise :-). If anyone has questions about it, even if you’d rather wait until next year, do feel free to ask me or James (who was Chair before me) about it. Note that the deliberately vague guidelines for Chair Elections are posted here: http://wiki.tei-c.org/index.php/TEI-Council-FAQ#How_is_the_TEI_Technical_Co… <http://wiki.tei-c.org/index.php/TEI-Council-FAQ#How_is_the_TEI_Technical_Co…> —it’s one of those things I’ve never done before as Chair, and so have gotten it somewhat wrong, but I don’t want to sneak back into the position, so I’ll issue a last call for self-nominations now. My own reasons for wanting to continue are: 1) I think I sort of have it figured out now 2) My job at Duke will allow me to devote the time needed to it 3) I’d like to think things will be easier this year If anyone objects or wants to stand, then we’ll set up an election. All the best, and wishing you all a happy new year, Hugh

6 16

revised TD for procmod
by Lou Burnard 24 Jan '16

24 Jan '16

I've now made a new branch in the repo for my revised version of TD containing the processing model documentation. Some way to go yet, notably in the element specs which still seem occasionally too vague to me, and test files are still missing. But I'd appreciate some reassurance that I haven't totally misunderstood something crucial. The branch is called lb42-procmod and is based on dev as of last night

1 0