Page last modified: July 13, 2006

More advanced decisions in marking up texts

More on uses for TEI texts

Yesterday's proposal: a publicly accessible CANE SI collection of Lives of Nepos.

Other examples. An XML language for transforming texts: XSLT. Some transformations:

Dated events in Jerome's Chronicle
Citations of ancient texts in Nagy, BofA
Index of personal names in Nepos

How much do you mark up?

"Standoff markup" (index) vs. "in-text markup"
One suggested guideline: after basic organizational structure, mark proper nouns
TEI is modular: e.g., can add a module with markup for names and dates (TEI.names.dates module)
License your work so others can extend it: choices of CC licenses

Citation and authority lists

Uniquely identifying features: TEI id and idref attributes, lang attributes
external authority lists for identifiers could use n attribute
An explicit notation for citation: CTS URNs
One collection of authority lists: chsreg browser
An application exploiting CTS URNs: Chris Blackwell's text finder

Other notes

Another technology to be aware of : version control (or "source control") sytems
TEI reference on line

Tasks

Add a paragraph to publicationStatement element of header with a CC license.
If you decide to mark either personal names or geographic names:
- add TEI.names.dates module to your document's preamble,
- mark persons with persName and/or geographic names with geogName element
- on a later pass, you can add n attributes identifying the persons or place

Add the following to your teiHeader, after the fileDesc element:

  <profileDesc>
      <langUsage>
        <language id="lat">Latin</language>
        <language id="eng">English</language>
      </langUsage>
  </profileDesc>

Put a lang attribute on the body of your document

Course materials and editions of ancient texts on this web site are made available under a Creative Commons Attribution-ShareAlike 2.5 License.

Web site last modified: July 13, 2006; installed on this server Fri, 14 Jul 2006