NEPOMUK-KDE

Use Cases

The first milestone of the implementation is intended to be based on the following use cases.

Resource tagging/annotation

The user can add tags to files using Konqueror or to emails using KMail or to contacts using the KAddressbook.

Keep email attachment meta information

Once an email attachment is stored on the local hard drive a lot of information like "Who send the file?" or "When was it sent?" is lost. By storing the connection between the email and the saved attachment this information can be preserved and used later on to find the email or the person that sent it.

Task
move RDF service, parser service to the public NEPOMUK SVN service registry for DBUS (done): NEPOMUK-KDE registry. Todo: have it in the KDE SVN and explain how to run it (branches/work/nepomuk-kde/registry)
have kgense code stored into the KDE playground as well.
RDF service (storage, indexing, querying) as a DBUS service delegating the real work to an RDF database: either Sesame2, Redland. Status: done for Sesame2. Todo: have it also running with Redland. .nepomuk/. See how to solve the Java dependencies issues with Micha and Stéphane
kgense should use the registry to get the storage and query service. definition of kgense: general data/metadabrowser and editor. kgense should use the client library
wiki editor based on Kate with: wiki syntax highlighting , completion. The wiki should delegate the parsing and the storage to the parser and the storage services.
create the parser service
create the annotation plugin using the semantic wiki editor, the parser service, the RDF services

Use case 1: email annotation

I right click on an email
An editor pops up
I enter some text
I click ok
The text is stored as a TextObject into the RDF database, with a statement linking the object to the related email

Needed:

KMail plugin for opening an editor
Identification service for referencing the email
RDF storage service
RDF query service (to know whether there's already a comment in the database)
use PIMO property or whatever for representing the classes and properties used

Use case 2: annotating a file from Konqueror: same than UC1 except the action and user interface

Use case 3: email attachment

I save an attachment to the filesystem
a statement drawing the link between the email and the file is automatically created (using a property "originates from" or...

Use case 4: file download

I download a file from the Internet
a statement drawing the link between the URL and the file is created
capture relevant contextual information that will help the user find again the downloaded file later on: actual download URL, URL of the context (i.e. page containing the link), time, query typed in Google that has conducted to the link

Use case 5: semantic wiki editor

Commments: analogy with a code editor Features:

completion according to an underlying ontologie (or several ones)
wiki syntax highlighting
CTRL+Click on a wiki document name lets the user navigate across wiki documents
inline queries: I can enter a SPARQL query and execute it in the editor itself
inline error display (wrt property range)
source formatting
etc.

Note:

possible conflict problems if the statements are edited from another application
SemanticWikiService.getWikiPageForResource() returns the statements where this resource appears as subject, serialized into a String

Needed:

wikimodel parser service

Use case 6: resource monitoring service

-> then real-time indexing

Use case 7: file open dialog allows semantic searching

Other use cases

Social use cases.

Main - This site is outdated. Please see http://nepomuk.kde.org > Use Cases
Version 1.3 last modified by StephaneLauriere on 16/10/2006 at 20:13