# LaTeX code for TEI XML

\documentclass[a4paper,11pt]{article}
\usepackage{ulem}
\usepackage{a4wide}
\usepackage[dvipsnames,svgnames]{xcolor}
\usepackage[pdftex]{graphicx}

\usepackage{hyperref}
% commands generated by html2latex

\begin{document}

Colette Leung

October 14, 2010
\begin{tabular}

\subsection{Contents}
\begin{itemize}
\end{itemize}
\end{tabular}\hypertarget{Background}{}

\subsection{Background}

The acronym \href{http://www.tei-c.org/index.xml}{TEI} can be used to refer to any of three different meanings.  TEI stands for Text Encoding Initiative, and can refer to either: \href{/index.php/File:TEI.png}{
\begin{itemize}
\item TEI as a research community
\item TEI as an organization and consortium
\item TEI XML.
\end{itemize}

This article focuses on TEI XML as a technology, including its meaning, its history, and its significance in both academia and wider realms.

XML is a markup language that is largely undefined ??? it is a meta-language that comes with rules and procedures, but there is no set vocabulary or syntax associated with XML.  Instead, XML is used to develop particular markup languages by encoders and document analysts.  Thus, XML is often accompanied by a DTD (document type definition) or Schema, which specifies the rules a particular encoding follows.  \href{/index.php/File:TEI_DTDs.png}{
\includegraphics{/AnnokiUploadAuth.php/thumb/9/9c/TEI_DTDs.png/200px-TEI_DTDs.png}}  The TEI XML is therefore a subset of XML itself; more precisely the TEI provides guidelines for encoding literary and linguistic texts in XML. These guidelines, which can be used to create a DTD or Schema for humanities projects, were created and are maintained by the TEI Consortium.

The TEI guidelines known as \href{http://www.tei-c.org/Guidelines/P4/index.xml}{P4} and \href{http://www.tei-c.org/Guidelines/P5/index.xml}{P5} propose specific \href{http://www.tei-c.org/Guidelines/P4/p4dtd.xml}{DTDs} and \href{http://www.tei-c.org/release/doc/tei-p4-doc/html/index.html}{tagsets} to use. While not a standard, TEI XML attempts to provide some basis of commonality to encoders.  TEI XML has been designed to suit encoding for a number of different types of documents in the humanities and social sciences: manuscripts, dictionaries, poems, prose, transcripts, etc.  The idea is that most scholarly documents should be able to be encoded using these guidelines.

There is a great deal of flexibility to TEI XML as well, which increases its desirability amongst users.  TEI XML can be customized to fit a project, ant the encoder chooses what they wish to tag or not tag.  This means that while TEI proposes a set of guidelines that allow for easier transference and sharing of documents amongst scholars, it doesn???t provide a standard, which would be an unflexible set of rules that all encoders must meet.  Therefore, different documents in TEI will be encoded differently.  A user can still make a document encoding their own, even while allowing it to be more accessible to other scholars.  Generally, TEI encoded documents include a core tag set (teiHeader), a base tag set (selection of prose, play, etc.) and an additional tag set (linking, figures, etc.)

The \href{http://www.tei-c.org/About/mission.xml}{mission of the TEI} is stated as follows: ???[to] develop and maintain a set of high-quality guidelines for the encoding of the humanities texts, and to support their use by a wide community of projects, institutions, and individuals.??? (TEI, 2010)  The TEI Consortium seeks to do this through developing guidelines, disseminating information, training workshops, and the cultivation of a research community.  Currently, the TEI is used by libraries, museums, publishers, and individual scholars to present texts for online research, teaching, and preservation.

\\\hypertarget{History}{}

\subsection{History}

The \href{http://www.tei-c.org/About/history.xml}{origins} of TEI XML must be traced back all the way to 1987.  It was during this year that the Poughkeepsie Conference was held in New York, and the TEI was founded out of this to develop guidelines for encoding machine-readable texts of interest to the humanities and social sciences.  We can see from this that although XML wasn???t initially involved, the desire for sharing, creating software and simplifying the training of encoders goes far back, as well as the desire to create some sort of control for the sprawl of markup languages.\href{/index.php/File:Poughkeepsie.png}{
\includegraphics{/AnnokiUploadAuth.php/thumb/c/c0/Poughkeepsie.png/200px-Poughkeepsie.png}} In June 1990, the P1 guidelines were created.  These were the guidelines outlined in the Poughkeepsie conference, and for the following three years, they were revised and improved.  This finally resulted in the P3 guidelines for markup languages in 1994.  These would become the most widely-used standard for text materials for performing online research and teaching, and are now the standard for the humanities.

However, by 1998, XML was recognized by the \href{http://www.w3.org/}{W3C}, and so the P3 had to be updated to enable users to work with the emerging XML toolset.  A consortium was created to maintain, develop, and promote TEI.  By 2002, \href{http://www.tei-c.org/Guidelines/P4/index.xml}{P4} was created, basically an XML version of P3.  The Consortium actively continued to work on these guidelines, even as \href{http://www.tei-c.org/Guidelines/P5/index.xml}{P5} was begun and released in 2007.  The P5 guidelines are currently still under revision.

The TEI website also maintains accessible \href{http://www.tei-c.org/Vault}{archives} to past guidelines and listservs. \hypertarget{Significance}{}

\subsection{Significance}

There are many online projects that use TEI XML.  The TEI website includes a \href{http://www.tei-c.org/Activities/Projects/}{list of major projects}, some of which include the \href{http://www.menota.org/}{Medieval Nordic Poetry Project}, \href{http://www.open.ac.uk/Arts/hestia/}{HESTIA: Herodotus timeline}, and \href{http://www.finerollshenry3.org.uk/home.html}{Fine Rills Henry III}.

Any one of these project websites can be visited.  Upon selecting ???View Source??? under the View Menu in your browser toolbar, you can see the TEI encoding used for these projects.\href{/index.php/File:Menota.png}{

What is perhaps most significant of the TEI XML, however, is its success.  Many argue that all of the goals of the Poughkeepsie conference have not only been met, but have been exceeded by the TEI.  The TEI is very significant in the history of humanities computing, as it is symbolic both of what technology can do for the humanities, but also because it is so widely used and recognized.  In fact, TEI XML is the encoding scheme of choice for the production of both small and large documents and projects in the humanities, whether they are texts, reference works, linguistic corpora, etc., as well as for cultural heritage collections.  As such, it can be seen that the TEI spreads across many subject areas, and is available to students, scholars, and the wider public.  This allows it to not only be easier to share work amongst scholars, but also can serve as a tool for long-term preservation.  TEI XML connects many different social science and humanist disciplines together, and has created a diverse research community, who can write in and recommend changes and additions to existing guidelines.

TEI XML has been endorsed by a number of organizations, including digital libraries, electronic text progress, and the Library of Congress.  The latter has produced guidelines for the best practice in applying TEI metadata.  Further, TEI has not only allowed an exchange of information, but ???\textit{improves} the ability to describe textual features.??? (Renear, 2004)  TEI allows for new possibilities of representation and communication, and illuminates new textual issues.  \hypertarget{Related_Technologies}{}

\subsection{Related Technologies}

TEI XML is a subset of XML, and so it worth remembering that is thus related to other technologies, such as SGML, XHTML and HTML.

Special recognition should also be given to a specific DTD of TEI, \href{http://www.tei-c.org/Guidelines/Customization/Lite/}{TEI Lite}.  This came into existence in 1995.  It is a subset of the full TEI encoding scheme, since there is much of the full TEI that is unnecessary.  TEI Lite is so efficient, however, that it meets 90\% of TEI community needs 90\% of the time.  (Vanhoutte 2004, 11)

It is also worth mentioning metadata schemes as related technologies of TEI XML.   These tend to be designed for specific purposes, instead of covering a wide expanse of documents such as what TEI XML does.  This makes certain metadata schemes incredibly useful in certain circumstances.\href{/index.php/File:DublinCore.png}{
\includegraphics{/AnnokiUploadAuth.php/thumb/2/2a/DublinCore.png/200px-DublinCore.png}} The \href{http://dublincore.org/}{Dublin Core} texts are perhaps one of the most popular of these metadata schemes.  There are 15 base texts in the Dublin Core, which were developed in Ohio, and not Ireland as the name might suggest.  This metadata scheme was meant for Library and Information Sciences, as well as Computer Sciences.  The mission of the Dublin Core is stated as ???to provide simple standards to facilitate the finding, sharing, and management of information.???  It was designed for books, digital videos, sound, image, or text files.

It is possible to use TEI in conjunction with these metadata schemes, much like one can choose to use many different TEI DTDs for one document, if there are different kinds of text in that document. (For example, a piece of literature may have poetry as well as prose.)\href{/index.php/File:METS.png}{
\includegraphics{/AnnokiUploadAuth.php/thumb/5/57/METS.png/200px-METS.png}} Another popular metadata scheme is that of \href{http://www.loc.gov/standards/mets/}{METS} (Metadata Encoding and Transmission Standard).  This is XML designed for digital libraries.  It is a standard for encoding descriptive, administrative, and structural metadata.  This standard is maintained in the Network Development and MARC Standards Office of the Library of Congress.  These are simply two examples of other XML metadata schemes. \hypertarget{Future}{}

\subsection{Future}

Considering the expansive use and scope of TEI XML, it easy to say that TEI will likely be a tool in existence for a long time, or at least as long as encoding languages are in use.  TEI is used for so many different projects, and covers so many different areas, it is difficult to imagine it disappearing overnight, especially as it is continually updated and revised, such as with the current TEI P5 guidelines.  This is part of what enables TEI to be projected as a tool for long-term preservation, and for software designs such as oXygen, an XML editor.

It is worth noting that many scholars speculate that TEI XML could benefit from more expansive and easier to use tutorials on how to use TEI XML.  Perhaps this a direction that the future of TEI XML could take.  As well, there is speculation that perhaps TEI XML will grow to include complicated kinds of text (Jannidis, 2009), instead of existing in conjunction only to metadata schemes such as the Dublin Core and METS.  \hypertarget{References}{}

\subsection{References}

Center for Digital Research in the Humanities.  University of Nebraska-Lincoln.  ???What is TEI????  Accessed October 3, 2010. \href{http://cdrh.unl.edu/articles/guide_site/tei.php}{http://cdrh.unl.edu/articles/guide\_site/tei.php}

Jannidis, Fotis.  ???TEI in a crystal ball.???  Literary \& Linguistic Computing 24 (2009): 253-265.  Accessed October 3, 2010.  doi:10.1093/llc/fqp015.  \href{http://ehis.ebscohost.com.login.ezproxy.library.ualberta.ca/eds/pdfviewer/pdfviewer?vid=1&hid=114&sid=bb4cc903-5aec-4931-b42a-af2869e86232%40sessionmgr113}{http://ehis.ebscohost.com.login.ezproxy.library.ualberta.ca/eds/pdfviewer/pdfviewer?vid=1\&hid=114\&sid=bb4cc903-5aec-4931-b42a-af2869e86232\%40sessionmgr113}

Mandell, Laura.  University of Ohio.  ???An Introduction to TEI.???  Accessed October 3, 2010. \href{http://www.users.muohio.edu/mandellc/xml/}{http://www.users.muohio.edu/mandellc/xml/}

Renear, Allen H.  ???Text Encoding.???  In Companion to Digital Humanities, ed. Susan Schreibman, Ray Siemens, John Unsworth.  Oxford: Blackwell, 2004. \href{http://www.digitalhumanities.org/companion/}{http://www.digitalhumanities.org/companion/}

Vanhoutte, Edward.  ???An Introduction to the TEI and the TEI Consortium.??? Literary \& Linguistic Computing 19 (2004): 9-15.  Accessed October 3, 2010. \href{http://ehis.ebscohost.com.login.ezproxy.library.ualberta.ca/eds/pdfviewer/pdfviewer?vid=2&hid=114&sid=78a98960-0f8c-4903-b61a-fb6268042a6c%40sessionmgr111}{http://ehis.ebscohost.com.login.ezproxy.library.ualberta.ca/eds/pdfviewer/pdfviewer?vid=2\&hid=114\&sid=78a98960-0f8c-4903-b61a-fb6268042a6c\%40sessionmgr111}\hypertarget{Useful_Links}{}

W3C Homepage: \href{http://www.w3.org/}{http://www.w3.org/}

TEI Homepage: \href{http://www.tei-c.org/index.xml}{http://www.tei-c.org/index.xml}

TEI Guidelines: \href{http://www.tei-c.org/Guidelines/P4/}{http://www.tei-c.org/Guidelines/P4/}

TEI Teach Yourself: \href{http://www.tei-c.org/Support/Learn/tutorials.xml}{http://www.tei-c.org/Support/Learn/tutorials.xml}

Projects Using TEI: \href{http://www.tei-c.org/Activities/Projects/}{http://www.tei-c.org/Activities/Projects/}

TEI Lite: \href{http://www.tei-c.org/Guidelines/Customization/Lite/}{http://www.tei-c.org/Guidelines/Customization/Lite/}

Dublin Core: \href{http://dublincore.org/}{http://dublincore.org/}

METS: \href{http://www.loc.gov/standards/mets/}{http://www.loc.gov/standards/mets/}

--\href{/index.php?title=User:ColetteLeung&action=edit&redlink=1}{ColetteLeung} 01:33, 3 December 2010 (UTC)

\end{document}