[Gzz-commits] manuscripts/FutureVision oplan.txt

[Benja Fallenstein]

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

Modified files:
        FutureVision   : oplan.txt 

Log message:
        ref

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

Patches:
Index: manuscripts/FutureVision/oplan.txt
diff -u manuscripts/FutureVision/oplan.txt:1.18 
manuscripts/FutureVision/oplan.txt:1.19
--- manuscripts/FutureVision/oplan.txt:1.18     Thu Nov 13 11:46:05 2003
+++ manuscripts/FutureVision/oplan.txt  Thu Nov 13 12:25:16 2003
@@ -92,6 +92,10 @@
 2 An item-based user interface
 ==============================
 
+(reviewer's comments:)
+Section 2, sentence 1: delete comma after \"medium\"
+Section 2, para 5: planning should not be capitalised
+
 The views simply show whatever they see in the structure
 around a given set of *focus* items:
 
@@ -147,9 +151,16 @@
 In this paragraph, need to explain about integration of documents
 into an item-centric system:
 
-    XXX
-
-    [#documents-as-files]_
+    Some of the items in the system will still be documents,
+    such as letters, e-mails, images and so on [#documents-as-files]_,
+    and the bodies of these documents will still be characters,
+    pixels and so on. However, as items, the documents will be woven
+    into the network of items and thus connected to e.g. the things that
+    they talk about, the people that created them, the meetings
+    they propose and the problems they solve;
+    we conjecture that it will be much easier to find relevant documents
+    in such a system than it is in the simplistic hierarchical
+    categorization of files and folders.
 
 And in notes:
 
@@ -178,7 +189,11 @@
     If you told the system to go backwards or forwards in time,
     it would ]]
 
-...
+Also: Views are not versioned; the structure is.
+Providing versioning information in the structure as *reflected*
+information (Example!) makes it easier to build views
+that can *show* the versioning, and allow the user
+to merge different users' changes to a document.
 
 Example images of a small structure and different views of it: [42]
     
@@ -187,11 +202,11 @@
 Mockup of different views, showing the local structure in as different
 ways as possible.
 
-Also: Views are not versioned; the structure is.
-Providing versioning information in the structure as *reflected*
-information (Example!) makes it easier to build views
-that can *show* the versioning, and allow the user
-to merge different users' changes to a document.
+Unbracket last paragraph (paper notes), add note:
+
+    .. [#more-vs-semantic-conns] The advantage of
+       using a network of items isn't to simply have *more*
+       connections; it is to have XXXY
 
 3.1 Zzstructure (used in ZigZag(tm))
 ------------------------------------
@@ -557,6 +572,19 @@
      publisher = {ACM Press},
      }
 
+    Recently, Kim (2002) proposed to use a graph-based model
+    as the basis for Engelbart's proposed Open Hyperdocument System,
+    to allow several underlying data structures to be combined.
+    This is essentially a proposal for using a hyperstructure,
+    even though Kim does not discuss visualization.
+
+    ADD REFERENCE:
+
+    **Kim, E.E.,** (2002) "Towards a Standard Graph-Based Data Model 
+    for the Open Hyperdocument System: Enabling Interoperability 
+    Between Collaborative Knowledge Applications". Available as
+    ``http://www.eekim.com/ohs/papers/graphmodel/``
+
 
 5.2 Structural computing 
 ------------------------
@@ -576,6 +604,14 @@
 
 5.3 RDF, Semantic Web
 ---------------------
+
+At end:
+
+    Also, schema languages developed for the Semantic Web
+    could find applications in Fenfire. For example, if
+    the system knows that every person has an address, it can
+    automatically create an address node when a person node is
+    created; the user then only needs to "fill in the blanks."
 
 
 5.4 This section does not exist