<?xml version="1.0" encoding="utf-8"?>
<?oxygen RNGSchema="../../common/schema/DHQauthor-TEI.rng" type="xml"?>
<?oxygen SCHSchema="../../common/schema/dhqTEI-ready.sch"?>
<TEI xmlns="http://www.tei-c.org/ns/1.0"
     xmlns:dhq="http://www.digitalhumanities.org/ns/dhq"
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
     xmlns:cc="http://web.resource.org/cc/">
   <teiHeader>
      <fileDesc>
         <titleStmt>
            <title>It’s For Sale, So It Must Be Finished: Digital Projects in the
         Scholarly Publishing World</title>
            <author>David Sewell</author>
            <dhq:authorInfo>
               <dhq:author_name>David <dhq:family>Sewell</dhq:family>
               </dhq:author_name>
               <dhq:affiliation>University of Virginia Press</dhq:affiliation>
         
               <email>dsewell@virginia.edu</email>
               <dhq:bio>
                  <p>David Sewell is the Editorial and Technical Manager of the University of Virginia Press’s
      Electronic Imprint division, which he joined in 2002. During 2008–9 he is serving as a member
      of the TEI Council responsible for the technical development of the Text Encoding Initiative’s
      guidelines, tools, and documentation. He has been involved with online communities and
      Unix-ish systems since graduate school at the University of California, San Diego, in the
      early 1980s, where he earned a Ph.D. in English and American literature. Before migrating into
      his current niche in the digital publishing world he taught in the English Department at the
      University of Rochester from 1984 to 1992, and was subsequently managing editor of
        <title rend="italic">Radiocarbon: An International Journal of Cosmogenic Isotope Research</title>, housed
      at the University of Arizona.</p>
               </dhq:bio>
            </dhq:authorInfo>
         </titleStmt>
         <publicationStmt>
            <idno type="DHQarticle-id">000039</idno>
            <idno type="volume">003</idno>
            <idno type="issue">2</idno>
            <dhq:articleType>article</dhq:articleType>
            <date when="2009-06-18">18 June 2009</date>
            <availability>
               <cc:License xmlns="http://digitalhumanities.org/DHQ/namespace"
                           rdf:about="http://creativecommons.org/licenses/by-nc-nd/2.5/"/>
            </availability>
         </publicationStmt>
         <sourceDesc>
            <p>Authored for DHQ; migrated from original DHQauthor format</p>
         </sourceDesc>
      </fileDesc>
      <encodingDesc>
         <classDecl>
            <taxonomy xml:id="dhq_keywords">
               <bibl>DHQ classification scheme; full list available in the <ref target="http://www.digitalhumanities.org/dhq/taxonomy.xml">DHQ keyword taxonomy</ref>
               </bibl>
            </taxonomy>
            <taxonomy xml:id="authorial_keywords">
               <bibl>Keywords supplied by author; no controlled vocabulary</bibl>
            </taxonomy>
         </classDecl>
      </encodingDesc>
      <profileDesc>
         <langUsage>
            <language ident="en"/>
         </langUsage>
      </profileDesc>
      <revisionDesc>
         <change when="2009-03-13" who="JHF">Added to SVN, updated header, added bios.</change>
      </revisionDesc>
   </teiHeader>
   <text>
      <front>
         <dhq:abstract>
            <p>Since the early 1990s, theorizing in the digital humanities has often celebrated
    open-endedness and incompletion as inherent qualities of digital work. But a scholarly publisher
    undertaking preparation and sale of digital objects cannot altogether dispense with traditional
    notions of deadlines and completion if those publications are to enter the dual marketplaces of
    peer review and institutional purchase. The Electronic Imprint of the University of Virginia
    Press was funded in 2001 with the goal of bringing born-digital scholarly projects under the
    aegis of the same review and marketing system that applies to books. In this article I describe
    how we defined the criteria for <q>done-ness</q> in creating two very different projects, a
    born-digital edition of Herman Melville’s <title rend="italic">Typee</title> manuscript and a conversion of
    the letterpress <title rend="italic">Papers of George Washington</title> into a digital edition. Our
    experience suggests that it is possible to categorize different genres of digital creations
    based on the extent to which intrinsic criteria for “done-ness” can be applied to them, and that
    decisions about completeness are always subject to extrinsic factors as well, such as budgetary
    constraints and the pressures created by competition and the evolution of standards.</p>
         </dhq:abstract>
         <dhq:teaser>
            <p>How does a publisher decide when a digital work is finished enough to enter the
    marketplace?</p>
         </dhq:teaser>
      </front>
      <body>
         <head>It's For Sale, So It Must Be 
Finished: Digital Projects in the Scholarly 
Publishing World</head>
         <div>
            <head>Some History of Terms</head>
            <p>Viewed from the perspective of 
someone who works for a university press, the 
semantics of the term <q>done</q> as 
applied to digital objects is rather curious. 
From our point of view, it's generally a good 
thing for a scholarly publication to be 
<q>done</q>: review copies can be sent 
out, books can be shipped to distributors, and 
budgets perhaps even met. Traditional publication 
in the scholarly publishing world has always 
meant the implicit guarantee that a work is the 
end product of a rigorous process of peer review, 
revision, copyediting, design, and proofreading 
shared institutionally by author, press boards, 
outside scholars, and in-house staff. When a book 
or journal issue is <q>done</q> it is a 
source of pride and satisfaction for everyone 
concerned.</p>
            <p>The case seems to be different 
with digital objects. The claim that a digital 
project or publication is <q>done</q> 
may be met with suspicion. What do you mean, your 
Web-thing is finished? Since it's nonlinear, 
how do you know where it starts or ends? Won't 
there always be more features or links you can 
add? If your Web-thing is  so much like an 
old-fashioned codex book that you can call it 
<q>done</q>, does it really belong 
online in the first place? This suspicion has a 
history. Theoretical discussion of projects in 
the digital humanities has, since the 1990s, 
suffered from semantic slippage between two 
related but nonidentical pairs of contradictory 
terms: on the one hand, <q>open</q> 
versus <q>closed</q>; on the other 
hand, <q>complete</q> versus 
<q>incomplete</q> (or 
<q>unfinished</q> versus 
<q>done</q>, etc.). The tendency has 
been to merge these two sets into a single pair, 
then to valorize the first pair of terms and to 
demonize the second.</p>
            <p>One of the more polished articles on 
Wikipedia these days, ironically, 
is on the topic <title rend="quotes">Unfinished Work</title>; it 
discusses incomplete works in various domains 
from literature and music through architecture to 
software. On the article's discussion page, the 
first thing we find is some amused perplexity 
about the label's applicability to the very 
source it appears in <ptr target="#wiki2007"/>:</p>
            <figure xml:id="figure01">
               <graphic url="resources/images/figure01.png"/>
               <figDesc>Screen shot of the quoted 
             discussion from Wikipedia</figDesc>
               <dhq:caption/>
            </figure>
            <p>It is a familiar conundrum about the 
nature of digital texts. Obviously, a formally 
defined text like a sonnet can be recognized as 
complete or incomplete; it's the difference 
between a well-wrought urn and a pot whose clay 
is still wet. But can a nonlinear, extensible, 
text ever be said to be finished? Is it by 
definition unfinished, or is the opposition 
<q>finished/unfinished</q> just plain inapplicable 
to open-ended texts?</p>
            <p>These are theoretical questions I'm 
