User:Kshawkin/My Council obligations/Plan for TEI Tite
Background
TEI Tite was created as a result of a grant from the Mellon Foundation and given to the TEI-C to host in its repository along with other customizations. Since outside support for its maintenance has not been secured, maintenance fell to the TEI Technical Council. The Technical Council decided in September 2012 to maintain Tite, as it has long done for TEI Lite.
Those involved with setting up AccessTEI agreed that Apex CoVantage would need a stable version of Tite to train staff on, so Apex forked the Tite spec to make some last-minute modifications to Tite before the launch of AccessTEI. It was always the intention to bring these revisions back into the canonical Tite source managed by the TEI-C, and in September 2010 the chair of the Technical Council appointed a task force to reconcile the two versions in use. Greg Suprock at Apex confirmed on 2012-07-20 that Apex is willing to begin using a revised version provided by the TEI-C. Kevin Hawkins gathered the DTD used by Apex (generated 2010-03-02, which Virginia McClure sent to Dan O'Donnell in April 2010) and a summary of the changes, as reviewed by and approved by representatives of the TEI, to compare against the canonical one maintained by the TEI-C to see what revisions needed to be made in the canonical version to reconcile the two.
In later correspondence with Kevin, Greg sent Kevin the DTD that he said Apex was using as of 2012-04-17, which turned out to be derived from the version of Tite released with P5 1.7.0 (2010-07-06). However, it was missing <handShift/> and included <biblScope>, etc. even though these contradicted changes made to the Apex prose documentation for AccessTEI at some point after February 2010, when Apex summarized various suggested revisions to Tite to Perry Trolard and maybe others. Greg responded on 2012-08-08 that Apex was still using an older version of the DTD though had begun to review of a newer DTD (presumably the one that he had sent on 2012-04-17).
Kevin Hawkins's intention
Kevin intended to first:
a) verify that all revisions by Apex had been made in the canonical version
and then do the following (in any order):
b) Implement other bugs and feature requests related to Tite
c) Rewrite Tite as an new-style inclusion ODD, as was done for Lite at revision 10700 (not at revision 8777 as the commit comments would have you believe).
and then finally:
d) Notify Apex that the TEI-C has caught up on updating Tite and ask them to begin using the latest version.
What has happened so far
a) Kevin implemented some tickets relating to Tite based on the notes from just before the launch of AccessTEI:
- removing elements and attributes accidentally included for bug 3136934 (old system) / 247 (new system) at revision 8764
- add
add
anddel
for encoding manuscripts for feature request 3136935 (old system) / 267 (new system) at revision 9559 - add
@facs
topb
for feature request 3136936 (old system) / 268 (new system) at revision 8764
Furthermore, Sebastian fixed a bug in the Tite ODD that included titlePage and titlePart from the wrong module at revision 9883.
In June 2012 Sebastian ran a comparison of the 2012-04-17 file against P5 1.7.0. I now realize that what he reported as (b) in his message is simply the result of revision 9883.
Then in July 2012(?) Kevin diff'd the Apex DTD from 2010-03-02 against Tite from P5 1.6.0, writing annotations on a printout.
b) A few of these tickets have have already been implemented:
- Becky W. added a description of the use of
handShift
for feature request 3418550 (old system) / 325 (new system) at revision 10799. - Martin H. clarified when and where to capture line breaks for bug 228 at revision 12925.
In addition, some other have been made to Tite as a result of changes to P5:
- Martin H. removed
data.code
for bug 3603291 (old system) / 529 (new system) at revision 11598.
Next steps
a) More fully compare Apex's DTD from 2010-03-02 (and not 2012-04-17!) against Tite from P5 1.6.0 for differences that can't be accounted for simply by changes to P5 (and would indicate other revisions from Apex that we should consider for canonical Tite). One could use NekoDTD or DtdAnalyzer if the diff function in <oXygen/> isn't sufficient.
b) See the remaining bugs and the remaining feature requests.