[Gzz-commits] manuscripts/storm article.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Benja Fallenstein <address@hidden>      03/02/05 20:03:33

Modified files:
        storm          : article.rst 

Log message:
        more

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/storm/article.rst.diff?tr1=1.96&tr2=1.97&r1=text&r2=text

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.96 manuscripts/storm/article.rst:1.97
--- manuscripts/storm/article.rst:1.96  Wed Feb  5 19:30:05 2003
+++ manuscripts/storm/article.rst       Wed Feb  5 20:03:33 2003
@@ -60,29 +60,22 @@
 make these issues much easier to deal with, since data
 can be recognized whereever it is moved. 
 
-Dangling links are an issue for published documents
-when they are moved between servers;
-when no network connection is available (on a laptop 
-or a dialup system), but there is a local copy (in the cache
-or downloaded permanently); or when the publisher removes
-a document from the network, but copies still exist,
-e.g. in a public archive (such as [ref web.archive.org])
-or on the local computer.
+Dangling links are an issue when documents are moved
+between servers; when no network connection is available,
+but there is a local copy (e.g. on a laptop or dialup system);
+or when the publisher removes a document permanently,
+but there are still copies (e.g. in a public archive such as
+[ref web.archive.org]). Dangling links are also an issue
+when a document and a link to it are received independently,
+for example as attachments to independent emails,
+or when a link is sent by mail and the document is available
+from the local intranet.
 
-For unpublished documents, dangling links are an issue
-when a document and a link to it are received independently
-(for example, as attachments to different emails, possibly
-from different senders). In the future, they may be an issue (XXX why)
-for ad-hoc sharing, for example when two people meet on the train
-and want to exchange documents they have stored locally
-[ref Thompton et al].
-
-.. that is:
-   - moved between servers
-   - removed by publisher
-   - off-line work
-   - doc and link received independently
-   ...which are missing?
+In the future, dangling links may be an issue when using
+local resources [ref Thompton et al], for example in an ad-hoc
+network formed when two people with WLAN cards meet on the train.
+If one accesses the other's documents, link targets should be
+retrieved from the other's machine... XXX
 
 Also, after a document is published, local backlinks to it
 should be shown together along with public backlinks made by others.