[Gzz-commits] manuscripts/FutureVision vision.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Benja Fallenstein <address@hidden>      03/09/18 11:21:52

Modified files:
        FutureVision   : vision.rst 

Log message:
        xxx with things that should be said

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/FutureVision/vision.rst.diff?tr1=1.102&tr2=1.103&r1=text&r2=text

Patches:
Index: manuscripts/FutureVision/vision.rst
diff -u manuscripts/FutureVision/vision.rst:1.102 
manuscripts/FutureVision/vision.rst:1.103
--- manuscripts/FutureVision/vision.rst:1.102   Thu Sep 18 11:01:20 2003
+++ manuscripts/FutureVision/vision.rst Thu Sep 18 11:21:51 2003
@@ -178,6 +178,9 @@
 view defaults for each task, providing quick access
 to the functionality needed for this task.)
 
+XXX create menus --> footnote saying that menus
+are usually 'item' structures themselves
+
 Instead of forcing the user to think in applications,
 such a system lends itself to be structured around
 the user's tasks. `Nelson (1999b)`_ uses the term
@@ -186,6 +189,17 @@
 system; when information from a different applitude
 is needed, it is always available. 
 
+XXX applitudes *may* be constructed by a
+programmer and delivered to customers; views
+in that applitude can be repurposed into other
+applitudes then (say this as note)
+
+XXX applitudes use loom buoys, so if you add
+more loom buoys, they look like a seamless part
+of the applitude. (as note?) 
+example: connect "population" information to the
+places on the historian's map
+
 Items are **not owned
 by any single applitude**: When you need to connect
 information to an item that doesn't fit into the
@@ -215,7 +229,8 @@
 we present zzstructure and RDF, two hyperstructures actually used
 in systems aiming at the goals we have described above 
[#databases-as-hyperstructure]_.
 
-XXX
+XXX using hyperstructure for internal data
+XXX thus, explorability
 
 We use the term hyperstructure to **denote** a **storage model**
 that allows different data structures to overlap, but to