Conal Tuohy wrote:
>One approach is to use a initial "normalizing" transformation, to
>"upconvert" P4 docs into P5, and then feed them into your new
>P5-processing code. This transformation would move the elements into the
>P5 namespace and convert other elements and attributes as required.
I agree; if the TEI P4 documents are writeable, then convert
them to TEI P5, dynamically or statically.
>Seems to me this could be done with an XSLT transformation, which would
>have templates matching the P4 (un-namespaced) elements, and could copy
>P5 elements unchanged, so you could even run the transform over your
>entire corpus (including the P5 documents) if you wanted to keep your
>processing setup generic. I think such a stylesheet would be a valuable
>resource for the TEI community in the transition period.
There is a generic p4top5 stylesheet at http://www.tei-c.org/P5/p4top5.xsl.
It has not had a lot of testing, so feel free to enhance it
and report errors. I haven't checked, but it will probably pass
through P5 as is - if it doesn't, it can obviously be tweaked.
Information Manager, Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
OSS Watch: JISC Open Source Advisory Service