not in a position to answer, but I would submit 
that early in the 1990s the postmodern admiration 
of the <q>open-ended</q> at the expense of the 
<q>closed</q> somehow got turned into a 
celebration of the <q>unfinished</q> 
and a suspicion of the <q>done,</q> and 
that this transmutation may have been one of the 
things that delayed the entrance of digital 
scholarship into the traditional system of 
peer-reviewed academic publication.</p>
            <p>Consider these assertions from George 
Landow and Paul Delany's 1991 essay 
<title rend="quotes">Hypertext, Hypermedia and Literary Studies: 
The State of the Art</title>:
          <cit>
                  <quote rend="block">Particularly 
inapplicable [to hypertext] are the notions of 
textual <q>completion</q> and of a 
<q>finished</q> product. Hypertext 
materials are by definition open-ended, 
expandable, and incomplete. If one put a work 
conventionally considered complete, such as the 
<title rend="italic">Encyclopedia Britannica</title>, into a 
hypertext format, it would immediately become 
<q>incomplete.</q>
                  </quote>
                  <ptr loc="13" target="#landow1991"/>
               </cit>
          A clever reader might object that even 
in print the <title rend="italic">Encyclopedia 
Britannica</title> is always incomplete: 
like any reference work, it is constantly being 
updated and reissued. So when Landow revises this 
particular passage for his 1992 book 
<title>Hypertext</title>, he makes the claim 
even more radical by making a single change to 
the second sentence to replace the encyclopedia 
with a work of literature:
             <cit>
                  <quote rend="block">Hypertextual 
materials, which by definition are open-ended, 
expandable, and incomplete call such notions into 
question. If one put a work conventionally 
considered complete, such as 
<title rend="italic">Ulysses</title>, into a hypertext format, 
it would immediately become 
<q>incomplete.</q>
                  </quote>
                  <ptr loc="59" target="#landow1992"/>
               </cit>
             Landow is now claiming that even a 
recognizably closed, well-wrought modernist text 
becomes both open and unfinished when put online. 
And he ends his 1992 discussion of completion by 
citing Derrida to the effect that <quote rend="inline">a form of textuality that goes 
beyond print <quote rend="inline">forces us to extend...the 
dominant notion of a <q>text</q>
                  </quote>,</quote> so that 
it <cit>
                  <quote rend="inline">is henceforth no longer a 
finished corpus of writing, some content enclosed 
in a book or its margins but a differential 
network, a fabric of traces referring endlessly 
to something other than itself, to other 
differential traces</quote>
                  <ptr target="#landow1992" loc="59"/>
               </cit>.</p>
            <p>Julia Flanders has observed in a 
memorable phrase that the digital humanities have 
sometimes suffered from <cit>
                  <quote rend="inline">a culture of the 
perpetual prototype</quote>
                  <ptr target="#flanders2007"/>
               </cit>, and identified some 
plausible economic and institutional causes. To 
them I think we can add the theoretical 
conflation of the digital with 
<foreign>différance</foreign>. After all, what 
was the postmodern project if not a cult of the 
perpetual prototype?</p>
         </div>
         <div>
            <head>Rotunda: A Scholarly Digital Imprint</head>
            <p>My organization, the Electronic 
Imprint of the University of Virginia Press, was 
established in 2001 to test the proposition that 
instances of digital scholarship <emph>can</emph> 
be bounded, completed, and presented for review, 
sale, and academic consumption in much the way 
journals and monographs had been for decades. We 
were grant funded, with support from the 
University and the Mellon Foundation awarded to a 
proposal co-written by the Press and John 
Unsworth, who was then head of the <ref target="http://www.iath.virginia.edu/">Institute 
for Advanced Technology</ref> (IATH) at Virginia. 
We became fully staffed in late 2002, and two 
years later released our first publication, a 
born-digital edition of Dolley Madison's 
correspondence, under our new imprint name of 
<q>Rotunda.</q> Since then we have 
expanded to a total of seven publications in two 
separate collections: nineteenth-century 
literature and culture, and the American Founding 
Era. Our main focus for the next few years will 
be creating fully-featured digital versions of 
the papers of American presidents and other 
Founding Era figures that began as multivolume 
(and often still ongoing) print editions, joining 
our <title rend="italic">Papers of George Washington Digital 
Edition</title> (<title rend="italic">PGWDE</title>), which was 
released in February 2007.</p>
            <p>The underlying data format of all of 
our Rotunda publications is XML, tagged according 
to the guidelines of the Text Encoding Initiative 
(TEI), plus accompanying digitized graphical 
material. Unlike many other university presses 
with digital projects, we outsource none of our 
technical work except for graphic Web design; our 
markup specifications, stylesheets for file 
transformation, and programming for Web delivery 
(mostly coded in XQuery using <ref target="http://www.marklogic.com/">MarkLogic 
Server</ref> as the back-end platform) are all 
done in-house by several programmers and 
technical editors.</p>
            <p>Born-digital Rotunda publications go 
through the same steps that our books go through: 
approval by a Press committee and then the Press 
Board after reports from external reviewers; 
signing of a contract complete with royalty 
agreements; sharing of <q>review 
copies</q> (in the form of password access) 
with librarians and academic reviewers. Digital 
editions such as <title rend="italic">PGWDE</title> that are 
based on existing print series are produced in 
close collaboration with the scholarly 
communities (historians and documentary editors) 
who create and use the letterpress volumes. 
Clearly all parties to our process of publication 
and sale are implicitly agreeing to bracket the 
theoretical issue of when or whether a digital 
work is ever <q>done</q> by applying a 
socioeconomic definition: it is 
<q>done</q> when the Press is prepared 
to offer it for purchase and customers are 
prepared to buy it.</p>
            <p>I turn now to two very dissimilar 
examples of our 
publications — <title rend="italic">PGWDE</title> and an 
edition of Herman Melville's 
<title rend="italic">Typee</title> manuscript — and discuss the 
decisions we made about what we could or 
couldn't include in the finished work; when we 
counted each as <q>done</q> for initial 
release; and to what extent we consider the 
published release genuinely complete or part of a 
work still in progress.</p>
         </div>
         <div>
            <head>Melville's <title rend="italic">Typee</title>: A Fluid-Text Edition</head>
            <figure xml:id="figure02">
               <graphic url="resources/images/figure02.png"/>
               <figDesc>Splash page of Rotunda 
"Typee" edited by John Bryant</figDesc>
               <dhq:caption>
                  <title rend="italic">Typee</title> splash page</dhq:caption>
            </figure>
            <p>John Bryant's edition of a portion 
of Herman Melville's novel <title rend="italic">Typee</title> 
was first envisioned and prototyped years before 
Rotunda came into existence. Bryant has been 
editing Melville's texts for two decades, and 
has long felt that any critical edition of a text 
that survives in more than a single version needs 
to be faithful to its evolutionary history; it 
should be what he calls a 
<q>fluid-text</q> edition. Because a 
fluid-text edition needs to capture a dynamic 
process, a computer-based format is a natural 
fit, and he began imagining one for Melville as 
early as the 1980s (personal communication).</p>
            <p>The textual history of 
<title rend="italic">Typee</title> is fairly complicated. The 
only surviving manuscript fragment covers about 
three chapters of the published novel. It 
contains a multitude of cancellations, erasures, 
and additions by Melville, both in ink from the 
time of first composition and in pencil from 
later stages of revision and proofreading <ref target="#figure03">Figure 3</ref>.
             <figure xml:id="figure03">
                  <graphic url="resources/images/figure03.jpg"/>
                  <figDesc>Sample manuscript page 
