<?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>Concepts of markup for scholarship</title>
	<author xml:id="JF">Julia Flanders</author>
      </titleStmt>
      <xi:include href="./boilerplate_publicationStmt.xml">
	<xi:fallback>
	  <publicationStmt status="restricted">
	    <note type="auto">WARNING: XInclude processing failed &#x2014; this file should not be copied or
	    used (and is invalid) as a result.</note>
	  </publicationStmt>
	</xi:fallback>
      </xi:include>
      <sourceDesc>
	<p>This is the source.</p>
      </sourceDesc>
    </fileDesc>
    <revisionDesc>
      <change when="2008-04-30" who="#SB">tiny tweaks to formatting</change>
      <change when="2008-01-05" who="#JF">created file</change>
    </revisionDesc>
  </teiHeader>
 <text>
  <presentation>
   <section>
    <head>Parallel texts and textual multiplicity</head>
   
    <slide>
    <figure>
     <graphic width="100%" url="../gfx/parallel_texts.png"/>
    </figure>
    </slide>
    <lectureNote>
     <p>So far we've covered a fair amount of basic encoding that's useful for a
      fairly wide range of texts</p>
     <p> focus so far on the encoding of primary sources in a transcriptional
      mode: representing the source reading </p>
     <p> At this point we're going to spend some time thinking about how we
      represent the specifically scholarly layer: the added information that
      expresses editorial activity and information of various kinds. </p>
     <p> I have several kinds of information like this in mind; please suggest
      others</p>
     
     <p>In a sense, this concept of parallelism is the overarching theme here:
      what scholars do (in a sense) when they work with a text is explore and
      express its plurality of meaning, of textual possibility this is true
      whether they are acting as editors or as critics: whether they're
      preparing a new version of the text for publication, or creating a version
      for their own interpretive use. </p>
     <p> First, some large-scale examples of this kind of parallelism: <list>
      <item>creating a parallel edition</item>
      <item>representing a translation</item>
     </list>
     </p>
     <p> The functional goal in creating these kinds of parallel structures is
      to be able to let the reader use the parallel texts to make comparisons,
      see similarities, read the translation against the original, search in one
      language and get results in the other language, etc. </p>
     <p> From the markup standpoint, the essential thing here is to be able to
      represent the alignment of the two texts, but the question of granularity
      (of how fine-grained the alignment is) depends on what kinds of functional
      goals you have </p>
     <p> We're not going to cover the mechanisms in detail, because they're
      complex and tricky, but I want to show you the concept so that if you're
      thinking about doing this you know the fundamentals of what's involved</p>
     
     
     <p>Start with showing alignment issues: <list>
       <item>coarse-grained (text level, stanza level): we can often infer the
        finer-grained alignment automatically (e.g. in verse where both texts
        have the same number of lines)</item>
       <item>fine-grained (line level, potentially below): in cases where more
        specific alignment is needed</item>
       <item>specific alignment doesn't scale up; instead, can use out-of-line
        approach</item>
      </list>
     </p>


    </lectureNote>
   </section>
   <section>
    <head>Encoding parallel structures</head>
    <slide>
     <figure>
      <graphic height="100%" url="../gfx/parallel_short.png"/>
     </figure>
     <eg>
<![CDATA[<lg type="stanza" xml:lang="fr">
  <l xml:id="fr2.01" corresp="#en2.01">Nos péchés sont têtus, nos repentirs sont lâches;</l>
  <l xml:id="fr2.02" corresp="#en2.02">Nous nous faisons payer grassement nos aveux,</l>
  <l xml:id="fr2.03" corresp="#en2.04">Et nous rentrons gaiement dans le chemin bourbeux,</l>
  <l xml:id="fr2.04" corresp="#en2.03">Croyant par de vils pleurs laver toutes nos taches.</l>
</lg>

<lg type="stanza" xml:lang="en">
  <l xml:id="en2.01" corresp="#fr2.01">Our sins are stubborn, craven our repentance.</l>
  <l xml:id="en2.02" corresp="#fr2.02">For our weak vows we ask excessive prices.</l>
  <l xml:id="en2.03" corresp="#fr2.04">Trusting our tears will wash away the sentence,</l>
  <l xml:id="en2.04" corresp="#fr2.03">We sneak off where the muddy road entices.</l>
</lg>
      ]]>
     </eg>
    </slide>
    <lectureNote>
     <p>Explain linking and pointers</p>
    </lectureNote>
   </section>
   <section>
    <head>More complex parallelism</head>
    <slide>
     <eg>
