[Gzz-commits] manuscripts/pointers Makefile article.rst block...

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Tuomas J. Lukka <address@hidden>        03/10/30 09:24:32

Modified files:
        pointers       : Makefile article.rst 
Added files:
        pointers       : blocks.mp 

Log message:
        Sync

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/pointers/blocks.mp?rev=1.1
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/pointers/Makefile.diff?tr1=1.2&tr2=1.3&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/pointers/article.rst.diff?tr1=1.38&tr2=1.39&r1=text&r2=text

Patches:
Index: manuscripts/pointers/Makefile
diff -u manuscripts/pointers/Makefile:1.2 manuscripts/pointers/Makefile:1.3
--- manuscripts/pointers/Makefile:1.2   Thu Oct 30 03:30:09 2003
+++ manuscripts/pointers/Makefile       Thu Oct 30 09:24:31 2003
@@ -1,5 +1,8 @@
 .SUFFIXES: $(SUFFIXES) .ps .dvi .png
 
+blocks.1: blocks.mp
+       mpost blocks
+
 # all: article.gen.ps article.gen.pdf article.gen.html
 all: article.gen.dvi
 
Index: manuscripts/pointers/article.rst
diff -u manuscripts/pointers/article.rst:1.38 
manuscripts/pointers/article.rst:1.39
--- manuscripts/pointers/article.rst:1.38       Thu Oct 30 05:29:47 2003
+++ manuscripts/pointers/article.rst    Thu Oct 30 09:24:32 2003
@@ -4,6 +4,12 @@
 
 .. (tentative title)
 
+Title suggestions and comments:
+
+should somehow say "Versioning on top of a simple basic model"...
+Totally **distributed** versioning
+Works even in ad hoc environments
+...
 
 
 Abstract
@@ -43,6 +49,8 @@
 on the shoulders of giants;" but how can we do that today,
 if the shoulders keep rotting away?
 
+XXX Wayback machine?
+
 .. Links shouldn't break when documents move or
    publishers lose interest
 
@@ -314,7 +322,8 @@
 by a system:
 
 Add permanent block
-    Given a bit string, adds the block into
+    Given a bit string and a MIME type,
+    adds the block into
     the system and return a *permanent id* for
     that exact bitstring,
     for example a cryptographic hash of the data.
@@ -370,9 +379,12 @@
 system relying only on the abstraction presented
 in the previous section.
 
+Our system is based on adding blocks to the system
+
+
 The PointerID is a combination of a public key of the
 owner of the pointer (possibly a certificate)
-and an indentifier. The association of the PointerID to
+and an identifier. The association of the PointerID to
 a particular data block is specified by adding a special
 *pointer block* into the system, which contains
 
@@ -443,6 +455,7 @@
 
 - ?
 
+
 Conclusions
 ===========
 
@@ -457,6 +470,11 @@
          unwanted versions get purged
 
     - spamming with new versions (only author due to DS, but still)
+
+    - Copyright issues
+
+       - on web, not such a great problem, as 
+         most of the web is about publishing things for all to see.
 
 - XXX
 - We have presented a peer-to-peer infrastructure that...with 
location-independent