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?
Of the above three mentioned technologies, only Nepomuk is part of "semantic
desktop".
The other two, while being used by Nepomuk as data sources, have their own,
orthogonal, use cases.
Strigi, or more precisely one of its building blocks ("libstreams"), is tasked
with providing metadata about files, e.g. artist of a digital music file,
date/time of capture of a digital photo file, etc.
Such information pieces are nowadays regarded essential by lots of users, e.g.
expect them to be displayed when hovering over such a file or when looking at
such a file's properties.
Since the information is also made available to Nepomuk, applications can
either use the technologies directly (link with libstreams, extract metadata
when needed) or by quering Nepomuk.
The latter approach obviously requiring Nepomuk to run but on the other hand
making a bigger set of meta data accessible, e.g. user generated meta data
such as rating, comments or tags, or application generated meta data such as
file origin (e.g. the web site is was downloaded from).
This type of information is not as expected as the first type, though rating is
increasingly being used for digital music and comments now are often applied
to digital photos (description of scenery, people on the photo. etc).
It seems the authors of applications dealing with meta data had anticipated a
faster growth of such needs, thus making the choice of augmented data access
more desirable.
Cheers,
Kevin
--
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.
