Hello guys, I just pushed a feature branch called domain-ontologies. It's a first attempt at providing the infrastructure for making it possible to have domain specific ontologies. First part is adapting the tracker_data_manager_init to have parameters domain and ontology_name. The idea would be that tracker-store gets told (via argv?) what domain and ontology_name to load. The meta.db would of course also be unique per domain (+ ontology_name). So the tracker_db_manager_init must be similarly adapted (not done yet). After that it should be possible to have a tracker-store per domain and per ontology, or just per domain. Etc. So that means adapting the D-Bus part (have a instance of the service per domain(+ontology_name), or make it possible for one tracker-store process to service multiple domains). Right now tracker-store can only run once. That will have to be adapted too. Noting that the default (NULL, NULL as parameter values) should do exactly the same as what current tracker-store does. Feel free to join, as I can't work on this very often. Kind regards, Philip
Attachment:
signature.asc
Description: This is a digitally signed message part