[Gzz-commits] manuscripts/storm article.rst

[Benja Fallenstein]

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

Modified files:
        storm          : article.rst 

Log message:
        Start writing use cases in prose

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.93 manuscripts/storm/article.rst:1.94
--- manuscripts/storm/article.rst:1.93  Wed Feb  5 17:57:10 2003
+++ manuscripts/storm/article.rst       Wed Feb  5 18:44:25 2003
@@ -60,26 +60,48 @@
 make these issues much easier to deal with, since data
 can be recognized whereever it is moved. 
 
-Examples for data mobility include today:
+Dangling links are an issue for published documents
+when data is moved between servers, and
+when documents are removed by the original publisher, but
+copies still exist in the network (e.g. in the web archive [ref])
+or on the local computer (after being downloaded and stored
+locally). In particular, the latter is important for off-line work
+(on a laptop or dialup system).
+Efficiency can be improved if documents can
+be found on the local machine if they have been cached or downloaded,
+or from any peer that has a copy in its cache. 
 
-- sharing versions (email attachment, disk) -> versioning
-- cvs-like central sync point(s) -> versioning
-- off-line work (dialup, laptop/cellphone/pda) -> links
-- publication -> links
-- mirroring -> links
-- downloading -> links, versioning if modified after download
-- moving between own systems (desktop/laptop, work/home) ->
-  versioning, links
-- web archive -> links, versioning (past versions)
-
-Future visions:
-
-- downloading from others' cache/permanent storage (load balancing) ->
-  links
-- hosting on own computer. others mirror -> links
-- ad-hoc sharing (train, cafe) -> links
+Dangling links are an issue for unpublished documents
+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, [XXX train collaboration].
+Also, after a document is published, local backlinks to it
+should be shown together along with public backlinks made by others.
+
+Alternate versions are an issue when 
+
+
+.. Examples for data mobility include today:
+
+   - sharing versions (email attachment, disk) -> versioning
+   - cvs-like central sync point(s) -> versioning
+   - off-line work (dialup, laptop/cellphone/pda) -> links
+   - publication -> links
+   - mirroring -> links
+   - downloading -> links, versioning if modified after download
+   - moving between own systems (desktop/laptop, work/home) ->
+     versioning, links
+   - web archive -> links, versioning (past versions)
+
+   Future visions:
+
+   - downloading from others' cache/permanent storage (load balancing) ->
+     links
+   - hosting on own computer. others mirror -> links
+   - ad-hoc sharing (train, cafe) -> links
+
+   Not really data mobility:
 
-.. not really data mobility:
    - comments and links on published document
 
 .. The design also allows for