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

rework of standoff proposal
by Peter Stadler 31 May '15

31 May '15

Dear all, a Council working group (PFS, LB, MH, FC, SM, PWS) just created an alternative proposal as the "Ann Arbor" branch at https://github.com/laurentromary/stdfSpec/tree/AnnArbor. The changes in detail: * killed mapStruct * renamed annotationGrp —> listAnnotation * renamed model.annotationPart —> model.annotation * got rid of dash in module name * removed class att.confidence in favor of https://sourceforge.net/p/tei/feature-requests/561/ * added some more elements to model.annotation * removed standOffHeader in favor of teiHeader(!!) We did not update the examples yet. I’m curious about Laurent’s reaction and will probably have a conf call in the next week with him (— Laurent?!) Best Peter

5 12

Recommendations on values of @xml:id (FR #540)
by Raffaele Viglianti 31 May '15

31 May '15

Hi all, Martin Mueller asked on the list for recommendations on good uses of xml:ids, which resulted in a good discussion and a FR. I summarized the main suggestions on the ticket on SourceForge, but I post them here as well because I think we need to discuss this further, see below. The Guidelines already have some recommendations (numbering based on doc structure): * The Guidelines already suggest numbering based on doc structure ( http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CORS2) * Use 3 letters (e.g. from the title)+ 3 digits, incremental. E.g. HOL001, HOL002, etc.. * Same as above, but no fix number of digits. E.g. HOL1, HOL2, etc. * Prefix an id with name of element (this is simpler version of what the Guidelines already recommend) * Give tei:TEI an id and prefix every other id in the document with it (to guarantee cross-corpus uniqueness) These are all reasonable suggestions and there can be plenty more - which is why I think that the TEI should *not* give any recommendation on best practices for xml:id because it's a project management issue, not an encoding one. Myself, I prefer random ids, a practice that avoids introducing yet another level of complexity and data management. I understand the human readability, but sequences are too easily broken. And when parsing, relying on ID content instead of TEI content sounds like a bad idea.

7 16

Next defaultVal to be nuked
by Martin Holmes 30 May '15

30 May '15

I hereby nominate att.divLike/@org's defaultVal: <http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.divLike.html> This has its own novel brand of silliness: There are two values, and the first value, "composite", means "no claim is made about the sequence in which the immediate contents of this division are to be processed, or their inter-relationships." Yet THIS IS NOT THE DEFAULT VALUE; the _other_ one, "uniform", which _does_ make a claim, is the default. Well FFS. It shall die unless I hear otherwise in the next few hours. cheers, Martin

3 5

eXist-db password changed
by Peter Stadler 29 May '15

29 May '15

Sid argued strongly that we should change the admin password for the eXist-db that serves Roma (the issue arose around the discussion of tickets [feature-requests:#527] and [bugs:#747]). Hence, I duly changed the password and documented it as described in [1] and briefly checked that Roma still works. If you encounter any side effects, please let me know! Best Peter [1] http://www.tei-c.org/Activities/Council/Working/tcw22.xml

2 1

Reconvene at 14:30
by Hugh Cayless 29 May '15

29 May '15

Sent from my phone.

1 0

First defaultVal for the chopping block
by Martin Holmes 29 May '15

29 May '15

My first candidate for an annoying and pointless defaultVal is @part. This has the defaultVal "n", which means: (no) either the element is not fragmented, or no claim is made as to its completeness. [Default] If it means "No claim is made as to its completeness", then there's no point whatsoever -- and actually the fact that this means _both_ "not fragmented" _and_ "I'm not saying whether this is fragmented or not" is just silly. Unless anyone gives me a good reason within the next 24 hours, I'm going to delete the defaultness and remove the latter part of the definition. I don't believe anyone has ever explicitly applied this attribute with the value "no" to mean the second part of its definition, so I don't see that any difference could be made to anyone's existing projects. Shout if you think I'm missing something. Cheers, Martin

1 0

Minutes Doc
by Hugh Cayless 28 May '15

28 May '15

https://docs.google.com/document/d/1V7RB54nYMKeXPqPAGxjbKmXwViz0vLFfwzGo4Ql… <https://docs.google.com/document/d/1V7RB54nYMKeXPqPAGxjbKmXwViz0vLFfwzGo4Ql…> Stefanie, ping me on skype when you’re able to join in. /** * Hugh A. Cayless, Ph.D * hugh.cayless(a)duke.edu * Duke Collaboratory for Classics Computing (DC3) * http://blogs.library.duke.edu/dcthree/ **/

3 4

DTW-Ann Arbor ride
by Lou Burnard 27 May '15

27 May '15

Anyone else arriving about 18h15 (or as the Americans say "6.30 pm") in DTW next Weds? Interested in sharing a cab rather than waiting for the 19h45 bus (or bemoaning the departure of the 18h02 one)?

12 46

Stand-off proposal
by Martin Holmes 27 May '15

27 May '15

Very minor niggle on the stand-off spec: <https://github.com/laurentromary/stdfSpec/blob/master/Specification/standof…> If the intention is to create a new module in TEI rather than add the new elements to an existing module, the module ident should be "standoff" rather than "stand-off", to align with existing modules ("namesdates", "textstructure"). Cheers, Martin

1 1

TEI Simple: Executive summary
by James Cummings 27 May '15

27 May '15

Dear Council, Please find attached an executive summary of the work of TEI Simple project and its proposal to Council. (The proposal really being the proto-ODDs on the github website.) Best wishes, James -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford

1 0