860 |
In a multi-user environment, we usually want only one user |
In a multi-user environment, we usually want only one user |
861 |
or group to be able to publish official versions a document. |
or group to be able to publish official versions a document. |
862 |
It is not yet clear how to do this. |
It is not yet clear how to do this. |
863 |
Signing pointer blocks digitally may be sensible, but |
Signing pointer blocks digitally may be sensible. |
|
digital signatures require a public key infrastructure |
|
|
and a trusted timestamping mechanism, which |
|
|
are hardly feasible for a system intended to be used |
|
|
for off-line as well as on-line work. |
|
864 |
For long-term publishing, one-time signatures have been |
For long-term publishing, one-time signatures have been |
865 |
found useful [anderson98erl]_. Currently, the pointer mechanism |
found useful [anderson98erl]_. Currently, the pointer mechanism |
866 |
works only in trusted Storm pools, e.g. |
works only in trusted Storm pools, e.g. |
867 |
in a workgroup collaborating on a set of documents. |
in a workgroup collaborating on a set of documents. |
868 |
|
|
869 |
|
.. digital signatures require a public key infrastructure |
870 |
|
and a trusted timestamping mechanism, which |
871 |
|
are hardly feasible for a system intended to be used |
872 |
|
for off-line as well as on-line work. |
873 |
|
|
874 |
The ability to retain multiple 'current' versions of a document |
The ability to retain multiple 'current' versions of a document |
875 |
can be useful, for example when there is no time to consolidate |
can be useful, for example when there is no time to consolidate |
876 |
changes at the time of synchronization. However, we need |
changes at the time of synchronization. However, we need |