/[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.70 by tjl, Thu Sep 18 11:22:24 2003 UTC revision 1.71 by benja, Thu Sep 18 11:22:58 2003 UTC
# Line 176  for **personal use - working/editing/aut Line 176  for **personal use - working/editing/aut
176    
177    
178    
179    With Nelson [XXXfw], we propose a user interface based
180    not on monolithic applications, but on *applitudes*:
181    
182  - user-interface -level co-operation by independently written applitudes  - user-interface -level co-operation by independently written applitudes
183    
184    - different applitudes add orthogonal behaviours and properties to items    - different applitudes add orthogonal behaviours and properties to items
# Line 392  in Hypermedia operating systems (Nürnber Line 395  in Hypermedia operating systems (Nürnber
395  and the subsequent structural computing framework (Nürnberg et al 1997)  and the subsequent structural computing framework (Nürnberg et al 1997)
396  are vital for an entirely item-based environment. XXX  are vital for an entirely item-based environment. XXX
397    
398            
399  RDF, Semantic Web  RDF, Semantic Web
400  -----------------  -----------------
401    
402  Our approach is different because ...  The Semantic Web [xxxref] community uses RDF to represent
403    *machine-readable information*. Berners-Lee [xxxref] argues that
404    the World Wide Web has been successful in integrating
405    human-readable documents, but a similar approach is needed
406    for machine-readable data.
407    
408    While we emphasize the use of an RDF hyperstructure
409    by a *human* user, much of the information a user
410    stores in Fenfire would be useful data from a Semantic Web
411    point of view. For example, a calendar created with
412    Fenfire might be published on the Web, allowing Semantic Web
413    tools to alert users in the case of conflicting appointments
414    in a working group.
415    
416    The other way around, information on the Semantic Web
417    can easily be shown inside Fenfire. For example, we might
418    show which doctors are available in our city, if the
419    local Yellow Pages publish this data as RDF on the Web.
420    
421    The Semantic Web community is building tools to automatically
422    convert data between different languages built on top of RDF
423    [xxxreftbl]. Such tools could be of great use in Fenfire;
424    for example, when using two views written by different programmers,
425    which show the same kind of information but assume different
426    RDF vocabularies, a data conversion tool could convert the
427    information into the vocabularies expected by either view.
428    
429    
430  Open Hypermedia  Open Hypermedia
431  ---------------  ---------------

Legend:
Removed from v.1.70  
changed lines
  Added in v.1.71

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