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

Re: [tei-council] location 4 tomorrow; bad list!
by James Cummings 25 Sep '16

25 Sep '16

What room are we in? -- Dr James Cummings, Academic IT Services, University of Oxford On 24 Sep 2016 7:40 p.m., Stefan Majewski <io(a)stefanmajewski.eu> wrote: Hi, it is actually Sonnenfelsgasse 19, 1010 Vienna (map<https://www.google.com/maps/place/Sonnenfelsgasse+19,+1010+Wien,+Austria/@4…>) for tomorrow. It is a large green door and I'll be there to pick you up a few minutes in advance. I picked up the key yesterday and am currently preparing a cake for tea/coffee break. As space will be rather limited for tomorrow's session, I think it's best to go to one of the places in the area. See you then, Stefan Am 24.09.2016 7:09 nachm. schrieb "Syd Bauman" <syd(a)paramedic.wwp.neu.edu<mailto:syd@paramedic.wwp.neu.edu>>: James -- We start at 09:30 at the Austrian Academy of Sciences (OeAW or &Oumlaut;AW). I don't remember what room. Address: Dr. Ignaz Seipel-Platz 2 1010 Vienna All (including Kevin, if you are our list master) -- The Council list seems to not be forwarding some mail items along, at least not to me. I've been reading them by reloading the archives page over and over! James' question just came through; both my and Elli's last post about dinner still hasn't made it to my e-mail client. -- 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 PLEASE NOTE: postings to this list are publicly archived

2 1

any XML document dicsussion
by Syd Bauman 25 Sep '16

25 Sep '16

[This is a re-post of what I sent 09-12 18:20, which may not have been posted.] Lou -- Overall this looks very good, and thanks for putting in all that effort. Three things I either don't understand correctly, or (if I do), I'm a bit uncomfortable with. * The basic underlying plan, if I grok correctly, is to use an <elementRef> with an @key of "anyElement" at the point in a PureODD model that any element is allowed. The definition of "anyElement", I presume, would itself allow any element with any attributes with any content. If I have this right, the overloading of the value of @key makes me nervous. (It overloaded because it has two definitions: 1) "the identifier used for the required element within the source indicated", and 2) a special keyword which means something completely different (any XML element with any XML content), and precludes the use of an element actually named <anyElement>.) This smacks to me of magic or voodoo, which we are supposed to shun. Why not an <anyElement/> or <anyXML/> element? * The <elementRef> does not currently have an @include, but it seems that supplying a namespace on this new attribute restricts the allowed elements. I guess there is an argument to be made that this is analogous to including elements from a module, but I'm worried that users may find this a bit confusing. (Can I supply 2 or more namespaces?) * If we're using <elementRef> instead of macro.anyXML, why does macro.anyXML need to be re-defined (as in section 6); or is that new definition the definition of <elementRef key="anyElement"/>? In either case, why is a text node allowed as a child (but only after an element)? I don't think we're going to need macro.anyXML at all in the new universe, but if we do, this content model seems screwy. But I may be missing something.

2 1

Bad News
by Raffaele Viglianti 25 Sep '16

25 Sep '16

Dear all, Unfortunately I am currently missing a visa document that is necessary for my re-entry into the US, so I was not able to fly to Vienna today. My flight reservation is currently "on hold" and in case the document is found by tomorrow, I can try and catch another flight and arrive on Sunday. However, there's a good chance that won't happen. If it's not too much trouble for you, I would still like to attend the meetings remotely - let me know if we can set that up. This is quite an unprecedented situation for me and I hope you'll accept my apologies for any inconvenience this will cause. Raff

6 9

dinner Sunday night
by Mylonas, Elli 24 Sep '16

24 Sep '16

Hi all - I am emailing as amanuensis for the crowd that is coming from Graz - they'll be arriving in Vienna around 6ish, probably at their lodgings before 7. Wondering about dinner 8ish or perhaps a bit earlier. It would be in the old town, as most us are staying pretty close from the google drive doc. Not sure about where to go, but maybe a light meal? We can decide where to meet once we know who's in.

7 19

