Re: New module proposal: tracker

[Philip Van Hoof <spam pvanhoof be>]

On Tue, 2009-08-18 at 17:21 +0200, Lennart Poettering wrote:
> On Tue, 18.08.09 11:18, Jamie McCracken (jamie mccrack googlemail com) wrote:

> > The indexer part is optional
> > 
> > The main part tracker-store is just a database with querying and is to
> > be used by zeitgeist
> > 
> > If the consensus is that indexer is not suitable for inclusion then the
> > separate tracker-store should be considered for inclusion separately 
> > 
> > the store does not do any indexing or file monitoring nor does it cosume
> > significant resources 
> 
> I have no idea what "tracker-store" is. Please elaborate. It sounds as
> it was the database that is normally filled by the indexing data, but
> what could it be good for if you rip out the indexer?

The tracker-store is a desktop service that offers the application
developer a query capability against data that it stores. The data that
it stores must be strictly defined by a schema (which is what in RDF is
called an ontology). The schemas that we ship by default are the Nepomuk
ones. The query language is SPARQL. The service provides the opportunity
to the application developer to store. The application developer uses
the an extension to SPARQL, SPARQL Update, which we support too. The
communication between application and tracker-store happens over DBus.

Nepomuk's ontologies:
http://www.semanticdesktop.org/ontologies/

SPARQL:
http://www.w3.org/TR/rdf-sparql-query/

SPARQL Update:
http://jena.hpl.hp.com/~afs/SPARQL-Update.html

RDF:
http://www.w3.org/RDF/

Let me know if that was a helpful description for you. I tried hard not
to sound like an old German philosopher ;-).


-- 
Philip Van Hoof, freelance software developer
home: me at pvanhoof dot be 
gnome: pvanhoof at gnome dot org 
http://pvanhoof.be/blog
http://codeminded.be