Monday 14 February: Overview

1 of 2 [68]

1. • Revision of week 1
   • The Internet
   • The World Wide Web
   • Hypertext
2. • Text and Computers
   • Text encoding and markup
     • Document analysis
     • Structure and content
     • Document Type Definition (DTD)

Goals of this lecture

2 of 2 [68]

• have no questions anymore about week 1 and the readings
• know the history of the Internet and the WWW
• understand what hypertext is
• be able to provide a definition of what hypertext is
• understand the problems with text and computers
• understand the problems with proprietary software
• be able to analyse a document
• understand what text encoding and markup are
• have a clue of what a DTD is

1. Monday 7 February: Introduction to this course - Humanities Computing.

1 of 1 [68]

1. Introduction to this course
   1. Objectives of this course
   2. (Non-)Assumptions
   3. Me & You
   4. Housekeeping Rules
   5. Overview of the Course
   6. Test Elementary Computer Skills
2. Introduction to Humanities Computing
   1. Humanities Computing: definitions
   2. Humanities Computing: a field, a discipline
      1. Associations involved
      2. Journals and mailinglists
      3. Publications
      4. Institutions
   3. Humanities Computing: short history
3. Computing
   1. Hardware
   2. Graphical Interface

3. The Internet & the WWW

1 of 11 [68]

• Definition
• Services
• Short history

What does this mean?

3 of 11 [68]

1. The Internet is a worldwide collection of computer networks connecting academic, governmental, commercial, and organizational sites.
2. It provides access to communication services and information resources to millions of users around the globe.
3. Internet services include:
   • direct communication (e-mail, IRC-chat)
   • online conferencing (Usenet News, e-mail discussion lists)
   • distributed information resources (World Wide Web, Gopher)
   • remote login and file transfer (telnet, ftp)
   • and many other valuable tools and resources (internet telephony)

A worldwide collection of computer networks: Short history

4 of 11 [68]

• 1964: Paul Baran - Packet switched network
• 1969: ARPANET - 4 nodes
• 1972: 24 nodes
• 1973: TCP/IP - Vinton Cerf - INTERNET
• 1976: TCP/IP on ARPANET
• 1977: demonstration of the Internet
• 1981: BITNET and CSNET
• 1983: domain server
• 1984: NFS backbone
• 1991: WWW - Tim Berners-Lee - Cern

The early days

5 of 11 [68]

• 1964: Paul Baran - Packet switched network ← → Circuit network
• 1969: ARPANET - 4 nodes
  First test with two computers: one in Los Angeles, one in Stanford
  On their first attempt to log into Stanford's computer by typing "log win", UCLA researchers crashed their computer when they typed the letter "g"
  • UCLA (Los Angeles)
  • Stanford
  • UC Santa Barbara
  • University of Utah
• 1972: 24 nodes

1973: TCP/IP - Vinton Cerf - INTERNET

6 of 11 [68]

• TCP: information is split up in a couple of packages which need not arrive in the same order as they were sent, or via the same route.
• IP: each package of information carries a stamp with the address of destination.

The Internet

8 of 11 [68]

• 1981: BITNET and CSNET
• 1983: domain server
• 1984: NFS backbone

e-mail

9 of 11 [68]

• 1971: Ray Tomlinson
• 1972: Larry Roberts: read, reply, forward, save...
• 1976: Queen Elisabeth sent mail
• 1983: Dynamic Name Server (University of Wisconsin)

Domain Server

10 of 11 [68]

• be
• ac
• ua
• uia

The growth of the Internet

11 of 11 [68]

• 08/1981: 213
• 10/1985: 1,961
• 10/1990: 313,000
• 07/1995: 8,200,000
• 07/2000: 93,047,785
• 01/2001: 109,574,429
• 07/2001: 125,888,197
• 01/2002: 147,344,723
• 07/2002: 162,128,493
• 01/2003: 171,638,297
• 01/2004: 233,101,481

4. World Wide Web

1 of 2 [68]

• all the resources and users on the Internet that are using the Hypertext Transfer Protocol (HTTP).

• The World Wide Web is the universe of network-accessible information, an embodiment of human knowledge.

1991: WWW - Tim Berners-Lee - Cern

2 of 2 [68]

• Information management
• Original name: Mesh
• Non-linear text system: hypertext

5. Hypertext

1 of 12 [68]

• Paul Otlet (1932)
• Vannevar Bush (1945)
• Ted Nelson (1965)
• NLS (oNLine System): Doug Engelbart
• HES (Hypertext Editing System): Andries van Dam en Ted Nelson
• FRESS (File Retrieval and Editing System): Brown University
• Commercial hypertext systems
• HTML: Tim Berners-Lee & Robert Caillau
• Browser war

Paul Otlet (1868-1944)

2 of 12 [68]

• Le Document: each carrier of information
  • facts
  • interpretation of facts
  • statistics
  • source material
• Standard 3"x5" card - data sheet:
  • Monographic Principle
  • Universal Decimal Classification (UDC)

The work desk

4 of 12 [68]

