34 |
Prospect |
Prospect |
35 |
-------- |
-------- |
36 |
|
|
37 |
Making applications in the desktop/PDA interoperate with RDF |
* Making applications in the desktop/PDA interoperate with RDF |
38 |
|
|
39 |
Handling inferences and composite graphs with our tools |
* Handling inferences and composite graphs with our tools |
40 |
|
|
41 |
|
* Downloading remote web resources, combining them with personal data, |
42 |
|
visualizing them as buoys in application tools. |
43 |
|
|
44 |
|
All applications store data in a shared, combined RDF |
45 |
|
graph. Applications are implemented as *views* of this graph and |
46 |
|
*actions* that can be executed on it. When a view shows information |
47 |
|
about a resource, a view manager will show next to it in the margin |
48 |
|
other views that show different information about the same resource. |
49 |
|
|
50 |
|
Fenfire is a Model-View-Controller architecture where all applications |
51 |
|
share a single RDF graph used as the model. |
52 |
|
|
53 |
|
Semantic Web data can be downloaded and shown as part of this |
54 |
|
graph. Applications will then take it into account when building their |
55 |
|
views. For example, a calendaring application could show information |
56 |
|
about a colleague's appointments, downloaded from the Web. |
57 |
|
|
58 |
|
(exporting parts of our graph?) Personal RDF data from the graph can |
59 |
|
also be shared by publishing it on the Web. |
60 |
|
|
61 |
|
This approach could be used to integrate applications in a Personal |
62 |
|
Digital Assistant environment ("use the term PDA, which is more |
63 |
|
familiar to people" -- reviewer 3). |
64 |
|
|
65 |
|
|
66 |
|
|
67 |
|
Fenfire: Using Semantic Web technologies to integrate desktop |
68 |
|
applications |
69 |
|
|
70 |
|
We describe Fenfire, a desktop environment under development which |
71 |
|
allows applications to interpolate through RDF. |
72 |
|
|
73 |
|
We describe a desktop environment allowing applications to |
74 |
|
interoperate through Semantic Web technologies. In our approach, all |
75 |
|
applications store data in a shared RDF graph, providing different |
76 |
|
*views* on this data. This allows applications to annotate resources |
77 |
|
originally used in different applications. |
78 |
|
|
79 |
|
We describe a desktop environment where applications interoperate |
80 |
|
by storing data in a shared RDF graph. For example, a scheduling and a |
81 |
|
genealogy application could interoperate by describing persons in |
82 |
|
overlapping ways-- they would both store a person's birthday. |
83 |
|
|
84 |
|
-- |
85 |
|
|
86 |
|
We describe the design of a desktop environment in which applications blend by |
87 |
|
storing data in a shared RDF graph. For example, a calendar and a |
88 |
|
genealogy application could share data about a person's birthday. |
89 |
|
We use a Model-View-Controller (MVC) architecture in which the shared |
90 |
|
RDF graph acts as the model. Applications provide *views* of the RDF data; |
91 |
|
in the margins around the main view, a *view manager* shows other |
92 |
|
applications' views of related information. Selecting a view in the margin |
93 |
|
animates it to the center, making it the main view. |
94 |
|
|
95 |
|
Data retrieved from the Semantic Web can be seamlessly integrated into |
96 |
|
the user's personal data by merging it with the shared RDF graph; e.g., |
97 |
|
one's friends' appointments could be retrieved by a query and |
98 |
|
shown alongside with one's own appointments. Semantic |
99 |
|
interoperability achieved by ontologies and inference may be used to |
100 |
|
allow independently developed applications to share data. |
101 |
|
|
102 |
|
Fenfire is currently under development as Free Software. At the |
103 |
|
moment, we have partial prototypes and are in the process of |
104 |
|
integrating them. |
105 |
|
|
106 |
|
-- |
107 |
|
|
|
Downloading remote web resources, combining them with personal data, |
|
|
visualizing them as buoys in application tools. |
|
108 |
|
|
109 |
Waffle |
Waffle |
110 |
------ |
------ |