[Gzz-commits] manuscripts/FutureVision vision.rst

[Benja Fallenstein]

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

Modified files:
        FutureVision   : vision.rst 

Log message:
        merge article skeleton in vision.rst. still one dangling reference, 
tuomas please check

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

Patches:
Index: manuscripts/FutureVision/vision.rst
diff -u manuscripts/FutureVision/vision.rst:1.12 
manuscripts/FutureVision/vision.rst:1.13
--- manuscripts/FutureVision/vision.rst:1.12    Wed Sep 17 14:28:41 2003
+++ manuscripts/FutureVision/vision.rst Wed Sep 17 15:05:39 2003
@@ -1,15 +1,73 @@
-==================================================================================
+===============================================================
+        The software everybody always needed (XXX title)
+===============================================================
+-----------------------------------------------------------------------
 Hyperstructure: A Fine-Grained Hypermedia Approach to Operating Systems
-==================================================================================
+-----------------------------------------------------------------------
+
+:Authors: Benja Fallenstein, Tuomas J. Lukka
+
+Contents
+========
+
+- `Introduction`_
+- `Related work`_
+- Example scenarios:
+
+  - `Personal information management`_
+  - `Literary research`_
+  - `Expert group process`_
+  - `Combining the scenarios`_
+
+- `Under the hood: Hyperstructure`_
+- `The Fenfire project`_
+- `Conclusions`_
+- `References`_
+
+
 
 Abstract
 ========
 
+XXX
+
 Introduction
 ============
 
-XXX The links should not be like this! They need to be in the **references**,
-with the author and title!
+Computers are supposed to be "information technology,"
+to help you to keep your information organized. But
+we still have no good **tools to** help us **remember** our tasks, 
+ideas and obligations; no tools to organize what we
+know about a thing, so that we can **understand** it better;
+no tools to **structure our thoughts**; no tools, 
+when grappling with our problems today,
+to remind us of the solutions of yesteryear.
+
+We need a computer that helps us keep track of addresses,
+appointments, birthdays, budgets, employees, phone calls,
+courses we have taken, marks we got,
+thoughts, ideas, types of poems, types of plants, 
+classes in a program and structures in a plot.
+
+Instead of being centered around irrelevant computery
+abstractions like "files" and "directories," such a system
+should **center around the things we care about**,
+the people, appointments, and so on. We propose a system
+in which these *items* (`Nelson 2000`_) are visible things
+that can be connected to each other; we propose,
+in technical terms, a hypermedia system in which items
+are first-class objects. 
+
+Such a system could look as shown in Figure 1.
+
+.. figure:: example1.gen.png
+
+   Figure 1: XXX (`larger image`__).
+
+   __ full-example1.gen.png
+
+
+.. OLD STUFF:
 
 Hypermedia was meant to be an extension to the mind.  "As We May Think,"
 Vannemar Bush entitled his famous article (`Bush 1945`); 
@@ -31,83 +89,13 @@
 __ http://www.xanadu.com.au/ted/zigzag/xybrap.html
 __ http://www.xanadu.com.au/mail/zzdev/msg02237.html
 
