Re: [Tracker] Full Proposal and plan of action for GSOC [draft]

[Philip Van Hoof <philip codeminded be>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/04/2015 13:45, Sam Thursfield wrote:

> On Sun, Mar 22, 2015 at 9:59 PM, kunaal jain <kunaalus gmail com>
> wrote:
> > Hi guys,
> >
> > I am sharing link for the full proposal and plan of action of
> > the project. I am uploading it to Google-melange. According to
> > GNOME, GNOME foundation members can log in to melange through
> > organisation and leave comments. Please consider leaving positive
> > comments there ;).
> >
> > Also please provide your valuable suggestions and edits/changes.
> > Once the community here approves this I'll submit the final
> > version to google.
> >
> > LINK 
> > http://www.google-melange.com/gsoc/proposal/public/google/gsoc2015/ku
naalus/5629499534213120
> >
>
> This looks like a major change, but something that could be really 
> good for Tracker if done right.
>
> I'm not involved in choosing which proposals get accepted, but one 
> thing that might help is if you had some example of what the API 
> changes will actually look like. In particular, you give 21 days
> to



There are two major API additions needed which do what these already do:


https://git.gnome.org/browse/tracker/tree/src/libtracker-sparql/tracker-
connection.vala#n152

https://git.gnome.org/browse/tracker/tree/src/libtracker-sparql/tracker-
connection.vala#n115

tracker_sparql_connection_get_with_params
+       * @ontology: a path to a installed ontology
+       * @instance: a UUID to indicate the database instance
        * @cancellable: a #GCancellable used to cancel the operation
        * @error: #GError for error reporting.


tracker_sparql_connection_get_async_with_params
+       * @ontology: a path to a installed ontology
+       * @instance: a UUID to indicate the database instance
         * @cancellable: a #GCancellable used to cancel the operation
         * @_callback_: user-defined #GAsyncReadyCallback to be called
                when asynchronous operation is finished.
         * @_user_data_: user-defined data to be passed to @_callback_



> the task of "Adapt libtracker-sparql and tracker-store to accept a 
> parameter for the cache database and ontology.".  Would this only 
> change the D-Bus API, or libtracker-sparql as well?

D-Bus will be affected too. The Steroids and the Resources D-Bus APIs
will similarly to the two APIs of libtracker-sparql expose
functionality to allow passing the two added parameters.

The Resources D-Bus object will be available multiple times separated
for example by the "instance" UUID based parameter.

 How, as an
> application, would I specify what set of ontologies I wanted to
> use: pass in a path to a directory containing them? Or something
> else? Similarly, would I pass in the path to the Tracker store I
> wanted to use?

A path and a UUID: one ontology can be used by multiple consumers, one
ontology can be reused by multiple instances. So two parameters are
needed.

use cases:
        * a shared Nepomuk storage (Nepomuk, shared-uuid)
        * a private Nepomuk storage (Nepomuk, own-uuid)
        * a shared custom ontology storage (Custom, shared-uuid)
        * a private custom ontology storage (Custom, own-uuid)

I'll leave the rest of the answers to Kunaal.

Kind regards,

Philip


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (MingW32)

iQEcBAEBAgAGBQJVJ9YqAAoJEEP2NSGEz4aDGWEIAKlMDZwmuv8IxgcbUGcRrQik
iDgMLc8Qahh9bD5YTAyXxenaFY03/b7um2HD31lhP3fZnwhk11FZB8q05YdM0nQ0
ZGALykgzeuX/J5krfxpuL1fPkZkEd+ZW8KkxvIxqbQJDwdDn0g23qhF9x/3AS6Qn
8qDNASlwhIiI2Krb+5QYOoqNn2btzQOVD0s6eeua01coc1IJInWHcZ7Quw2Q3ZQV
b7gotynAm5hxARh4hGl5nwscy8mViqpxJ+dcuZzvd/6LxBwGCP89Fj/qENIyA0lb
J5sm6b/7CiXBeTBqkooOiRq+gs1kO89rVJuOhg+mFHwrF5nurvAB9bJl66qQibg=
=IJyh
-----END PGP SIGNATURE-----