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

dataRef attr descriptions
by Syd Bauman 18 Feb '16

18 Feb '16

The description of dataRef/@key is "the identifier used for this datatype specification". This is confusing, if not outright nuts: the identifier used for this particular data reference element would be specified on @xml:id. I'm of a mind that the three "what I'm referring to" attributes should have parallel descriptions. Something like: key = The datatype being referred to from the set of provided or custom TEI datatypes, indicated by its identifier (e.g., "teidata.language") name = The datatype being referred to from the datatypes found in _XML Schemas: Part 2: Datatypes_, indicated by its name (e.g., "gYear") ref = The datatype being referred to in an external datatype library, indicated by a URI although I'm sure those can be improved upon. Meanwhile I've discovered that the dataRef.xml/elementSpec/listRef/ptr/@target pointed to the wrong section, and that in that file @ref was defined as a name, not a URI. I have fixed these corrigible errors, but did not want to muck with the wording on my own.

2 1

@restriction doesn't make it to documentation
by Syd Bauman 18 Feb '16

18 Feb '16

Apologies if this has been pointed out before, I'm a bit behind on PureODD. I just realized that although the pattern specified on @restriction of <dataRef> makes it into the .rnc file (and .rng, and I presume .xsd although I couldn't care less), it does not make it into the HTML customized documentation file.

2 1

need input on ticket 1331, dating attributes
by Syd Bauman 15 Feb '16

15 Feb '16

