Currently working in Nokia. Joined to maemo 3 years ago to put tracker into the platform and since then I've been very involved in its evolution into a bleeding edge triplet store. As far as i know the first one with widespread real world usage. And in a mobile device. Yes, i am proud.
I have been talking about Tracker in multiple conferencies, including GUADEC and Maemo summits.
Email: ivan.frade_AT_nokia.com IRC: frade in #tracker/gimpnet, #meego/freenode and multiple other channels
A store of information using something called "triplets" instead of the traditional Entity-Relation paradigm. That triplets-model allows tracker to store user data from different sources in a common well-define schema and to query that information in an efficient way (using Sparql, an specific query language). By user data, we refer to Contacts, calendar, multimedia, feeds, messages and so on.
The common schema has two big advantages in the architecture:
1. A common schema to represent information means that providers and consumers are cleanly decoupled. An application interested on contacts doesn't need to know who put them there; and a new source of contacts (like a new online service) can easily push information into the store.
2. That schema allows to link any kind of content with any other. This allow applications to link contacts with locations with multimedia files. Or contacts with messages and with feeds. With this infrastructure the development of mash-ups and rich applications is suddenly much easier.
Content FW is a box with Tracker and few other components to complement its functionality: how to handle thumbnails, how to link actions and items coming from Tracker and some convenience libraries for the average Qt/C++ developer. Some components are already there, some are still under construction and some only exist on our mind. This is definitely an area where application developers feedback is needed.