/[fenfire]/journals/plans/SA_2003.rst
ViewVC logotype

Diff of /journals/plans/SA_2003.rst

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

revision 1.97 by tjl, Tue May 13 15:32:49 2003 UTC revision 1.98 by tjl, Tue May 13 15:44:16 2003 UTC
# Line 67  environment. Line 67  environment.
67  The work leading to the current Fenfire project (formerly known as GZigZag and Gzz)  The work leading to the current Fenfire project (formerly known as GZigZag and Gzz)
68  was started in 1999.  was started in 1999.
69    
70    Fenfire consists of three components:
71    
72  Our system uses xanalogical storage model [ted-xu-model]_ as a  Hyperstructured data model
73  basis for hyperstructured media. Xanalogical storage keeps an index of      ... RDF + Xu
74  transclusions: identical characters copied into different documents.  
75  Through this mechanism, the system can show to the user all documents  Novel focus+context user interfaces
76  that share text with the current document.  In the xanalogical storage model,      The bidirectionally linked hyperstructural approach to information opens new
77  links are not between documents, but individual characters. For example, in the      possibilities to user interfaces.
78  World Wide Web links are between documents, while in the xanalogical storage model      The user can connect any two items which
79  links are between individual characters. Each character has a      will then be near each other in hyperspace, easily visible and
80  permanent, globally unique identifier. A xanalogical link is shown between      accessible from one to the other.
81  any two documents containing the characters that the link connects. Xanalogical links  
82  are external and bidirectional.  P2P information sharing
83        To support data mobility, we have developed a software library, named as Storm
84  The bidirectionally linked hyperstructural approach to information opens new      (STORage Module), for storing and retrieving data as immutable byte sequences, which
85  possibilities to user interfaces.      are identified by cryptographic content hashes. With Storm, we plan to use globally
86  The user can connect any two items which      unique, semantic-free references for locating data in Peer-to-Peer environment.
87  will then be near each other in hyperspace, easily visible and      Location-independent identifiers allows a peer-to-peer lookup system find documents
88  accessible from one to the other.      wherever they are moved. We believe that the properties of Peer-to-Peer technology,
89        such as the ad hoc connectivity and the lack of central authority, are prerequisites
90  We study how location-independent identifiers can      while mobilizing our system. Additionally, Storm allows us to study two important
91  support *data mobility*. For instance, documents are often transferred quite freely      issues *of data mobility*: dangling links and version management.
92  between computers: they are sent as e-mail attachments, carried around on disks and      We study how location-independent identifiers can
93  published on the web. We use 'data mobility' as a collective      support *data mobility*. For instance, documents are often transferred quite freely
94  term for the movement of documents between computers (or folders!),      between computers: they are sent as e-mail attachments, carried around on disks and
95  and movement of content between documents (through copy&paste).      published on the web. We use 'data mobility' as a collective
96        term for the movement of documents between computers (or folders!),
97  To support data mobility, we have developed a software library, named as Storm      and movement of content between documents (through copy&paste).
 (STORage Module), for storing and retrieving data as immutable byte sequences, which  
 are identified by cryptographic content hashes. With Storm, we plan to use globally  
 unique, semantic-free references for locating data in Peer-to-Peer environment.  
 Location-independent identifiers allows a peer-to-peer lookup system find documents  
 wherever they are moved. We believe that the properties of Peer-to-Peer technology,  
 such as the ad hoc connectivity and the lack of central authority, are prerequisites  
 while mobilizing our system. Additionally, Storm allows us to study two important  
 issues *of data mobility*: dangling links and version management.  
98    
 In several hypertext systems today, following a link means a *disruptive* change  
 in the user's workflow, replacing the current context (e.g., a Web page) with an  
 entirely different one.  
 This is partly caused by the dominant graphical user interface paradigm  
 (developed in the 70s at Xerox PARC; see, e.g., [kay93smalltalk]_) in which *pages*  
 are shown in overlapping, rectangular, unconnected viewports (windows).  
 In this paradigm, following a link can only create a new window  
 or replace the contents of the current window.  
 In our opinion, this is one of the root causes  
 of hypertext disorientation  
 [edwards-hardman89lost-in-hyperspace]_  
 [conklin87hypertext-onpage-38-40]_.  
99    
 Improving user orientation through user interface improvements has  
 recently received much attention. There have been much work  
 on providing more context of the link destination or making  
 the transition less abrupt [zellweger98fluid-andalso-fc-zooming-andalso-schilit98digital]_.  
 However, the underlying one-directionally linked hyperstructure of  
 the Web and many other hypermedia systems can also cause disorientation.  
100    
101    
102    
# Line 275  are shown in overlapping, rectangular, u Line 250  are shown in overlapping, rectangular, u
250  In this paradigm, following a link can only create a new window  In this paradigm, following a link can only create a new window
251  or replace the contents of the current window.  or replace the contents of the current window.
252  In our opinion, this is one of the root causes of hypertext disorientation.  In our opinion, this is one of the root causes of hypertext disorientation.
253    [edwards-hardman89lost-in-hyperspace]_
254    [conklin87hypertext-onpage-38-40]_.
255    
256    Improving user orientation through user interface improvements has
257    recently received much attention. There have been much work
258    on providing more context of the link destination or making
259    the transition less abrupt [zellweger98fluid-andalso-fc-zooming-andalso-schilit98digital]_.
260    However, the underlying one-directionally linked hyperstructure of
261    the Web and many other hypermedia systems can also cause disorientation.
262    
263  Geometry  Geometry
264  ''''''''  ''''''''

Legend:
Removed from v.1.97  
changed lines
  Added in v.1.98

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