46 |
Introduction |
Introduction |
47 |
============ |
============ |
48 |
|
|
49 |
|
[tjl] XXX: the idea that the global graph can be constructed |
50 |
|
using semantic interoperability is not apparent here! *NEEDS* |
51 |
|
to be. Otherwise, referee: "Yes, great, but what does it have |
52 |
|
to do with SemWeb?" |
53 |
|
|
54 |
Assume that a user needs to coordinate the activities of her |
Assume that a user needs to coordinate the activities of her |
55 |
workgroup. She has at her disposal applications for email, |
workgroup. She has at her disposal applications for email, |
56 |
project planning, scheduling appointments with her colleagues, |
project planning, scheduling appointments with her colleagues, |
57 |
keeping track of unresolved issues, creating presentations, |
keeping track of unresolved issues, creating presentations, |
58 |
text documents, and spreadsheets. |
text documents, and spreadsheets. |
59 |
|
|
60 |
In a traitional desktop system, she will keep track of the |
In a conventional desktop system, she will keep track of the |
61 |
project's goals in one application, write them up as a |
project's goals in one application, write them up as a |
62 |
presentation in another, schedule the presentation in a |
presentation in another, schedule the presentation in a |
63 |
third application, and write the agenda in a fourth. If the |
third application, and write the agenda in a fourth. If the |
68 |
her computer, it will be scattered across different files. |
her computer, it will be scattered across different files. |
69 |
|
|
70 |
In this article, we describe the design of Fenfire, |
In this article, we describe the design of Fenfire, |
71 |
a desktop environment allowing applications like these |
a desktop environment and framework allowing applications like these |
72 |
to be integrated into a seamless whole. |
to be integrated into a seamless whole. |
73 |
|
|
74 |
In Fenfire, all of the above applications would store |
In Fenfire, all of the above applications would store |
96 |
email application (XXX figure of simplified graph). |
email application (XXX figure of simplified graph). |
97 |
|
|
98 |
The desktop environment would make these connections visible. |
The desktop environment would make these connections visible. |
99 |
Whenever an email raising a comment is shown |
Whenever an email raising an issue is shown |
100 |
by the email application, Fenfire would show |
by the email application, Fenfire would show |
101 |
issues raised by it floating in a margin (XXX figure n-a)), |
issues raised by it floating in a margin (XXX figure n-a)), |
102 |
rendered by the issue tracking application. |
rendered by the issue tracking application. |
103 |
When clicking on an issue, it would become |
When clicking on an issue, it would become |
104 |
the main view, as when following an HTML link |
the main view, as when following an HTML link |
105 |
(XXX figure n-c)). The email would become a marginal note |
(XXX figure n-c XXX *except* non-disruptively)). |
106 |
|
The email would become a marginal note |
107 |
or *buoy* connected to the issue. |
or *buoy* connected to the issue. |
108 |
|
|
109 |
.. The figure above should have three parts: |
.. The figure above should have three parts: |