• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!


Minutes January 2016

Page history last edited by Gabriel Bodard 7 years, 5 months ago

Present: Ryan Baumann (RB), Gabriel Bodard (GB), Hugh Cayless (HC), Tom Elliott (TE), Pietro Liuzzo (PL), Emmanuelle Morlock (EMo), Elli Mylonas (EMy), Simona Stoyanova (SS).

1) GB updated on EFES progress. There has been no word on funding from Lyon, but regardless of whether that turns out to be possible or not, we will still have more work to do. GB will draft a 2-page outline of a work plan including development by Jamie Norrish, documentation and testing, and two workshops to test the tool and training materials on non-technical papyrologist/epigraphist users, and use that to seek funding.

2) HC reported on forthcoming TEI changes in the next release (probably late March/April) that might impact on EpiDoc, including: global @source/@resp attributes (YAY!); "pure ODD" (aka Foxglove) implementation, which will require only a few trivial tweaks to the EpiDoc ODD. EMy will look over other recent TEI tickets and report back next month whether (a) there's anything else that will affect us on release, and (b) whether there's anything that we want to promote as especially desirable to the TEI.

3) EMy noticed some error messages in SVN update of the whole EpiDoc repository. We ascertained that all of these were in old tagged versions, and most were references to versioned instances of the TEI Stylesheets, which were since deleted from the Sourceforge repo where we were referencing them. Our external reference from trunk correctly points to the new Github copy of this repo, so there is no harm to our functionality.

4) We began looking through SF tickets, but only discussed at any length EMy's recommendations for improving the header and footer navigation sections of the EpiDoc Guidelines. Two actions arise from this discussion:

(i) EMy's recommendation for improving the header and footer have been added to the ticket at https://sourceforge.net/p/epidoc/feature-requests/84/ and should be discussed and finalized in order to be implemented for the next release.

(ii) GB will make a first pass at re-figuring the EpiDoc table of contents (front page), which he will then post to http://www.stoa.org/epidoc/gl/dev/ for comment by the group. (Note: translated versions should then be updated accordingly.)

Comments (0)

You don't have permission to comment on this page.