/[gzz]/manuscripts/FutureVision/oplan.txt
ViewVC logotype

Diff of /manuscripts/FutureVision/oplan.txt

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

revision 1.20 by benja, Thu Nov 13 17:44:19 2003 UTC revision 1.21 by benja, Thu Nov 13 18:29:20 2003 UTC
# Line 441  REFERENCES: Line 441  REFERENCES:
441  4.4 FenPDF  4.4 FenPDF
442  ----------  ----------
443    
444    Beginning:
445    
446        FenPDF is the first concrete prototype of our architecture,
447        using buoys, Libvob, RDF, and Xanalogical structure.
448        It is a tool for making sense of academic literature.
449    
450    After figure:
451    
452        FenPDF is used to structure a set of articles
453        in PostScript or PDF format. Users can transclude
454        pieces of articles onto *spatial canvases*: infinite,
455        scrollable papers.
456        Transclusions are automatically bidirectionally connected
457        to the article they are from; a buoy shows a shrunk version
458        of the article, and clicking on the buoy brings the article
459        to the center for the user to read.
460    
461        Additionally, the user can type text onto the canvases,
462        and link two pieces of text on different canvases
463        (linked canvases are shown as buoys).
464    
465        In the figure, there are two foci.
466        The **upper focus** shows **a PDF article**
467        and its buoys there show the places of
468        canvases on which there are transclusions from the article.
469        The **lower focus** shows a **spatial canvas**, containing
470        **transclusions of PDF articles**,
471        and the buoys show
472        other canvases navigationally linked to the canvas, and
473        source articles for transclusions.
474    
475        The canvases and papers use unique backgrounds
476        (`Kujala and Lukka 2003`_) to endow them *identity*
477        in the eyes of the viewer.
478    
479        We use FenPDF collaboratively in our research group
480        (synchronizing the RDF graph through CVS).
481        In practice, we have:
482    
483        - A canvas for each source (for example, conference,
484          journal issue), with transclusions of the titles
485          and author lists of the articles published there.
486        - Canvases for different topics, such as open hypermedia,
487          spatial hypertext, and so on. These canvases
488          contain transclusions of particularly relevant parts
489          of articles, allowing us to collect the central ideas
490          from several different articles.
491        - Canvases for each article we are working on,
492          containing notes and transclusions from important
493          references.
494        - Canvases for communicating specific ideas. These
495          contain Memex-like "trails" of transclusions from
496          different articles, intersersed with text discussing these.
497        - A central canvas that has links to the other canvases.
498    
499        In FenPDF, articles, spatial canvases, transclusions
500        of an article and pieces of text on a canvas are all
501        represented by RDF nodes.
502        On the structure side, FenPDF uses four small RDF vocabularies:
503    
504        [the vocabs]
505    
506        The implementation [...] Unlike in most [...] any kinds
507        of structure.
508    
509        Explicit support for taxonomic hypertext (`Parunak 1991`_)
510        and hierarchies is currently being planned.
511    
512        FenPDF will first [...] into Fenfire.
513    
514        Let us briefly explore how a user could extend
515        this applitude using the techniques presented in
516        `Section 2`_.
517    
518        First, metadata about articles, such as author
519        and publication date, could be represented through simple
520        RDF connections. Using our RDF views, one could then
521        for example browse the list of articles of one particular author,
522        sorted by date.
523    
524        Similarly, we would probably replace the canvases
525        categorizing articles by source with RDF metadata,
526        and browse the articles from one source sorted
527        by e.g. author or date.
528    
529        XXXY
530        
531    
532  [31] FenPDF as an applitude: describe how it could  [31] FenPDF as an applitude: describe how it could
533  integrate with the network of items (this is then  integrate with the network of items (this is then
534  an example of a non-itemgular structure being  an example of a non-itemgular structure being

Legend:
Removed from v.1.20  
changed lines
  Added in v.1.21

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