Hi,
Seems reasonable (sorry again that I couldn't make the meeting). Just in case there was some confusion though, the oXygen plugin does not 'reach into the Vault for source to TEI'. It is bundled with it as part of the framework. It is only if someone chooses to update the framework by using the add-on system that they'll get prompted for updates. Otherwise they are stuck with whatever is in oxygen/frameworks/tei/ with p5subset.xml being in ${framework}/xml/tei/odd/ and it really mostly using the relaxng at ${framework}/xml/tei/custom/schema/relaxng/tei_all.rng
But I agree that if an editor has the capability to check for updates online and use those then reaching into the vault to get them would be a good thing. It would, of course, be preferred for it to have a local copy of the schema to enable offline editing.
Does this really need documentation on how the Vault is structured except to say that the most current release of the RNG schema is at: http://www.tei-c.org/Vault/P5/current/xml/tei/custom/schema/relaxng/tei_all.rng (with .rnc schemas next to it if they prefer)? Editor frameworks aren't grabbing things from p5subset.xml or the rest of the Guidelines are they?
(I'm *not* saying that better documentation on the Vault isn't a good idea...it is, just that it is barely needed for an editor framework.)
Many thanks,
James
--
Dr James Cummings, James.Cummings@newcastle.ac.uk
School of English Literature, Language, and Linguistics, Newcastle University
Dear Board,
Marjorie Burghart recently contacted the Council with a suggestion. She wants to apply to a DARIAH EU grant for sustainability to push forward the development of a free and open TEI/XML editor, in this case a plugin for jEdit. See https://www.dariah.eu/2018/06/29/dariah-theme-funding-call-2018-2019/. Submission deadline is September 9.
We have discussed it in our last Council call and support the idea since there is obviously high demand for a free editor with native TEI support.
We think that the Council’s part in this could be to provide data and documentation in a form, where it would be possible to develop a plugin for _any_ XML editor.
Like oXygen plug-in, the newly developed editor should reach into the Vault for source to TEI. We should document how the Vault is structured so that developers can use it appropriately. We then would consider supporting it in the ongoing release process if it conforms to agreed-upon conventions.
We would hope that the Board also supports this effort and would suggest to draft a joint letter of support by the Council and Board for Marjorie to lend more weight to her proposal.
Best wishes,
Martina