I am not clear about the link between HTML output and pedagogical
purpose in what Linda proposes/endorses.

Case A: distributing the fruit of one's TEI-lite labours

Using XSLT, one can also output text stripped of markup. See For some purposes
this may be better than outputing HTML.

Case B: having students play with TEI-lite and display thereof

One commercial browser (distributed for free) will take XML files and
display them as a tree. It does so in a fashion that permits the user to
collapse (-) and expand (+)  elements. As well this commercial browser
allows for CSS files to be associated with a given XML file

        <?xml-stylesheet type="text/css" href="URI"?>

For pedagogical purposes, students can work both TEI-lite and CSS file and
play. For example, styling the header:

        teiHeader { border: thick solid #99FF99;

                      background-color: #99FF99 }

Food for thought

Linda commented:
> Any development of TEI-lite would be greatly appreciated by those of us
> who do not try to do the heavy duty TEI encoding needed for archived
> material, but do try to do TEI-lite in order to develop teaching materials
> for our courses. One way to make sure that TEI is not underused is to
> allow such hybrids, so that different kinds of experimental uses could
> be tried. There are many of us using classic texts, and to justify our
> investment in TEI, we need to make the texts accessible online in html for
> our students. So a hearty endorsement of what Daniel suggested!
>          Linda Patrik
> On Wed, 9 Feb 2005, Daniel O'Donnell wrote:
> > I've been thinking about our discussion of incompatibilities between tei
> > and xhtml, and especially Sabastian's point that commerical browsers are
> > not xml-neutral in the sense that they expect html tags like <img>
> > rather than tei tags like <figure>.
> >
> > I wonder if it would it be worthwhile (or possible) to design a
> > 'tei-lite' that incorporated what we for want of a better word might
> > call the necessary html "operational" tags like <img> in anotherwise tei
> > tagset. Perhaps better described as "tei-hybrid" this set would allow
> > users to code directly for browsers and CSS style.
> >
> > I can see an obvious philolosphical objection: the resulting packet
> > would not be valid tei and hence would affect document exchange and
> > interoperability. I can also see an obvious practical objection: xslt
> > already exists to transform tei-xml to xhtml. But, especially in the
> > case of incompatibilities between tei and xhtml like paragraph internal
> > block quotes, one solution might be to keep the tei whenever possible
> > and only transform the bits that work otherwise work in a browser.
> >
> > Ideas?
> > -dan
> >
> >
> >
> > --
> > Daniel Paul O'Donnell, PhD
> > Associate Professor of English
> > University of Lethbridge
> > Lethbridge AB T1K 3M4
> > Tel. (403) 329-2377
> > Fax. (403) 382-7191
> > E-mail <[log in to unmask]>
> > Home Page <>
> > The Digital Medievalist Project: <>
> >

Francois Lachance, Scholar-at-large

2005 Year of Comparative Connections. DIA: Comparative connections? LOGZ:
Connection, first. Comparison, next. DIA: Check. Comparable ways of
connecting. LOGZ: Selection outcomes, first. Comparative Connections,