[Gzz-commits] manuscripts Alph1/alph.rst FutureVision/vision.rst

[Tuomas J. Lukka]

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

Modified files:
        Alph1          : alph.rst 
        FutureVision   : vision.rst 

Log message:
        Arch sync.

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

Patches:
Index: manuscripts/Alph1/alph.rst
diff -u manuscripts/Alph1/alph.rst:1.2 manuscripts/Alph1/alph.rst:1.3
--- manuscripts/Alph1/alph.rst:1.2      Wed Sep 17 03:44:39 2003
+++ manuscripts/Alph1/alph.rst  Wed Sep 17 13:48:07 2003
@@ -33,7 +33,10 @@
 Introduction
 ============
 
-..  Starting point: [nelson99xanalogicalneeded]_, where no references to 
tumblers &c are made.
+...  Starting point: [nelson99xanalogicalneeded]_, where no references to 
tumblers &c are made.
+
+... "What is text" by DeRose(? not sure), hierarchical content objects, ...
+Text models
 
 Udanax ...
 
@@ -44,6 +47,18 @@
 systems described in [nelson99xanalogicalneeded]_
 is, formally,
 
+Advantages
+
+Downsides
+
+- increased resource consumption for text (for images, sound, ... it's 
unnoticeable)
+
+    - not really an issue
+
+- central servers, content fetching, performance, ...
+
+    - we present
+
 Making an implementation of referential fluid media practical: Two concrete 
models
 
==================================================================================
 
@@ -159,11 +174,25 @@
 ------------
 
 
-Implementation in Java + OpenGL
-===============================
+Free (Libre) Implementation in Java + OpenGL
+============================================
+
+XXX Finish alph indices, ...
 
 Applications
 ============
+
+In most languages, Strings are such a primitive data type
+that replacing them is not easy...
+
+need some programming
+
+Insert Alph into
+
+- an editor
+
+- 
+
 
 Conclusion
 ==========
Index: manuscripts/FutureVision/vision.rst
diff -u manuscripts/FutureVision/vision.rst:1.10 
manuscripts/FutureVision/vision.rst:1.11
--- manuscripts/FutureVision/vision.rst:1.10    Wed Sep 17 06:52:07 2003
+++ manuscripts/FutureVision/vision.rst Wed Sep 17 13:48:07 2003
@@ -1,5 +1,5 @@
 
==================================================================================
-Hyperstructure: A Fine-Grained Approach to Hypermedia Systems
+Hyperstructure: A Fine-Grained Hypermedia Approach to Operating Systems
 
==================================================================================
 
 Abstract
@@ -128,7 +128,7 @@
 
     - sessions, though, defined with fixed schemas
 
-VIKI: find structure based on spatial placements
+VIKI: find structure based on spatial placements (`Marshall and Shipman 
(1993)`, `Marshall et al(1994)`)
 
 Dolphin (`Haake et al 1994`): 
 structured and unstructured information, moving from
@@ -155,6 +155,10 @@
       send and receive mail - MUCH MUCH better but still...
       REF: Task-oriented MIT project tuukkah discussed
 
+    - This is not meant to underestimate the work - OHM people have
+      done a lot of interesting, difficult work
+      in connecting monolithic, closed applications.
+
 FOHM: step towards hyperstructure: different domains
 unified into a single conceptual structure.
 
@@ -162,12 +166,41 @@
 Hyperstructure
 ==============
 
-- focus on personal hypertext from the start!
+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.
+
+- basic premise:
+
+    - user-interface -level co-operation by independently written applitudes 
+
+       - different applitudes add orthogonal behaviours and properties to data 
items
+
+       - one applitude controls only *aspects* of a data item
+
+- focus on personal hypertext 
+
+    - not really just personal, but any *use* except presentation
 
 Applet vs applitude
 
-Building blocks
-===============
+What is needed for hyperstructure
+---------------------------------
+
+- common fine-grained user-comprehensible underlying structure
+
+    - Nelson: "Look under the world, find a turtle..."
+
+    - similar to HOSS / structural computing
+
+- user interface toolkit / protocol to allow fluid co-operation between 
applitudes
+
+
+
+Concrete architectures
+======================
 
 ZigZag(tm) structure
 --------------------
@@ -182,30 +215,31 @@
 programming is more difficult since representing one-to-many
 and many-to-many relations is, while possible, laborious.
 
-RDF
----
+While the structure *per se* is simple to implement and there are at least X
+independent implementations, 
 
-RDF is ...
+- are applitudes actually implemented?
 
-Semantic web
+Fenfire
+=======
 
+- focus on personal hypertext!
 
-Xanalogical permanent media structure
--------------------------------------
+RDF
 
-Can be integrated into nearly any system
+Libvob
 
-NOT THE FULL XANADU(tm) FUNCTIONALITY
+    - keys, structures allow "annotations"
 
-Delivers significant benefits...
+Fenfire structures are defined by as simple RDF vocabularies as possible
 
-Fenfire
-=======
+    - implemented separately by classes
+
+    - intent: combine into applitudes, have metadata
 
-- focus on personal hypertext!
 
-An example applitude: FenPDF
-============================
+An example applitude combining multiple structures: FenPDF
+==========================================================
 
 Combines different types of hypertext
 
@@ -238,14 +272,14 @@
 
 .. _`Marshall et al. (1991)`
 
-**Marshall, C.C., Halasz, F.G., Rogers, R.A., Janssen, W.C. Jr.** (1991)
+**Marshall, C.C., Halasz, F.G., Rogers, R.A., Janssen, W.C. Jr.,** (1991)
 "Aquanet: a hypertext tool to hold your knowledge in place".
 ACM Hypertext'91 proceedings, 261-275.
 
 
 .. _`Marshall and Rogers 1993`
 
-**Marshall, C.C., and Rogers, R.A., ** (1993)
+**Marshall, C.C., and Rogers, R.A.,** (1993)
 "Two years before the mist: experiences with Aquanet".
 ACM Hypertext'93 proceedings, 53-62.
 
@@ -261,12 +295,16 @@
 "VIKI: spatial hypertext supporting emergent structure", 
 ACM Hypertext'94 proceedings, 13-23.
 
+.. _`Nürnberg et al (1997)`
+
+    Peter J. Nürnberg, John J. Leggett, Erich R. Schneider
+
 Notes
 =====
 
 (XXX Link to text)
 
-The fundamental ideas in what we call hyperstructure are due to Ted Nelson.
+The fundamental ideas in hyperstructure are due to Ted Nelson.
 The authors were exposed to these ideas in connection with the Gzz (earlier 
called GZigZag)
 project, whose goal was to implement Ted Nelson's ZigZag(tm) (trademark of Ted 
Nelson) structure
 in collaboration with him.
@@ -376,3 +414,13 @@
        - users can manipulate schema graphs
 
     RDF, Semantic Web
+
+Xanalogical permanent media structure
+-------------------------------------
+
+Can be integrated into nearly any system
+
+NOT THE FULL XANADU(tm) FUNCTIONALITY
+
+Delivers significant benefits...
+