12 |
Relationship between item-based and files: |
Relationship between item-based and files: |
13 |
|
|
14 |
Computers should help us with **organizing our lives**, rather |
Computers should help us with **organizing our lives**, rather |
15 |
than making them more difficult. We need |
than making them more difficult. We conjecture that we need |
16 |
a system **structured** around **items** -- |
a system **structured** around **items** -- |
17 |
**things that we care about**, such as people, arguments and ideas, |
**things that we care about**, such as people, arguments and ideas, |
18 |
and able to express the relationships between them, |
and able to express the relationships between them, |
259 |
object)* triples, where each triple is an edge between the |
object)* triples, where each triple is an edge between the |
260 |
subject and the object and with the predicate as its label. |
subject and the object and with the predicate as its label. |
261 |
|
|
262 |
|
When discussing RDF, URIs are often abbreviated, |
263 |
|
for example ``foaf:Person`` for ``http://xmlns.com/foaf/0.1/Person``. |
264 |
|
|
265 |
While the zzstructure is simple to browse locally, |
While the zzstructure is simple to browse locally, |
266 |
because it has higher-level (user-centred) semantics, |
because it has higher-level (user-centred) semantics, |
267 |
programming is often easier in RDF, because many-to-many |
programming is often easier in RDF, because many-to-many |
314 |
[26] Graph visualization in general ref |
[26] Graph visualization in general ref |
315 |
|
|
316 |
|
|
317 |
NEW [between 3 and 4] Examples |
NEW 3.3 A real-world example |
318 |
============================== |
========================================== |
|
|
|
|
[30] Examples: |
|
|
|
|
|
- Expanding on the Carli example (also explaining |
|
|
how to handle large number of neighbours in e-mail case) [6] |
|
|
- Real-world example (poems) |
|
|
- Connecting thoughts (better than paper). |
|
319 |
|
|
320 |
Use RDF to concretify the examples. |
**[30] Poems example:** |
321 |
|
|
322 |
Need to drive home through this how this can "help us |
In this section, we give a example of hyperstructure |
323 |
organize our lives." |
in real-world use. |
324 |
|
We present how Christel Fallenstein, a fan of Austrian author |
325 |
|
Friederike Mayröcker, uses hyperstructure to keep track of the information |
326 |
|
she wants to remember about Mayröcker's work. |
327 |
|
|
328 |
|
This is currently done in zzstructure |
329 |
|
(using our implementation, Gzz), because the Fenfire implementation |
330 |
|
is in too early prototype stage. Below, we will give a |
331 |
|
list of the different information structures in this applitude |
332 |
|
and show how they could be realized in RDF. We can unfortunately not |
333 |
|
include screenshots because of the copyrighted and unpublished |
334 |
|
material as well as the private character of the information |
335 |
|
in this space. |
336 |
|
|
337 |
|
Poems |
338 |
|
The heart of this information space is a collection |
339 |
|
of published and unpublished poems by Friederike Mayröcker |
340 |
|
(node type ``poems:Poem``). For each poem, we store |
341 |
|
the ``poems:dateWritten`` and for some the ``poems:dateRevised``; |
342 |
|
also, we store the ``poems:title`` and ``poems:text`` of the poem. |
343 |
|
Finally, we store who the poems are ``poem:dedicatedTo`` |
344 |
|
as connections to the items representing these people. |
345 |
|
|
346 |
|
The collection of poems is primarily viewed sorted by |
347 |
|
date written and by *day and month* written, i.e. |
348 |
|
ignoring the year. The latter is useful to see the |
349 |
|
influence of seasons on Mayröcker's work, i.e., to see |
350 |
|
how two poems from February, but from two different years, |
351 |
|
may be similar. |
352 |
|
|
353 |
|
Contacts |
354 |
|
For people (node type ``foaf:Person``) we store their |
355 |
|
``foaf:name`` and possibly their contact information: |
356 |
|
``foaf:mbox`` (the e-mail address), ``person:address``, |
357 |
|
and ``person:phoneNumber``. |
358 |
|
|
359 |
|
A relatively common use is to look for a person by name, |
360 |
|
then look for poems dedicated to this person. The |
361 |
|
contact information is useful because the user of this |
362 |
|
system often knows the people poems are dedicated to |
363 |
|
and exchanges letters or e-mails with them. |
364 |
|
|
365 |
|
Correspondence |
366 |
|
In addition to the poems, the space contains correspondence |
367 |
|
with Mayröcker and other people interested in Mayröcker's work, |
368 |
|
for example translators of Mayröcker's work in different |
369 |
|
languages, by e-mail and paper mail. A ``m:Letter`` or ``m:Mail`` |
370 |
|
(subclasses of ``m:Correspondence``) has ``m:from`` and ``m:to`` |
371 |
|
properties connecting them to instances of ``foaf:Person``, |
372 |
|
as well as an ``m:date``. Mails also have an ``m:subject``. |
373 |
|
|
374 |
|
A usual task is to view all the correspondence with |
375 |
|
(from or to) a particular person in chronological order. |
376 |
|
|
377 |
|
Finally, and most importantly, correspondence is connected |
378 |
|
on ``m:about`` to poems it discusses. This way, it is |
379 |
|
possible to see, when looking at a particular poem, |
380 |
|
all correspondence discussing this poem. This is the most |
381 |
|
important reason for using hyperstructure in this context. |
382 |
|
|
383 |
|
Telephone notes |
384 |
|
Fallenstein and Mayröcker talk on the phone almost daily. |
385 |
|
During these conversations, Fallenstein takes notes about |
386 |
|
their discussions. For each call (``m:Call``), there is a list |
387 |
|
of short notes (``m:CallNote``). A call has a ``m:callDate`` |
388 |
|
and possibly some text connected on ``m:callInfo``, noting |
389 |
|
additional information, for example if Mayröcker was on |
390 |
|
vacation. |
391 |
|
|
|
Refer to FenPDF section below as giving another example. |
|
392 |
|
|
393 |
|
|
394 |
4 The Fenfire project |
4 The Fenfire project |