--===============6856027957147467224==
Content-Type: multipart/signed;
  boundary="nextPart1602465.gapzv6f5bn";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1602465.gapzv6f5bn
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

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 "semanti=
c=20
desktop".

The other two, while being used by Nepomuk as data sources, have their own,=
=20
orthogonal, use cases.

Strigi, or more precisely one of its building blocks ("libstreams"), is tas=
ked=20
with providing metadata about files, e.g. artist of a digital music file,=20
date/time of capture of a digital photo file, etc.

Such information pieces are nowadays regarded essential by lots of users, e=
=2Eg.=20
expect them to be displayed when hovering over such a file or when looking =
at=20
such a file's properties.

Since the information is also made available to Nepomuk, applications can=20
either use the technologies directly (link with libstreams, extract metadat=
a=20
when needed) or by quering Nepomuk.

The latter approach obviously requiring Nepomuk to run but on the other han=
d=20
making a bigger set of meta data accessible, e.g. user generated meta data=
=20
such as rating, comments or tags, or application generated meta data such a=
s=20
file origin (e.g. the web site is was downloaded from).

This type of information is not as expected as the first type, though ratin=
g is=20
increasingly being used for digital music and comments now are often applie=
d=20
to digital photos (description of scenery, people on the photo. etc).

It seems the authors of applications dealing with meta data had anticipated=
 a=20
faster growth of such needs, thus making the choice of augmented data acces=
s=20
more desirable.

Cheers,
Kevin

=2D-=20
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

--nextPart1602465.gapzv6f5bn
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iD8DBQBQp5EynKMhG6pzZJIRAkjHAJ968TcowNYMnxAZuWUPOo1CUrHL2gCfa9SH
GOR5cFfnG2Sdo+W2gd6GUJ8=
=VysA
-----END PGP SIGNATURE-----

--nextPart1602465.gapzv6f5bn--

--===============6856027957147467224==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

___________________________________________________
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.
--===============6856027957147467224==--