from Melville's Typee</figDesc>
                  <dhq:caption>Part of a 
<title rend="italic">Typee</title> manuscript page, showing 
Melville's typical deletions and insertions; 
the circled <emph>x</emph> above the fourth line 
is keyed to a separate insertion leaf.</dhq:caption>
               </figure>
             We know that Melville made changes in 
proof before the first English edition was 
issued, and that the first American edition 
contained still more changes, some requested by 
Melville, others made by the publisher probably 
without the author's assent. Bryant's goal 
for a digital fluid-text edition was to capture 
all of these stages and to allow the reader to 
follow the sequence of composition and the 
editor's narrative reconstruction of that 
sequence, zooming in and out to any point in 
manuscript time and space during the entire 
period from initial composition through the 
published editions.</p>
            <div>
               <head>Development of the Edition</head>
               <p>Bryant was not himself a 
programmer or XML specialist, but he did have 
ideas about what a computer edition might look 
like, and created detailed storyboards before any 
actual programming work began. Although these 
were necessarily static, they used frame- and 
button-like boxes to suggest how a screen 
presentation might respond dynamically to reader 
choices (<ref target="#figure04">Figure 4</ref>). In 1998 he 
was named an IATH <ref target="http://www.iath.virginia.edu/other_fellows.html">Visting 
Fellow</ref> and received technical assistance to 
create a first proof-of-concept prototype of the 
edition <ptr target="#bryant2000"/>, which 
translated the storyboards into standard HTML 
frames (<ref target="#figure05">Figure 5</ref>).</p>
               <figure xml:id="figure04">
                  <graphic url="resources/images/figure04.png"/>
                  <figDesc>One of John Bryant's 
original storyboards for the Typee 
edition</figDesc>
                  <dhq:caption>An early storyboard by 
John Bryant illustrating a possible interface and 
layout for the <title rend="italic">Typee</title> 
edition</dhq:caption>
               </figure>
               <figure xml:id="figure05">
                  <graphic url="resources/images/figure05.png"/>
                  <figDesc>Screen shot of an early 
prototype of the Typee edition</figDesc>
                  <dhq:caption>A first prototype of the 
<title rend="italic">Typee</title> edition produced in 2000 by 
IATH at the University of Virginia</dhq:caption>
               </figure>
               <p>In late 2003 we received 
Bryant's <q>manuscript</q> of the 
edition, consisting of Microsoft Word and 
PageMaker files containing manuscript 
transcriptions flagged with hundreds of 
<q>revision sites</q> and for each 
separate revision site a <q>revision 
sequence</q> and a <q>revision 
narrative.</q> We licensed from the New York 
Public Library the rights to reproduce their 
full-color photographs of the entire manuscript. 
Our goals at this point were (1) to convert all 
transcription and commentary to TEI-XML, and (2) 
to design an environment that could deliver 
combinations of text and image to realize as 
closely as possible the author's intentions for 
his edition. Our own finished rendering of the 
original concept <ptr target="#bryant2006"/> 
would look like this: </p>
               <figure xml:id="figure06">
                  <graphic url="resources/images/figure06.png"/>
                  <figDesc>Screen shot 1 from Rotunda's Typee edition</figDesc>
                  <dhq:caption>Default view of the 
Rotunda version of <title rend="italic">Typee</title>, with a 
manuscript page image in the top frame and a 
bitmapped typographic transcription in the lower 
one (the current state of HTML made browser 
rendering impractical). Readers can choose to 
display different combinations of image and 
transcription state in either frame. JavaScript 
controls allow upper and lower frames to scroll 
in unison.</dhq:caption>
               </figure>
               <figure xml:id="figure07">
                  <graphic url="resources/images/figure07.png"/>
                  <figDesc>Screen shot 2 from Rotunda's Typee edition</figDesc>
                  <dhq:caption>The lower frame now shows 
a textual transcription of the same lines 
rendered in HTML, where color-coding represents 
<q>revision sites</q> from different stages of 
compositional history.</dhq:caption>
               </figure>
               <figure xml:id="figure08">
                  <graphic url="resources/images/figure08.png"/>
                  <figDesc>Screen shot 3 from Rotunda's Typee edition</figDesc>
                  <dhq:caption>Clicking on any 
highlighted revision site brings up a window 
containing Bryant's reconstruction of the 
revision sequence and a narrative explanation of 
it.</dhq:caption>
               </figure>
               <p>Once we had our basic page display 
working, all that remained was to code a search 
page and add the editorial introductions before 
declaring the edition <q>done</q> and 
releasing it in March 2006.</p>
               <p>Three months later we added an 
enhancement, our major one to date, an XML-based 
version of the entire first British edition of 
the novel, which the University of Virginia 
Library digitized for us from a copy in their 
holdings. We created for it a display interface 
combining a transcription of the text  with 
images (<ref target="#figure09">Figure 9</ref>).</p>
               <figure xml:id="figure09">
                  <graphic url="resources/images/figure09.png"/>
                  <figDesc>Screen shot of first 
British edition page from the Rotunda 
Typee</figDesc>
                  <dhq:caption>The added first British 
edition includes an XML-based transcription of 
the text plus optionally viewable page images 
from the printed text.</dhq:caption>
               </figure>
            </div>
            <div>
               <head>Is Our <title rend="italic">Typee</title> Done?</head>
               <p>Neither Bryant nor the Press 
