Difference between revisions of "Integration of JTEI Schemas and Tools"
Jump to navigation
Jump to search
(→Who needs to be involved) |
(→What needs to be done) |
||
| Line 4: | Line 4: | ||
# Integrate the JTEI article schema currently maintained by Ron Van den Branden and Martin Holmes into the main P5 release. Essentially this means the ODD file, which contains full detailed documentation for the customization. The JTEI schema will appear as one of the standard TEI-supported customizations alongside TEI Lite, TEI Tite etc. This presumably involves adding tei_journal.odd, tei_journal.template, and tei_journal.tei to the Exemplars directory. I don't yet know what the .tei file is for. | # Integrate the JTEI article schema currently maintained by Ron Van den Branden and Martin Holmes into the main P5 release. Essentially this means the ODD file, which contains full detailed documentation for the customization. The JTEI schema will appear as one of the standard TEI-supported customizations alongside TEI Lite, TEI Tite etc. This presumably involves adding tei_journal.odd, tei_journal.template, and tei_journal.tei to the Exemplars directory. I don't yet know what the .tei file is for. | ||
| − | |||
# Integrate the specialized transformations used by the Journal editors to generate ODT and OpenEdition output files from the article source into the TEI Stylesheets package. This will presumably involve creating a special profile, and may also require that we figure out how to warn users that these transformations are intended only to operate on documents complying with the journal schema. | # Integrate the specialized transformations used by the Journal editors to generate ODT and OpenEdition output files from the article source into the TEI Stylesheets package. This will presumably involve creating a special profile, and may also require that we figure out how to warn users that these transformations are intended only to operate on documents complying with the journal schema. | ||
| − | |||
# Integrate support for the Journal schema and transformations into the oxygen-tei plugin. Some of this should presumably happen automatically, but other components such as the Author-mode CSS we have developed for semio-wysiwyg editing will need to be added manually. | # Integrate support for the Journal schema and transformations into the oxygen-tei plugin. Some of this should presumably happen automatically, but other components such as the Author-mode CSS we have developed for semio-wysiwyg editing will need to be added manually. | ||
Revision as of 23:29, 2 March 2015
Contents
What needs to be done
This page lays out the procedure we intend to take to integrate the schema, authoring tools and transformations created by JTEI (see [TEI Journal Encoding Package]) into the main P5 distribution, the TEI Stylesheets, and the Oxygen-TEI plugin. This work is being carried out on the instructions of Council ([1]). The objective is to achieve the following three major steps, if practical before the code freeze preceding the April 2015 release of the TEI Guidelines:
- Integrate the JTEI article schema currently maintained by Ron Van den Branden and Martin Holmes into the main P5 release. Essentially this means the ODD file, which contains full detailed documentation for the customization. The JTEI schema will appear as one of the standard TEI-supported customizations alongside TEI Lite, TEI Tite etc. This presumably involves adding tei_journal.odd, tei_journal.template, and tei_journal.tei to the Exemplars directory. I don't yet know what the .tei file is for.
- Integrate the specialized transformations used by the Journal editors to generate ODT and OpenEdition output files from the article source into the TEI Stylesheets package. This will presumably involve creating a special profile, and may also require that we figure out how to warn users that these transformations are intended only to operate on documents complying with the journal schema.
- Integrate support for the Journal schema and transformations into the oxygen-tei plugin. Some of this should presumably happen automatically, but other components such as the Author-mode CSS we have developed for semio-wysiwyg editing will need to be added manually.
In addition, we also need to thoroughly document what we do through the production of a TEI Council Working Paper (TCW); there is at present no documentation (to my knowledge) which addresses any of the processes above.
Who needs to be involved
Prime movers:
- Martin Holmes
- Ron Van den Branden
Indispensable advisors:
- Sebastian Rahtz (P5 infrastructure, Stylesheets, Oxygen plugin)
- Someone from Oxygen (Oxygen plugin, Oxygen release process and schedule)
- Other members of Council (final decisions/approval on various stages)
