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. -- Add mimetype and interpretation helper utils to public API https://bugs.launchpad.net/bugs/586524 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: Triaged Bug description: See linked branch _______________________________________________ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp