85 |
.. using location-independent identifiers for |
.. using location-independent identifiers for |
86 |
non-breaking links: |
non-breaking links: |
87 |
|
|
88 |
If desktop documents could be refered to independently |
If desktop documents could be referred to independently |
89 |
of their location, it would be feasible to make |
of their location, it would be possible to make |
90 |
non-breaking links to them: When a document is published |
non-breaking links to them: When a document is published |
91 |
on the Web, it would have the same URI as on the |
on the Web, it would have the same URI as on the |
92 |
author's desktop; when a link to a document is emailed, |
author's desktop; when a link to a document is emailed, |
132 |
rendered this assumption obsolete. Distributed hashtables (DHTs) |
rendered this assumption obsolete. Distributed hashtables (DHTs) |
133 |
[malkhi02viceroy-andalso-maymounkov02kademlia-andalso-ratnasamy01can-andalso-stoica01chord-andalso-zhao01tapestry]_ |
[malkhi02viceroy-andalso-maymounkov02kademlia-andalso-ratnasamy01can-andalso-stoica01chord-andalso-zhao01tapestry]_ |
134 |
allow location-independent identifiers |
allow location-independent identifiers |
135 |
to be resolved on a global scale. In fact, authors argue in |
to be resolved on a global scale. In fact, |
136 |
[balakrishnan03semanticfree]_ that DHTs are suitable for the next generation |
Balakrishnan et al. [balakrishnan03semanticfree]_ argue |
137 |
|
that DHTs are suitable for the next generation |
138 |
Reference Resolutions Services (RRS) [#]_. |
Reference Resolutions Services (RRS) [#]_. |
139 |
|
|
140 |
.. [#] Domain Name System (DNS) [rfc1101]_ is a widely used RRS |
.. [#] Domain Name System (DNS) [rfc1101]_ is a widely used RRS |