location 4 tomorrow; bad list!
by Syd Bauman 24 Sep '16

24 Sep '16

James -- We start at 09:30 at the Austrian Academy of Sciences (OeAW or &Oumlaut;AW). I don't remember what room. Address: Dr. Ignaz Seipel-Platz 2 1010 Vienna All (including Kevin, if you are our list master) -- The Council list seems to not be forwarding some mail items along, at least not to me. I've been reading them by reloading the archives page over and over! James' question just came through; both my and Elli's last post about dinner still hasn't made it to my e-mail client.

2 1

council meeting venue
by James Cummings 24 Sep '16

24 Sep '16

Can someone remind me of the name and address of the council meeting venue on Sunday since I'll be arriving late? (And I'll try emailing if I can't get in. ;-) ) -James -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford

1 0

Re: [tei-council] dinner Saturday night
by Mylonas, Elli 24 Sep '16

24 Sep '16

I meant Saturdays, that is, today. spologied. Elli Mylonas [Sent from my phone, please excuse typos or autocorrect] On Sep 24, 2016 2:39 PM, "Lou Burnard" <lou.burnard(a)retired.ox.ac.uk> wrote: > Do you mean Sunday? Today is Saturday sfaics... I am arriving in about 3 > hours myself. > > Sent from my Honor Mobile > > -------- Original Message -------- > Subject: [tei-council] dinner Sunday night > From: "Mylonas, Elli" > To: tei-council(a)lists.tei-c.org > CC: > > Hi all - I am emailing as amanuensis for the crowd that is coming from Graz > - they'll be arriving in Vienna around 6ish, probably at their lodgings > before 7. Wondering about dinner 8ish or perhaps a bit earlier. It would be > in the old town, as most us are staying pretty close from the google drive > doc. Not sure about where to go, but maybe a light meal? > > We can decide where to meet once we know who's in. > -- > 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 > -- > 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 >

2 1

Re: [tei-council] Simple : victory declared, going home.
by Scholger, Martina (martina.scholger＠uni-graz.at) 23 Sep '16

23 Sep '16

