[Gzz-commits] manuscripts/FutureVision oplan.txt

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Benja Fallenstein <address@hidden>      03/11/13 08:03:43

Modified files:
        FutureVision   : oplan.txt 

Log message:
        intro

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/FutureVision/oplan.txt.diff?tr1=1.9&tr2=1.10&r1=text&r2=text

Patches:
Index: manuscripts/FutureVision/oplan.txt
diff -u manuscripts/FutureVision/oplan.txt:1.9 
manuscripts/FutureVision/oplan.txt:1.10
--- manuscripts/FutureVision/oplan.txt:1.9      Thu Nov 13 04:16:50 2003
+++ manuscripts/FutureVision/oplan.txt  Thu Nov 13 08:03:42 2003
@@ -9,6 +9,16 @@
 Abstract
 ========
 
+Relationship between item-based and files:
+
+    Computers should help us with **organizing our lives**, rather
+    than making them more difficult. We need
+    a system **structured** around **items** -- 
+    **things that we care about**, such as people, arguments and ideas,
+    and able to express the relationships between them,
+    so that connected to e.g. an idea we see all arguments
+    we have considered for or against it.
+
 [1]: mention the smallness of space here, and that 
 we distinguish between explored and unexplored spaces
 and that it affects our user interfaces
@@ -18,17 +28,55 @@
 1 Introduction
 ==============
 
+s/a system, in technical terms/in technical terms/
+
+Remove the "irrelevant computery abstractions" goof,
+replace by discussion about document-centric vs. item-centric:
+
+    This system
+    should **center around the things we care about**,
+    the people, appointments, plants, articles we read, 3D models we create
+    and so on. We need a system
+    in which these **items** (`Nelson 2000`_) are visible things
+    that can be connected to each other;
+    in technical terms, a hypermedia system in which items
+    are first-class objects [#can-use-structcomp]_. 
+
+    In contrast, in the mainstream file system paradigm,
+    only documents and categories of documents are represented 
+    as first-class objects.
+    While documents certainly qualify as things that we care about,
+    other items like people, theories, or places are not 
+    explicitly represented in this paradigm at all. 
+    Additionally, file systems are simple hierarchies,
+    rather than allowing arbitrary relationships between items
+    to be expressed. Information like "In this meeting, we discussed
+    possible solutions A, B, C to problem X, and our consensus
+    was that...," for example, might be hidden in a document called
+    "Minutes 2003-07-24."
+
+    In an item-centric system, this information would be expressed
+    as relationships between a couple of items-- the problem, the meeting,
+    the solutions discussed, the arguments raised in this discussion,
+    the decisions reached. Looking at the problem item, for example,
+    the user would connect to it the solutions that have
+    been discussed for it, and to them
+    the arguments that have presented in favor or against each
+    of the solutions-- no matter in which meeting, in which e-mail,
+    in which memo or in which chat session they were made.
+    (On the other hand, the user could just as well look at all the points
+    made in a particular meeting, no matter which topic they were about.)
+
 [4],[5] Make explicit the difference between a file
 and items, "a thing we care about":
 
-    Things currently represented by files or folders,
-    such as documents or projects, are usually
-    items, but there are several items that are not files:
-    appointments (often all appointments are stored
-    in a binary, proprietary database file by programs), 
-    emails (usually several stored in one file), ...
-
-    XXX
+    Also, many items that do have a representation in current systems--
+    for example appointments (often all appointments are stored
+    in a binary, proprietary database file) and e-mail
+    (usually several stored in one file)-- are not represented as files.
+    It is not possible to make connections
+    between an e-mail and an appointment if they are stored
+    in different files.
     
 (XXX mention longhorn calendar?)
 
@@ -82,7 +130,8 @@
 Defer to ZZ tutorial for details (say that explaining
 how zzstructure is used is beyond the scope of this paper).
 
-[22] Add screenshot of Gzz in action, to illustrate ZZ
+[22] Add screenshot of Gzz in action, to illustrate ZZ:
+change2.png, hop1.png (rename :))
 
 
 3.2 Resource Description Framework (RDF)