All about the search infrastructure of Akonadi.

Contents 1 Concept 2 Query Language 3 Search Backends 3.1 Possible Backends 3.2 Delegation to Resources 4 Virtual Collections 5 Nepomuk Feeder Agents

[edit] Concept

Concept of the Akonadi search infrastructure:

[edit] Query Language

Options:

• SPARQL: de-facto standard by now (used by Nepomuk and Tracker), but way too complex for automatic query transformations.
• XESAM (?)

[edit] Search Backends

Requirements:

• fast enough
• cross-platform
• persistent/live search with change notifications

[edit] Possible Backends

• Nepomuk with Sesame2 or Virtuoso
• Tracker (?)
• XESAM (?)

[edit] Delegation to Resources

• Requires query transformation
• Requires management for live searches
• Requires the ability to report search results (needs protocol extension) [done by now]

[edit] Virtual Collections

Virtual collections are used to report results, for details see Projects/PIM/Akonadi/VirtualCollections.

[edit] Nepomuk Feeder Agents

• The delete/add approach removes otherwise added information such as tags when an item is modified.
• Category to tag conversion uses non-Fast Nepomuk resources.