Schedule: Semantic KDE

Jos van den Oever
Stéphane Laurière
Day Saturday
Room H.1301
Start time 14:00
End time 14:45
Duration 00:45
Event type Podium
Track KDE
Language English
Slides (PDF)
Semantic KDE

Semantic KDE - Advanced metadata in KDE with Nepomuk.

The Nepomuk-KDE project aims to recreate the way metadata is handled throughout the KDE desktop. Semantic annotation of resources is only the beginning.

NEPOMUK-KDE is a sub-project of the Semantic-Desktop project Nepomuk which aims to provide a full implementation of the standards and APIs defined in Nepomuk on the KDE Desktop. As a sub-project of Nepomuk the two main issues are the maintenance and intensive usage of metadata throughout the desktop and powerful peer-to-peer collaboration techiques.

In the first phase of the NEPOMUK-KDE project the focus lies on the metadata part. There are basicly three kinds of metadata to be found on the desktop:

  • Metadata that can be found in files stored on the local harddisk like tag information in audio files, timestamps, or simple indexed text. This metadata can be extracted and indexed at any time and is exactly the type of information current desktop search projects like Beagle or Strigi are based on.
  • Metadata created manually by the user. In the most simple case this can be a comment to a file or an email. But it could also mean the grouping of several resources under one topic and so on.
  • The most interesting type of metadata is, however, the kind that cannot be extracted easily by an indexer and is not generated by the user manually.
This includes for example the url of a file that is downloaded from the internet. Once saved on the local harddisk this information is lost. The same goes for the (rather popular) example of email attachments: Once an email attachment is saved to the local harddisk its connection to the email and with it the connection to the sender is lost. These are just two examples relating to the source of files. There are many more. The goal of the NEPOMUK-KDE project is to create facilities to allow each KDE application to take advantage of this metadata. That means that a KDE application can easily create new metadata, search metadata, search relations between resources based on metadata, and so on.