[Gzz-commits] manuscripts/storm article.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Benja Fallenstein <address@hidden>      03/02/15 08:56:51

Modified files:
        storm          : article.rst 

Log message:
        refactor xu section

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.155 manuscripts/storm/article.rst:1.156
--- manuscripts/storm/article.rst:1.155 Sat Feb 15 08:29:03 2003
+++ manuscripts/storm/article.rst       Sat Feb 15 08:56:51 2003
@@ -426,31 +426,27 @@
 the user enters between two saves of a document). Therefore, we hope
 that this will not be a major scalability problem. Otherwise,
 systems that allow range queries, such as skip graphs [AspnesS2003]_, 
-skipnet [ref], may prove useful.
+may prove useful.
 
-One question raised by xanalogical storage is which links to show
-for a popular document that has been linked to by many users.
+One question is how to select links to show
+when a popular document has been linked to by a large number of users.
 We hope to address this problem by collaborative filtering
-of links [explain, ref (grouplens.org pubs?)]. There has been research on
-collaborative filtering in peer-to-peer systems
-without compromising participants' privacy 
[canny02collaborative-andalso-canny02factor]_.
-For some purposes simple rules based on e.g. belonging to a group may be
-applicable as well: e.g. when working on a project with a project group, it
-may be beneficial for the members of the group to see other members'
-comments of articles etc.
+of links. Collaborative filtering in peer-to-peer systems is possible
+without compromising participants' privacy [canny02collaborative]_.
+Prioritizing links made by others in the same working group
+will also be useful.
 
 Figure [ref-figdocmovement]_ 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.
+anchors in D2, A and B. The links actually are to the *spans* A and B
+with permanent addresses, as illustrated by the
+dashed lines. Next, D2 is split in two parts, D2.1 and D2.2,
+moving the link targets into different documents.
+Even though D1 is not changed, the links still work as the link targets
+(spans) still have the same location-independent identifiers.
+Finally, A is copied to a new document, D3. Again without changing D1,
+the link now points to both locations of A.
 
 .. raw:: latex