gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gzz-commits] manuscripts/FutureVision vision.rst


From: Benja Fallenstein
Subject: [Gzz-commits] manuscripts/FutureVision vision.rst
Date: Wed, 17 Sep 2003 15:35:24 -0400

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Benja Fallenstein <address@hidden>      03/09/17 15:35:24

Modified files:
        FutureVision   : vision.rst 

Log message:
        restructure, moving the notes that are there around

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

Patches:
Index: manuscripts/FutureVision/vision.rst
diff -u manuscripts/FutureVision/vision.rst:1.16 
manuscripts/FutureVision/vision.rst:1.17
--- manuscripts/FutureVision/vision.rst:1.16    Wed Sep 17 15:17:13 2003
+++ manuscripts/FutureVision/vision.rst Wed Sep 17 15:35:24 2003
@@ -100,47 +100,44 @@
 ..
 
 
-Under the hood: Hyperstructure
-==============================
-
-Definition
-----------
-
-In this section, we shall attempt to define what we mean by the word 
"hyperstructure",
-as used e.g. in the name of the First Hyperstructure Workshop at XXX.
+The user interface / user experience
+====================================
 
-- basic premise:
+(XXX better section title)
 
-    - user-interface -level co-operation by independently written applitudes 
+- user-interface -level co-operation by independently written applitudes 
 
-       - different applitudes add orthogonal behaviours and properties to data 
items
+  - different applitudes add orthogonal behaviours and properties to items
 
-       - one applitude controls only *aspects* of a data item
+  - one applitude controls only *aspects* of an item
 
 - focus on personal hypertext 
 
-    - not really just personal, but any *use* except presentation
+  - not really just personal, but any *use* except presentation
 
 Applet vs applitude
 
-What is needed for hyperstructure
----------------------------------
+- user interface toolkit / protocol to allow fluid co-operation between 
applitudes
 
-- common fine-grained user-comprehensible underlying structure
+- "annotations"
 
-    - Nelson: "Look under the world, find a turtle..."
+Under the hood: Hyperstructure
+==============================
 
-    - similar to HOSS / structural computing
+.. In this section, we shall attempt to define what we mean by the word 
"hyperstructure",
+   as used e.g. in the name of the First Hyperstructure Workshop at XXX.
 
-- user interface toolkit / protocol to allow fluid co-operation between 
applitudes
+- Definition
+
+- common fine-grained user-comprehensible underlying structure
 
+    - Nelson: "Look under the world, find a turtle..."
 
+    - similar to HOSS / structural computing
 
-Concrete architectures
-----------------------
 
-ZigZag(tm) structure
-""""""""""""""""""""
+Zzstructure (used in ZigZag)
+----------------------------
 
 Ted Nelson's original
 hyperstructure and applitude concepts
@@ -157,13 +154,17 @@
 
 - are applitudes actually implemented?
 
-Fenfire
-"""""""
 
-- focus on personal hypertext!
+Resource Description Format (RDF)
+---------------------------------
 
 RDF
 
+
+
+The Fenfire project
+===================
+
 Libvob
 
     - keys, structures allow "annotations"
@@ -173,10 +174,6 @@
     - implemented separately by classes
 
     - intent: combine into applitudes, have metadata
-
-
-The Fenfire project
-===================
 
 An example applitude combining multiple structures: FenPDF
 ----------------------------------------------------------




reply via email to

[Prev in Thread] Current Thread [Next in Thread]