5 |
Abstract |
Abstract |
6 |
======== |
======== |
7 |
|
|
8 |
Problems of data mobility, such as broken links, are identified. |
Dangling links and tracking of alternative versions are identified as |
9 |
Motivations and potential solutions are reviewed, and a design for |
problems of data mobility, which is defined as a collective term for the |
10 |
a system being developed for (these purposes) is presented. |
movement of documents between computers, locations on one computer and |
11 |
The design and a partial implementation of it is evaluated |
movement of content between documents. |
12 |
in light of use cases from realistic(?) scenarios. Open issues are |
Motivations and potential solutions in existing hypermedia research are |
13 |
discussed, and the areas for future work in such as |
reviewed. The design for Storm (for storage module) is |
14 |
interoperability, scalability and security is identified. |
presented, addressing the problems of data mobility by utilising |
15 |
|
location-independent globally unique identifiers, immutable block storage |
16 |
|
and peer-to-peer networking for hypermedia. |
17 |
|
The design and a partial implementation of it is evaluated in |
18 |
|
light of use cases from scenarios, that illustrate the benefits of storm for |
19 |
|
e.g. mobile knowledge workers. [mention some of the additional benefits?] |
20 |
|
Open issues are discussed, and possibilities for future work in areas such as interoperability, |
21 |
|
scalability and security are identified. |
22 |
|
|
23 |
Keywords: hypermedia, P2P, peer-to-peer, location-independent identifiers, |
Keywords: hypermedia, P2P, peer-to-peer, location-independent identifiers, |
24 |
versioned hypermedia, xanalogical storage, distributed hashtables |
versioned hypermedia, xanalogical storage, distributed hashtables |