<![CDATA[<linkGrp type="alignment">
  <link targets="#fr2.01 #en-a2.01 #en-b2.01 #en-c2.01 #en-d2.01"/>
  <link targets="#fr2.02 #en-a2.02 #en-b2.02 #en-c2.02 #en-d2.02"/>
  <link targets="#fr2.03 #en-a2.03 #en-b2.03 #en-c2.04 #en-d2.03"/>
  <link targets="#fr2.04 #en-a2.04 #en-b2.04 #en-c2.03 #en-d2.04"/>
</linkGrp>
      ]]>
     </eg>
     <figure>
      <graphic url="../gfx/parallel_linkgrp.png" width="100%"/>
     </figure>
    </slide>
   </section>
   <section>
    <head>Textual splitting: parallelism at a more local level </head>
    <slide>
     <figure>
      <graphic height="400px" url="../gfx/askew_sample_small.png"/>
     </figure>
     <eg><![CDATA[<p>...with them, bycause they woulde
<lb/>not be 
    <choice>
       <abbr>boūde</abbr>
       <expan>bounde</expan>
    </choice> 
also for an other wo]]><hi rend="css( font-style: italic; font-weight: normal; )">[see below]</hi><![CDATA[
<lb/>mā at theyr pleasure, whom they
<lb/>knewe not, nor yet what matter
<lb/>was layed unto her charge. Not
<lb/>wythstandynge at the laste, after
<lb/>moche a do and reasonyng to and
<lb/>fro, they toke a bonde of them of
<lb/>recognisaunce for my fourth com
<lb/>mynge. And thus I was at the
<lb/>last, 
    <choice>
      <orig>delyuered</orig>
      <reg>delyvered</reg>
    </choice>. 
Written by me An
<lb/>ne Askewe.
</p>
]]></eg>
     <eg>
<![CDATA[<choice>
  <abbr>
    <choice>
      <sic>wo<lb/>mā</sic>
      <corr>wo-<lb/>mā</corr>
    </choice>
  </abbr>
  <expan>
    <choice>
      <sic>wo<lb/>man</sic>
      <corr>wo-<lb/>man</corr>
    </choice>
  </expan>
</choice>]]>
     </eg>
    </slide>
    <lectureNote>

     <p> There are a number of kinds of local editorial changes that are often
      made in the process of transcription and editing: processes of
      regularization and correction that are often done silently and noted in an
      introduction: <list>
       <item>correction of typographical errors in the source</item>
       <item>regularization or modernization of spelling and typography</item>
       <item>expansion of abbreviations</item>
      </list>
     </p>
     <p> In print-based editing, these choices are exclusionary: whichever kind
      of reading you decide to show the reader, its complementary version has to
      be suppressed (it could be indicated in a note or an appendix but it can't
      typically be displayed as part of the regular reading surface) </p>
     <p>In an XML transcription, however, it's possible to represent both (or in
      principle multiple) readings in a data structure that shows their
      parallelism and treats them as alternatives, which can then be chosen
      (displayed, searched, etc.) when desired. </p>
     <p> In TEI, this mechanism is the <gi>choice</gi> element, which represents
      a moment of textual forking, where instead of a single reading the text
      offers a choice of readings </p>
    </lectureNote>
   </section>
   <section><head>Transcriptional complexities</head>
    <slide>
     <figure>
      <graphic width="100%" url="../gfx/ms_original.jpg"/>
     </figure>
     <eg>
