[Gzz-commits] manuscripts/Alph1 alph.rst

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Tuomas J. Lukka <address@hidden>        03/09/17 03:44:39

Modified files:
        Alph1          : alph.rst 

Log message:
        Arch sync

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/Alph1/alph.rst.diff?tr1=1.1&tr2=1.2&r1=text&r2=text

Patches:
Index: manuscripts/Alph1/alph.rst
diff -u manuscripts/Alph1/alph.rst:1.1 manuscripts/Alph1/alph.rst:1.2
--- manuscripts/Alph1/alph.rst:1.1      Mon Sep 15 06:42:10 2003
+++ manuscripts/Alph1/alph.rst  Wed Sep 17 03:44:39 2003
@@ -14,17 +14,17 @@
 We present three techniques to make the model 
 easily applicable to modern systems.
 
+The permanent addresses in the spans refer to *scrollblocks*, 
+clearly delimited, permanent blocks
+of fluid media data. A span can only contain fluid media units 
+from one scrollblock.
+
 Random-id content-carrying spans are useful for text: 
 they allow most of the advantages
 of Xanalogical fluid media with only an increase 
 in space in non-Xanalogical uses, i.e., no 
 fetching the content of the span from afar.
 
-The permanent addresses in the spans refer to *scrollblocks*, 
-clearly delimited, permanent blocks
-of fluid media data. A span can only contain fluid media units 
-from one scrollblock.
-
 PageImage scrollblocks are used for interoperability 
 with the modern real world, where
 receiving PDFs and Postscript files, i.e., images of pages, is a reality.
@@ -44,10 +44,10 @@
 systems described in [nelson99xanalogicalneeded]_
 is, formally,
 
-Making an implementation of referential fluid media practical
-=============================================================
+Making an implementation of referential fluid media practical: Two concrete 
models
+==================================================================================
 
-In this section, we present the three most important developments
+In this section, we present two different 
 
 As discussed by Nelson [nelson99xanalogicalneeded]_, 
 the most fundamental and secret idea
@@ -57,14 +57,31 @@
 with a permanent, universal
 identifier.
 
-Scrollblocks
-------------
+Content-addressed RFM (CARFM)
+-------------------------------------------------
+
+Content addressing is a ... hash (NOTE)
+
+http://www.intranetjournal.com/articles/200306/ij_06_04_03a.html
+
+Instead of continuous permascrolls as the Udanax implementation uses,
+the content-addressed referential fluid media (CARFM) model is based on
+*scrollblocks* which are fixed blocks of fluid media referenced through 
+content-addressing.
+
+... A *span* in Alph is a reference to a single, contiguous (rectangular) 
+block of fluid media units
+inside a single scrollblock.
 
-We have presented the basic idea of scrollblocks in [lukka02guids]_, 
+Inserting text character by character is achieved through first creating
+a *temporary*, modifiable scroll block and temporary span objects
+using that, and converting the temporary scrollblock into a permanent,
+content-addressed scroll block before saving the data.
 
+We have first presented the basic idea of using scrollblocks in 
[lukka02guids]_, 
 
-Random-id content-carrying spans
---------------------------------
+Random-id content-carrying RFM (RICC RFM)
+-----------------------------------------
 
 Random-id content-carrying (RICC) spans are a novel twist 
 on the basic referential fluid
@@ -80,7 +97,7 @@
 there is no real
 reference in them, just the identifier.
 
-The spans with the same UUID form a virtual scrollblock...
+- ... random numbers of 160 bits sufficient for ...
 
 Pros:
 
@@ -104,58 +121,42 @@
     - not, e.g., the full keystroke record envisioned by Nelson 
       (private communication)
 
-PageImage Spans
----------------
+- Spoofing ?
 
+    - cannot really do damage, as comparison is applied to *both* id *and* 
content
 
 
-The Alph Fluid Media Model formally
+Operability in a real-world context
 ===================================
 
-The Alph Fluid Media Model (AFMM) is a simple model
-based on the lowest-level referential fluid media concepts 
-of the Xanalogical model.
-
-Instead of continuous permascrolls as the Udanax implementation uses, 
-the Alph model is based on *scrollblocks* which are fixed blocks 
-of permanent media.
-
-A *span* in Alph is a reference to a single, contiguous (rectangular) 
-block of fluid media units
-inside a single scrollblock.
+Page Image Spans (PS/PDF/DjVu/...)
+----------------------------------
 
+The support for *PageImages* is one of the aspects of Alph geared 
+towards reasonable operability in a modern context.
 
-Storm URIs
+Fake Spans
 ----------
 
-- Like Data URIs, but with content hashes instead of data
-
-Text
-----
-
-We have developed three different types of text spans 
-
-Storm text spans
-""""""""""""""""
-
-Storm text spans [lukka02guids]_ are the earliest 
-of the text spans developed
-for Alph. A storm text span is simply a Storm URI 
-along with an offset and a length.
+The Alph Content Format
+=======================
 
-XXX Character sets?
+- XML format used by ALPH
 
+- incl. URN-5, Storm URI
+of the Xanalogical model.
 
-Images
-------
 
+Storm URIs
+----------
 
+- Like Data URIs, but with content hashes instead of data
 
-PageImages (PS/PDF/DjVu/...)
-----------------------------
+URN-5
+-----
 
-The support for *PageImages* is one of the aspects of Alph geared 
-towards reasonable operability in a modern context.
+The Alph DTD
+------------
 
 
 Implementation in Java + OpenGL
@@ -182,10 +183,13 @@
 The name Alph has its origins in the same poem as Xanadu(tm), 
 as the "sacred river".
 
+160 bits of randomness, or of hash are sufficient. blah blah
 
 
 The full model in a modern context
 ==================================
+
+
 
 Aspects that have been implemented in other systems
 ---------------------------------------------------