Todo

The following list gives a rough overview of the tasks planned in the Nepomuk-KDE project for the near future. If you change this list, please drop me a line: mailto:strueg@mandriva.com so I can keep an overview of the development myself.

PrioComponentTaskDue/FinishedAssignedProgress
NormalKMeta DataAdd support for providence data for statements (only creation date is stored).-Sebastian Trueg100%
LowKMeta DataHow about fallback properties like the example in NAO: if no symbol is defined for an instance fall back to the symbol defined for the type of the instance.--0%
NormalBackboneImplement the OntologyService (still called PIMOService in Nepomuk) - This service should provide convenience methods to create resources (construct new uris), get internationalized class and property labels and comments, load ontologies into the store (Make use of KDE's service discovery system to discover installed Nepomuk-KDE ontologies), and create providence data for statements.-Sebastian Trueg: I already started implementing the Konto lib which wraps ontologies. This could be used.0%
LowKMeta DataPort to the new OntologyService.--0%
NormalBackboneMake starting the service registry daemon more reliable and implements some locking mechanism.--0%
NormalKDECreate an abstract read-only KPart that can be used to display arbitrary Resource types. App developers can then derive from this one to create special parts that display special kinds of resources. For that we also need a new desktop file entry that defines the supported resource types.-Sebastian Trueg100%
NormalKMetaDataAllow multiple types for each resource and handle them properly.-Sebastian Trueg100%
NormalKMetadataExtended query functionality, not as powerful as SPARQL but to be used by "normal" applications for everyday query stuff--0%
NormalSopranoImplement an RDF inferencing machine to handle sets of roles like the Jena Inference ruleset.-Sebastian Trueg100%
NormalNepomukImplement a recommender service: A service that listens to metadata and tries to map resources that represent the same concept. This could be rule-based. A rule could then have different outcomes: 1. link definitely, or 2. ask user, or 3. whatever. This way one could for example annotate a picture with "depicts" and then the service would try to map the name to a contact in the adressbook.--0%
LowBackboneImplement the Nepomuk Middleware federation SOAP uplink (suspended)--0%
NormalAllWrite more unit tests.All the timeEverybody-
 
NormalKMeta DataImprove the ontology parser and make it create "plugins" for the main KMetaData libs which can be used to ease access to specific ontologies. + namespace expanding so both ns abbreveations like rdf: and the full namespace are supported. There should be 2 modes: one makes a shared lib and one makes a static lib or simply creates a list of sources that can be added to a cmake target.31.03.2007Sebastian Trueg80%
HighStrigiWrite a Nepomuk indexer which writes all fields to the RDFRepository. Do not use libKNep since we cannot have a reverse dependancy (kdelibs depends on strigi and libknep depends on kdelibs or is part of it) but use D-Bus directly. (Indexer is now part of kdebase)-Sebastian Trueg100%
NormalKMetaDataAdd standard ontologies (RDF, RDFS, NRL, NGM, NIE, and NAO) in an "ontologies" folder, add desktop files for them and make them searchable through the KDE service system. Then let the OntologyService read them on startup and put them into the RDF store if they are not already there.-Sebastian Trueg50%
NormalRedlandExtend the Raptor Turtle parser to handle TriG.15.06.2007Sebastian Trueg (patch sendto Dave) (patch integrated into raptor)100%
NormalKNepomukHandle the renaming, moving, copying, and deleting of files in the repository. This means that NFO:fileUrl properties have to be updated and probably a new property like has to be introduced. The question is how strigi can be used here? Strigi already has preliminary support for inotify. maybe this is already sufficient in combination with the Nepomuk Strigi backend. (The filewatch service can be found in the kde svn at: playground/base/nepomuk-kde/filewatch)-Sebastian Trueg70%
 
NormalSopranoMake the Backends pluggable12.02.2007Sebastian Trueg100%
NormalSopranoAllow using different Redland backends like SQLite12.02.2007Sebastian Trueg100%
NormalBackboneAdd proper error handling using QDBus: add another QDBusMessage argument to all slots in all DBusInterface classes and if the method call fails just do a message.sendError before returning some value (which will be ignored). The QDBus error may contain arbitrary error codes in addition to the already defined DBus errors and a message string. I (Trueg) already defined a small set of error codes that can be used.15.02.2007Sebastian Trueg100%
NormalBackboneAdapt the RDFRepository API that was agreed on at the integration meeting in Kaiserslautern 01/200714.02.2007Sebastian Trueg100%
Main - Todo
Version 1.47 last modified by SebastianTrueg on 28/02/2008 at 23:20

NEPOMUK-KDE


Creator: SebastianTrueg on 2007/01/24 09:16
NEPOMUK Consortium and KDE
1.1.1