/[gzz]/manuscripts/FutureVision/vision.rst
ViewVC logotype

Diff of /manuscripts/FutureVision/vision.rst

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.10 by tjl, Wed Sep 17 10:52:07 2003 UTC revision 1.11 by tjl, Wed Sep 17 17:48:07 2003 UTC
# Line 1  Line 1 
1  ==================================================================================  ==================================================================================
2  Hyperstructure: A Fine-Grained Approach to Hypermedia Systems  Hyperstructure: A Fine-Grained Hypermedia Approach to Operating Systems
3  ==================================================================================  ==================================================================================
4    
5  Abstract  Abstract
# Line 128  The Aquanet system by `Marshall et al (1 Line 128  The Aquanet system by `Marshall et al (1
128    
129      - sessions, though, defined with fixed schemas      - sessions, though, defined with fixed schemas
130    
131  VIKI: find structure based on spatial placements  VIKI: find structure based on spatial placements (`Marshall and Shipman (1993)`, `Marshall et al(1994)`)
132    
133  Dolphin (`Haake et al 1994`):  Dolphin (`Haake et al 1994`):
134  structured and unstructured information, moving from  structured and unstructured information, moving from
# Line 155  Open Hypermedia Line 155  Open Hypermedia
155        send and receive mail - MUCH MUCH better but still...        send and receive mail - MUCH MUCH better but still...
156        REF: Task-oriented MIT project tuukkah discussed        REF: Task-oriented MIT project tuukkah discussed
157    
158        - This is not meant to underestimate the work - OHM people have
159          done a lot of interesting, difficult work
160          in connecting monolithic, closed applications.
161    
162  FOHM: step towards hyperstructure: different domains  FOHM: step towards hyperstructure: different domains
163  unified into a single conceptual structure.  unified into a single conceptual structure.
164    
# Line 162  unified into a single conceptual structu Line 166  unified into a single conceptual structu
166  Hyperstructure  Hyperstructure
167  ==============  ==============
168    
169  - focus on personal hypertext from the start!  Definition
170    ----------
171    
172    In this section, we shall attempt to define what we mean by the word "hyperstructure",
173    as used e.g. in the name of the First Hyperstructure Workshop at XXX.
174    
175    - basic premise:
176    
177        - user-interface -level co-operation by independently written applitudes
178    
179            - different applitudes add orthogonal behaviours and properties to data items
180    
181            - one applitude controls only *aspects* of a data item
182    
183    - focus on personal hypertext
184    
185        - not really just personal, but any *use* except presentation
186    
187  Applet vs applitude  Applet vs applitude
188    
189  Building blocks  What is needed for hyperstructure
190  ===============  ---------------------------------
191    
192    - common fine-grained user-comprehensible underlying structure
193    
194        - Nelson: "Look under the world, find a turtle..."
195    
196        - similar to HOSS / structural computing
197    
198    - user interface toolkit / protocol to allow fluid co-operation between applitudes
199    
200    
201    
202    Concrete architectures
203    ======================
204    
205  ZigZag(tm) structure  ZigZag(tm) structure
206  --------------------  --------------------
# Line 182  While the ZigZag(tm) structure is simple Line 215  While the ZigZag(tm) structure is simple
215  programming is more difficult since representing one-to-many  programming is more difficult since representing one-to-many
216  and many-to-many relations is, while possible, laborious.  and many-to-many relations is, while possible, laborious.
217    
218  RDF  While the structure *per se* is simple to implement and there are at least X
219  ---  independent implementations,
220    
221  RDF is ...  - are applitudes actually implemented?
222    
223  Semantic web  Fenfire
224    =======
225    
226    - focus on personal hypertext!
227    
228  Xanalogical permanent media structure  RDF
 -------------------------------------  
229    
230  Can be integrated into nearly any system  Libvob
231    
232  NOT THE FULL XANADU(tm) FUNCTIONALITY      - keys, structures allow "annotations"
233    
234  Delivers significant benefits...  Fenfire structures are defined by as simple RDF vocabularies as possible
235    
236  Fenfire      - implemented separately by classes
237  =======  
238        - intent: combine into applitudes, have metadata
239    
 - focus on personal hypertext!  
240    
241  An example applitude: FenPDF  An example applitude combining multiple structures: FenPDF
242  ============================  ==========================================================
243    
244  Combines different types of hypertext  Combines different types of hypertext
245    
# Line 238  ACM Hypertext'94 proceedings, 1-12. Line 272  ACM Hypertext'94 proceedings, 1-12.
272    
273  .. _`Marshall et al. (1991)`  .. _`Marshall et al. (1991)`
274    
275  **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)
276  "Aquanet: a hypertext tool to hold your knowledge in place".  "Aquanet: a hypertext tool to hold your knowledge in place".
277  ACM Hypertext'91 proceedings, 261-275.  ACM Hypertext'91 proceedings, 261-275.
278    
279    
280  .. _`Marshall and Rogers 1993`  .. _`Marshall and Rogers 1993`
281    
282  **Marshall, C.C., and Rogers, R.A., ** (1993)  **Marshall, C.C., and Rogers, R.A.,** (1993)
283  "Two years before the mist: experiences with Aquanet".  "Two years before the mist: experiences with Aquanet".
284  ACM Hypertext'93 proceedings, 53-62.  ACM Hypertext'93 proceedings, 53-62.
285    
# Line 261  ACM Hypertext'93 proceedings, 217-230. Line 295  ACM Hypertext'93 proceedings, 217-230.
295  "VIKI: spatial hypertext supporting emergent structure",  "VIKI: spatial hypertext supporting emergent structure",
296  ACM Hypertext'94 proceedings, 13-23.  ACM Hypertext'94 proceedings, 13-23.
297    
298    .. _`Nürnberg et al (1997)`
299    
300        Peter J. Nürnberg, John J. Leggett, Erich R. Schneider
301    
302  Notes  Notes
303  =====  =====
304    
305  (XXX Link to text)  (XXX Link to text)
306    
307  The fundamental ideas in what we call hyperstructure are due to Ted Nelson.  The fundamental ideas in hyperstructure are due to Ted Nelson.
308  The authors were exposed to these ideas in connection with the Gzz (earlier called GZigZag)  The authors were exposed to these ideas in connection with the Gzz (earlier called GZigZag)
309  project, whose goal was to implement Ted Nelson's ZigZag(tm) (trademark of Ted Nelson) structure  project, whose goal was to implement Ted Nelson's ZigZag(tm) (trademark of Ted Nelson) structure
310  in collaboration with him.  in collaboration with him.
# Line 376  Extensible storage frameworks Line 414  Extensible storage frameworks
414          - users can manipulate schema graphs          - users can manipulate schema graphs
415    
416      RDF, Semantic Web      RDF, Semantic Web
417    
418    Xanalogical permanent media structure
419    -------------------------------------
420    
421    Can be integrated into nearly any system
422    
423    NOT THE FULL XANADU(tm) FUNCTIONALITY
424    
425    Delivers significant benefits...
426    

Legend:
Removed from v.1.10  
changed lines
  Added in v.1.11

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26