[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gzz-commits] manuscripts/FutureVision oplan.txt
From: |
Benja Fallenstein |
Subject: |
[Gzz-commits] manuscripts/FutureVision oplan.txt |
Date: |
Thu, 13 Nov 2003 13:29:21 -0500 |
CVSROOT: /cvsroot/gzz
Module name: manuscripts
Branch:
Changes by: Benja Fallenstein <address@hidden> 03/11/13 13:29:20
Modified files:
FutureVision : oplan.txt
Log message:
fenpdf
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/FutureVision/oplan.txt.diff?tr1=1.20&tr2=1.21&r1=text&r2=text
Patches:
Index: manuscripts/FutureVision/oplan.txt
diff -u manuscripts/FutureVision/oplan.txt:1.20
manuscripts/FutureVision/oplan.txt:1.21
--- manuscripts/FutureVision/oplan.txt:1.20 Thu Nov 13 12:44:19 2003
+++ manuscripts/FutureVision/oplan.txt Thu Nov 13 13:29:20 2003
@@ -441,6 +441,94 @@
4.4 FenPDF
----------
+Beginning:
+
+ FenPDF is the first concrete prototype of our architecture,
+ using buoys, Libvob, RDF, and Xanalogical structure.
+ It is a tool for making sense of academic literature.
+
+After figure:
+
+ FenPDF is used to structure a set of articles
+ in PostScript or PDF format. Users can transclude
+ pieces of articles onto *spatial canvases*: infinite,
+ scrollable papers.
+ Transclusions are automatically bidirectionally connected
+ to the article they are from; a buoy shows a shrunk version
+ of the article, and clicking on the buoy brings the article
+ to the center for the user to read.
+
+ Additionally, the user can type text onto the canvases,
+ and link two pieces of text on different canvases
+ (linked canvases are shown as buoys).
+
+ In the figure, there are two foci.
+ The **upper focus** shows **a PDF article**
+ and its buoys there show the places of
+ canvases on which there are transclusions from the article.
+ The **lower focus** shows a **spatial canvas**, containing
+ **transclusions of PDF articles**,
+ and the buoys show
+ other canvases navigationally linked to the canvas, and
+ source articles for transclusions.
+
+ The canvases and papers use unique backgrounds
+ (`Kujala and Lukka 2003`_) to endow them *identity*
+ in the eyes of the viewer.
+
+ We use FenPDF collaboratively in our research group
+ (synchronizing the RDF graph through CVS).
+ In practice, we have:
+
+ - A canvas for each source (for example, conference,
+ journal issue), with transclusions of the titles
+ and author lists of the articles published there.
+ - Canvases for different topics, such as open hypermedia,
+ spatial hypertext, and so on. These canvases
+ contain transclusions of particularly relevant parts
+ of articles, allowing us to collect the central ideas
+ from several different articles.
+ - Canvases for each article we are working on,
+ containing notes and transclusions from important
+ references.
+ - Canvases for communicating specific ideas. These
+ contain Memex-like "trails" of transclusions from
+ different articles, intersersed with text discussing these.
+ - A central canvas that has links to the other canvases.
+
+ In FenPDF, articles, spatial canvases, transclusions
+ of an article and pieces of text on a canvas are all
+ represented by RDF nodes.
+ On the structure side, FenPDF uses four small RDF vocabularies:
+
+ [the vocabs]
+
+ The implementation [...] Unlike in most [...] any kinds
+ of structure.
+
+ Explicit support for taxonomic hypertext (`Parunak 1991`_)
+ and hierarchies is currently being planned.
+
+ FenPDF will first [...] into Fenfire.
+
+ Let us briefly explore how a user could extend
+ this applitude using the techniques presented in
+ `Section 2`_.
+
+ First, metadata about articles, such as author
+ and publication date, could be represented through simple
+ RDF connections. Using our RDF views, one could then
+ for example browse the list of articles of one particular author,
+ sorted by date.
+
+ Similarly, we would probably replace the canvases
+ categorizing articles by source with RDF metadata,
+ and browse the articles from one source sorted
+ by e.g. author or date.
+
+ XXXY
+
+
[31] FenPDF as an applitude: describe how it could
integrate with the network of items (this is then
an example of a non-itemgular structure being
- [Gzz-commits] manuscripts/FutureVision oplan.txt, (continued)
- [Gzz-commits] manuscripts/FutureVision oplan.txt, Benja Fallenstein, 2003/11/13
- [Gzz-commits] manuscripts/FutureVision oplan.txt, Tuomas J. Lukka, 2003/11/13
- [Gzz-commits] manuscripts/FutureVision oplan.txt, Benja Fallenstein, 2003/11/13
- [Gzz-commits] manuscripts/FutureVision oplan.txt, Tuomas J. Lukka, 2003/11/13
- [Gzz-commits] manuscripts/FutureVision oplan.txt, Benja Fallenstein, 2003/11/13
- [Gzz-commits] manuscripts/FutureVision oplan.txt, Benja Fallenstein, 2003/11/13
- [Gzz-commits] manuscripts/FutureVision oplan.txt, Tuomas J. Lukka, 2003/11/13
- [Gzz-commits] manuscripts/FutureVision oplan.txt, Benja Fallenstein, 2003/11/13
- [Gzz-commits] manuscripts/FutureVision oplan.txt, Benja Fallenstein, 2003/11/13
- [Gzz-commits] manuscripts/FutureVision oplan.txt, Benja Fallenstein, 2003/11/13
- [Gzz-commits] manuscripts/FutureVision oplan.txt,
Benja Fallenstein <=
- [Gzz-commits] manuscripts/FutureVision oplan.txt, Tuomas J. Lukka, 2003/11/13
- [Gzz-commits] manuscripts/FutureVision oplan.txt, Benja Fallenstein, 2003/11/13
- [Gzz-commits] manuscripts/FutureVision oplan.txt, Tuomas J. Lukka, 2003/11/13
- [Gzz-commits] manuscripts/FutureVision oplan.txt, Tuomas J. Lukka, 2003/11/13
- [Gzz-commits] manuscripts/FutureVision oplan.txt, Tuomas J. Lukka, 2003/11/13
- [Gzz-commits] manuscripts/FutureVision oplan.txt, Tuomas J. Lukka, 2003/11/13
- [Gzz-commits] manuscripts/FutureVision oplan.txt, Tuomas J. Lukka, 2003/11/13
- [Gzz-commits] manuscripts/FutureVision oplan.txt, Tuomas J. Lukka, 2003/11/13
- [Gzz-commits] manuscripts/FutureVision oplan.txt, Benja Fallenstein, 2003/11/13
- [Gzz-commits] manuscripts/FutureVision oplan.txt, Tuomas J. Lukka, 2003/11/13