Memo of Modifying the TEI P5 Teilite.Xsd
Total Page:16
File Type:pdf, Size:1020Kb
Memo of modifying the TEI p5 teilite.xsd
Holly Wang (November 25, 2008)
Modification to the original teilite.xsd
The original schema is located at: http://www.tei-.org/release/xml/tei/custom/schema/xsd/teilite.xsd
The modified teiliteOH.xsd is located at(exactly the same copy on two servers): http://digidev2.library.ucla.edu/xslt/schema/teiliteOH.xsd (\\lit304v\d$\Apache\Digital2\htdocs\xslt\schema) http://digital2.library.ucla.edu/xslt/schema/teiliteOH.xsd (\\lit308v\d$\Apache\Digital2\htdocs\xslt\schema)
I have done following modification:
1. milestone: add start and end as the attribute 2. add the att.timed.attributes, and the att.timed.attribute.start, att.timed.attribute.end as while 3. add four definitions: particDesc, listPerson, person, persName (we have these tags from the 35 TEI files from calculture)
We selected Milestone to record the timestamp. There are two organization have done it: Documenting American South and CalCulture. DAS add an attribute for milestone to record the timestamp. Here is an example:
Here is a piece of code from CalCulture to apply milestone tag on oralhistory document for UCLA.
The end timestamp is generated automatically by InqScribe. I decided to keep it in case it could be useful in the future for Flash Player application. The following is a piece of example of the XML file for transcript with timestamp that we decided to go with:
Okay. This is Jane Collings interviewing Fran Diamond in her home on April 8th, 2007.
Okay. This is Jane Collings interviewing Fran Diamond in her home on April 8th, 2007.
Appendix 2: Modified part of teiliteOH.xsd
1: Milestone
2. start and end attribute
3. particDesc
4. particDesc, listPerson, person, persName
Solution One: manfully apply the changes.
Steps:
1. In Oxygen, Find 2. Find in= and replace with > 3. Find out= and replace with end= 4. Close the milestone tags 5. Check the document forms to make sure all tags are matching and closed Closed milestone tag examples: Solution two: apply a XSLT stylesheet on the XML file to get the XML file that we wanted. The sample that I created is using XSLT 2.0, and you need to change the parser into Saxon 8. Here is how to change the parser: 1. Click the configure transformation scenario icon at the top, after the small window pop up, select the xml-stylesheet processiong instruction and clik Edit. 2. In the edit scenario window, under the Transformer, select the Saxon 9b as the transformer. Remember, Xalan is a good parser for XSLT 1.0 and you may want to set it back once you finished with current task. 3. Now you can apply the transformation scenario by click the icon which has a red triangle in a circle.