gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gzz-commits] manuscripts/storm article.rst


From: Toni Alatalo
Subject: [Gzz-commits] manuscripts/storm article.rst
Date: Wed, 12 Feb 2003 11:41:06 -0500

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Toni Alatalo <address@hidden>   03/02/12 11:41:06

Modified files:
        storm          : article.rst 

Log message:
        additional 'use case' about movement of data between documents, based 
on the discussion with Benja

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.136 manuscripts/storm/article.rst:1.137
--- manuscripts/storm/article.rst:1.136 Wed Feb 12 08:57:41 2003
+++ manuscripts/storm/article.rst       Wed Feb 12 11:41:06 2003
@@ -94,6 +94,8 @@
 from the local intranet. When two people meet e.g. on the train,
 they should be able to form an ad-hoc network and follow links
 to documents stored on either one's computer [ref Thompson et al].
+Furthermore, when a document is split to parts, links to 
+the elements in the parts that are then in new documents should not break.
 
 Advanced hypermedia systems such as Microcosm and Hyper-G
 address dangling links through a notification system [ref]:
@@ -1104,6 +1106,10 @@
 able to see each other's documents and follow links to them if a
 peer-to-peer implementation of Storm is used (and pools published
 accordingly..? what should be discussed here?).
+Finally, if a document is split to parts, links to the elements that are
+then in the new documents do not break, bacause with xanalogical storage
+the links are actually to spans that are transcluded in all the documents
+that show them.
  
 *Tracking alternative versions*. Because Storm utilises immutable blocks,
 each modification to a document creates a new block. When a document is




reply via email to

[Prev in Thread] Current Thread [Next in Thread]