[Gzz-commits] manuscripts/storm short-paper.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Benja Fallenstein <address@hidden>      03/05/30 17:08:23

Modified files:
        storm          : short-paper.rst 

Log message:
        many twids

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/storm/short-paper.rst.diff?tr1=1.38&tr2=1.39&r1=text&r2=text

Patches:
Index: manuscripts/storm/short-paper.rst
diff -u manuscripts/storm/short-paper.rst:1.38 
manuscripts/storm/short-paper.rst:1.39
--- manuscripts/storm/short-paper.rst:1.38      Fri May 30 15:34:07 2003
+++ manuscripts/storm/short-paper.rst   Fri May 30 17:08:23 2003
@@ -13,14 +13,16 @@
 
     \begin{abstract}
     We present Storm, a storage system which unifies the
-    desktop and the public network. Storm assigns each document
+    desktop and the public network, making Web links between
+    desktop documents more practical. 
+    Storm assigns each document
     a permanent unique URI when it is created. Using peer-to-peer
     technology, we can locate documents even though our URIs
     do not include location information.
     Links continue to work unchanged when documents are emailed
     or published on the network.
     We have extended KDE to understand
-    torm URIs. Other systems such as GNU Emacs are able to use Storm 
+    Storm URIs. Other systems such as GNU Emacs are able to use Storm 
     through an HTTP gateway.
     \end{abstract}
 
@@ -73,9 +75,9 @@
 .. non-breaking links seem not globally resolvable:
 
 A major obstacle to hypermedia 
-on the desktop is broken links. A user receiving
+on the desktop are broken links. A user receiving
 hyperlinked documents by email, for example, would have to reconstruct
-the original directory structure; otherwise the links
+the original directory structure; otherwise, the links
 will not work.
 Many hypermedia systems
 assume that identifiers either
@@ -97,16 +99,16 @@
 to be resolved on a global scale. 
 Balakrishnan et al.  [balakrishnan03semanticfree]_ argue
 that DHTs are suitable for the next generation 
-Reference Resolutions Services (RRS) [#]_.
+Reference Resolution Services (RRS) [#]_.
 DHTs can not only be used to efficiently retrieve documents,
 but also metadata *about* documents. For example,
 unlike many link services that only query a limited
-set of servers for links [hill94extending]_,
-all published external links to a document can be found using
+set of servers for links (e.g., [hill94extending]_),
+all published external links to a document can be found efficiently using
 a DHT.
 
-.. [#] Domain Name System (DNS, RFC 1101) is a widely used RRS 
-   system in the Internet.
+.. [#] The Domain Name System (DNS, RFC 1101) is an RRS 
+   system widely used on the Internet.
 
 .. Freenet's cryptographical identifiers:
 
@@ -116,17 +118,17 @@
 Location-independent identifiers enable non-breaking links
 on the desktop and the Web:
 When a document is published
-on the Web, it would have the same URI as on the
+on the Web, it will have the same URI as on the
 author's local desktop; when a link to a document is emailed,
-the receiver could follow the link as long as their
-software can locate the linked document-- on its local
-harddisk, attached to another email, on the work group server
+the receiver can follow the link as long as their
+software can locate the linked-to document-- on its local
+harddisk, attached to another email, on a work group server
 or on the
 public Internet.
 In Freenet [freenet-ieee]_, an anonymous P2P
 publication system, *cryptographic hashes* [#]_
-are used for location-independent identifiers of 
-documents versions. 
+are used as location-independent identifiers of 
+document versions. 
 
 ..  [#] A cryptographic hash
     is short bit-string (often 160 bits)
@@ -162,17 +164,16 @@
 Storm (for STORage Module)
 is a library for both local and distributed storage
 and publishing.
-On the lowest level, storm handles data in *blocks*
+On the lowest level, Storm stores data in *blocks*,
 which are immutable byte sequences.
-As opposed to filesystems, Storm uses
-uses Freenet-like cryptographic identifiers to
-manipulate the blocks.
+As opposed to file systems, Storm
+uses Freenet-like cryptographic identifiers.
 This may seem like a bad tradeoff: while these identifiers
 enable secure location-independent references, they 
 do not allow
-the documents referred to by the identifiers to change 
+the identified documents to change 
 and
-are also less comprehensible for humans.
+are also less comprehensible to humans.
 However, these downsides are dealt with by the higher abstraction
 levels
 of Storm.
@@ -183,12 +184,13 @@
 of *pointer blocks*
 to build mutable documents on top of
 the lowest layer append-and-delete-only model.
-A pointer block is simply a storm block which says
-"The identifier X points to document Id, and this block overrides 
-the previous pointer blocks a, b" and contains
-a digital signature of the above information. The pointer Id
+A pointer block is a Storm block which says
+"The identifier *X* points to the current version of
+document *Y*, and this block overrides 
+the previous pointer blocks *a, b*" and contains
+a digital signature of the above information. The pointer *Y*
 contains the public key used for signatures --- this allows
-only the originator of the document to validate new versions.
+only the author of the document to validate new versions.
 A suitable user interface around pointers allows the user to
 still see old-style file names, but with the file names attached
 to his/her person, not to a particular computer.