Add mimetype and interpretation helper utils to public API

It may be worthwhile to point at Michal Hruby's datahub rewritten in Vala. This uses the mimetype->interpretation mappings from libzeitgeist which are more full featured than the ones we have inside the Zeitgeist Python codebase.

The work is at: lp:~mhr3/zeitgeist/datahub-vala

@Mikkel can we have this map somehow in a public API then. It wouldn't be bad to allow apps to just send in the mimetype of their document and we then attach the type to it :)

no, please don't add this extra level of complexity. This is definitely something the client should take care of.

About the original intention of this bugreport:
The only way to solve this is to define a mapping format (let's say some json based format) which describes the mimetype->interpretation mapping and translate this into python code/vala during build time of zg or libzg.
That's IMHO the only way to get something like this into core zg. As long as we don't have this clients can still use the ctypes wrapper around libzg trick I posted on the merge proposal.

+1 :)
Lets create the jason crap then

On Sat, Aug 7, 2010 at 1:38 PM, Markus Korn <email address hidden> wrote:

> no, please don't add this extra level of complexity. This is definitely
> something the client should take care of.
>
> About the original intention of this bugreport:
> The only way to solve this is to define a mapping format (let's say some
> json based format) which describes the mimetype->interpretation mapping and
> translate this into python code/vala during build time of zg or libzg.
> That's IMHO the only way to get something like this into core zg. As long
> as we don't have this clients can still use the ctypes wrapper around libzg
> trick I posted on the merge proposal.
>
> --
> Add mimetype and interpretation helper utils to public API
> https://bugs.launchpad.net/bugs/586524
> You received this bug notification because you are subscribed to The
> Zeitgeist Project.
>
> Status in Zeitgeist Framework: Triaged
>
> Bug description:
> See linked branch
>
>
>

--
This is me doing some advertisement for my blog http://seilo.geekyogre.com

@markus I think the python-zeitgeist bindings should do the work of mapping the mimetype -> interpretation before inserting. What do you think?

Okidoki, I had a hard time thinking about this *again*, and although I still don't like the idea of having the mapping logic in zeitgeist itself, I see the usefulness of such feature for some clients.

But I've a few requirements:
   * the code should go into a new module, like zeitgeist.mimetype_helpers and should *never* be loaded in zeitgeist.datamodel
   * we should adapt the definition and logic from what libzeitgeist has now
   * this needs also a converter tool in libzeitgeist to convert the python mappings into C ones, similar to the solution for the ontology and the symbols. This way we only have one place where we define the mappings.

thekorn +1

I'm taking over the python part of the story now, Michal agreed on doing the libzeitgeist part once we released a zeitgeist.mimetypes modul