49 |
to a different computer, and after modifying the data on both systems, |
to a different computer, and after modifying the data on both systems, |
50 |
it should be easy to bring the two copies back in sync. |
it should be easy to bring the two copies back in sync. |
51 |
|
|
52 |
|
Another motivation (right?) for the data sharing / data mobility is |
53 |
|
collaboration. Within an organization or a project group, there often is a |
54 |
|
shared file system, e.g. a file server in the local network, so that |
55 |
|
different people do not need their personal copies of the data but can work |
56 |
|
(synchronously) on the same items. Often, however, especially when |
57 |
|
crossing organizationary boundaries there is no access each-others' |
58 |
|
filesystems even though data is shared. In actual collaboration, where |
59 |
|
several individuals work on the same items -- possibly at the sametime -- |
60 |
|
the data effectually forks. So similarly(?) to the the situation where a |
61 |
|
particular user has data on different computers, data needs to be kept in |
62 |
|
sync when there is collaboration. |
63 |
|
|
64 |
Our system allows documents and document content to be freely copied |
Our system allows documents and document content to be freely copied |
65 |
without breaking links. As long as a link and the documents |
without breaking links. As long as a link and the documents |
66 |
it links are currently accessible, the link can be shown. |
it links are currently accessible, the link can be shown. |