[Gzz-commits] manuscripts/storm article.rst

[Toni Alatalo]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Toni Alatalo <address@hidden>   03/02/13 10:40:32

Modified files:
        storm          : article.rst 

Log message:
        explanation of the figure (series), ok in ch4? refered to from where 
mentioned in evaluation too

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.143 manuscripts/storm/article.rst:1.144
--- manuscripts/storm/article.rst:1.143 Thu Feb 13 09:27:05 2003
+++ manuscripts/storm/article.rst       Thu Feb 13 10:40:31 2003
@@ -503,6 +503,25 @@
 may be beneficial for the members of the group to see other members'
 comments of articles etc.
 
+Figure XYZ illustrates how xanalogical storage addresses the issue of
+movement of data between documents. Initially, there are documents D1 and
+D2, with two links (directed arrows in the figure) from D1 to two different
+elements in D2, A and B. The links actually are to the /spans/ A and B that
+are stored in the scroll, but shown as parts of D2, as illustrated with the
+dashed lines. Then, when in the next step the document D2 is split in two --
+becoming documents D2.1 and D2.2 -- with link target A in the first and B
+ind the second new document, the links to them from D1 (and wherever) do not
+break as they still are to the spans that just show in different documents
+now. Also, when A is copy-pasted to an all new document D3, the system will
+actually transclude it there and that will also as an additional end point
+for links to A, as illustrated in the last (part of the) diagram.
+
+.. don't know how to put figs in .rst (yet) but wrote the descs anyhow
+
+doc2doc_movement-initial.eps
+doc2doc_movement-split.eps
+doc2doc_movement-additional.eps
+
 4. Storm block storage
 ======================
 
@@ -1123,7 +1142,8 @@
 Finally, if a document is split to parts (or content from one copy-pasted to
 another), 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.
+are transcluded in all the documents that show them (as illustrated in
+figure XYZ in section 3, xanalogical storage).
  
 *Tracking alternative versions*. Because Storm utilises immutable blocks,
 each modification to a document creates a new block. When a document is