#119 Use and document ODD chaining in releases

[Hugh A. Cayless]

As discussed in our 2016-10-18 EDAG meeting, we should consider pegging each EpiDoc release to a particular version of TEI by putting a @source attribute on the schemaSpec. This will ensure that EpiDoc schemata generated from our ODD are stable (i.e. they won't produce different results if TEI has released a new version in the interim).

Furthermore, we should consider releasing a compiled ODD in addition to the tei-epidoc-full.xml. That would permit other customizations to base themselves on EpiDoc, and similarly to peg themselves to particular releases of both EpiDoc and TEI.

[Hugh A. Cayless]

Did we release a compiled ODD in the latest version? If not, I will go do it...

[BODARD Gabriel]

We didn't. But more urgent than just doing it, in my view, is documenting exactly how we go about doing it. Ideally, once we have added a point to the ReleaseProc saying that this is part of the process, I would suggest Poli have a go at doing it, both to spread the knowledge, and to test the instructions are clear. It can be added to the directory in Stoa after the event, but if we wanted to include it in the release download, she would have to do a 8.23.1 version for that (and I don't think it's urgent). Let's make sure the process and instructions are in place for 8.24.

[BODARD Gabriel]

I've just realized that this question wasnt' asked on [bugs:#155], where the above was explicitly requested as part of the feedback from release 8.23. Apologies if my comment above was opaque in the circumstances!