[Gzz-commits] manuscripts/FutureVision vision.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Benja Fallenstein <address@hidden>      03/09/18 13:34:27

Modified files:
        FutureVision   : vision.rst 

Log message:
        hyperstructure, explorability

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

Patches:
Index: manuscripts/FutureVision/vision.rst
diff -u manuscripts/FutureVision/vision.rst:1.120 
manuscripts/FutureVision/vision.rst:1.121
--- manuscripts/FutureVision/vision.rst:1.120   Thu Sep 18 13:22:26 2003
+++ manuscripts/FutureVision/vision.rst Thu Sep 18 13:34:27 2003
@@ -231,11 +231,30 @@
 a person's name and e-mail, while a genealogy structure might
 give their parents, children, and spouses.
 
-XXX using hyperstructure for internal data
-XXX thus, explorability. Nelson: "Look under the world, find a turtle..."
-XXX focus+context
+To be used in this way, a hyperstructure must have a
+simple visualization that allows a user to browse and edit
+the network of items. When the user is looking at an item,
+this visualization must show the related items nearby;
+if the user has to scroll or click through menus first,
+the network of items loses its usefulness.
+
+With `Nelson (1999b)`_, we propose to use hyperstructure
+not only for the network of user-relevant items, but also
+for the data the system needs to store internally.
+
+For example, when placing items onto a map, these items' 
+x/y coordinates are normally not relevant to the user,
+and therefore not items. Still, they can be stored in the
+hyperstructure, available for the user to look at if they
+want to [#unix-command-line]_.
+
+By making the internals of the system work the same way
+as the network of items that users use daily, they can
+be more easily understood even by a non-advanced user,
+making them less arcane. "Look under the world, find a turtle,"
+in Nelson's terms (private communication, 2001).
 
-We use the term hyperstructure to **denote** a **storage model**
+We use the term hyperstructure to **denote a storage model**
 that allows different data structures to overlap, but to
 **connote** being used as the basis of an **item-based hypermedia system**.
 This is the sense of the word in which it was used in the title
@@ -343,6 +362,8 @@
 4.2.1 RDF Focus+Context views
 """""""""""""""""""""""""""""
 
+In this section, we describe our visualizations of RDF XXX
+
 - our 'basic hyperstructure' visualization of rdf
 
 - wheel: f+c (see fig.1)
@@ -403,13 +424,15 @@
     Figure XXX: a diagram of buoy animation (`larger image`__).
     The "screenshots" with black edges represent
     keyframes, and the others the animation.
+    
     The first keyframe shows the user viewing the orange-colored
     document; the user clicks on the light-blue buoy
     and the animation to the second keyframe ensues.
     There, the user clicks on the green buoy
     and the animation to the third keyframe follows.
-    There are no disruptive changes to what the user
-    sees - going back from the second keyframe
+    
+    **There are no disruptive changes to what the user
+    sees** - going back from the second keyframe
     to the orange document is trivial without
     an explicit "back button".
 
@@ -947,6 +970,12 @@
    characters, in turn, would be connected to your notes
    about them, in this case the idea about how to develop
    one of them.
+
+.. [#unix-command-line] Hyperstructure would have an analogous
+   role to text files on the UNIX command line: It would store both
+   the user's information and, unified in the same model, the data
+   used internally by the system, and be processable by
+   a lot of generic commands.
 
 ..  [#zzstructure-rdf] RDF and zzStructure are actually closely
     related: zzStructure is obtained if a RDF graph is constrained