This site is outdated. Please see http://nepomuk.kde.org

Welcome To the NEPOMUK-KDE Wiki!

This is the place where Nepomuk and KDE come together.

• Nepomuk-KDE mailing-list
• Developer Main - documentation for developers
• Releases - releases

News

09.12.2007 - Nepomuk-KDE Demo Screencast online

June 2007 - Nepomuk-KDE to be presented at the aKademy 2007 by Tudor Groza, DERI

June 2007 - Online videos and blogs about Nepomuk-KDE

Liquidat recently posted articles about the Nepomuk-KDE project:

• Semantic Desktop and KDE 4 - State and Plans of Nepomuk-KDE
• More about Nepomuk-KDE: Soprano and KDE integration
• Nepomuked Dolphin's screencast

28.05.2007 - Soprano project page started + first official Soprano release

04.04.2007 - KMetaData first steps tutorial now available

10.01.2007 - Nepomuk-KDE Workshop in Paris

15.12.2006 - Nepomuk-KDE Meta Package 0.1 released

About

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.

To achieve this goal the NEPOMUK-KDE project consists of the following parts:

• The Backbone Library (libKNep) which provides the basis for the service-oriented architecture that is defined by the Nepomuk project. It provides a service registry and a convinience library that hides all communication issues from the user. KNep allows to query services and publish services to the system. It also provides interfaces for the standard NEPOMUK services such as RDF storage and query.
• The KDE MetaData Library (which might be inappropriatly named) provides a wrapper about the NEPOMUK desktop ontology and allows for simple meta data manipulation (meta data of type 3).
• The actual services implementations which implement the interfaces defined in libKNep and do the actual work behind the scenes.
• Little helper Tools that mainly assist the developers.
• The most important part of the project from the point of view of the user are without a doubt the NEPOMUK-KDE clients which provide the GUI to the services. This includes metadata generation and the graphical representation of it.

Interesting stuff

• Contact
• Todo
• Frequently asked questions
• Use cases
• Soprano the QT based RDF storage solution
• Ideas gathered around the web

Related Projects

• Strigi - Desktop Search
• Beagle++