[Insert pun about the attributes required to get a ticket for a medieval match.com here.] [New folks -- e-mail from me should almost always be read with a fixed-width or monospaced font. This one is no exception.] For ticket 1331 (https://github.com/TEIC/TEI/issues/1331) I'm supposed to jigger the prose a bit, and develop a table of the semantics of the various combinations of @from, @to, @notBefore, and @notAfter. I've gotten a very good start on this, but am running into trouble with the table, and am seeking help and advice. Issues, in rough order of importance: 1. There are two combinations of these attributes that I don't know what to do with. As far as I'm concerned, it makes no sense to use the pairs @from & @notBefore or @to & @notAfter. That said, some *might* argue that using three of the four (either @from with @notBefore & @notAfter, or @to with @notBefore & @notAfter) does make sense. (Specifying a duration that starts at @from and ends sometime in the range specified by the other two, or that ends at 3A@to and starts sometime in the range specified by the other two.) So: a) What should I put for the makes-no-sense pairs? b) Should I be writing prose to support the ( (@from|@to), @notBefore, @notAfter ) encoding? Or is that too wild? Or is there some other interpretation we should be considering? 2. Since order of attribute specification is inconsequential, and an attribute may only be specified once, making a full 4x4 table of these attributes results in 4 cells that make no sense because they are for the same attribute twice, and each of the other unique 6 cells is duplicated (for a total of 16 cells). A B C D A XX ba ca da B ba XX cb db C ca cb XX dc D da db dc XX Should we display all 16 cells? Or make an abbreviated chart, e.g.: A B C D A XX -- -- -- B ba XX -- -- C ca cb XX -- D da db dc XX Or, noting that in the above chart row A and column D are useless, make a truncated chart, e.g.: A B C B ba XX -- C ca cb XX D da db dc If you look at the draft of the chapter I have at the moment (http://paramedic.wwp.neu.edu/~syd/temp/TEI_Council/html/ND.html#NDATTSda) you'll see that there several (ugly) versions of this table. Which one should we use? 3. The default HTML styling of <table>, <tr>, and <td> is not good for this purpose, and I see no easy way to special-case this. (Putting @style on <td>, and maybe <tr>, does not work; the attribute does not get propagated to the HTML.) Does anyone know of a way around this, or already know where in the Stylesheets I should be working to get @style working? If you take a look at http://paramedic.wwp.neu.edu/~syd/temp/TEI_Council/test-table-of-attrs-layo…, you'll see a set of tables closer to what I think they should look like.

3 2

versions
by Lou Burnard 13 Feb '16

13 Feb '16

I've been asked to run a workshop on ODD at the Ecole Nationale des Chartes at the start of March, and I'd like to use the latest version of pure ODD, plus Stylesheets that process it. So, remind me chaps, what do I need to do to ensure that workshop participants get the right stuff installed in their oxygens? Or will we really have a release 2.9 out before then? (My workshop is on the 3rd, so this is cutting it fine in any case...)

1 0

odd reminder
by Lou Burnard 09 Feb '16

09 Feb '16

I haven't heard from anyone since I asked Council members to check that their existing ODDs continue to work as expected using the lb42-pureodd branch. So maybe no Council members actually have any ODDs to check, or maybe those who do have all checked and have nothing to report, or maybe they just haven't got round to it yet. I don't know, but just in case it's the 3rd possibility, please could I urge you to give it a go this weekend? If you prefer, you could just bung me a copy of the ODD and I'll test it for you! Why the pressure? Well, mostly that I've just been reminded that we're aiming for a pre-release freeze for the end of the current month, and I'm going to be buried in the French countryside with only intermittent net access until then.

7 20

Re: [tei-council] Testing Pure ODD
by James Cummings 09 Feb '16

09 Feb '16

Well, as I said, mostly this was very very simple relaxng content models in any case. I might mock up some more complex ODD doing something bizarre with datatypes.... when I get some time. -James On 09/02/16 11:41, Lou Burnard wrote: > Thanks James.. V encouraging! > > Sent from my Honor Mobile > > -------- Original Message -------- > Subject: [tei-council] Testing Pure ODD > From: James Cummings > To: TEI Council > CC: > > Hi Lou and Council, > > I've been looking around for a TEI ODD file where I redefined > content models. Mostly I just add/delete > elements/attributes/classes which isn't really changing. Finally > remembered I had changed some content models in my tei_corset > ODD. This was a mass-digitisation ODD for the Stationers' > Register project where the keying company was willing to use any > XML schema but would charge per kilobyte of output. So I renamed > everything to be shorter names, etc. in a tei_corset namespace > which over a lot of text input saved us money and was easy to > convert back. > > Where I used any relax ng in this it was fairly minimal and the > conversion able to be done automatically with no problems: > > a) to rename <TEI> to be <file> and say that its content model > was just <teiHeader> and <body> (both renamed elsewhere) > Old ODD: > https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… > Pure ODD: > https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… > This just changes to two <elementRef>s. > > b) to rename <teiHeader> to be <header> and give it a content > model of <title> followed by zero or more model.pLike > Old ODD: > https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… > Pure ODD: > https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… > This just changes to an <elementRef> followed by a <classRef> > > c) for various reasons some empty elements were changed to allow > text content. For example <gap> was renamed <gp> and had a > content of <rng:text> > Old ODD: > https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… > Pure > ODD:https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_c… > <rng:text> just becomes <textNode/> > > d) exactly the same thing for <space> renamed <spc>: > Old ODD: > https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… > Pure ODD: > https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… > > > The resulting schema validates against the files I had. I did > have to change some other things in the ODD, but these had to do > with the moving of rendition things into att.global.rendition > from att.global. (Since this ODD was 3 or 4 years old.) > > I converted the Pure ODD to HTML and everything worked as expected. > > Clearly not an exhaustive test of all of the functionality of > Pure ODD, but just another confirmation that migrating to Pure > ODD is able to be semi-automated and for most people's low > hanging fruit doesn't introduce any major problems. > > -James > > > -- > Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT > Services, University of Oxford > -- > tei-council mailing list > tei-council(a)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(a)it.ox.ac.uk Academic IT Services, University of Oxford

2 1

Testing Pure ODD
by James Cummings 09 Feb '16

09 Feb '16

Hi Lou and Council, I've been looking around for a TEI ODD file where I redefined content models. Mostly I just add/delete elements/attributes/classes which isn't really changing. Finally remembered I had changed some content models in my tei_corset ODD. This was a mass-digitisation ODD for the Stationers' Register project where the keying company was willing to use any XML schema but would charge per kilobyte of output. So I renamed everything to be shorter names, etc. in a tei_corset namespace which over a lot of text input saved us money and was easy to convert back. Where I used any relax ng in this it was fairly minimal and the conversion able to be done automatically with no problems: a) to rename <TEI> to be <file> and say that its content model was just <teiHeader> and <body> (both renamed elsewhere) Old ODD: https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… Pure ODD: https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… This just changes to two <elementRef>s. b) to rename <teiHeader> to be <header> and give it a content model of <title> followed by zero or more model.pLike Old ODD: https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… Pure ODD: https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… This just changes to an <elementRef> followed by a <classRef> c) for various reasons some empty elements were changed to allow text content. For example <gap> was renamed <gp> and had a content of <rng:text> Old ODD: https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… Pure ODD:https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_c… <rng:text> just becomes <textNode/> d) exactly the same thing for <space> renamed <spc>: Old ODD: https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… Pure ODD: https://github.com/jamescummings/conluvies/blob/master/tei_corset/tei_corse… The resulting schema validates against the files I had. I did have to change some other things in the ODD, but these had to do with the moving of rendition things into att.global.rendition from att.global. (Since this ODD was 3 or 4 years old.) I converted the Pure ODD to HTML and everything worked as expected. Clearly not an exhaustive test of all of the functionality of Pure ODD, but just another confirmation that migrating to Pure ODD is able to be semi-automated and for most people's low hanging fruit doesn't introduce any major problems. -James -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford

2 1

Roma eXist-db down?
by Peter Stadler 08 Feb '16

08 Feb '16

Dear all, at present, I can’t access Roma (I may enter the first pages but Roma is unable to fetch module information etc.) and it seems the eXist-db is down. Looking in the logs at /var/www/vhosts/tei-c.org/opencms_tomcat/lv1/local/tomcat_6.0.14_teicms/webapps/exist/WEB-INF/logs/exist.log states: 2016-02-08 07:01:18,941 [main] INFO (BrokerPool.java [shutdown]:1495) - shutdown complete ! 2016-02-08 07:23:49,589 [http-8040-9] INFO (XQueryServlet.java [init]:135) - form-encoding = UTF-8 2016-02-08 07:23:49,590 [http-8040-9] INFO (XQueryServlet.java [init]:139) - container-encoding = UTF-8 2016-02-08 07:23:49,590 [http-8040-9] INFO (XQueryServlet.java [init]:143) - encoding = UTF-8 2016-02-08 07:23:49,631 [http-8040-9] WARN (Descriptor.java [<init>]:96) - Giving up unable to read descriptor file from /descriptor.xml 2016-02-08 07:23:49,631 [http-8040-9] WARN (Descriptor.java [<init>]:115) - Giving up unable to read descriptor.xml file from classloader in package org.exist.http So, it looks as if the db was shutdown and failed to restart. Does anyone know any details and how to proceed? (I’m unfamiliar with eXist within Tomcat …) Best Peter

4 5

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

processing model use of CSS
by Lou Burnard 05 Feb '16

05 Feb '16

Decision please. The current description of the processing model tacitly assumes that CSS is used to express output rendition, and it's hard to see how else the job would be done, but the text of the Guidelines is rather vague on the topic. Should we say a) outputRendition *must* be expressed using CSS b) it is *recommended* that CSS be used c) we don't care what you use, but our examples assume you will use CSS If we choose b or c, we will presumably need to add some complexity to the scheme (e.g. to say what has been used instead if it's not CSS)

5 17