Sebastian Rahtz wrote:
> On 7 Sep 2010, at 19:45, Kevin Hawkins wrote:
>> I would like to write a stylesheet for converting XML produced by
>> AccessTEI ( http://accesstei.apexcovantage.com/ ) into more standard TEI
>> for further processing and donate this stylesheet to the TEI wiki (
>> http://wiki.tei-c.org/ ) for community use and modification.
> Such a mapping was foreseen early on in the development of Tite,
> and is managed within the ODD file which defines TEI Tite. For
> <elementSpec ident="b" mode="add" ns="http://www.tei-c.org/ns/tite/1.0">
> <equiv filter="tite-acdc.xsl" mimeType="text/xsl" name="b"/>
> this says that the element <b> can be mapped to TEI by running
> the template called "b" in "tite-acdc.xsl".
> If one runs the script "make-acdc.xsl" on "tei_tite.odd", it creates
> a transformation script which you can run on an instance document.
> See http://www.tei-c.org/release/xml/tei/custom/odd/tite-acdc.xsl
> Not tested on real-life AccessTEI files, but I see no reason to think
> it won't work. I strongly encourage you to test and develop
> these stylesheets.
> HOWEVER, remember that an AccessTEI file has no metadata, so you'll
> always need to write your own <teiHeader> provider from some other
> source. Writing a completely generic converter will always be
> problematic for that reason.
Very interesting. This will indeed provide a good starting point for
the cases of syntactic sugar, but unfortunately I'll still be left with
cases where TEI deviates from TEI convention while using TEI elements:
for example, in using <div type="half-title"> instead of <titlepage
And then there are changes introduced by Apex in their use of Tite not
included in Tite as published on tei-c.org. These will take me some
more time to work through ...