conceived of the <title rend="italic">Typee</title> edition as 
an open-ended project. The editor's work was 
done once he had finished all the manuscript 
transcription, identification of revision sites, 
exposition of revision sequences and narratives, 
and the introductory editorial essay. Our work 
was done once we had translated the editor's 
vision into a fully functional edition that 
coordinated photographic facsimiles with several 
transcription formats, and that hyperlinked all 
<q>revision sites</q> with their 
editorial expansions. The March 2006 edition was 
lacking one intended feature, the first British 
edition, owing to extrinsic factors (our 
library's digitization schedule). Once that was 
added, <title rend="italic">Typee</title> was for practical 
purposes stable and complete.</p>
               <p>Nevertheless, we were aware of the 
potential for improvements and enhancements, some 
more immediately practicable than others:</p>
               <list type="unordered">
                  <item>We could generate RDF 
metadata files in the format used by the <ref target="http://nines.org/software/collex/index.html">Collex</ref> 
tool created by Jerry McGann and his <ref target="http://www.nines.org/">NINES</ref> 
team. In July 2007 we did this, so that the base 
view of each manuscript page exists as an indexed 
object in Collex, along with the editorial 
introduction and the publication home page.</item>
                  <item>The full-text search needs 
improvements to return hits on supplied text and 
to properly handle word tokens containing XML 
tags (for example: 
<code>savage&lt;add&gt;ry&lt;/add&gt;</code>). 
The first item is on our to-do list; the second 
is on hold until our MarkLogic software adds the 
ability to ignore selected elements for the 
purpose of word tokenization.<note>In fact we could get around this 
software limitation by adding TEI tagging to 
provide the regularized word tokens for indexing, 
and adjusting our processing code accordingly. 
The decision not to do so was based on a 
cost-benefit analysis, feeling that the amount of 
time it would require outweighed the added 
utility in the context of this particular 
publication.</note>
                  </item>
               </list>
               <p>More radically still, it is 
conceivable that all of our underlying XML markup 
and presentation might be entirely revised if 
John Bryant were to incorporate the proposals for 
temporal encoding in genetic digital editions 
that Elena Pierazzo has advanced <ptr target="#pierazzo2007"/>, as both her tagging 
strategy and theoretical approach vary 
significantly from his own. A revision of that 
magnitude would be analogous to issuing a second 
edition of a book that differs markedly from the 
original because it has responded to new evidence 
and/or arguments. All scholarly and scientific 
publications are potentially imperfect and thus 
<q>incomplete</q> to the extent that 
later work can call them into question, but it 
would be an equivocation to say that they are 
therefore always unfinished in a formal sense.</p>
            </div>
         </div>
         <div>
            <head>The <title rend="italic">Papers of George 
Washington Digital Edition</title>
            </head>
            <figure xml:id="figure10">
               <graphic url="resources/images/figure10.png"/>
               <figDesc>Splash page of Papers of 
George Washington Digital Edition</figDesc>
               <dhq:caption>
                  <title rend="italic">PGWDE</title> splash page in July 2007</dhq:caption>
            </figure>
            <p>The <title rend="italic">Papers of George 
Washington Digital Edition</title> 
               <ptr target="#pgwde2007"/> is a very different 
project, one initiated in 2004 by the Press in 
collaboration with the editorial staff of the 
<ref target="http://gwpapers.virginia.edu/">Papers of 
George Washington</ref>  (also based at the 
University of Virginia), and partially funded by 
a grant from Mount Vernon. Our mission was to 
produce an online version of the fifty-two 
volumes then in print of our letterpress 
<title rend="italic">Papers of George Washington</title> 
               <ptr target="#pgw1976"/>, the authoritative scholarly 
edition of the documentary legacy of the first 
president. Owing to the size and complexity of 
the letterpress edition,
<note>
                  <p>The size and scope of the project can be 
illustrated with a few statistics:</p>
                  <list type="unordered">
                     <item>52 printed volumes (originally 
published between 1976 and 2004) totalling ca. 
30,000 printed pages, rekeyboarded and tagged as 
TEI-XML</item>
                     <item>ca. 18,500 separate documents from 
29,000 original sources (much of Washington's 
official correspondence survives in multiple 
drafts and copies)</item>
                     <item>entries from Washington's diaries 
covering 560 months, with 6800 separate daily 
entries</item>
                     <item>2930 unique document authors and 1900 unique recipients</item>
                     <item>corpus of ca. 11.5 million words 
(documents + annotation), with ca. 91,000 
different word tokens, all indexed for full-text 
searching</item>
                     <item>separate back-of-the-book indexes 
from each volume merged into a consolidated index 
containing over 35,000 main entries and nearly 
100,000 subentries, with a total of over 400,000 
separate page references</item>
                  </list>
               </note>
its adaptation to a fully-featured online format 
offered us as many design and programming 
challenges as a born-digital project like 
<title rend="italic">Typee</title>. We needed to establish an 
appropriate XML schema and encoding 
specifications, decide on what structural and 
semantic tagging to do and what metadata to add, 
figure out how much regularization of 
inconsistencies in the letterpress edition we 
could accomplish, and design a Web environment 
for display, navigation, and searching of the 
edition usable by advanced scholars and beginning 
students alike.</p>
            <p>For the editorial staffs of The 
Papers of George Washington and UVa Press, the 
criteria for regarding a letterpress volume as 
complete have been well established since the 
project began in the 1970s:
             <list type="unordered">
                  <item>all known documents from the 
period covered by the volume are included or 
referenced</item>
                  <item>all document transcriptions 
are complete and have been checked for accuracy 
against manuscript facsimiles</item>
                  <item>all possible identifications of persons have been 
made and included in the endnotes</item>
                  <item>all other annotation and 
editorial introductions are written</item>
                  <item>the manuscript has been copyedited</item>
                  <item>page proofs have been 
checked and used to produce a back-of-the-book 
index.</item>
               </list>
             But for us, including the full 
content of the print edition would not be 
sufficient. We could consider 
<title rend="italic">PGWDE</title> 
               <q>done</q> only 
when we had reliably translated textual and 
scholarly conventions into an online format that 
offered as much (to use the inevitable marketing 
phrase) added value as possible beyond simply 
being able to access the publication without 
visiting a library.</p>
            <div>
               <head>Goals for the <title rend="italic">PGWDE</title>
               </head>
               <p>Determining where we could add 
value to the print edition required a preliminary 
analysis of what makes a scholarly edition 
valuable in the first place. In such an edition, 
the basic textual unit is the single document, 
always accompanied at a minimum by 
bibliographical information and usually by 
editorial annotation, and sometimes by 
translations, enclosed documents, or other 
ancillary material. (Diaries and journals are a 
special case: depending on how chronologically 
structured they are, the basic textual unit may 
be the single-day entry, the single-month entry, 
or a longer narrative.) Besides the original text 
and editorial material, documents contain 
metadata, cross-references, abbreviations and 
other special features that are represented using 
a variety of editorial and typographical 
conventions, as highlighted in the facsimile of the 
original letterpress version of a letter from 
William Livingston to George Washington (shown <ref target="#figure11">below</ref>). Beyond 
the document level, most volumes contain 
scholarly apparatuses (lists of abbreviations and 
bibliographic expansions of short-title 
references), editorial and historical 
introductions, and a detailed index of all proper 
names and hundreds of topic categories. The 
translation of all of these print conventions 
into their TEI-XML equivalents is what must 
undergird a digital edition. (Our final XML 
encoding of the Livingston letter may be seen in 
the <ref target="#appendix">appendix</ref>.)</p>
               <figure xml:id="figure11">
                  <graphic url="resources/images/figure11.png"/>
                  <figDesc>A sample page from the print edition of PGWDE</figDesc>
                  <dhq:caption>A page from the 
Revolutionary War Series of the print edition of 
<title rend="italic">The Papers of George Washington</title>. 
Many, but by no means all, of the features in a 
documentary edition that need to be captured in 
the underlying XML representation are 
typographically distinct; determining the optimal 
mixture of automated and human tagging is one of 
the challenges of converting a legacy 
edition.</dhq:caption>
               </figure>
               <p>Our initial goals for the digital edition were:</p>
               <list type="ordered">
                  <item>to provide 
document-by-document display (or, for diaries, 
month-by-month or day-by-day, as appropriate) 
closely resembling that of the letterpress 
source;</item>
                  <item>to offer a wide variety of 
means for navigating into the documents: through 
full-text search; through a hyperlinked 
consolidated index based on the back-of-the-book 
print indexes; via tables of contents similar to 
those in the print edition; and by chronology (in 
order to collect all documents and  diary entries 
for a given date, for example);</item>
                  <item>to use as much tagged 
information as possible for display, linking, and 
refinement of searching;</item>
                  <item>to create a genuinely new 
edition incorporating corrections to the print 
edition submitted by the Papers of George 
Washington staff, along with consolidated and 
regularized lists of names and titles that had 
varied from volume to volume in the letterpress 
edition.</item>
               </list>
               <p>Work on <title rend="italic">PGWDE</title> began 
in fall of 2004; a beta version for public 
display was ready by October 2006; and we 
formally released a published version for sale in 
February 2007. Screen captures of the online 
version of the Livingston letter illustrate how 
we realized some of our goals (<ref target="#figure12">Figure 12</ref>, <ref target="#figure13">Figure 13</ref>). Compasses are used 
to navigate the four hierarchies identifed in 
goal 2. A <q>breadcrumb trail</q> 
allows quick navigation up to any higher node of 
the current tree. Hyperlinks or mouseovers 
provide dynamic equivalents of their print 
counterparts in ways that are familiar to Web 
users: endnote superscripts connect to their 
notes via bidirectional linking; abbreviations 
and short-title references (indicated by dotted 
underlining) are expanded when the user mouses 
over the abbreviated text; and cross-references 
to other documents in <title rend="italic">PGWDE</title> are 
active links.</p>
               <figure xml:id="figure12">
                  <graphic url="resources/images/figure12.png"/>
                  <figDesc>Screen capture of 
completed display of Livingston letter in Rotunda 
PGWDE edition</figDesc>
                  <dhq:caption>Top of the Livingston 
letter in a browser view.</dhq:caption>
               </figure>
               <figure xml:id="figure13">
                  <graphic url="resources/images/figure13.png"/>
                  <figDesc>Screen capture of 
completed display of Livingston letter in Rotunda 
PGWDE edition</figDesc>
                  <dhq:caption>Bottom of the Livingston letter.</dhq:caption>
               </figure>
               <p>Along with the document navigation 
and display, we programmed a search page that 
combines full-text search with optional filtering 
based on author, recipient, and/or date range; 
and we added an online version of the 
consolidated index that resembles a 
back-of-the-book index except that document 
titles and dates replace page numbers and are, of 
course, hyperlinked.</p>
               <p>We had scheduled official release 
of <title rend="italic">PGWDE</title> for President's 
Day — February 19, 2007. By a month or so 
ahead of this deadline, we realized that every 
last cleanup task could not be completed by that 
date. Online publication meant we could do a 
triage: fix first the things that affect the most 
documents, or that are most obvious to the 
average reader; fix afterwards problems or errors 
limited to single documents, or ones that would 
be noticed only by a specialist (for example, an 
incorrect birth year for a minor historical 
figure). Corrections of bad links and minor 
formatting glitches continued for about a month 
after the February 19 release. Corrections to 
errors in transcriptions or annotations, as 
identified by Papers of George Washington staff, 
have been ongoing. So, too, have further 
regularization and consolidation: since first 
publication, PGW staff have provided us with 
fully normalized lists of names of all document 
authors and recipients that we have used to 
update the document metadata, and with a 
corrected and up-to-date list of  repository 
abbreviations and expansions based on <ref target="http://www.loc.gov/marc/organizations/">MARC 
codes</ref> that we have used to globally update 
the XML volume files.</p>
            </div>
            <div>
               <head>Planned Enhancements</head>
               <p>So is <title rend="italic">PGWDE</title> done? 
Yes and no. It is a stable release version with 
some remaining imperfections, but there's a lot 
more we plan to do with it, even apart from 
adding content as we digitize new volumes after 
they appear in print. We've recently met with 
the PGW staff to agree on a list of priorities 
for enhancement. The tasks fall into three 
general categories:
                <list type="ordered">
                     <item>Optimization of existing 
features. Examples: improving search speed and 
index retrieval; rewriting the search parser to 
make it more Google-like and to include more 
boolean operators.
          </item>
                     <item>New features. Add an 
<q>advanced search</q> 
page that will allow users to search by document 
features or language, for example. We'll add 
full-text searching on the index. Farther down 
the road may be <q>keeping up with the 
Joneses</q> enhancements, like enabling the 
user to save a personal workspace containing 
bookmarked documents and search result sets as 
the <ref target="http://edwards.yale.edu/archive/">Works 
of Jonathan Edwards Online</ref> at Yale has done.
          </item>
                     <item>Features required by 
aggregating <title rend="italic">PGWDE</title> into the larger 
Founding Era collection. Over the next year we 
will be adding editions of the <title rend="italic">Adams 
Family Papers</title>, the <title rend="italic">Papers of 
Thomas Jefferson</title>, and <title rend="italic">The 
Documentary History of the Ratification of the 
Constitution</title>. In order to build an 
extensible framework, we have already begun a 
thorough rewrite of our delivery code and 
encoding specifications so that our publication 
system will scale gracefully as more publications 
are added.</item>
                  </list>
                But it is impossible for us to 
project all of the enhancements that may become 
desirable or possible in the future. We are in a 
position not too different, really, from that of 
the editors who began planning American 
documentary historical editions beginning in the 
1950s. They of course knew that their completed 
volumes would eventually need to be supplemented 
and corrected as new documents and historical 
information emerged. What they couldn't 
envision was a time, our own, when scholarship 
that exists only in print is increasingly seen as 
<hi rend="italic">ipso facto</hi> lacking an 
essential quality. Likewise, we can really only 
guess at what new features advancing technology 
may make possible. For instance, we have often 
wished we had time and funding to add rich XML 
tagging for personal and place names (beyond the 
author/recipient identifications in existing 
metadata), and assumed that this would require a 
major commitment of human labor. But it's not 
impossible that advances in automated <ref target="http://en.wikipedia.org/wiki/named_entity_recognition">named 
entity recognition</ref> will enable us in a 
not-too-distant future to pipe 
<title rend="italic">PGWDE</title> through a program that will 
reliably recognize and tag those names and link 
them to, say, genealogical databases or a 
GIS-based interface like Google Earth.
             </p>
               <p>So we don't really expect ever 
to be able to say more than that 
<title rend="italic">PGWDE</title> is done — for now.</p>
            </div>
         </div>
         <div>
            <head>A Few Conclusions: Generalizing 
from the Rotunda Experience</head>
            <epigraph>
               <cit>
                  <quote rend="block">
                     <p>Ask any developer out there if 
a program is ever finished and they'll tell you, 
<q>No, of course not, I still need to...</q>. But, 
ask any developer out there if the program is 
<emph>almost</emph> finished and, assuming that 
the development cycle has progressed far enough 
along, their answer will invariably be, <q>Yes, 
all I have to do is...</q>. They may even quantify 
it: <q>80% complete</q>. Ask them a couple of 
days, weeks, months (depending on the magnitude 
of the project) later and you will get a similar 
response, but with a different percentage, say 
90%. And so forth…but never 100%.</p>
                  </quote>
                  <ref target="http://quay.wordpress.com/2007/05/20/never-finished/">
                     <title rend="quotes">Never Finished; or Zeno's Paradox 
as an Analog to Software Development</title>
                  </ref>
               </cit>
            </epigraph>
            <p>It is entirely possible to define 
<q>done-ness</q> for computer software 
in such a way that no instantiation of a software 
project can ever satisfy the definition. For 
example, suppose we stipulate that:
          <quote rend="block">A program is complete and 
can be distributed when it (1) satisfies all 
initial design requirements, (2) is known to run 
100% bug-free under all potential conditions of 
use, and (3) incorporates state-of-the-art 
programming techniques and tools at the time of 
distribution to offer the user an optimal mix of 
powerful features and ease of use.</quote>
           The second and third criteria entail 
that none but the simplest programs could ever 
count as complete. To claim <q>my program is 
bug-free because I have found no bugs in it</q> 
is <foreign>argumentum ad ignorantiam</foreign>; 
that you haven't found any doesn't mean they 
aren't there. And criterion 3 turns done-ness 
into a Red Queen's race, since the state of the 
art is constantly advancing, and at release time 
most complex software projects are already 
<q>belated</q> relative to the cutting 
edge of technology. To the extent that digital 
publications count as software projects, they too 
would fail ever to count as finished under such a 
definition.</p>
            <p>The adjective <q>simplest</q> in the 
preceding paragraph hints at a way around the 
paradox. If my goal is to write a <q>hello 
world</q> program in Perl and I respond with 
the one-line program <quote rend="block">
                  <code>print "Hello 
World!\n";</code>
               </quote> I can confidently say 
I'm done. If my task is to write a new 
operating system, it's another matter. As a 
rule, the more <hi rend="italic">complex</hi> a 
task is, the less susceptible it is of being 
judged finished by any set of formal criteria. 
Contrast these two assignments:
             <list type="ordered">
                  <item>Create a crop circle in the 
shape of a simple circle with a diameter of 40 
meters.</item>
                  <item>Create a crop circle 
representing the coastline of Great Britain at 
1/10000 scale.</item>
               </list>
             The first project is done once 
you've made a single circuit while tromping 
down wheat at the end of a 20m tether. The second 
project is done when you've created as accurate 
a representation as your time and skill allow. 
Tracing a coastline is a problem in fractal 
geometry for which completeness will always be 
relative. In a sense, it is a formal property of 
project 2 that it is done only when you decide it 
is done. To put it another way, intrinsic 
criteria are used in both cases to determine when 
the project qualifies as finished, but as project 
2 is formally undecidable (embodying the Turing 
halting problem that Matt Kirschenbaum mentions 
in his introduction), extrinsic criteria are also 
required to make the determination.</p>
            <p>The digital publications that we have 
worked on in Rotunda have tended to resemble the 
fractal project more than the simple circle. With 
<title rend="italic">PGWDE</title>, for example, the 
<q>coastline</q> we needed to reproduce 
was, like that of Britain, a pre-existing and 
well-defined object, the fifty-two volumes of the 
print edition. To have omitted a volume would 
have been as clear a sign of incompleteness as 
leaving Cornwall out of the crop circle. But 
decisions about the richness of our feature set 
were very much a matter of <q>how far to 
trace</q>, and in the end were dictated by our 
available time and skill (and budget). If our 
experience is representative, deciding when to 
call a digital project <q>done</q> usually requires a 
process of negotiation between intrinsic criteria 
and external factors.</p>
            <div>
               <head>Intrinsic Criteria</head>
               <p>Intrinsic criteria are formalist: 
they assume that the completeness of an object 
derives from its inner properties alone, without 
reference to any social or other external 
context. In the following table there is a 
continuum from objects like a monograph (or a 
lyric poem) that can be judged to possess organic 
unity, to ones like a collaborative virtual world 
that cannot. It is no accident that the latter 
are the ones felt to be characteristically 
<q>digital</q>.</p>
               <table>
                  <head>
                     <q>Done</q> as a 
function of intrinsic criteria</head>
                  <row role="label">
                     <cell>Category</cell>
                     <cell>Object has definable boundaries?</cell>
                     <cell>Object has satisfied its design goals?</cell>
                     <cell>Print world example</cell>
                     <cell>Digital example</cell>
                     <cell>Is it <q>done</q>?</cell>
                  </row>
                  <row>
                     <cell>1</cell>
                     <cell>yes</cell>
                     <cell>yes</cell>
                     <cell>monograph, journal article</cell>
                     <cell>monograph-like object, online article</cell>
                     <cell>yes</cell>
                  </row>
                  <row>
                     <cell>2</cell>
                     <cell>yes</cell>
                     <cell>no</cell>
                     <cell>preprint, <q>rough cuts</q>
                     </cell>
                     <cell>beta or 0.9 release</cell>
                     <cell>not yet</cell>
                  </row>
                  <row>
                     <cell>3</cell>
                     <cell>no</cell>
                     <cell>yes (for current stage)</cell>
                     <cell>encyclopedia; any work issued in discrete series</cell>
                     <cell>same as for print world</cell>
                     <cell>yes (for now)</cell>
                  </row>
                  <row>
                     <cell>4</cell>
                     <cell>no</cell>
                     <cell>no</cell>
                     <cell>? ?</cell>
                     <cell>open-ended wiki, 
collaborative blog or social space, virtual 
world, etc.</cell>
                     <cell>no (by definition)</cell>
                  </row>
               </table>
               <p>Category 1 objects are the most 
familiar in scholarly publishing, hence the most 
fully integrated into the tenure-and-review 
system. Bryant's <title rend="italic">Typee</title> 
essentially falls into this category. Probably 
owing to the influence of online publishing, 
Category 2 objects are becoming more familiar: 
online preprints are accredited scholarly 
communications in a growing number of 
disciplines, and cutting-edge book publishers 
like O'Reilly with their <ref target="http://www.oreilly.com/roughcuts/">Rough 
Cuts</ref> series of early-access PDF are 
adopting a <q>versioned</q> model of 
publication.</p>
               <p>Category 3 objects are also 
familiar from the print world, where they 
represent the one kind of open-endedness that 
does not upset traditional notions about 
scholarly authority. The <title rend="italic">Oxford English 
Dictionary</title> is a good example. It has been 
supplemented, transformed, and extended many 
times since the first fascicles were issued in 
1884. Yet each discrete stage of publication was 
accepted by the academic community as 
authoritative for its moment. It is no accident 
that this category has translated easily to 
digital format: the only essential difference 
between the print and online <title rend="italic">OED</title> 
is that the latter is updated far more often.</p>
               <p>Category 4 is the one to which the 
term <q>done</q> seems the most 
inapplicable. Its characteristic objects are more 
like processes than products, and it is difficult 
to think of genuine analogues in the print world 
outside the realm of experimental literature of 
the Oulipo variety. A publication like 
<title>Wikipedia</title> can perhaps be seen as a 
special case of Category 3 in which discrete 
stages succeed each other with extreme rapidity, 
but a virtual world like <ref target="http://secondlife.com/">
                     <title>Second 
Life</title>
                  </ref> exists in such constant motion 
that it requires something akin to calculus for 
adequate description. Unsurprisingly, Category 4 
is the form of digital creation least amenable to 
naturalization in the academic reward system or 
the scholarly publishing marketplace.</p>
            </div>
            <div>
               <head>Extrinsic Factors</head>
               <p>For a scholarly publisher, 
intrinsic criteria of done-ness are important but 
are often trumped by extrinsic factors. The 
judgement that a book manuscript is done and 
ready for press requires an agreement among 
author, acquiring editor, external reviewers, and 
the manuscript editorial and production 
departments that is based largely on its formal 
content. But completely extrinsic factors such as 
the desire to include the book in a particular 
season's list will often lead a press to veto 
an author's wish to continue tinkering with a 
manuscript. Similarly, an author may not consider 
a monograph on Chinese art formally complete 
without the inclusion of several dozen full-page 
color reproductions on glossy inserts, but a 
publisher may omit them for the wholly extrinsic 
reason that the profit-and-loss sheet doesn't 
budget for them. Once a book is in print, 
decisions about its subsequent 
<q>done-ness</q> (i.e., whether to 
reprint, revise, issue in paperback, etc.) are 
based almost entirely on economic factors. In the 
case of digital publications, I will suggest, 
extrinsic factors become important at an earlier 
stage and are proportionately more important at 
every stage of composition and publication.</p>
               <p>The following list of extrinsic 
factors is not meant to be exhaustive; they are 
the ones that have been most prominent in 
Rotunda's experience.</p>
               <list type="gloss">
                  <item>
                     <label>Economic constraints</label>
                     <p>Two maxims apply: <emph>(1) 
if a digital publication doesn't sell, it's 
<q>done</q>; (2) if the projected cost 
of upgrade exceeds projected revenue, it's 
<q>done</q>
                        </emph>. (For freely 
distributed projects, substitute <q>when no more 
grant funding or volunteer time is available, 
it's done.</q>) </p>
                  </item>
                  <item>
                     <label>Competition</label>
                     <p>Maxim: <emph>when your 
competition is adding features to its product, 
they can render your finished product 
<q>incomplete.</q>
                        </emph> In the print 
world, this phenomenon is familiar in textbook 
and reference publishing. In the digital world, 
it is absolutely pervasive. No online 
publication, free or for sale, can afford 
long-term stasis when the peer publications it is 
compared with are adding bells and whistles (a 
list that would include, as of 2008, things like 
Ajax-powered form fields, tag clusters, user 
reviews and personal workspaces, page previews on 
mouseover, selectable themes or 
<q>skins</q> . . .) In the 
prestige economy as in the market economy, 
keeping up with the Joneses is not optional.</p>
                  </item>
                  <item>
                     <label>Standards evolution</label>
                     <p>Maxim: <emph>even absent 
competition, the evolution of standards can make 
a finished project 
<q>incomplete.</q>
                        </emph> This is 
primarily a matter of adhering to best practices, 
though not entirely free from the 
keeping-up-with-the-Joneses factor. Certainly if 
your academic discipline adopts a new format for 
metadata, or your institution adds a requirement 
that Web publications meet accessibility 
guidelines, your projects need to be revised for 
conformity. In other cases, it may be a matter of 
pride to demonstrate that a project has upgraded 
to the latest standard, for example by converting 
archival XML from TEI P4 to P5 compliance, or by 
following the very latest W3C recommendation for 
XHTML or CSS.</p>
                  </item>
                  <item>
                     <label>Aggregation</label>
                     <p>Maxim: <emph>a stand-alone 
publication will probably become 
<q>incomplete</q> when it is aggregated 
with other material.</emph> In Rotunda's 
experience, it is inevitable that the user 
interface and back-end coding one develops for a 
single digital project will need to be 
substantially revised once a second project is 
added and meant to interoperate with the first. 
(As a case in point, it would require major 
effort to get our first publication, the <ref target="http://rotunda.upress.virginia.edu:8080/dmde/">
                           <title rend="italic">Dolley 
Madison Digital Edition</title>
                        </ref>, seamlessly 
integrated with <title rend="italic">PGWDE</title>, as the 
back-end programming and underlying XML data 
formats of the two publications are quite 
different.)</p>
                  </item>
                  <item>
                     <label>Technological change</label>
                     <p>Maxim: <emph>new technology 
<hi rend="bold">will</hi> make your publication 
<q>incomplete</q>
                        </emph>. This goes 
almost without saying. The evolution of hardware, 
operating systems, programming languages, and Web 
standards will eventually make any online 
publication obsolete. Failure to migrate a 
digital object periodically as technical 
conditions require is the analogue of allowing a 
published book to go out of print. (In fact 
it's worse: it's like printing the book on 
high-acid-content paper with ink that fades on 
exposure to light, and <emph>then</emph> letting 
it go out of print.)</p>
                  </item>
               </list>
            </div>
            <div xml:id="synthesis">
               <head>A Necessary Synthesis</head>
               <p>Whether you are a publisher or the 
editor of an open-access publication, allowing 
extrinsic factors to influence your decision 
about whether a digital project is done is in no 
way an admission of defeat or an abdication of 
responsibility. It is, in fact, the only way to 
avoid the form of Zeno's paradox whimsically 
propounded in the epigraph to this section. The 
progress of knowledge in the arts and sciences is 
continuous, but in order for it to happen at all, 
scholarly discourse must be distributed in the 
form of discrete objects that can be shared, read 
or viewed, responded to, assimilated, quoted, 
disputed, and revised. In the marketplace of 
ideas, it's less important how you decide when 
your piece is done than that you <emph>do</emph> 
decide, label it and put it on display, and 
prepare to haggle with others over its value.</p>
            </div>
         </div>
         <div xml:id="appendix">
            <head>Appendix: XML markup of a sample Washington letter</head>
            <p>(Formatting has been applied for convenience in reading; carriage
          returns are not introduced within mixed-content elements in the
          original files.)</p>
            <eg>&lt;div1 xml:id="Rev13d180" type="doc"&gt;
    &lt;FGEA:mapData id="GEWN-03-13-02-0189"&gt;
      &lt;bibl&gt;
        &lt;title&gt;From William Livingston, 13 January 1778&lt;/title&gt;
        &lt;author&gt;Livingston, William&lt;/author&gt;
        &lt;name type="recip"&gt;GW&lt;/name&gt;
        &lt;date when="1778-01-13"/&gt;
      &lt;/bibl&gt;
      &lt;FGEA:Author&gt;Livingston, William&lt;/FGEA:Author&gt;
      &lt;FGEA:Recipient&gt;GW&lt;/FGEA:Recipient&gt;
      &lt;FGEA:mapDates&gt;
        &lt;FGEA:searchRange from="1778-01-13" to="1778-01-13"/&gt;
        &lt;FGEA:dayRange from="1778-01-13" to="1778-01-13"/&gt;
      &lt;/FGEA:mapDates&gt;
      &lt;FGEA:pageRange from="Rev13p227" to="Rev13p227"/&gt;
    &lt;/FGEA:mapData&gt;
    &lt;pb n="Rev13p227"/&gt;
    &lt;head&gt;From William Livingston&lt;/head&gt;
    &lt;div2 type="docbody"&gt;
       &lt;opener&gt;
          &lt;salute&gt;Sir&lt;/salute&gt;
          &lt;dateline&gt;Morris Town [N.J.] &lt;date when="1778-01-13"&gt;13th Jany
             177[8]&lt;ptr n="1" target="Rev13d180n1"/&gt;&lt;/date&gt;&lt;/dateline&gt;
       &lt;/opener&gt;
       &lt;p&gt;Upon frequent Complaints that Capt. 
Kennedy's Residence at his Farm was
          injurious to the State, &amp;amp; occasioned great Clamours from the
          People in This Neighbourhood, the 
Council ordered his Attendance on the
          Board—they at the same time desired a Gentleman near the Spot, to
          procure what Affidavits he could 
respecting Captn Kennedy's Conduct—He
          sent us by return of the Express three Affidavits with Copies of which
          I take the Liberty of troubling you; Capt. Kennedy denies the
          Accusations sworne against him, &amp;amp; refers to a Parole he signed
          to your Excellency in this Town. The Board would therefore be glad to
          know the Nature of that Parole (of which he has no Copy) &amp;amp;
          whether you consider him as a Prisoner of War, since Your Excellency
          has taken Paroles from persons professedly Subjects of this State
          &amp;amp; not pretending to any Connextions with Britain, meerly to
          prevent their being detrimental to this State as disaffected
          Subjects—If he is considered as a 
Prisoner we suppose him exchangeable
          &amp;amp; in the mean time it would probably be best to have him
          removed at a greater Distance from the 
Enemy's Lines—If his Parole was
          taken only to prevent mischief &amp;amp; in Aid of the magestrate whose
          Authority was then very inadequate to suppress Disaffection we shall
          consider him as altogether within the Civil Line&lt;ptr n="2"
          target="Rev13d180n2"/&gt;—I have the Honor to be With great Respect
          your Excellys Most Hum: Servt&lt;/p&gt;
       &lt;closer&gt;
          &lt;signed&gt;Wil: Livingston&lt;/signed&gt;
       &lt;/closer&gt;
       &lt;ps&gt;
          &lt;p&gt;P.S. I am sorry that Troup has been suffered to return to the Enemy
             after being so clearly convicted of being a Spy. I have this moment
             received Intelligence that a party is engaged to way-lay me between
             this place &amp;amp; my house, of which I have reason to think Troup
             is at the bottom.&lt;ptr n="3" target="Rev13d180n3"/&gt;&lt;/p&gt;
       &lt;/ps&gt;
    &lt;/div2&gt;
    &lt;div2 type="docback"&gt;
       &lt;note type="source" xml:id="Rev13d180sn"&gt;
          &lt;p&gt;
             &lt;bibl n="docSource"&gt;
                &lt;rs type="dType"&gt;
                   &lt;abbr&gt;LS&lt;/abbr&gt;
                &lt;/rs&gt;
                &lt;rs type="dWhere"&gt;
                   &lt;ref target="GWPrep37" type="repository"&gt;DLC:GW&lt;/ref&gt;
                &lt;/rs&gt;
             &lt;/bibl&gt; The postscript is in Livingston's writing.&lt;/p&gt;
       &lt;/note&gt;
       &lt;note n="1" type="fn" xml:id="Rev13d180n1"&gt;
          &lt;p&gt;Livingston wrote '1777.'&lt;/p&gt;
       &lt;/note&gt;
       &lt;note n="2" type="fn" xml:id="Rev13d180n2"&gt;
          &lt;p&gt;The New Jersey council of safety had agreed on 10 Jan. 'that a
             Warrant do issue for apprehending and bringing before the Board
             Archibald Kennedy Esqr, that an Enquiry be made into his past
             conduct, and that the Oaths of 
Government may be tendered to him.'
             On 13 Jan., Kennedy appeared before the council, which after
             considering 'sundry Affidavits' 
resolved that 'a letter be written
             to Genl Washington respecting the nature of Captn Kennedy's Parole
             &amp;amp; that copies of the Affidavits relative to his conduct be
             also transmitted with the Same' (&lt;ref target="PGWst1204"
             type="short-title"&gt; &lt;hi rend="italic"&gt;N.J. Council of Safety
             Minutes&lt;/hi&gt;&lt;/ref&gt;, 186–88). Copies 
of the affidavits of Nathaniel
             Camp, Jr., Robert Neil, and Robert 
Nicholls, all dated 12 Jan., are in
             &lt;ref target="GWPrep37" type="repository"&gt;DLC:GW&lt;/ref&gt;. See also
             &lt;ref type="document" 
target="Rev13d236"&gt;GW's letter to Kennedy of 20
             January&lt;/ref&gt;.&lt;/p&gt;
       &lt;/note&gt;
       &lt;note n="3" type="fn" xml:id="Rev13d180n3"&gt;
          &lt;p&gt;See &lt;ref target="Rev13d242" type="document"&gt;GW's first letter to
             Livingston of 20 January&lt;/ref&gt;.&lt;/p&gt;
       &lt;/note&gt;
    &lt;/div2&gt;
&lt;/div1&gt;</eg>
         </div>
      </body>
      <back>
         <listBibl>
            <bibl xml:id="bryant2000" label="Bryant 2000">
          
               <editor>Bryant, J.</editor> (ed.) 
<title rend="italic">The Melville Electronic Library</title>. 
Prototype, ca. 1998–2000, at <ref target="http://www3.iath.virginia.edu/melville/">http://www3.iath.virginia.edu/melville/</ref>, 
accessed <date when="2007-08-01">1 August 
2007</date>.
       </bibl>
            <bibl xml:id="bryant2006" label="Bryant 2006">
          
               <editor>Bryant, J.</editor> (ed.) 
<title rend="italic">Herman Melville's <title rend="quotes">Typee</title>: A Fluid-Text 
Edition</title>.  <publisher>University of 
Virginia Press</publisher>, 
<pubPlace>Charlottesville VA</pubPlace>, <date when="2006">2006</date>. URL: <ref target="http://rotunda.upress.virginia.edu/melville">http://rotunda.upress.virginia.edu/melville</ref>
            </bibl>
            <bibl xml:id="flanders2007" label="Flanders 2007">
          
               <author>Flanders, J.</author> Panel 
presentation during session <title rend="quotes">Coalition of Digital Humanities 
Centers</title>, Digital Humanities 2007, 
Urbana-Champaign IL, <date when="2007-06-05">5 
June 2007</date>.
       </bibl>
            <bibl xml:id="landow1991" label="Landow and Delany 1991">
        
               <author>Landow, G. P.</author> and
        <author>Delany, P.</author>
               <title rend="quotes">Hypertext, Hypermedia 
and Literary Studies: The State of the 
Art</title>. In <editor>Paul Delany</editor> and 
<editor>George P. Landow</editor> (eds.), 
<title rend="italic">Hypermedia and Literary Studies</title>. 
<publisher>MIT Press</publisher>, 
<pubPlace>Cambridge</pubPlace> (<date when="1991">1991</date>), <biblScope type="pages">pp. 
3–50</biblScope>.</bibl>
            <bibl xml:id="landow1992" label="Landow 1992">
          
               <author>Landow, G. P.</author>
               <title rend="italic">Hypertext: The Convergence of 
Contemporary Critical Theory and 
Technology</title>.
          <publisher>Johns Hopkins University 
Press</publisher>, <pubPlace>Baltimore</pubPlace> 
and <pubPlace>London</pubPlace> (<date when="1992">1992</date>).
       </bibl>
            <bibl xml:id="pgw1976" label="PGW 1976">
          
               <title rend="italic">The Papers of George 
Washington</title>, ed. D. Jackson et. al. 
<publisher>University of Virginia 
Press</publisher>, <pubPlace>Charlottesville 
VA</pubPlace>, 1976–.
       </bibl>
            <bibl xml:id="pgwde2007" label="PGWDE 2007">
          
               <editor>Crackel, T. J.</editor> (ed.) 
<title rend="italic">The Papers of George Washington Digital 
Edition</title>.  <publisher>University of 
Virginia Press</publisher>, 
<pubPlace>Charlottesville VA</pubPlace>, <date when="2007">2007</date>. URL: <ptr target="http://rotunda.upress.virginia.edu/pgwde"/>
            </bibl>
            <bibl xml:id="pierazzo2007" label="Pierazzo 2007">
          
               <author>Pierazzo, E.</author>
               <title rend="quotes">The Encoding of 
Time in Manuscripts Transcription: Toward Genetic 
Digital Editions</title>. Paper delivered at 
Digital Humanities 2007, Urbana-Champaign IL, 
<date when="2007-06-05">5 June 2007</date>; 
abstract available at <ref target="http://www.digitalhumanities.org/dh2007/abstracts/xhtml.xq?id=172">http://www.digitalhumanities.org/dh2007/abstracts/xhtml.xq?id=172</ref>.
       </bibl>
            <bibl xml:id="wiki2007" label="'Unfinished Work' 2007">
          
          Discussion page for article <title rend="quotes">Unfinished Work</title>, from 
<title rend="none">Wikipedia, the Free Encyclopedia</title> 
(<ref target="http://en.wikipedia.org/wiki/talk:unfinished_work">http://en.wikipedia.org/wiki/Talk:Unfinished_work</ref>), 
accessed <date when="2007-08-01">1 August 
2007</date>.
       </bibl>
         </listBibl>
      </back>
   </text>
</TEI>
