43 |
.. documents can be linked like web pages, |
.. documents can be linked like web pages, |
44 |
which would make them part of the web: |
which would make them part of the web: |
45 |
|
|
46 |
Documents written with OpenOffice or Microsoft Word |
Bush's Memex [XXX] was to be a hypermedia device |
47 |
can nowadays be hyperlinked like web pages-- |
for personal use, not for hypermedia publication. |
48 |
but users don't do so. URLs of web pages are pasted |
Yet, while many Web pages are densely interlinked today, |
49 |
into documents and emails, but links to other |
desktop documents still have rarely any hypermedia |
50 |
documents and emails are rarely used. |
functionality. Even though documents written with |
51 |
|
OpenOffice.org or Microsoft Word can nowadays be |
52 |
Such links could be of great benefit to small |
linked just like HTML files, users almost never |
53 |
workgroups, for example, to communicate |
do so. |
54 |
connections between documents better. |
|
55 |
|
Hypermedia on the desktop would be useful for |
56 |
|
keeping hyperlinked notes, for referring to |
57 |
|
pieces of documents in discussion, or to |
58 |
|
refer from a short memo to a document |
59 |
|
with more in-depth information. |
60 |
|
Both individuals and workgroups could benefit |
61 |
|
from such functionality. |
62 |
|
|
63 |
.. links needed that don't break when documents are moved: |
.. links needed that don't break when documents are moved: |
64 |
|
|
65 |
We believe that a major reason is that such links |
We believe that a major burden to hypermedia |
66 |
would break when documents are published, moved |
on the desktop is that links break when documents |
67 |
between folders, or sent by email. Changing all the links |
are published, moved between folders, or sent by email. |
68 |
when moving a document is too inconvenient. |
|
69 |
|
When sending a couple of hyperlinked notes per |
70 |
|
mail, the receiver would have to assemble them |
71 |
|
into the sender's directory structure. A document |
72 |
|
collaboratively authored by sender and receiver |
73 |
|
could not be linked to, except if both parties |
74 |
|
place it in exactly the same directory. |
75 |
|
|
76 |
.. using location-independent identifiers for |
.. using location-independent identifiers for |
77 |
non-breaking links: |
non-breaking links: |
78 |
|
|
79 |
In order for links not to break, documents would have |
If desktop documents could be refered to independently |
80 |
to be identified independently of their location. |
of their location, it would be possible to make |
81 |
|
non-breaking links to them. When a document is published |
82 |
|
on the Web, it would have the same URI [XXX] as on the |
83 |
|
author's desktop. When a link to a document is emailed, |
84 |
|
the receiver could follow the link as long as their |
85 |
|
computer can find the linked document-- on its local |
86 |
|
harddisk, attached to another email, or on the |
87 |
|
public Internet. |
88 |
|
|
89 |
|
Systems like Lotus Notes [XXX], a popular database sharing |
90 |
|
and collaboration tool, use location-independent, |
91 |
|
global identifiers to refer to documents. |
92 |
|
|
93 |
|
.. Freenet's cryptographical identifiers: |
94 |
|
|
95 |
|
XXX |
96 |
|
|
97 |
.. non-breaking links seem not globally resolvable: |
.. non-breaking links seem not globally resolvable: |
98 |
|
|
99 |
However, many hypermedia systems |
Many hypermedia systems (including Lotus Notes) |
100 |
assume that identifiers either have to |
assume that identifiers either have to |
101 |
say where a document can be found on the network, or they |
say where a document can be found on the network, or they |
102 |
cannot be efficiently resolved on a global scale. |
cannot be efficiently resolved on a global scale. |
110 |
|
|
111 |
.. but DHTs can do it: |
.. but DHTs can do it: |
112 |
|
|
113 |
Recent developments in peer-to-peer systems have |
However, recent developments in peer-to-peer systems have |
114 |
rendered this assumption obsolete. Structured overlay networks |
rendered this assumption obsolete. Distributed hashtables |
115 |
|
(DHTs) and other structured overlay networks |
116 |
[stoica01chord-andalso-ratnasamy01can-andalso-zhao01tapestry-andalso-rowston01pastry-andalso-maymounkov02kademlia-andalso-malkhi02viceroy-andalso-AspnesS2003-andalso-bonsma02swan]_ |
[stoica01chord-andalso-ratnasamy01can-andalso-zhao01tapestry-andalso-rowston01pastry-andalso-maymounkov02kademlia-andalso-malkhi02viceroy-andalso-AspnesS2003-andalso-bonsma02swan]_ |
117 |
allow location-independent identifiers |
allow location-independent identifiers |
118 |
to be resolved on a global scale. |
to be resolved on a global scale. |
125 |
all external links to a document can be found using |
all external links to a document can be found using |
126 |
a DHT. |
a DHT. |
127 |
|
|
128 |
.. brief summary how DHTs work: XXX |
.. brief summary how DHTs work? XXX |
129 |
|
|
130 |
This, we believe, may be the most important result of peer-to-peer |
This, we believe, may be the most important result of peer-to-peer |
131 |
research with regard to hypermedia. |
research with regard to hypermedia. |
132 |
|
|
|
.. Freenet's cryptographical identifiers: |
|
|
|
|
133 |
.. structure of this paper: |
.. structure of this paper: |
134 |
|
|
135 |
|
|