-
Notifications
You must be signed in to change notification settings - Fork 4
/
tables.html
103 lines (99 loc) · 6.13 KB
/
tables.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
<!DOCTYPE HTML>
<html lang="en-us">
<head>
<meta charset="utf-8">
<title>Tables: HTML & CSS | Accessible Future</title>
<style type="text/css" media="all">
</style>
</head>
<body>
<h1>Schedule for November 4</h1>
<table summary="Schedule for November 4. We start at 8:30. Find the time for each session in the first column, and the topic for that session in the second column.">
<thead>
<tr>
<th class="time">Time</th>
<th class="topic">Topic</th>
</tr>
</thead>
<tbody>
<tr>
<th scope="row">8:30–8:45</th>
<td>
<p><strong>Continental Breakfast provided in the <a href="#logistics">Scholars’ Lab</a></strong></p>
</td>
</tr>
<tr>
<th scope="row">8:45–9:00</th>
<td>
<p><strong>Welcome and agenda-setting</strong></p>
<p> <strong>Bethany Nowviskie</strong> will outline the summit’s program and themes, organizers’ motivation and desired outcomes, and will facilitate introductions.</p>
</td>
</tr>
<tr>
<th scope="row">9:00–10:30</th>
<td>
<p><strong>Symposium Session 1: Tacit Knowledge in Code</strong></p>
<p>Drawing on his research into the history and literature of craftsmanship or tacit knowledge, and building on pragmatic work in computer-assisted fabrication and physical computing, <strong>William J. Turkel</strong> will offer concrete and inspiring examples of the ways in which unspoken understandings impact the theoretical and practical dimensions of code.</p>
<p><strong>Activity</strong>: Brainstorming a working list of areas in which tacit understanding and hands-on journeyman learning experiences make it difficult for scholars and junior developers to engage with the theoretical side of DH code craft.
</p>
</td>
</tr>
<tr>
<th scope="row">10:30–10:45</th>
<td>
<p><strong>Break</strong></p>
</td>
</tr>
<tr>
<th scope="row">10:45–12:15</th>
<td>
<p><strong>Symposium Session 2: Procedural Interface Design</strong></p>
<p> <strong>Stéfan Sinclair</strong> will draw on his scholarly interests in the algorithmic, combinatoric, and playful practices of the OuLiPo literary movement to explicate code written with human interaction in mind. This presentation will address the division that can occur between design and development, even in humanities projects in which design elements take on particular rhetorical or interpretive significance.</p>
<p><strong>Discussion</strong>: What is unspoken but critical in DH design? What is ill-understood or under-theorized—and what can the community do about that?
</p>
</td>
</tr>
<tr>
<th scope="row">12:15–1:30</th>
<td>
<p><strong>Lunch</strong></p>
<p>Lunch on your own (at UVa or on <a href="http://en.wikipedia.org/wiki/The_Corner_%28Charlottesville,_Virginia%29">the Corner</a>)</p>
</td>
</tr>
<tr>
<th scope="row">1:30–2:45</th>
<td>
<p><strong>Symposium Session 3: Designing Text Models for Language</strong></p>
<p>Digital humanities software developers must cultivate a sophisticated understanding of the structures of textual information, and help articulate the ways in which those structures contribute to or inhibit humanities arguments. <strong>Hugh Cayless</strong> will present approaches to the semantics, structures and representations of texts.</p>
<p><strong>Activity</strong>: Create a quick-and-dirty intellectual model of a humanities document or book object. What existing theories and text technologies did your work draw on?
</p>
</td>
</tr>
<tr>
<th scope="row">2:45–3:00</th>
<td>
<p><strong>Break</strong></p>
</td>
</tr>
<tr>
<th scope="row">3:15–4:45</th>
<td>
<p><strong>Symposium Session 4: Messy Understandings</strong></p>
<p>Little conversation takes place among developers, across digital humanities projects, on decision-making with regard to uniformity or incongruity of data. <strong>Mia Ridge</strong> will discuss the process by which one might decide to support or disregard “edge cases” in cultural heritage metadata, and the manner in which decisions about ambiguous or contradictory information can affect ongoing database design and development.</p>
<p><strong>Discussion</strong>: Share your own stories. How have you worked to incorporate ambiguity or contradictory evidence in humanities computing projects? When have you decided to elide it, why, and with what impact on the scholarly arguments your tool enabled?
</p>
</td>
</tr>
<tr>
<th scope="row">6:00pm</th>
<td>
<p><strong>Working dinner</strong></p>
<p>Dinner provided at <a href="http://trinityonthecorner.com/">Trinity Irish Pub</a>.</p>
<p><strong>Nowviskie</strong> introduces tomorrow’s “Project Pitches” and “Development Sessions.” Other possible activities include: round-robin contributions to a <strong>Speaking in Code</strong> idea-hopper (concrete actions required to address the problems surfaced today) or a table-based brainstorming/discussion session led by <strong>Wayne Graham</strong>, <strong>Jeremy Boggs</strong>, and <strong>Eric Rochester</strong>: DH developer community needs, scholarly communications vectors.
</p>
</td>
</tr>
</tbody>
</table>
</body>
</html>