2. 1. The text of both the document and of the
work should be encoded;
2. All editorial acts should be attributed;
3. All materials should, by default, be available
by a Creative Commons share-alike license;
4. All materials should be available independent
of any one interface;
5. All materials should be held in a sustainable
long-term storage system, such as an
institutional repository
3. 1. The text of both the document and of
the work should be encoded
“Traditional” TEI --
“New” TEI (Ch. 11 of P5) --
5. www.textualcommunities.usask.ca
Anyone for refsDecl? We are…
This tells the processor: the document tree is made of
pages containing columns containing lines
Do the same for the entity tree (each <div> is a part of
the Tales, containing <l> elements for each line)
Map this to an ontology, put all these chunks into a
database, and you are done
16. What I said
Collaboration between textual scholars and digital
humanists is a mistake
Digital humanists should get out of textual scholarship;
and if they don’t, textual scholars should throw them
out
17. What I did not say
Textual scholars should not use digital methods
NO. The medium has always been central to textual
scholarship. We have to know everything there is to
know about digital texts – and we have to make digital
texts.
18. The mistakes we have made together
The story of <add> and <del>
BUT
Inferno iii, 9: Riccardiana 1005
NOT
19. The mistakes we have made together
• Digital scholarly editions are more than TEI
encoding
• Alan Galey is wrong. You don’t need to know PHP,
grep, Apache, the history of browsers, XSLT …
• Angle brackets are NOT good for you
20. How we may work
NOT:
One Project/One Scholar/One Digital Humanist
INSTEAD:
Lots of projects with lots of scholars creating lots
of data, open to all
Lots of other people doing lots of things with the
data – making interfaces, exploring it different
ways
Many Projects/Many Scholars/Many Digital Humanists