<![CDATA[<lg>
<head>After <del>an</del><add>the <del>unsolv'd</del></add> argument</head>
<l><del>The</del><add><del>Coming in,</del> A group of</add> little children, and their
   <lb/>ways and chatter, flow in <del>upon me</del></l>
<l>Like <add>welcome</add> rippling water o'er my
   <lb/>heated <add>nerves and</add> flesh.</l>
</lg>
      ]]>
     </eg>
    </slide>
    <lectureNote>
     
     
     <p>What's at stake here: because the transcription of manuscript materials (and often printed texts as well)
      involves significant efforts of decipherment and in many cases conjecture
      or interpretation, and also because primary sources are informationally complex
      (authorial revision, erasures, missing letters, illegible passages, etc.),
      a responsible transcription needs to capture not just the end product but
      also information about the process and the editorial decision-making: not
      just produce a clean-looking innocent butter-wouldn't-melt-in-its-mouth
      transcription but preserve information about what was difficult or unclear</p>
     <p>conventions for accomplishing this are familiar from print: carets and
      brackets for marking insertions and deletions, italics to indicate unclear
      text, footnotes to indicate hypothetical readings or to describe damaged
      sections</p>
     <p> In text markup, the goal is to formalize as much of this information as
      possible and represent it systematically <list>
       <item>to classify the reasons for illegibility (where possible), to
        formalize the rationales for determining whether a given letter is
        illegible or simply unclear</item>
       <item>with the goal of making it possible to control the display of the
        reading surface of the text: to show or hide the deleted words and
        hypothetical readings, perhaps even to let the reader control the
        threshold of conjecture at which readings are displayed or hidden ("only
        show me things you're really certain about")</item>
      </list>
     </p>
    
     <p> Next: show basic encoding features: unclear, supplied, gap, add, del
     </p>
    </lectureNote>
   </section>
   <section>
    <head>More examples</head>
    <slide>
     <figure>
      <graphic url="../gfx/ms_receipt.jpg" height="200px"/>
     </figure>
     <eg>
<![CDATA[<p>Johnston etc 1764 Mr Nikl<unclear>e</unclear>
<supplied>s</supplied><gap reason="folded" extent="unknown"/> Brown 
<unclear>&amp;Co</unclear> to me George <unclear>Beverly juner</unclear> 
to ten Rum Barels at Four pound &per; Barel — — —  £40</p>
      
      ]]>
     </eg>
    </slide>
   </section>
   <section>
    <head>Critical apparatus</head>
       <slide>
     <figure>
      <graphic url="../gfx/critical_apparatus.png" height="600px"/>
     </figure>
     
    </slide>
    <lectureNote>
    
     <p>Critical apparatus is a structured expression of a complex textual field
      in which there are multiple possible readings: either because there are
      multiple witnesses, or because the nature of the text requires emendation
      (because of damage, scribal error, etc.)</p>
     <p>Showing variant readings, emendations, etc. and organizing them into
      systems</p>
     <p>In markup, the goal is to create a data structure that can express the
      relationships between the various pieces of information, while also
      preserving the documentary nature of the text (and allowing other
      information to be preserved, such as renditional information, genre,
      syntactic markup, etc.)</p>
     <p>In some ways, similar to the <gi>choice</gi> mechanism: a data structure
      that represents a set of textual alternatives</p>
     
     <p> The key pieces of information in play: <list>
      <item>the lemma or the base reading, if your editorial theory includes
       this concept (it need not: you might not want to express a preference)</item>
      <item>one or more readings: these might be from other textual witnesses,
       or from editorial conjecture</item>
      <item>information about which witness each reading comes from</item>
     </list>
     </p>
    </lectureNote>
   </section>

   <section>
    <head>Critical commentary and annotation</head>
    <slide>
     <figure>
      <figDesc>page image of commentary notes</figDesc>
      <graphic width="100%" url="../gfx/editorial_notes1.png"/>
     </figure></slide></section>
   <section><head>Another example</head>
    <slide>
     <figure>
      <figDesc>page image of commentary notes</figDesc>
      <graphic width="100%" url="../gfx/editorial_notes2.png"/>
     </figure>
    </slide>
    <lectureNote>
     <p>Critical commentary and annotation <list>
       <item>at its simplest, can be expressed as prose: in effect, an essay
        associated with the text; familiar as <term>a note on the text</term> or a critical
        essay</item>
      <item>may also express editorial principles or details of the transcription approach (e.g. regularization practices)</item>
       <item>In a TEI-encoded text, this kind of prose can be treated as metadata: in TEI header (e.g. the
        <gi>notesStmt</gi>, the <gi>samplingDesc</gi>, the
        <gi>editorialDecl</gi>)</item></list></p></lectureNote></section>
   <section>
    <head>Notes as metadata</head>
    <slide>
     <eg><![CDATA[<teiHeader>
  <fileDesc>
    <!-- ... -->
    <notesStmt>
      <note type="textual">As far as we know, <title>Warning to the Dragon</title> 
      is Lady Eleanor's first printed tract...</note>
    </notesStmt>
  </fileDesc>
  <encodingDesc>
    <editorialDecl>
      <p>...Capital letters have been reduced to lower case when, for 
      example, the second letter of a word at the opening of a tract is
      capitalized in the base text. Title pages have been regularized...</p> 
    </editorialDecl>
   </encodingDesc>
</teiHeader>]]></eg>
    </slide>
   </section>
   
   <section><head>Notes</head>
    <slide>
     <eg><![CDATA[<p>It seemed good unto me, having a perfect understanding 
given mee in these things, and the dispensation of them, an office
not a trade; to roote out, to pull down, to build, and to plant, by
the grace and bounty of JESUS our Lord God. To present this Visitation
to your view, joyning you together of the <seg xml:id="anchor01">first 
Arke, and universall great House</seg>, vessels of Honor and dishonor, 
some cleane and purified, others having need of purging.</p>
      ...
<note type="editorial" target="#anchor01">See Gen. 7.</note>]]></eg>
    </slide>
    <lectureNote><p>
       Commentary can also be made more granular: in the form of notes attached to
       specific places in the text; this is also a familiar formulation</p>
     <p>In TEI, notes like these are encoded using the <gi>note</gi> element
       these can be classified: to indicate responsibility, to indicate
        what kind of note (using any classification system that seems useful:
        e.g. annotation, correction, hypothesis, context, gloss, etc.)
      
     </p> 
    </lectureNote>
   </section>





  </presentation>
 </text>
</TEI>
