ap90
7.1 KB
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
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Challenges of Access and Preservation panel remarks</title>
</head>
<body>
<address>by <a href="http://www.w3.org/People/Connolly/">Dan Connolly</a>
at the <cite><a
href="http://www.utexas.edu/president/symposium/index.html">Research
Library in the 21st Century</a></cite> symposium in Austin, Texas, 12
September 2006.</address>
<p><em>See also: <a
href="http://dig.csail.mit.edu/breadcrumbs/node/159">notes on the
event</a></em></p>
<ul>
<li class="row0">❑ Access and Preservation panel
<ul>
<li class="row1">❑ Opening Statement
<ul>
<li class="row0">❑ W3C's mission is to keep the web from fragmenting a la VHS vs Betamax
<ul>
<li class="row1">❑ W3C has about 400 member organizations
<ul>
<li class="row0">❑ some of them in this room: Google, Microsoft</li>
<li class="row1">❑ others: Creative Commons, Boeing, Mozilla foundation</li>
</ul>
</li>
<li class="row0">❑ I'm one of about 70 staff at 3 hosts.
<ul>
<li class="row1">❑ MIT in the Americas</li>
<li class="row0">❑ ERCIM in France</li>
<li class="row1">❑ Keio University in Japan</li>
</ul>
</li>
<li class="row0">❑ Tim Berners-Lee is the Director and the only current staff member who has been there longer than I have.</li>
<li class="row1">❑ We have about 30 working groups, from HTML to XML to Web Accessibility to Internationalization Guidelines to the Semantic Web, to Web Architcture</li>
</ul>
</li>
<li class="row0">❑ Much of my work is done over the network, but a big part of my job is getting people together in the same room to build trust, and maintain relationships.
<ul>
<li class="row1">❑ What my job has in common with yours: I'm trying to make W3C a place where interesting people want to come and contribute. We're all recruiting and competing for attention and loyalty.</li>
<li class="row0">❑ What did timbl do? Invent technology? What's novel is that he shared it and he works every day to keep it open.</li>
<li class="row1">❑ What web publishing shares with traditional publishing: yes, it's cheaper to distribute the text, but it's just as expensive to get attention, loyalty, and endorsement; to build an audience and a reputable editorial board.
<ul>
<li class="row0">❑ And with so many more texts available, it's more expensive to decide which texts to read.</li>
</ul>
</li>
</ul>
</li>
<li class="row1">❑ Principle #1 of Web Architecture is: use URIs.
<ul>
<li class="row0">❑ While some links in the web do break, following links in the web is about 96% reliable. Library efforts should not run from the existing HTTP and DNS URLs because of the 4%, but apply your expertise in access and preservation to increase the reliability of following links in scholarly communication.</li>
<li class="row1">❑ Douglas Englebart was and is a visionary in digital collaborate work; in his 1990 paper on requirements for computer supported collaborative work, he wrote:
<ul>
<li class="row0">❑ The Hyperdocument "Library System" - where hyperdocuments can be submitted to a library-like service that catalogs them and guarantees access when referenced by its catalog number, or "jumped to" with an appropriate link. Links within newly submitted hyperdocuments can cite any passages within any of the prior documents, and the back-link service lets the online reader of a document detect and "go examine" any passage of a subsequent document that has a link citing that passage.</li>
<li class="row1">❑ recent release of his work in HTML/javascript</li>
</ul>
</li>
<li class="row0">❑ W3C has a strong culture/tradition of persistence. Most of our 10-year old URIs still work. We take broken links seriously. Our policy begins:
<ul>
<li class="row1">❑ "When information is made available on the Web, it is important for the integrity of the Web, and the society based upon it, that the URIs used to reference information be used well into the future, and that the information persist as identified."</li>
<li class="row0">❑ We're working with MIT libraries etc. to back this persistence policy with long-term institutional commitment</li>
<li class="row1">❑ Think about domain names
<ul>
<li class="row0">❑ newproject.org or newproject.utexas.edu?</li>
<li class="row1">❑ www.utexas.edu/dr_doe/file23.html</li>
<li class="row0">❑ You can create a virtual organization in no time, but there is no shortcut to getting its value understood and appreciated.
<ul>
<li class="row1">❑ Friday night football games are a big part of building loyalty to an institution. How does the meta university do that?</li>
<li class="row0">❑ Anyone can distribute a new technical specification on the Web. What brings them to W3C is our reputation for our review process and our established culture and policies.</li>
<li class="row1">❑ Think about scaling down as well as scaling up. Movie recommendations from yahoo.com are not augmenting, not replacing recommendations from friends and family.</li>
</ul>
</li>
</ul>
</li>
<li class="row0">❑ A shift from publishers recovering costs from consumers to endowed publication looks very promising; please invest in it.
<ul>
<li class="row1">❑ I have a son in 6th grade; his science textbook is on the web, but behind a password. How long until Open Courseware and the like remove that barrier? It's hard to compete with free; can we shift from cost-recovery via consumers to endowed publication?</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
<li class="row0">❑ Other points as time permits
<ul>
<li class="row1">❑ Movie studios aggregate risk for big-budget films. Libraries have a similar role.</li>
<li class="row0">❑ Some things only change as generations pass. Universities have a new generation every 4 years (every year, or 6 years...)</li>
</ul>
</li>
</ul>
</li>
</ul>
</body>
</html>