• fitted with machines and auxiliary instruments of intellectual work
• machines to transform speech into writing and vice versa
• an application of television, to allow texts to be made available for remote reading
• reading machines scanning the physical items (search and retrieval)
• add to existing texts held remotely in such a way that the original texts were not disturbed

• screens
• loudspeaker
• selection machines

Ted Nelson

7 of 12 [68]

• Xanadu
• docuverse

NLS, HES, FRESS

8 of 12 [68]

• NLS (oNLine System): Doug Engelbart
• HES (Hypertext Editing System): Andries van Dam en Ted Nelson
• FRESS (File Retrieval and Editing System): Brown University

1. internal structure of nodes or documents
2. alternate views
3. bidirectional linking
4. link classification

Commercial systems

9 of 12 [68]

• Storyspace
• Guide
• Notecards
• Hypercard

Hypertext Markup Language (HTML): Tim Berners-Lee & Robert Caillau

10 of 12 [68]

• text
• formulae
• drawings
• graphics
• simple
• http (hypertext transfer protocol)

Hypertext: a definition

12 of 12 [68]

• An electronic multilinear visualisation of
• a set of information units (nodes) which
• may contain text, sound, and/or images, and which
• are linked to each other by way of hyperlinks.

Workflow: mantra in 9 lines

2 of 15 [68]

1. Project definition
2. Document analysis
3. Encoding design
4. Encoding
5. Validating
6. Functionality: storyboard
7. Transform, generate, implement
8. Document
9. Publish

6. Why electronic texts?

3 of 15 [68]

1. digitally created (born digital)
2. digitized

1. technological progress
2. • create access to material
   • support preservation policy
   • collection acquisition/completion
   • flexible use
   • institutional and strategic advantage (prestige)
   • research
   • education

2 different strategies

4 of 15 [68]

1. Short term thinking
   • document creation/production
   • print
   • mail
   • document lay-out
   • ease of the word processor
   • WYSIWYG interface
   • → .rtf, .doc, .wpd, .pdf, .xls, .dmb
   • → Word, WordPerfect, Adobe Acrobat, Excel, Access
2. Long term thinking
   • justify investments
   • retain access to material
   • exchange of data
   • document structure
   • → ISO standards and W3C norms

2 Main Problems

10 of 15 [68]

• Interchange between systems and platforms causes loss of information
  → Short data life cycle
• Loss of semantic information by translation to visual information

Solution

14 of 15 [68]

• is software and platform independent
• can describe the logical, structural, and semantic elements of a text

Solution

15 of 15 [68]

• is software and platform independent
• can describe the logical, structural, and semantic elements of a text

<title>Die Leiden des jungen Werther</title> is an
<emph>exceptionally</emph> good example of a book full of
<lang="German">Weltschmerz</lang>.

Workflow: mantra in 9 lines

1 of 25 [68]

1. Project definition
2. Document analysis
3. Encoding design
4. Coding
5. Validating
6. Functionality: storyboard
7. Transform, generate, implement
8. Document
9. Publish

7. Text encoding and markup

2 of 25 [68]

• Texts are more than simply sequences of glyphs
  → They have structure and content and they also have multiple readings

Workflow: mantra in 9 lines

4 of 25 [68]

1. Project definition
2. Document analysis
3. Encoding design
4. Encoding
5. Validating
6. Functionality: storyboard
7. Transform, generate, implement
8. Document
9. Publish

Text encoding and markup

5 of 25 [68]

• Texts are more than simply sequences of glyphs
  → They have structure and content and they also have multiple readings
• Text encoding or markup provides a means of making such structure, content, and readings explicit

Texts have structure and content 1

6 of 25 [68]

POOREDWARDDIDYOUHEARTHENEWSABOUTEDWARD?ONTHEBACKOFHISHE
ADHEHADANOTHERFACEWASITAWOMAN'SFACEORAYOUNGGIRLTHEYSAID
TOREMOVEITWOULDKILLHIMSOPOOREDWARDWASDOOMEDTHEFACECOULD
LAUGHANDCRYITWASHISDEVILTWINANDATNIGHTSHESPOKETOHIMTHIN
GSHEARDONLYINHELLBUTTHEYWEREIMPOSSIBLETOSEPARATECHAINED
TOGETHERFORLIFEFINALLYTHEBELLTOLLEDHISDOOMHETOOKASUITEO
FROOMSANDHUNGHIMSELFANDHERFROMTHEBALCONYIRONSSOMESTILLB
ELIEVEHEWASFREEDFROMHERBUTIKNEWHERTOOWELLISAYSHEDROVEHI
MTOSUICIDEANDTOOKPOOREDWARDTOHELL

Texts have structure and content 2

7 of 25 [68]

Poor Edward. Did you hear the news about Edward? On the back of
his head he had another face. Was it a woman's face or a
young girl? They said to remove it would kill him, So poor
Edward was doomed. The face could laugh and cry. It was his devil
twin. And at night she spoke to him things heard only in hell. But
they were impossible to separate, Chained together for life. Finally
the bell tolled his doom. He took a suite of rooms and hung himself
and her from the balcony irons. Some still believe he was freed
from her, but I knew her too well. I say she drove him to suicide,
and took poor Edward to hell.

Texts have structure and content 3

