On Saturday, 2012-11-17, Jerome Yuzyk wrote: > With all the hassles added by Akonadi and Nepomuk and Strigi for some > higher "social/semantic desktop" purpose, does anyone actually _use_ the > stuff? Ok, this is basically the second part of [1] Similar to how Strigi is tasked with providing meta data in a uniform way across a wide spectrum of file formats, Akonadi is tasked with providing data access in a uniform way across a wide spectrum of data storage formats and locations. Also similar to Strigi, this involves libraries which can also be used directly by applications, but, again, are most often used indirectly through a service. As I wrote in my reply to Duncan's reaction to [1], KDE developers will often prefer a service based approach due to some qualities and advantages inherent in it and being a time proven option widely used on Unix like operating systems. As a matter of fact it is no conicidence that both major providers [2] of Free Software infrastructure for end user programs are using that approach while direct backend access is employed by stand-alone application providers. Anyway, the topic at hand is the relation ship of this particular technology with "semantic desktop" and the point is that its usefulness and goals are independent of that. I see Georg has just explained that as well, but I guess I can't hurt to repeat: semantic desktop builds upon technologies such as Akonadi and Strigi, but they serve a wider range of purposes than just that or in other words, semantic desktop is one of their additional usage scenarios. Cheers, Kevin [1] http://lists.kde.org/?l=kde&m=135315899718567&w=2 [2] KDE and GNOME -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring
Attachment:
signature.asc
Description: This is a digitally signed message part.
___________________________________________________ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
