/[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.102 by benja, Thu Sep 18 15:01:20 2003 UTC revision 1.103 by benja, Thu Sep 18 15:21:51 2003 UTC
# Line 178  have been the user who re-purposed them Line 178  have been the user who re-purposed them
178  view defaults for each task, providing quick access  view defaults for each task, providing quick access
179  to the functionality needed for this task.)  to the functionality needed for this task.)
180    
181    XXX create menus --> footnote saying that menus
182    are usually 'item' structures themselves
183    
184  Instead of forcing the user to think in applications,  Instead of forcing the user to think in applications,
185  such a system lends itself to be structured around  such a system lends itself to be structured around
186  the user's tasks. `Nelson (1999b)`_ uses the term  the user's tasks. `Nelson (1999b)`_ uses the term
# Line 186  An applitude is not "walled off" from th Line 189  An applitude is not "walled off" from th
189  system; when information from a different applitude  system; when information from a different applitude
190  is needed, it is always available.  is needed, it is always available.
191    
192    XXX applitudes *may* be constructed by a
193    programmer and delivered to customers; views
194    in that applitude can be repurposed into other
195    applitudes then (say this as note)
196    
197    XXX applitudes use loom buoys, so if you add
198    more loom buoys, they look like a seamless part
199    of the applitude. (as note?)
200    example: connect "population" information to the
201    places on the historian's map
202    
203  Items are **not owned  Items are **not owned
204  by any single applitude**: When you need to connect  by any single applitude**: When you need to connect
205  information to an item that doesn't fit into the  information to an item that doesn't fit into the
# Line 215  Hyperstructure may be implemented in man Line 229  Hyperstructure may be implemented in man
229  we present zzstructure and RDF, two hyperstructures actually used  we present zzstructure and RDF, two hyperstructures actually used
230  in systems aiming at the goals we have described above [#databases-as-hyperstructure]_.  in systems aiming at the goals we have described above [#databases-as-hyperstructure]_.
231    
232  XXX  XXX using hyperstructure for internal data
233    XXX thus, explorability
234    
235  We use the term hyperstructure to **denote** a **storage model**  We use the term hyperstructure to **denote** a **storage model**
236  that allows different data structures to overlap, but to  that allows different data structures to overlap, but to

Legend:
Removed from v.1.102  
changed lines
  Added in v.1.103

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