10 |
Agora Center, University of Jyväskylä |
Agora Center, University of Jyväskylä |
11 |
P.O.Box 35, FIN-40014 Jyväskylä, Finland |
P.O.Box 35, FIN-40014 Jyväskylä, Finland |
12 |
E-mail: b.fallenstein@gmx.de, lukka@iki.fi |
E-mail: b.fallenstein@gmx.de, lukka@iki.fi |
13 |
|
Key features: `References`_; Figures XXX |
14 |
|
|
15 |
|
|
|
Contents |
|
|
======== |
|
|
|
|
16 |
.. contents:: |
.. contents:: |
17 |
|
|
18 |
|
|
28 |
theories of cognition - we're speaking of the mind |
theories of cognition - we're speaking of the mind |
29 |
|
|
30 |
|
|
31 |
Introduction |
1 Introduction |
32 |
============ |
============== |
33 |
|
|
34 |
Computers are supposed to be "information technology," |
Computers are supposed to be "information technology," |
35 |
to help you to keep your information organized. |
to help you to keep your information organized. |
103 |
|
|
104 |
|
|
105 |
|
|
106 |
The user interface / user experience |
2 The user interface / user experience |
107 |
==================================== |
====================================== |
108 |
|
|
109 |
(XXX better section title) |
(XXX better section title) |
110 |
|
|
220 |
help us to **organize our thoughts**. |
help us to **organize our thoughts**. |
221 |
|
|
222 |
|
|
223 |
Under the hood: Hyperstructure |
3 Under the hood: Hyperstructure |
224 |
============================== |
================================ |
225 |
|
|
226 |
At the bottom of an item-centered computing environment, |
At the bottom of an item-centered computing environment, |
227 |
is the *network of items*. This network is a **hyperstructure**, |
is the *network of items*. This network is a **hyperstructure**, |
244 |
|
|
245 |
Hyperstructure may be implemented in many ways. |
Hyperstructure may be implemented in many ways. |
246 |
In the remainder of this section, |
In the remainder of this section, |
247 |
we present zzstructure and RDF, two hyperstructures actually used |
we present zzstructure and RDF [#zzstructure-rdf]_, |
248 |
|
two hyperstructures actually used |
249 |
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]_. |
250 |
|
|
251 |
|
|
252 |
|
|
253 |
Zzstructure (used in ZigZag(TM)) |
3.1 Zzstructure (used in ZigZag(TM)) |
254 |
-------------------------------- |
------------------------------------ |
255 |
|
|
256 |
Ted Nelson's original |
Ted Nelson's original |
257 |
hyperstructure and applitude concepts |
hyperstructure and applitude concepts |
280 |
|
|
281 |
|
|
282 |
|
|
283 |
Resource Description Framework (RDF, used in Fenfire) |
3.2 Resource Description Framework (RDF, used in Fenfire) |
284 |
----------------------------------------------------- |
--------------------------------------------------------- |
285 |
|
|
286 |
The RDF structure (`Lassila and Swick 1999`_) is, for our purposes, |
The RDF structure (`Lassila and Swick 1999`_) is, for our purposes, |
287 |
a 3-hypergraph. By interpreting the hyperedge components |
a 3-hypergraph. By interpreting the hyperedge components |
292 |
|
|
293 |
|
|
294 |
|
|
295 |
The Fenfire project |
4 The Fenfire project |
296 |
=================== |
===================== |
297 |
|
|
298 |
Fenfire is a free software project aiming at implementing |
Fenfire is a free software project aiming at implementing |
299 |
the applitude-oriented user interface concepts on top of an RDF graph. |
the applitude-oriented user interface concepts on top of an RDF graph. |
327 |
flexible definition of applitudes |
flexible definition of applitudes |
328 |
|
|
329 |
|
|
330 |
Views |
4.1 Views |
331 |
----- |
--------- |
332 |
|
|
333 |
- Loom structure views, particularly wheel |
- Loom structure views, particularly wheel |
334 |
|
|
365 |
__ buoysMotion.png |
__ buoysMotion.png |
366 |
|
|
367 |
|
|
368 |
Libvob |
4.2 Libvob |
369 |
------ |
---------- |
370 |
|
|
371 |
Libvob is a subproject of Fenfire, providing a flexible user-interface |
Libvob is a subproject of Fenfire, providing a flexible user-interface |
372 |
toolkit with some novel features that allow the independent |
toolkit with some novel features that allow the independent |
395 |
a generated vobscene and adds buoys to the nodes in it - regardless |
a generated vobscene and adds buoys to the nodes in it - regardless |
396 |
of who placed those nodes in there. |
of who placed those nodes in there. |
397 |
|
|
398 |
An example applitude combining multiple structures: FenPDF |
4.3 An example applitude combining multiple structures: FenPDF |
399 |
---------------------------------------------------------- |
-------------------------------------------------------------- |
400 |
|
|
401 |
FenPDF is the first concrete prototype of our architecture. |
FenPDF is the first concrete prototype of our architecture. |
402 |
It is a tool to make sense of academic literature. |
It is a tool to make sense of academic literature. |
443 |
Explicit support for taxonomical hypertext (`Parunak 1991`_) |
Explicit support for taxonomical hypertext (`Parunak 1991`_) |
444 |
and hierarchies is currently being planned. |
and hierarchies is currently being planned. |
445 |
|
|
446 |
Related work |
5 Related work |
447 |
============ |
============== |
448 |
|
|
449 |
|
|
450 |
The system we are proposing is a logical extension |
The system we are proposing is a logical extension |
454 |
as introduced by `DeRose (1989)`_ is an important concept |
as introduced by `DeRose (1989)`_ is an important concept |
455 |
in this context. |
in this context. |
456 |
|
|
457 |
Flexible structure - Unifying structured and unstructured information |
5.1 Flexible structure - Unifying structured and unstructured information |
458 |
--------------------------------------------------------------------- |
------------------------------------------------------------------------- |
459 |
|
|
460 |
The Aquanet system, introduced by `Marshall et al (1991)`_, |
The Aquanet system, introduced by `Marshall et al (1991)`_, |
461 |
unified ideas from the freely structured hypertext systems |
unified ideas from the freely structured hypertext systems |
496 |
than the types of the items themselves. |
than the types of the items themselves. |
497 |
|
|
498 |
|
|
499 |
Structural computing |
5.2 Structural computing |
500 |
-------------------- |
------------------------ |
501 |
|
|
502 |
The change of the computer system abstractions |
The change of the computer system abstractions |
503 |
in Hypermedia operating systems (`Nürnberg et al 1996`_) |
in Hypermedia operating systems (`Nürnberg et al 1996`_) |
505 |
are vital for an entirely item-based environment. XXX |
are vital for an entirely item-based environment. XXX |
506 |
|
|
507 |
|
|
508 |
RDF, Semantic Web |
5.3 RDF, Semantic Web |
509 |
----------------- |
--------------------- |
510 |
|
|
511 |
The Semantic Web [xxxref] community uses RDF to represent |
The Semantic Web [xxxref] community uses RDF to represent |
512 |
*machine-readable information*. Berners-Lee [xxxref] argues that |
*machine-readable information*. Berners-Lee [xxxref] argues that |
536 |
information into the vocabularies expected by either view. |
information into the vocabularies expected by either view. |
537 |
|
|
538 |
|
|
539 |
Open Hypermedia |
5.4 Open Hypermedia |
540 |
--------------- |
------------------- |
541 |
|
|
542 |
XXX Should we just not mention open hypermedia? |
XXX Should we just not mention open hypermedia? |
543 |
|
|
557 |
unified into a single conceptual structure. |
unified into a single conceptual structure. |
558 |
|
|
559 |
|
|
560 |
Fluid Links and Transpointing Windows |
5.5 Fluid Links and Transpointing Windows |
561 |
------------------------------------- |
----------------------------------------- |
562 |
|
|
563 |
Buoys are somewhat similar to fluid links (`Zellweger et al 1998`_) in |
Buoys are somewhat similar to fluid links (`Zellweger et al 1998`_) in |
564 |
that they show something of the link target. |
that they show something of the link target. |
568 |
Nelson (private communication) also claims that they are |
Nelson (private communication) also claims that they are |
569 |
an instance of transpointing windows ... XXX |
an instance of transpointing windows ... XXX |
570 |
|
|
571 |
Conclusions |
6 Conclusions |
572 |
=========== |
============= |
573 |
|
|
574 |
Novel - things originating at our group: |
Novel - things originating at our group: |
575 |
|
|
877 |
about them, in this case the idea about how to develop |
about them, in this case the idea about how to develop |
878 |
one of them. |
one of them. |
879 |
|
|
|
.. [#databases-as-hyperstructure] Hyperstructure might also be |
|
|
implemented, for example, as a relational database, |
|
|
with individual data structures being represented as tables. |
|
|
This would necessiate a system where users could add |
|
|
new tables at any time, without hazzle. |
|
|
|
|
880 |
.. [#zzstructure-rdf] RDF and zzStructure are actually closely |
.. [#zzstructure-rdf] RDF and zzStructure are actually closely |
881 |
related: zzStructure is obtained if a RDF graph is constrained |
related: zzStructure is obtained if a RDF graph is constrained |
882 |
by two uniqueness conditions: for all x, y, there can be |
by two uniqueness conditions: for all x, y, there can be |
883 |
at most one triple of the form (x, y, \*), and |
at most one triple of the form (x, y, \*), and |
884 |
at most one triple of the form (\*, x, y). |
at most one triple of the form (\*, x, y). |
885 |
|
|
886 |
|
.. [#databases-as-hyperstructure] Hyperstructure might also be |
887 |
|
implemented, for example, as a relational database, |
888 |
|
with individual data structures being represented as tables. |
889 |
|
This would necessiate a system where users could add |
890 |
|
new tables at any time, without hazzle. |
891 |
|
|
892 |
.. [#zzstructure] zzStructure is the "generic term" Nelson |
.. [#zzstructure] zzStructure is the "generic term" Nelson |
893 |
recommends for discussing the structure used in ZigZag(TM), |
recommends for discussing the structure used in ZigZag(TM), |
894 |
(Nelson's trademark). |
(Nelson's trademark). |