61 |
History of location-dependence: `TBL ref`_ (like in HT'03 paper) |
History of location-dependence: `TBL ref`_ (like in HT'03 paper) |
62 |
|
|
63 |
This can be accomplished by replacing URIs that include |
This can be accomplished by replacing URIs that include |
64 |
a server name by location-independent, self-verifying identifiers |
a server name by URIs that are |
65 |
like cryptographic hashes. |
|
66 |
|
- location-independent: do not refer to a particular server |
67 |
|
that the file is to be downloaded from; |
68 |
|
- semantic-free: don't include human-readable information; |
69 |
|
if an identifier is semantic-free, there is no incentive |
70 |
|
to change it when a site is re-designed; |
71 |
|
- self-verifying: after downloading an alleged copy of a document, |
72 |
|
there is a cryptographical algorithm to test whether |
73 |
|
this is *really* a copy of this document. |
74 |
|
|
75 |
|
The most prominent example are cryptographic hashes. |
76 |
A file identified by a cryptographic hash |
A file identified by a cryptographic hash |
77 |
can be downloaded from any server that has a copy; the client |
can be downloaded from any server that has a copy; the client |
78 |
can then check the integrity of the file by checking it against the hash. |
can then check the integrity of the file by checking it against the hash. |
84 |
This way, a page's URI never needs to change.>>> |
This way, a page's URI never needs to change.>>> |
85 |
|
|
86 |
In 1996, Tim Berners-Lee [name-myth]_ argued that |
In 1996, Tim Berners-Lee [name-myth]_ argued that |
87 |
using location-independent identifiers |
using location-independent, semantic-free identifiers |
88 |
is not viable on a global scale: |
is not viable on a global scale: |
89 |
"[I]f you put information in a name, it decreases its longevity; |
"[I]f you put information in a name, it decreases its longevity; |
90 |
if you don't you can't dereference it to a resource." |
if you don't you can't dereference it to a resource." |