Documentation

This page is to direct developers to documentation that they would find helpful when developing their application to make use of Tracker technologies. This page is still being written, so some of this information is not yet available. This page is for Tracker > 0.6 only (a lot of the principles and documentation here do not apply to 0.6.x).

What can I do?

APIs

There are two approaches to Tracker:

Everything in tracker is built around a common well-defined schema called ontology so in both cases is worthy to take a look to this schema.

For data querying and updating see:

Tracker is a daemon running in DBus and can be used directly from there (not recommended):

To write new miners take a look to:

If the miner wants to access an online source (e.g. Twitter), it needs to be associated with an account:

To add support new file types (for files in the filesystem), write an extractor plugin for it:

For the ontology which describes how the data is related see (common for all the previous components):

API and ontology changes between major releases

Ontologies

SPARQL

Tracker uses the W3C standard query language SPARQL for Queries and Updates. To run queries in SPARQL you need to know the query language itself and the ontology. In both cases it is fairly easy to get the idea following examples.

Examples

Contributing

How Do Things Work?

Client Side

Server Side

Discussion

Tracker/Documentation (last edited 2011-08-10 18:22:03 by AdrienBustany)