EDAG June 2019 call

Date: Tuesday 18th June 2019

Apologies: Hugh Cayless, Emmanuelle Morlock, Simona Stoyanova, Charlotte Tupman, Polina Yordanova, Scott Vanderbilt

Present: Gabriel Bodard, Pietro Liuzzo, Laura Löser, Elli Mylonas

Agenda items:

• Minutes from April: APPROVED

• Discuss teiCorpus bug in epidoc schema more.  Gabby fixes it now. 

• EM post on markup with follow up to Harri Kiiskinen  saying that teiCorpus will be deprecated by TEI but we are allowing it to serve as root which was a mistake. Also check w/ TEI council about timing for implementation and deprecation.

• Set a date for next release 9.1

• Laura and Scott Vanderbilt had volunteered in the distant past. Laura will contact him again and see if he’s still on, and then set a date ideally around early September. (including Gabby, Tom or Hugh for backup and uploading)

• Request for EpiDoc workshop in Berlin 21 August 2019 (through Markup List) (Pietro gave availability for this already to T. Costea, and Laura wanted to join)

• Unclear what exactly is needed. Pietro is figuring this out. Consulting and intro to Epidoc. On Pietro.

• Adding to the Reference Stylesheets the example epidoc to XSL-FO transformation?

• Pietro made a epidoc branch (xslfo) and ask for that to be merged when he’s ready. https://github.com/EpiDoc/Stylesheets/tree/xslfo On Pietro

• This does not yet include a start-pdf.xsl which would output a small pdf with the rendered PDF

• Could we have an update from Wien?

•  TE Not here. Need an update later.

• Reference stylesheets parameter/Leiden consistency

• John Bodel’s email about consistency with Panciera or other conventions. Perhaps we don’t want to stick to Panciera (ex broken word has “=”, but it’s not widely used, we use “-”) but need to document our usage. And if we use Panciera, we should conform to Panciera. Need epidoc sprint to figure out where we conform and where we don’t. 

• Perhaps rename the default transformation - but shouldn’t make up our own conventions by picking and choosing. Make sure we are using a documented style. 

• Diplomatic also has inconsistencies. <gap> not same as <supplied reason=”lost”> in rendering.

• http://epidoc.dainst.org/ tool to show the different parameters

• Something as easy to use as http://iospe.kcl.ac.uk/5.1.html but to show different Leiden styles to emphasize flexibility in representation of EpiDoc files

• Any more ideas/plans regarding EpiDoc semester? (online course on EpiDoc to be organised over the course of a few weeks/months, with video calls later uploaded to youtube or similar)

• Brainstorming file here: https://docs.google.com/document/d/1RouGl6LmhlB7jB_6S-yv6eq_sojpfG-Mo0t2aS_iM3Q/edit?usp=sharing

• Pietro will look into adding links to the EpiDoc Guidelines in the ODD as it is done in Beta Masaheft, so that on transformation one gets the link to the guidelines as well.

This is however over writing the definition in TEI, which instead should stay, and probably needs some changes to the ODD 2 RNG transformation flow in the TEI Stylesheets (teiodds.xsl).

Next calls:

Tuesday 9th July 

Tuesday 20th August

Tuesday 24th September Fourth Tuesday rather than third!

Tuesday 15th October

Tuesday 19th November

Please e-mail Laura if you foresee problems (e.g. holidays, EpiDoc training events etc.) for future dates