Text only | Skip links
Skip links||IT Services, University of Oxford

Contents

1. Publishing

A great number of people use the TEI as their encoding scheme, but you rarely get to know about it except in conference papers about their projects. They tend not to expose their TEI XML source files because of a mistaken perception that people will judge the results.

  • Now that it's all in TEI XML, what next?
  • Varieties of XML delivery system
  • Some real life examples

2. A reminder: what is XML for?

  • exchanging data
    1. between people
    2. between people and machines
    3. between machines
  • preserving information
    1. independent of particular applications
    2. independent of medium or hardware
    3. without unnecessary redundancy or duplication of effort

But is XML any good as a means of delivering information?

3. What are the options?

  • for delivery:
    • transform into HTML on the server and deliver that
    • deliver XML; use clever client-side processing to handle it
  • for management:
    • the filesystem
    • a content management system
    • a database
  • for tools development:
    • generic digital library solutions
    • LAMP style toolkits
    • roll-your-own solutions

4. Early America's Digital Archive

material
transcriptions of early printed books
organization
library metaphor
technologies
XSLT rendering in the browser; simple search via php
TEI source visible?
Yes, via view source

http://www.mith2.umd.edu/eada/

5. Artamène, ou Le Grand Cyrus

material
Immensely long 17th c. French novel
organization
Hierarchic, down to page level
technologies
Apache+AxKit, Xpathscript, Philologic (for freetext search)
TEI source visible?
yes; also downloadable in HTML, PDF, Word, Ebook for Palm...

http://www.artamene.org/

6. Arnamagnæan Mss Catalogue

material
Detailed manuscript descriptions
organization
independent XML documents, stored in a database
technologies
eXist, PHP, perl
TEI source visible?
no

http://www.am-mss.org

7. Robert Graves' Diary

material
transcriptions, page images, abstracts, annotations
organization
chronologically ordered; search interface
technologies
Cocoon, eXist, Xquery, javascript
TEI source visible?
Yes, plus documentation

http://www.tapor.uvic.ca:8080/cocoon/graves/index.xml

8. Swinburne Archive

material
texts, images, criticism related to AG Swinburne
organization
digital archive
technologies
XTF
TEI source visible?
Yes

http://swinburnarchive.indiana.edu

9. OUCS Demo

  • Oxford University Computing Services website: TEI XML + XSLT
  • All TEI documents checked for validity before published
  • http://www.oucs.ox.ac.uk/

10. Management and search of name data

The Lexicon XML records are managed using the eXist XML database (http://www.exist-db.org/) and accessed using XQuery.

The simplest interface is http://rahtz.oucs.ox.ac.uk:81/LGPN/search.xql, which allows for browsing by place or profession, and search by transliterated name (using Lexicon transliteration, with no accents). This can include partial name-matching, so searching for both Polugnwtos and Polug.* is supported.

Instead of the web page displaying the results, the answers can also be downloaded as a TEI XML file.

11. More expert use

12. Data returned by web service

<listNym rend="lexnames">
 <nym n="Anqulosxml:id="Anqulos">
  <form xml:lang="el-grc">᾿Ανθύλος</form>
  <form xml:lang="el-grc-x-lgpn">Anqu1los</form>
  <form xml:lang="el-grc-x-perseus">*)anqu/los</form>
  <p>
   <date notBefore="-0225notAfter="-0175"/>
   <num>1</num>
  </p>
 </nym>
</listNym>

13. Data returned by web service (2)

