[Gzz-commits] manuscripts/FutureVision vision.rst

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Tuomas J. Lukka <address@hidden>        03/09/18 14:01:57

Modified files:
        FutureVision   : vision.rst 

Log message:
        More OHM

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

Patches:
Index: manuscripts/FutureVision/vision.rst
diff -u manuscripts/FutureVision/vision.rst:1.128 
manuscripts/FutureVision/vision.rst:1.129
--- manuscripts/FutureVision/vision.rst:1.128   Thu Sep 18 13:59:31 2003
+++ manuscripts/FutureVision/vision.rst Thu Sep 18 14:01:57 2003
@@ -663,28 +663,11 @@
 Instead of focusing on unifying the internal data
 model and views and avoiding different "applications",
 OHM focuses on hyperlink interoperability between existing
-applications (`Pearl 1989`).
+applications (`Pearl 1989`_).
 
-However, the OHM field 
-
-FOHM (Millard et al 2000)
-
-XXX Should we just not mention open hypermedia?
-
-    - Focus: interoperability, existing apps.
-
-    - Nelson (XXX) says "An application is a prison" -- 
-      an Open Hypermedia -enabled
-      application is a prison where you can get visitors and
-      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.
+However, the FOHM model (`Millard et al 2000`_) is an interesting
+step towards a similar approach: the FOHM model combines the different
+hypertext domains into a single conceptual structure.
 
 
 5.5 Fluid Links and Transpointing Windows