back to main page

      1. back to main page
  2. About subproject Accessing (Meta)Data on the Desktop
    1. Components Overview
      1. RDF Repository component
      2. Data Wrapper component
      3. PIMO Service component
      4. PimoEditor
      5. Local Data Alignment
      6. User work context
      7. Nepomuk Client
    2. How to help
  3. Contact

About subproject Accessing (Meta)Data on the Desktop

This subproject interconnects and links all kind of information elements in a personal workspace (i.e., address book entries, files on the desktop, ...). It provides an API for accessing and linking to data stored in standard desktop applications such as browsers and e-mail clients.

Some picture showing a prototype, this subproject's architecture or something like that.

Components Overview

RDF Repository component

All Desktop applications can use the RdfRepository database to share metadata about resources, and through this sharing it is possible to integrate them on the level of data and ontologies.

Data Wrapper component

The DataWrapper component wraps data from native applications, such as files in the filesystem. Datawrappers read data from various applications and store them in the RdfRepository. This indicates that you have read only access to the RDF (in the RdfRepository).

PIMO Service component

The PimoService implements commonly used methods to access personal data structures in the RdfRepository. It knows about the personal namespace of the user and manages URIs.

PimoEditor

Editing Things in a JSP based project.

Local Data Alignment

The LocalDataAlignment analyzes your data and detects how things are connected to each other. It aligns multiple resources, giving suggestions which resources are actually describing the same entity. The suggestions are confirmed or rejected in a user interface. As a result, the context of persons, places, projects is enriched.

User work context

Detecting the current workflow of the user by observing the operations the user does. Operations are notified to the User Observation Hub, listeners to this hub can detect the current work context of the user.

Nepomuk Client

The main idea behind the Nepomuk Client is to provide all necessary jars for a client in one package. The current implementation use XML/RPC to communicate with the Nepomuk Server.

How to help

  • End users can help by...
    • join the mailinglist - report bugs, make suggestions
    • edit these wiki pages :-)
  • Developers can help by...
    • doing code review
    • fix TODOs/FIXMEs (see sources)
    • send in contributions as patch via mail (address see below)

Contact