[Gzz-commits] gzz/Documentation/Manuscripts Paper/paper.tex U...

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Tuomas J. Lukka <address@hidden>        02/11/25 06:05:21

Modified files:
        Documentation/Manuscripts/Paper: paper.tex 
        Documentation/Manuscripts/URN5: urn5.rst 

Log message:
        Editing

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/Documentation/Manuscripts/Paper/paper.tex.diff?tr1=1.65&tr2=1.66&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/Documentation/Manuscripts/URN5/urn5.rst.diff?tr1=1.3&tr2=1.4&r1=text&r2=text

Patches:
Index: gzz/Documentation/Manuscripts/Paper/paper.tex
diff -u gzz/Documentation/Manuscripts/Paper/paper.tex:1.65 
gzz/Documentation/Manuscripts/Paper/paper.tex:1.66
--- gzz/Documentation/Manuscripts/Paper/paper.tex:1.65  Sat Nov 23 15:42:35 2002
+++ gzz/Documentation/Manuscripts/Paper/paper.tex       Mon Nov 25 06:05:21 2002
@@ -34,14 +34,15 @@
 \maketitle
 
 % XXX Mention that these are something like marbled paper
-
 % XXX Ref to xstarfish!
+% XXX icons
 
 \begin{abstract}
 We introduce unique backgrounds: procedurally generated background textures 
based on  
 the identity of the document or data item.
-for assisting user orientation
-in navigating hyperstructures using Focus+Context views.
+Unique backgrounds could be useful for assisting user orientation
+in several different user interfaces; our primary application
+is navigating hyperstructures using Focus+Context views.
 %
 %We can rapidly generate a texture for any document the user visits, 
 %and the user will be able to learn the textures of the 
@@ -56,16 +57,17 @@
 the texture should produce a random feature vector on the cortex
 {\bf after} visual feature extraction. 
 
-We have designed a hardware-accelerated implementation on the NV10 and NV20
-of unique backgrounds.
-The implementation works by combining a small set of basis textures
-and perceptually chosen colors
-on the GPU.
-% XXX: perceptually?
-
-We show an example user interface for browsing linked PDF documents
+We discuss our freely available hardware-accelerated implementation 
+of unique backgrounds
+on the NV10 and NV20, and
+show an example user interface for browsing linked PDF documents
 in a focus+context view using unique backgrounds.
 
+% The implementation works by combining a small set of basis textures
+% and perceptually chosen colors
+% on the GPU.
+% XXX: perceptually?
+
 % READABILITY
 
 % - saving bits
@@ -86,28 +88,29 @@
 data identity as a navigation aid in focus+context views.
 Because the topic is related to three different research areas,
 we have split this introduction to three subsections.
+In the following section, we introduce unique backgrounds 
 
 \subsection{Focus+Context views}
 
 Focus+Context, or, fisheye views\cite{fc-fisheye} are 
 a paradigm for viewing large, 
 structured information sets 
-which has gained popularity in the research community\cite{XXX} 
-but less so in production systems.
-
-The current area of 
-interest (focus) is shown magnified, 
+by showing the current area of 
+interest (focus) magnified
 and the structurally connected but further-away 
-elements with are shown peripherally, with less magnification.
+elements peripherally, with less magnification.
+
+% which has gained popularity in the research community\cite{XXX} 
+% but less so in production systems.
 
 We distinguish two basic modes of application:
 \begin{enumerate}
 \item exploring data that the user
-has not seen before.  The research questions asked are, for example, 
-how fast the user can find a particular node in an unknown
-information hierarchy\cite{pirolli01informationscent,XXX}.
-\item everyday use of the user's own, familiar data.
-This use is seen for example in \cite{mackinlay91perspectivewall}.
+has not seen before\cite{pirolli01informationscent,XXX}.  
+%The research questions asked are, for example, 
+%how fast the user can find a particular node in an unknown
+%information hierarchy\cite{pirolli01informationscent,XXX}.
+\item everyday use of the user's own, familiar 
data\cite{mackinlay91perspectivewall}.
 \end{enumerate}
 
 In this article, we focus on the latter application, and on
@@ -131,40 +134,51 @@
 % uniq.textures really help only on systems that do this part right. 
 
 The identity of data is an important concept which 
-most current computer systems have not been programmed to handle properly. 
+most current computer systems have not been programmed to handle properly,
+and is usually not visualized at all: icons are used to represent different
+file {\em types}, instead of the identities of the actual files.
 
 % The concept of ``file'', which was developed early in the history
 % of computers has become so pervasive that...
 
 For instance, consider a published scientific article
 available through several different URLs on the WWW,
-e.g.~both through citeseer\cite{XXX} and the ACM portal. 
-Now, when a user downloads one copy, the relationship between
+e.g.~both through CiteSeer\cite{XXX}, the ACM portal and
+the author's web site. 
+Now, when a user downloads and saves one copy, the relationship between
 the local copy and the original on the WWW is severed, so 
-in the computer's opinion there are essentially three different articles.
+in the computer's opinion there are now {\em four} different entities,
+whereas the user thinks of them as the same article.
 
 When following another link to the same article at a different
 server, the computer has no idea that the article has already been downloaded