8 of 25 [68]

Poor Edward

Did you hear the news about Edward?
On the back of his head he had another face
Was it a woman's face or a young girl?
They said to remove it would kill him
So poor Edward was doomed

The face could laugh and cry
It was his devil twin
And at night she spoke to him
Things heard only in hell
But they were impossible to separate
Chained together for life

Finally the bell tolled his doom
He took a suite of rooms
And hung himself and her from the balcony irons
Some still believe he was freed from her
But I knew her too well
I say she drove him to suicide
And took poor Edward to hell

Texts have structure and content 4

9 of 25 [68]

Poor Edward

<line>Did you hear the news about Edward?</line>

<line>On the back of his head he had another face</line>

<line>Was it a woman's face or a young girl?</line>

<line>They said to remove it would kill him</line>

<line>So poor Edward was doomed</line>

<line>The face could laugh and cry</line>

<line>It was his devil twin</line>

<line>And at night she spoke to him</line>

<line>Things heard only in hell</line>

<line>But they were impossible to separate</line>

<line>Chained together for life</line>

<line>Finally the bell tolled his doom</line>

<line>He took a suite of rooms</line>

<line>And hung himself and her from the balcony irons</line>

<line>Some still believe he was freed from her</line>

<line>But I knew her too well</line>

<line>I say she drove him to suicide</line>

<line>And took poor Edward to hell</line>

Texts have structure and content 5

10 of 25 [68]

Poor Edward

<stanza>

<line>Did you hear the news about Edward?</line>

<line>On the back of his head he had another face</line>

<line>Was it a woman's face or a young girl?</line>

<line>They said to remove it would kill him</line>

<line>So poor Edward was doomed</line>

</stanza>

<stanza>

<line>The face could laugh and cry</line>

<line>It was his devil twin</line>

<line>And at night she spoke to him</line>

<line>Things heard only in hell</line>

<line>But they were impossible to separate</line>

<line>Chained together for life</line>

</stanza>

<stanza>

<line>Finally the bell tolled his doom</line>

<line>He took a suite of rooms</line>

<line>And hung himself and her from the balcony irons</line>

<line>Some still believe he was freed from her</line>

<line>But I knew her too well</line>

<line>I say she drove him to suicide</line>

<line>And took poor Edward to hell</line>

</stanza>

Texts have structure and content 6

11 of 25 [68]

<poem>

<title>Poor Edward</title>

<stanza>

<line>Did you hear the news about Edward?</line>

<line>On the back of his head he had another face</line>

<line>Was it a woman's face or a young girl?</line>

<line>They said to remove it would kill him</line>

<line>So poor Edward was doomed</line>

</stanza>

<stanza>

<line>The face could laugh and cry</line>

<line>It was his devil twin</line>

<line>And at night she spoke to him</line>

<line>Things heard only in hell</line>

<line>But they were impossible to separate</line>

<line>Chained together for life</line>

</stanza>

<stanza>

<line>Finally the bell tolled his doom</line>

<line>He took a suite of rooms</line>

<line>And hung himself and her from the balcony irons</line>

<line>Some still believe he was freed from her</line>

<line>But I knew her too well</line>

<line>I say she drove him to suicide</line>

<line>And took poor Edward to hell</line>

</stanza>

</poem>

2 Operable Conditions

13 of 25 [68]

• Markup should be separated from content
• Markup should be processable → logical & predictable

Markup should be separated from content

14 of 25 [68]

<tag>content</tag>

Markup should be processable

15 of 25 [68]

• Logical
• Predictable

Markup Model for a Book

18 of 25 [68]

<book>

  <chapter n="1">

    <section n="1">

      <p>...</p>

      <p>...</p>

    </section>

    <section n="2">

      <p>...</p>

      <p>...</p>

    </section>

  </chapter>

  <chapter n="2">

    <!- - more sections and paragraphs - ->
  </chapter>

</book>

Markup should be processable

19 of 25 [68]

• Logical
• Predictable

Document Type Definition (DTD)

20 of 25 [68]

• Poetry
• Prose
• Drama
• Letters
• Bibliographies
• Dictionaries
• Lists
• ...

Document Type Definition (DTD)

21 of 25 [68]

• Poetry
• Prose
• Drama
• Letters
• Bibliographies
• Dictionaries
• Lists
• ...

Document Type Definition (DTD)

22 of 25 [68]

• names for all your elements
• names and default values for their attributes
• rules about how elements can nest
• names for re-usable pieces of data (entities)
• and a few other things

Summary

23 of 25 [68]

• Computers work with representations of text
• Proprietary software merges structure, content, meaning, and layout in one code
  → 2 problems
  • Short data life cycle
  • Visual information = semantic information
• Solution: standard for text encoding
  → Markup explicitly articulates structure, content, and readings
• Markup should be separated from content
  → Tags
• Markup should be processable
  → OHCO thesis
• A markup language is defined by its Document Type Definition

Workflow: mantra in 9 lines

24 of 25 [68]

1. Project definition
2. Document analysis
3. Encoding design
4. Encoding
5. Validating
6. Functionality: storyboard
7. Transform, generate, implement
8. Document
9. Publish