DEMMR - March 2018 University of Pennsylvania Workshop

A Digital Editing Workshop with University of Pennsylvania MS Roll 1563

Author: Ryan Gerber

Homework 03/30/18

MIDDLE ENGLISH – I would like the Middle English portions of this MS Roll to be individually searchable. I think we should use the xml:lang attribute in a div tag for these portions. As well as the <hi> tag for the red color. Something like this:

<div xml:lang=“enm”>
        <ab>
           <hi rend=“red”>
                    And also the uertuys of thys<lb/> oryson kan no man telle. For
                    Seynt paule ma<lb/>te hyt by inspiracion of the holy gost.
                   <!– text until end of ME portion –>
             </hi>
        </ab>

 </div>

 

Not all of the red text is ME, though, and I wonder if there is a more specific, unique, and compact tag for the ME portions. Also are we using <lb/> or <l> </l> more frequently?

 

PEOPLE – From my selection, at least, this text seems to allude to the origins of these prayers and legitimates them by attaching them to religious figures (e.g. St. Paul above). I think we should use the <rs> for this (e.g. <rs type=”person”> Seynt paule</rs>) but I would like to be more specific for those looking for actions attributed to important figures.

 

DECORATED INITIALS – The decorated initials are pretty regular in their design, but are of two different sizes, so we should maybe use <hi rend=”d1”>D</hi> as well as <hi rend=”d2”>d</hi>

And <hi rend=”a1”>A</hi> with the <desc type=“initial”> tag appended to it. 

 

DAMAGE TYPES – Damage and type of damage, I think, will be an important descriptor for this roll. We can use the <damage agent=”*type of damage*”> tag to be more descriptive of the types of damage on the manuscript (triangle at the beginning, red blob, dark abrasions). How extensive should we be with these, though?

<P> and <AB> – There are paragraph rubrications in this text and we should reserve <p> for those rubrications and not for the ME portions, which are of a different textual register in the context of this roll.

Pre-Workshop Reflection

     Both of these readings have really made me excited to engage in the critical conversation surrounding text encoding. Lou Burnard’s article offers an optimistic vision of text-encoding as a possible “interlingua for the sharing of interpretations” (6), but Amanda Gailey presents some real problems and limitations that challenge Burnard’s slightly utopian ideas. While Burnard speaks with the hope of an ideal “unified approach” (3) that text-encoding allows, I find that Gailey’s call for “deep editing” in light of text-encoding is more tethered to the realities and limitations of applying close reading to digital markup. Gailey points out that XML (TEI) encoding “would almost certainly fail to accommodate several different interpretations of the text coexisting in the same file”(8), which conflicts with Burnard’s hope for a shareable “critical consensus”. Indeed, as many of us know, critical consensus is rare at best in our respective fields, and Gailey is speaking our language when she voices skepticism about an unproblematic vision of what text encoding can be. We are made to confront the fact that a full encoded text, including analysis, would need to be able to accommodate multiple scholarly perspectives.

     Another important limitation that Gailey brings up is the problems inherent in encoding a fully “searchable” document by modern standards which, as opposed to old fashioned close reading, involves a cursory glance or term-based search of certain themes or topics. Often, an author – especially if they are working in a literary tradition –  will not explicitly mention the topic they are discussing whether for hyperbolic or metaphorical effect – as in Whitman’s “O Captain! My Captain!”, which refers to Abraham Lincoln without mentioning him by name (Gailey 6) – or simply because of some compositional circumstance that allows for its omission – as in the Jaybird pun in Joel Chandler Harris’ tale that Gailey discusses (13). These hidden or obscured meanings (and here Gailey is exceptionally insightful) need to be made explicit for researchers through the use of encoding, or they risk being merely a reliable digital text without any of the potential that text encoding makes possible.

     Gailey’s problems with how encoding will affect the canon and perhaps present a “underdeveloped or optimistically skewed” (16) idea of the past are also interesting and highly relevant to the practice of digitizing texts – prompting questions familiar to anyone who has worked with the study of the literary canon such as which texts do we choose to digitize, and why? What do we leave out, and why? I look forward to working through these ideas and more with all of you!

-Ryan Gerber

Skip to toolbar