Languages: عربي | Asturianu | Català | Česky | Kaszëbsczi | Dansk | Deutsch | English | Esperanto | Español | Eesti | فارسی | Suomi | Français | Galego | Italiano | 日本語 | 한국어 | Norwegian | Polski | Português Brasileiro | Română | Русский | Svenska | Slovenčina | Slovenščina | српски | Türkçe | Tiếng Việt | Українська | 简体中文 | 繁體中文
This page is dedicated to Nepomuk development ideas, progress, experiments, and is a general starting point for new developers.
For general information about the Nepomuk project see the dedicated Nepomuk homepage.
IRC: #nepomuk-kde on Freenode
Mailing List: email@example.com
Maintainer: Sebastian Trueg
Developers: Vishesh Handa
The Nepomuk page on UserBase has information and troubleshooting for users.
The following links provide good reads for getting used to the Nepomuk system and its APIs.
As Nepomuk is highly dependent on its data in the RDF store and the used ontologies, one might consider to read up on RDF and the Nepomuk ontogies:
Nepomuk is a rather young project with a notorious shortage in developers. There are many tasks and subprojects to get ones hands dirty on. Unlike other projects like Plasma, however, developing for Nepomuk is not easy. One has to read up on a lot of things and fight some day-to-day annoyances. But: helping with the development will improve the situation in any case.
If you are interested in working on a task in this list, please contact Sebastian Trueg.
If you want to get into Nepomuk development quickly by taking over a small task have a look at our Junior Job page.
The low-level development tasks are those that are not directly reflected in the GUI or even in the API used by most developers. However, they are important in terms of performance, scalability, and compatibility.
Virtuoso 5 provides inference on rdfs:subClassOf and rdfs:subPropertyOf. These are the most important ones and for now all we need in Nepomuk.
The current implementation of the Virtuoso Soprano backend does not enable inference. We need a configuration option to do exactly that. It could happen along the lines of the existing config options or with the introduction of dedicated inference configuration options on the Soprano::Backend level.
Soprano is the RDF database framework used in Nepomuk. Currently Soprano does not support transactions, i.e. sets of commands that can be rolled back. An experimental development branch exists which already contains new API for transaction support (while keeping BC).
It still misses an implementation of the transaction support in Soprano backends (Sesame2 and Virtuoso) and in the client/server architecture.
Another idea is to create a new API based on the design that Sesame2 follows: Repository and RepositoryConnection classes. The former creates instances of the latter which then has all the actual data handling methods and acts as one transaction object.
Provide a GUI that allows to call methods such as optimize and rebuildIndex on the storage service. The latter method is not commited yet due to the KDE 4.3 feature freeze but will be afterwards.
It would also be useful to have Nepomuk register such operations (including the data conversion when changing backends) via the notification system.
|Projects/Nepomuk/OntologyBasics/en||Projects/Nepomuk/Qualified Relations Idea||Projects/Nepomuk/QueryLibrary|