-Browsing our notes would be part of our thought process,
-making links would be part of understanding an idea.
-Such a computer would become a part of ourselves, an extension
-to the mind, like the written word. It would *aid the thought
-process* like scribbling down notes on a piece of paper,
-unifying all the notes into a single place, an
-external memory of sorts that would allow us to call up
-all of our thoughts about a subject with the flick of an
-electronic stylus.
-
-This is yet to happen.
-
-Current computer systems are not at all suited to the task.
-
-What is needed is a hypermedia system in which the
-concepts people care about-- the places, appointments, ideas,
-the *items*, in Nelson's words (2000__)-- are visible in
-and linkable the system. What is needed, in technical terms,
-is a hypermedia system in which items are first-class objects.
-
-__ http://www.xanadu.com.au/mail/zzdev/msg02237.html
-
-In such a system, to remember that we have "a meeting with
-Carli today at 2:15 about the book", we would create a new
-item (the meeting) and link it to Carli (another item) and 
-the book (a third item), and also connect the meeting to its
-scheduled time.
-
-Then, whenever we come across the book or the person in any
-context, we could see their connections to the meeting.
-For example, when we are mulling about an issue we have noted
-we must discuss with Carli (a note that would be linked
-to the Carli-item), we could quickly see that we will meet
-with her today. We could then link the issue to be part
-of the meeting's agenda (an item the meeting is linked to).
-
-(Using typed links, we could also turn particular types
-of links on and off, and thus would not have to see the
-connection *all* the time when thinking about Carli--
-only when meetings are on our mind.)
-
-Such a system would be able to appropriately represent
-the interconnectedness of items in our lives, making hypermedia
-truly a tool for thought.
-
-But as long as information is stored in disconnected files,
-as long as it is not naturally connected to the *items* it
-is about, this will not happen (and the best we can do 
-even with advanced navigational hypertext tools 
-is to link information *in addition to* 
-entering it into the system, rather than linking it
-*by* putting it into the system)
-
-Therefore, we need a new computer environment, centered around
-*items* rather than applications and files, an environment
-where everything we do, all information that we enter, is part
-of the network of linked items. 
-
-We need a system in which
-appointments aren't pieces of data entered into a calendar
-application, but items linked to other items; a system where
-letters are not files we need to store in a directory structure,
-but items connected to the recipients of the letter and the
-things that are discussed in the letter; a system where our
-ideas and problems exist as first class objects *at all*, linked
-to the things that we need to know about them.
-
-This is what, we submit, common-use hypermedia can be,
-ten years from now.
-
 Related work
-------------
+============
 
 The system we are proposing touches on a number of ...
 
 Flexible structure - Unifying structured and unstructured information
-"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+---------------------------------------------------------------------
 
 The Aquanet system by `Marshall et al (1991)`_ 
 
@@ -135,7 +123,7 @@
 one to another freer structure
 
 Structural computing 
-""""""""""""""""""""
+--------------------
 
     Hypermedia operating systems (HOSS)
 
@@ -145,7 +133,7 @@
     RDF, Semantic Web
 
 Open Hypermedia
-"""""""""""""""
+---------------
 
     - Focus: interoperability, existing apps.
 
@@ -163,8 +151,32 @@
 unified into a single conceptual structure.
 
 
-Hyperstructure
-==============
+Example scenarios
+=================
+
+Personal information management
+-------------------------------
+
+..
+
+Literary research
+-----------------
+
+..
+
+Expert group process
+--------------------
+
+..
+
+Combining the scenarios
+-----------------------
+
+..
+
+
+Under the hood: Hyperstructure
+==============================
 
 Definition
 ----------
@@ -200,10 +212,10 @@
 
 
 Concrete architectures
-======================
+----------------------
 
 ZigZag(tm) structure
---------------------
+""""""""""""""""""""
 
 Ted Nelson's original
 hyperstructure and applitude concepts
@@ -221,7 +233,7 @@
 - are applitudes actually implemented?
 
 Fenfire
-=======
+"""""""
 
 - focus on personal hypertext!
 
@@ -238,8 +250,11 @@
     - intent: combine into applitudes, have metadata
 
 
+The Fenfire project
+===================
+
 An example applitude combining multiple structures: FenPDF
-==========================================================
+----------------------------------------------------------
 
 Combines different types of hypertext
 
@@ -252,8 +267,10 @@
 
 - fluid links
 
-Conclusion
-==========
+Conclusions
+===========
+
+..
 
 References
 ==========
@@ -270,7 +287,7 @@
 "Coexistence and transformation of informal and formal structures: 
requirements for more flexible hypermedia systems". 
 ACM Hypertext'94 proceedings, 1-12.
 
-.. _`Marshall et al. (1991)`:
+.. _`Marshall et al (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".
@@ -295,6 +312,10 @@
 "VIKI: spatial hypertext supporting emergent structure", 
 ACM Hypertext'94 proceedings, 13-23.
 
+.. _`Nelson 2000`:
+
+XXX
+
 .. _`Nürnberg et al (1997)`:
 
     Peter J. Nürnberg, John J. Leggett, Erich R. Schneider
@@ -388,15 +409,17 @@
 Frame-based
 -----------
 
+..
+
 Xanalogical
 -----------
 
-.
+..
 
 Taxonomic (set inclusions)
 --------------------------
 
-.
+..
 
 Relational / schema-based / object-oriented 
 -------------------------------------------