The same summary data may be obtained in JSON (http://www.json.org/) format; this supports a callback query parameter, so a full call of http://rahtz.oucs.ox.ac.uk:81/LGPN/search.xql?query=Anqulos&searchBy=summary&style=json&callback=processname produces
processname({ "names" : [ {"id": "Anqulos", "query": "Anqulos", "greek": "᾿Ανθύλος", "notBefore": "-0225", "notAfter": "-0175", "number": "1"} ] });
which is suitable for consuming by Javascript.

14. A simple HTML microformat

Building on these services, we have defined a simple HTML microformat for use in web pages, and an implementation using Javascript and the JSON format described above. This is demonstrated at http://rahtz.oucs.ox.ac.uk:81/LGPN/Demo/test.html.

15. How does that work?

Any names marked in a <span> with class attribute of ‘lgpn’ are looked up in the Lexicon, and enhanced with summary information. Names found are underlined in red; these turn green after a succesful lookup.

16. Example

<body>
 <p> Greek Unicode names:
 <span class="lgpn">Θεόδοτος</span>
   and <span class="lgpn">᾿Ανθύλος</span>
 </p>
 <p>
  <span class="lgpn">Ξάνθος</span> =
 <abbr class="lgpntitle="Ξάνθος">Ξάνθου</abbr>
 </p>
 <p>Two forms <span class="lgpn">Τέρτυλλος</span>
   and <span class="lgpn">Τέρτυλλος</span>
  <p>
   <abbr class="lgpntitle="Ἰωσούα">Ἰωσούᾳ</abbr>
  </p>
  <p>Transliterated names: <span class="lgpn">Polugnwtos</span>
  </p>
  <script type="text/javascriptsrc="greeknames.js"/>
 </p>
</body>

17. Microformat in action

A much larger, real, example (taken from the Inscriptions of Aphrodisias project at Kings College, London), is shown at http://rahtz.oucs.ox.ac.uk:81/LGPN/Demo/iAph110055.html

18. A TEI XML geo record

<place type="collegexml:id="mert">
 <placeName>Merton College</placeName>
 <event notBefore="1264type="officialstatus">
  <label>Foundation</label>
 </event>
 <location type="address">
  <address>
   <addrLine>Oxford</addrLine>
   <postCode>OX1 4JD</postCode>
  </address>
 </location>
 <trait type="url">
  <desc>
   <ptr target="http://www.merton.ox.ac.uk/"/>
  </desc>
 </trait>
 <trait type="iturl">
  <desc>
   <ptr target="http://mcit.merton.ox.ac.uk/"/>
  </desc>
 </trait>
 <place subtype="primarytype="building">
  <placeName>Lodge</placeName>
  <location when="2007-01-20T21:26:32.601Z">
   <geo rend="180">-1.252216100692749 51.75129113668488</geo>
   <note> recorded by Sebastian Rahtz</note>
  </location>
 </place>
 <place type="building">
  <placeName>Warden's Lodgings</placeName>
  <location when="2007-01-20T21:28:55.222Z">
   <geo rend="190">-1.249623 51.751628</geo>
   <note> recorded by Sebastian Rahtz</note>
  </location>
 </place>
 <place type="building">
  <place type="room">
   <placeName>The Chapel</placeName>
  </place>
 </place>
</place>

19. This can be used to make a timeline

http://www.oucs.ox.ac.uk/oxpoints/demo/timeline.html

Using timeline from MIT Simile project

20. Linking the timeline to a map

http://www.oucs.ox.ac.uk/oxpoints/demo/timemap-colleges.html

Using timeline and timemap

21. Publishing Conclusions

  • Even the simplest of approaches allows you to share your encoding, your analysis
  • The more ambitious your markup, the more sophisticated the possibilities
  • There is a common set of techniques and tools: you don't need to re-invent the wheel
  • TEI XML empowers the data provider: you determine what can be done with your materials
  • We all benefit from the open exchange, availability and licensing of the materials we produce

22. Contact and Website

Post
Sebastian Rahtz
Oxford University Computing Services
University of Oxford
13 Banbury Road, Oxford, OX2 6NN, UK
Email
Sebastian.Rahtz@oucs.ox.ac.uk
Course Website
http://tei.oucs.ox.ac.uk/Oxford/2008-03-taiwan/


Date: 2008-03-05
Copyright University of Oxford