-(from another server) by the user, and that the user has linked to that version
-of the article in her own work.
-The burden of matching the identities is left entirely on the shoulders of the 
user.
-The user has to notice that this is a familiar article and search for her 
other references
-to it on the local disk, if desired.
+(from another server) by the user, 
+and that the user has annotated\cite{XXX} that version
+of the article.
+The burden of matching the identities and locating the local version, if 
desired, is on the user.
 
 In a system based on identities, all references to the article would be made 
through
 the same identifier. The computer {\em would} know that this is a familiar 
article
-and would also be able to show the user's other work related to the article
-in a focus+context view.
+and would also be able to show the user's annotations even in the above case;
+it would even be possible to show anyone else's published annotations and links
+to the article.
 
 Systems based on identities as opposed to files
-{\em do} exist: the Xanadu hypermedia 
model\cite{ted-xanalogical-structure-needed},
-the first implementation of which was recently published as Udanax\cite{XXX}, 
and the later Gzz
-project based on the same ideas\cite{lukka99cybertext,lukka02guids}.
+{\em do} exist, but mostly still only in research stage: 
+the Xanadu hypermedia model\cite{ted-xanalogical-structure-needed},
+the first implementation of which was recently published as Udanax\cite{XXX}, 
+and the later Gzz
+project based on the same ideas\cite{lukka02guids}.
 Also, on a more recent (Xanadu was began in the 1960s), but more established 
basis,
 URNs (Uniform Resource Names)\cite{rfc1737} are moving towards the same goal,
 and the recently opened informal URN-5 namespace\cite{fallenstein02urn5} being
 one example of a different direction of identity..
 
+
+OHS
+Other identity stuff!
+CiteSeer?
+
 % Different versions
 
 % The reason for this state of the matter is that
@@ -173,6 +187,14 @@
 % use the information to advantage; likewise, developing such interfaces
 % is next to useless without having the backend functionality.
 
+In this article, we introduce the use of procedurally generated unique 
backgrounds
+as a visualization of data identity: if each data item with a different 
identity has 
+a different, easily distinguishable texture, the user can become aware of the 
identity
+of a displayed item at a glance, without explicitly reading the title.
+Even more importantly, the user can become aware of the identity just by 
seeing 
+any {\em fragment} of the item, instead of the ``title page''.
+
+
 \subsection{Texturing}
 
 The word {\em texture}, taken literally, is the translation-invariant 
statistical microstructure of a surface.
@@ -180,12 +202,12 @@
 the word {\em texturing} is used in a somewhat looser 
sense\cite{catmull74,heckbert86survey}:
 it refers to mapping 2D arrays of numerical values onto graphics primitives
 such as polygons or Bezi\'er patches, modifying their rendered appearance 
-in some way (coloring\cite{catmull74}, bump mapping\cite{blinn78bump} etc)..
+in some way (coloring\cite{catmull74}, bump mapping\cite{blinn78bump} etc.).
 
 Due to the price of texturing-capable hardware, most uses of texturing until 
the mid-1990s were
 in scientific visualization and the computer graphics industry.
 During the last decade, computer games helped to drive the price of suitable
-3D accelerators down, making them standard in modern computers.
+3D accelerators down, making them standard in modern desktop computers.
 However, texturing has still found relatively little use outside the three 
fields
 mentioned above.
 
@@ -215,7 +237,8 @@
 
 It is easy to become disoriented and lost in an environment where different 
locations
 are very similar
-(example: adventure game ``you are in a maze of twisty little passages, all 
alike'')
+(example: adventure game ``you are in a maze of twisty little passages, all 
alike'' XXX
+which game?!)
 
 Features orthogonal to human perception (e.g.~color, direction of fastest 
luminance change)
 should be independently random, and features not orthogonal (e.g. colors of 
neighbouring
@@ -658,8 +681,11 @@
 strongly on the text scale; making it easy for the user to zoom
 fluidly in and out helps.
 
+So far, we have concentrated mostly on low-end hardware, and
+have not even tapped the full potential of the NV20 and NV25 chips.
+
 We are currently working on implementing
-similar algorithms on ATI hardware, due to their release
+similar algorithms on ATI hardware, due to their recent release
 of a Linux driver.
 The new graphics chips, ATI R300 and NVIDIA NV30 support
 a great deal more of procedural texturing and it will
Index: gzz/Documentation/Manuscripts/URN5/urn5.rst
diff -u gzz/Documentation/Manuscripts/URN5/urn5.rst:1.3 
gzz/Documentation/Manuscripts/URN5/urn5.rst:1.4
--- gzz/Documentation/Manuscripts/URN5/urn5.rst:1.3     Sun Nov 17 15:56:37 2002
+++ gzz/Documentation/Manuscripts/URN5/urn5.rst Mon Nov 25 06:05:21 2002
@@ -36,7 +36,7 @@
 - Digital signatures
 - freenet IDs
 - URN
-
+- OID!!
 
 
 URN namespaces