<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="../stylesheets/yaps-tei.css"?>
<?oxygen RNGSchema="../schema/yaps.rnc" type="compact"?>
<?oxygen SCHSchema="../schema/yaps.sch"?>
<TEI xmlns="http://www.wwp.brown.edu/ns/yaps/1.0" xmlns:xi="http://www.w3.org/2001/XInclude">
  <teiHeader>
    <fileDesc>
      <titleStmt>
	<title>Overview of the TEI</title>
	<author xml:id="JF">Julia Flanders</author>
      </titleStmt>
      <editionStmt>
        <edition>Texas A &amp; M University</edition>
      </editionStmt>
      <publicationStmt>
        <distributor>Women Writers Project (via website)</distributor>
        <address>
          <addrLine>wwp@Brown.edu</addrLine>
        </address>
        <date when="2009-04-17"/>
        <availability status="restricted">
          <p>Copyright 2007 Syd Bauman, Julia Flanders, and Brown WWP</p>
	  <p>This TEI-encoded XML file is available under the terms of
	  the <ref target="http://creativecommons.org/licenses/by-sa/3.0/">Creative
	  Commons Attribution-ShareAlike 3.0 (Unported)</ref>
	  license.</p>
        </availability>
        <pubPlace>Providence, RI  USA</pubPlace>
      </publicationStmt>
      <sourceDesc>
	<p>This is the source.</p>
      </sourceDesc>
    </fileDesc>
    <revisionDesc>
     <change when="2008-01-06" who="#JF">Made new short version</change>
      <change when="2006-03-13" who="#SB">automatically converted from presentation.odd conforming to
	yaps.odd conforming using p2y.xslt and p2y.perl</change>
      <change when="2006-03-02" who="#JF">removed SGML &amp; P5 -specific slides</change>
      <change when="2006-02-13" who="#JF">Added slides on What is XML and more on P5. </change>
      <change when="2006-03-05" who="#JF">Added more detail on TEI</change>
    </revisionDesc>
  </teiHeader>
  <text>
    <presentation>
     <section>
      <head>Motives for Text Encoding</head>
      <slide>
       <list type="unordered">
        <item>To store information for the long term</item>
        <item>To analyse information</item>
        <item>To share information</item>
       </list>
       <p>...which is why the TEI is so useful...</p>
      </slide>
      <lectureNote>
       <p>We've been talking so far about the kinds of responsibility that document modelling and text encoding express concerning the text itself: to represent it adequately in an intellectual sense </p>
       <p>How about the larger context? Why do we need text encoding, socially? What function does it serve in the larger ecology of scholarship?</p>
       <p>There are several other important functions text encoding can perform:
        <list>
         <item>To store information for the long term, in a format that is not vulnerable to changes
          in hardware and software</item>
         <item>served by using an non-proprietary, open data format like XML</item>
         <item>To exchange information meaningfully with colleagues and other projects, and to publish it for future
          use.</item>
         <item>to achieve this, you need not just an adequate conception of how you want to model your textual information: you need to agree on this conception with anyone you plan to share data with</item><item>in other words, you need some sort of lingua franca, a common standard that expresses what you all agree are the important concepts and structures</item>
         <item>for this, you also need some sort of infrastructure for developing and maintaining the
          markup system and even more importantly its documentation, so that people who want to use it
          have a place to go find it, learn about it.</item>
         <item>you might be able to come up with a perfectly good encoding system all by yourself; if
          you lived on a desert island, you wouldn't have any motive to do otherwise</item>
         <item>but insofar as text encoding is a community-oriented activity, inventing your own
          system from scratch can be a very solipsistic activity</item>
        </list>
       </p>
       <p>This is ultimately why the TEI exists: to provide a long-term, detailed, analytically rich markup system that is understood by an entire community and can be used to create sharable, durable representations of the textual objects that community cares about.</p>
      </lectureNote>
     </section>

      <section>
	<head>What is the TEI?</head>
	<slide>
	  <p>Technically: a standards organization for humanities text encoding</p>
	  <p>Organizationally: an international membership consortium</p>
	  <p>Socially: a community of people and projects</p>
	</slide>
	<lectureNote>
	  <p>Technically: The TEI is a standards organization that exists to create, maintain, and
	    disseminate a standard for humanities text encoding<list>
	      <item>a common language for encoding humanities documents of all sorts, typically for
		research or archival purposes</item>
	      <item>internationally developed and used</item>
	      <item>widely supported and used within the academy, libraries, museums, anywhere people have
		important humanities data</item>
	    </list></p>
	  <p>Organizationally: The TEI is an international consortium whose members are institutions that
	    want the TEI to continue to exist</p>
	  <p>Socially: The TEI is a community of people and projects who use text encoding in a wide
	    variety of ways, and who communicate with one another about their research and the practical
	    problems associated with it.</p>
	  <p>The TEI is also, importantly, the set of guidelines and XML specifications that make up the
	    TEI Guidelines.<list>
	      <item>first published in 1990; a major release in 1994 (P3) which was the first version to be
		widely used</item>
	      <item>an XML version published in 2001 (P4)</item>
	      <item>now, a fully revised version being prepared, which will use schemas rather than DTDs
		and will also add a number of new features. This will be released next year as P5.</item>
	    </list></p>
	</lectureNote>
      </section>

      <section>
	<head>The TEI Guidelines</head>
	<slide>
	  <list>
	    <item>Can be applied strictly or loosely</item>
	    <item>Can adapt to local conditions</item>
	    <item>Designed as a set of modules that can be selected as needed</item>
	   <item>Not unlike a human language in some respects</item>
	  </list>
	</slide>
	<lectureNote>
	  <p>The TEI Guidelines are a flexible specification:</p>
	  <list>
	    <item>Not intended to be difficult or burdensome to use</item>
	    <item>Not intended to require uniformity from all users</item>
	    <item>Intended to be adapted and customized</item>
	   <item>Not unlike a human language: has idiomatic usage, dialects, local usage</item>
	  </list>
	</lectureNote>
      </section>

     
      <section>
	<head>Areas of Usage</head>
	<slide>
	  <list>
	    <item>Digital libraries and digital archives</item>
	    <item>Literary and cultural materials</item>
	    <item>Scholarly editions</item>
	    <item>Manuscript collections and descriptions</item>
	    <item>Dictionaries</item>
	    <item>Language corpora</item>
	    <item>Historical documents</item>
	    <item>Anthropology and social sciences</item>
	    <item>Authoring</item>
	    <item>Many other areas...</item>
	  </list>
	</slide>
	<lectureNote>
	  <list>
	    <item>Digital libraries and digital archives</item>
	    <item>Literary and cultural materials</item>
	    <item>Scholarly editions</item>
	    <item>Manuscript collections and descriptions</item>
	    <item>Dictionaries</item>
	    <item>Language corpora</item>
	    <item>Historical documents</item>
	    <item>Anthropology and social sciences</item>
	    <item>Authoring</item>
	    <item>Many other areas…</item>
	  </list>
	</lectureNote>
      </section>

      <section>
	<head>Diagram of TEI Usage</head>
	<slide>
	  <figure>
	    <graphic height="600px" url="./gfx/tei_areas.jpg"/>
	  </figure>
	</slide>
      </section>

      <section>
	<head>Customization</head>
	<slide>
	  <p>The process of altering the TEI schema and documentation to
	    match your needs.</p>
	  <p>Changes include:
	    <list>
	      <item>
		choosing which parts to use or omit
	      </item>
	      <item>changing the names of elements or attributes</item>
	      <item>restricting the values of attributes</item>
	      <item>adding new elements</item>
	      <item>adding new attributes</item>
	    </list></p>
	</slide>
	<lectureNote>
	  <p>It’s important to note that the TEI is not a fixed tag set that is written in stone<list>
	      <item>it is intended to be customized: both for users to select a subset of the TEI that they
		really need, and for users to add elements for particular features in their texts</item>
	    </list></p>
	  
	  <p>In fact, the TEI is not really ever used directly in its raw form. In all
	    cases a customized <soCalled>view</soCalled> of the TEI,
	    or a <soCalled>customization</soCalled> is what is used.</p>
	  <p>When users want to create TEI schemas, they create a
	    customization file that lists the modules they would
	    like to use, the specific elements they would like to
	    add or delete, the attributes they change, etc. </p>
	  <p>As a result, in actual practice there is both a common core of usage that is more or less universal among TEI projects—the stuff that everyone agrees on—and also beyond it a thinning penumbra of specialized uses and extensions that express the needs of particular groups and projects </p>
	  <p>There is no single orthodox TEI practice: there are greater and lesser degrees of adherence to a set of central principles and usages</p>
	  <p>For projects in which consistency and use of a common standard is very important (for instance, digital library collections) there's greater emphasis on best practices and a tendency to discourage idiosyncrasy, but for projects and individuals where the need for local expressiveness is much greater, specialized TEI methods are very common and arguably essential to good practice</p>
	</lectureNote>
      </section>

     
      <section>
	<head>Sources of Information</head>
	<slide>
	  <p>Where and how to find out more:</p>
	  <list>
	    <item>The WWP seminars site and the WWP <title>Guide to Scholarly Text Encoding</title></item>
	    <item>TEI web site</item>
	    <item>The TEI listserv (TEI-L)</item>
	    <item>Colleagues at other projects</item>
	  </list>
	</slide>
	<lectureNote>
	  <p>The most important takeaway message here concerning the TEI is that it is adaptable; expressive but requires some thought (in other words, it won't do the analytical work for you); it's a tool that has arisen out of certain strands of humanities thought and that carries with it certain assumptions that are worth probing</p>
	  <p>This grant program (the seminars and the supporting services that accompany them) is intended to encourage faculty and students to learn more about the TEI, and to give them the kinds of information that they will find legible and relevant to their interests</p>
	</lectureNote>
      </section>
    </presentation>
  </text>
</TEI>