Dear all, As suggested before, I completed a number of simple corrections in the tei-simple.odd and committed them. There are a couple of issues that I would like to bring up with the rest of you, though. :: Short Example: : The last sentence of the first paragraph is unclear, I don't understand what "the former" and "the latter" actually refers to. : I would find it useful to have a full example (including the TEI header) in addition to the "Short Example" e.g. at the end of the document. :: Footnote 1: which XML tutorial should be referred to? :: The following elements are listed as part of the TEI Simple schema, but there is no further explanation of them in the document. Some elements are used in an example. char (used in an example) charDecl charName (used in an example) charProp desc (used in an example) glyph glyphName handNote localName mapping (used in an example) unicodeName value :: The following elements and attributes are mentioned at various places in the text, even though they are not part of TEI Simple. I would suggest to either take those elements out all together or make clear that they are included for the sake of completeness, but not part of TEI Simple (which is already done in some cases). : <sourceDoc> : <term> : <gloss> : <index> (isn't described above as claimed in 13.2.1.; not clear) : @ulx/@uly etc. isn't explained in 14. Encoding a digital facsimile : <mentioned> (made clear that it is not part of Simple) : <said> (made clear that it is not part of Simple) :: Some examples use elements, which are a) not explained in the document (or explained at a later point), b) not part of TEI Simple : 3.3.2 Drama contains <emph> which isn't part of Simple : 3.5.3 Foreign Words or Expressions: <s> is used in the second example but explained several pages later. : 4.2. Omissions: @reason and @hand are used in the example but aren't further discussed. The same applies to <desc> and <term> in the following examples. Also <name> and <date> are used, which are covered at a later point in TEI Simple. :: 2 Structure : the <TEI> specification mentions model.resourceLike class. At this point, classes have not been explained. It think that would be necessary at the beginning of the document. :: 4.1. The transcription example (Henry V) claims that there is the phrase "Table of green feelds", however, in figure 1 it actually says "Table of greene fields". So, while the example is actually nice, it doesn't refer to the original (figure 1)... :: 5.1. Names and Referring Strings The last example contains @key attributes, I'd change this to @ref since @key isn't described and @ref fulfills the same purpose. By the way, I changed <sic> to <orig> in the example. :: Things that I wouldn't consider 'simple', but I'm sure these have been discussed before (several times) : <biblFull> in 7 Bibliographic Citation : @part in 3.3.2. Drama : @role for <table> in 8 Table, especially the values 'sum' and 'total'. There isn't even an example in the full TEI Guidelines. : The TEI header section is very extensive and complex. I would suggest to at least put the examples in their context for better orientation by adding the parent element. For example it is unclear where to actually put the <extent> element (15.1.3 The Extent Statement) :: The simple case to align text and facsimile is explained twice, almost identically, once at the end of 3.4 Page and Line Numbers and another time at the end of 9 Figures and Graphics. :: I added a suggestion for the missing @type values of <name> at the end of chapter 11 (please have a look at it). Would it make sense to use the same values as the element names in the full TEI Guidelines, e.g. genName etc.? :: PDF and HTML output : The line breaks in the examples on the PDF are coming out very weird, is there anything that can be done to remedy that? : the values (<val>) in the TEI Guidelines are displayed in simple quotation marks, but not in TEI Simple : the attributes are not displayed with a preceding @ in the PDF Best, Martina -----Ursprüngliche Nachricht----- Von: Martin Mueller [mailto:martinmueller@northwestern.edu] Gesendet: Freitag, 12. August 2016 13:50 An: Scholger, Martina (martina.scholger(a)uni-graz.at) tei-council(a)lists.tei-c.org Betreff: Re: AW: [tei-council] Simple : victory declared, going home. Martina, Lou deserves a break. If you send your list to me, I will follow up from there. MM Martin Mueller Professor emeritus of English and Classics Northwestern University On 8/12/16 12:03 AM, "Scholger, Martina (martina.scholger(a)uni-graz.at)" <martina.scholger(a)uni-graz.at> wrote: >Dear Lou, > >I read the first 60 pages of the TEI Simple document. What is the best >way to give you my remarks? > >First of all, the whole document is written very comprehensible and >will be a great start into the TEI world! > >I'd suggest to correct typos, punctuations, formatting, spellings etc. >by myself in the version on GIT and then send you the issues where I >have remarks and suggestions but which require some discussion or >decision on your part as PDF? > >Issues I would fix myself, if you agree: >: Typos and punctuation >: encoding errors (e.g. values that aren't encoded as <val>) >: Spellings (e.g. standardized and standardised - since in the >Guidelines everything is written with the "z" spelling, I'd suggest >doing the same in TEI Simple) >: Capitalization (TEI header, TEI scheme, TEI Simple, Processing Model, >TEI Guidelines) >: Remove indentation after code examples, lists, etc. > >Best, >Martina > > > >-----Ursprüngliche Nachricht----- >Von: tei-council-bounces(a)lists.tei-c.org >[mailto:tei-council-bounces@lists.tei-c.org] Im Auftrag von Lou Burnard >Gesendet: Donnerstag, 28. Juli 2016 19:24 >An: tei-council(a)lists.tei-c.org; Martin Mueller >Betreff: [tei-council] Simple : victory declared, going home. > >I have now made all the changes I've so far identified as necessary to >the TEI Simple Exemplar, and checked in a semi-final version for >Council to review. It needs someone, not me, to read it carefully and >nit-pickingly, or at least the first sixty pages or so pages of it. And >it needs someone to do some testing of the schema. And it needs someone >to fix the stylesheets so that the processing model info contained in >the ODD is displayed in HTML/PDF outputs. > >The ODD source is, as per usual, in the repository at >https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_TEIC_TE >I_b >lob_d9f349185b6a7263990c3c6fccc93567eb675e8e_P5_Exemplars_tei-5Fsimple. >odd >&d=CwIFAw&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=rG8zxOdssqSzD >Rz4 >x1GLlmLOW60xyVXydxwnJZpkxbk&m=EhVssORjMVfEc0-HfeERETaDqNF4nwVxWRSS7_AKm >8c& s=ApEg4VMCz1FL9vX_8c9cLG5oGn3UxYgrL9M5_1W2Qsk&e= > >The RELAXNG schema is at >https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_TEIC_TE >I_b >lob_d9f349185b6a7263990c3c6fccc93567eb675e8e_P5_Exemplars_tei-5Fsimple. >rnc >&d=CwIFAw&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=rG8zxOdssqSzD >Rz4 >x1GLlmLOW60xyVXydxwnJZpkxbk&m=EhVssORjMVfEc0-HfeERETaDqNF4nwVxWRSS7_AKm >8c& s=sV7jjGN72Z4No9BCBJa9ZQjAkRCyk9Dm02w5rOqGyJ4&e= > >I also have a massive HTML version, and a massive PDF version, which >for the moment I have just bunged into my personal webspace at >https://urldefense.proofpoint.com/v2/url?u=http-3A__lb42.github.io_tei- >5Fs >imple.html&d=CwIFAw&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=rG8 >zxO >dssqSzDRz4x1GLlmLOW60xyVXydxwnJZpkxbk&m=EhVssORjMVfEc0-HfeERETaDqNF4nwV >xWR SS7_AKm8c&s=3tpf0_gmXjpeo9wgd-4GH57bU5NuC3sqPpl-idBX70I&e= and >https://urldefense.proofpoint.com/v2/url?u=http-3A__lb42.github.io_tei- >5Fs >imple.odd.pdf&d=CwIFAw&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r= >rG8 >zxOdssqSzDRz4x1GLlmLOW60xyVXydxwnJZpkxbk&m=EhVssORjMVfEc0-HfeERETaDqNF4 >nwV xWRSS7_AKm8c&s=q3xnsfaL_hvxCEYHO8TAHaUvsaos1Np9dYwrSzpbHFY&e= >respectively. (Yes, I know the graphics dont show up in the HTML >version) > >I look forward to Council's feedback as to whether this is (as I >devoutly >hope) now (nearly) ready for prime time. > > > > > >-- >tei-council mailing list >tei-council(a)lists.tei-c.org >https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.lists.tei-2Dc >.or >g_mailman_listinfo_tei-2Dcouncil&d=CwIFAw&c=yHlS04HhBraes5BQ9ueu5zKhE7r >tNX >t_d012z2PA6ws&r=rG8zxOdssqSzDRz4x1GLlmLOW60xyVXydxwnJZpkxbk&m=EhVssORjM >VfE >c0-HfeERETaDqNF4nwVxWRSS7_AKm8c&s=_HL2i6HbEpEg3JbiTaFZWb1JmDNZxmrd-xFfD >-Ny >WOY&e= > >PLEASE NOTE: postings to this list are publicly archived

3 3

Sunday: TEI-council@oeaw
by Stefan Majewski 23 Sep '16

23 Sep '16

Dear all, today I am going to fetch the key from the Austrian Academy of Sciences. I have spotted the right location in the Agenda, so let's meet there on Sunday. I think I will buy some bread, spreads, fruit and stuff to eat so that we have some small lunch there together. If we find this too difficult, we can go to one of the places around there and reserve a table in the morning. Regarding dietary requirements, please get in touch with me directly if there is anything you can't or don't want to eat. I try to get some variety of things from the market. meanwhile have a safe trip! cheers, Stefan

2 1

Whither TEI Sessions
by Hugh Cayless 21 Sep '16

21 Sep '16

I've tried to distill the ideas in the Google Doc into 3 presentations. Can you all take a look and see if you agree with my choices? We'll need volunteers for each talk, which will entail writing and giving a short presentation (definitely under 10 minutes, 5 would be ideal). We also need a moderator. The rest of us should be available to the presenters as support both before and during the session. I think all of the talks would benefit from canvassing the community beforehand. I did a little thinking about what a survey of customization usage might look like and put some sample questions in there. Any feedback from the community should be solicited ASAP, I think, since we're less than 4 weeks out. Thanks, Hugh

7 20