60 |
make these issues much easier to deal with, since data |
make these issues much easier to deal with, since data |
61 |
can be recognized whereever it is moved. |
can be recognized whereever it is moved. |
62 |
|
|
63 |
{{The design also allows for |
.. The design also allows for |
64 |
automatic balancing of the load, which occurs in location-dependent |
automatic balancing of the load, which occurs in location-dependent |
65 |
situations with popular items. [benja says: This is not related |
situations with popular items. [benja says: This is not related |
66 |
to the central point as expressed in the title; therefore, I believe |
to the central point as expressed in the title; therefore, I believe |
67 |
it should be given as a benefit of the system somewhere later |
it should be given as a benefit of the system somewhere later |
68 |
in the paper (like many others) but not put here...]}} |
in the paper (like many others) but not put here...] |
69 |
|
|
70 |
Advanced hypermedia systems such as Microcosm and Hyper-G |
XXX use cases |
|
address dangling links through a notification system: |
|
|
When a document is moved, servers storing links to it are notified. |
|
|
Hyper-G uses an efficient protocol for delivering such notifications |
|
|
on the public Internet. |
|
|
|
|
|
The use of location-independent identifiers |
|
|
for documents, resolved through a peer-to-peer lookup system, |
|
|
makes such a notification unnecessary; when a document is moved, |
|
|
but retains its identifier, it can be found by the same mechanism as |
|
|
before the move. It is possible to retrieve the document |
|
|
from any system storing a copy; this means that documents may be |
|
|
accessible even after the original publisher has taken them off-line [#]_. |
|
|
|
|
|
.. [#] Intentionally or unintentionally. We believe that it is |
|
|
a good thing if published documents remain available even when |
|
|
the original publisher wants to retract them; however, discussion |
|
|
of the ethical implications of this is outside the scope of this paper. |
|
|
(But see [XXX search for refs! ;-)]) |
|
|
|
|
|
Such a system also works for data not publicized on the Internet. |
|
|
For example, if one email has a document attached to it, and another email |
|
|
links to this document, an index of locally stored documents |
|
|
by permanent identifier allows the system to follow the link. |
|
|
This would be extremely difficult to realize through a |
|
|
notification mechanism like Microcosm's and Hyper-G's. |
|
|
|
|
|
XXX say something about versioning |
|
71 |
|
|
72 |
In this paper, we present Storm (for *storage module*), a design |
In this paper, we present Storm (for *storage module*), a design |
73 |
dealing with these issues. Storm is a library |
dealing with these issues. Storm is a library |
90 |
.. [General figure of Storm, i.e. application layer, storm layer, |
.. [General figure of Storm, i.e. application layer, storm layer, |
91 |
netowork layer ? -Hermanni] |
netowork layer ? -Hermanni] |
92 |
|
|
93 |
No work on integrating Storm with current programs (in the spirit of Open Hypermedia) |
.. [Move somewhere else -b]: |
94 |
has been done so far. It is not clear how far this is possible |
No work on integrating Storm with current programs (in the spirit of Open Hypermedia) |
95 |
without changing applications substantially, if advantage |
has been done so far. It is not clear how far this is possible |
96 |
of our implementation of Xanalogical storage is to be taken. |
without changing applications substantially, if advantage |
97 |
(Vitali [ref] notes that Xanalogical storage necessiates |
of our implementation of Xanalogical storage is to be taken. |
98 |
strong discipline in version tracking, which current systems lack.) |
(Vitali [ref] notes that Xanalogical storage necessiates |
99 |
|
strong discipline in version tracking, which current systems lack.) |
100 |
|
|
101 |
.. Investigating the degrees of interoperability with Open Hypermedia |
.. Investigating the degrees of interoperability with Open Hypermedia |
102 |
(/Structural Computing?) and (more primitive?) other (Web) XXX is a possible |
(/Structural Computing?) and (more primitive?) other (Web) XXX is a possible |
130 |
several approaches has been proposed to deal with the dangling/other link |
several approaches has been proposed to deal with the dangling/other link |
131 |
management problems. |
management problems. |
132 |
|
|
133 |
|
Advanced hypermedia systems such as Microcosm and Hyper-G |
134 |
|
address dangling links through a notification system: |
135 |
|
When a document is moved, servers storing links to it are notified. |
136 |
|
Hyper-G uses an efficient protocol for delivering such notifications |
137 |
|
on the public Internet. |
138 |
|
|
139 |
|
The use of location-independent identifiers |
140 |
|
for documents, resolved through a peer-to-peer lookup system, |
141 |
|
makes such a notification unnecessary; when a document is moved, |
142 |
|
but retains its identifier, it can be found by the same mechanism as |
143 |
|
before the move. It is possible to retrieve the document |
144 |
|
from any system storing a copy; this means that documents may be |
145 |
|
accessible even after the original publisher has taken them off-line [#]_. |
146 |
|
|
147 |
|
.. [#] Intentionally or unintentionally. We believe that it is |
148 |
|
a good thing if published documents remain available even when |
149 |
|
the original publisher wants to retract them; however, discussion |
150 |
|
of the ethical implications of this is outside the scope of this paper. |
151 |
|
(But see [XXX search for refs! ;-)]) |
152 |
|
|
153 |
|
Such a system also works for data not publicized on the Internet. |
154 |
|
For example, if one email has a document attached to it, and another email |
155 |
|
links to this document, an index of locally stored documents |
156 |
|
by permanent identifier allows the system to follow the link. |
157 |
|
This would be extremely difficult to realize through a |
158 |
|
notification mechanism like Microcosm's and Hyper-G's. |
159 |
|
|
160 |
Microcosm addressed the linking problems of large archives |
Microcosm addressed the linking problems of large archives |
161 |
by separating the links from the documents and storing them on dedicated |
by separating the links from the documents and storing them on dedicated |
162 |
linkbases, with the the following requirement: when a document (where a |
linkbases, with the the following requirement: when a document (where a |