This page catalogs all the applications that are currently using Nepomuk, and will need to be ported to Baloo.
Please note that Baloo is not a drop in replacement for Nepomuk. Since Nepomuk relied on RDF, the way applications used it was very different than how applications will use Baloo. Nepomuk was often the central storage medium in KDE. Baloo does not have one central database.
Dolphin has been completely ported to Baloo. All traces of Nepomuk have been removed. There are some minor bugs which need to be addressed, but for the most part it is feature complete.
KDEPIM was a heavy user of Nepomuk. It gains the most by migrating to Nepomuk. The indexing infrastructure has already been ported to Baloo. The tagging and search backend still requires porting.
The Amarok project provided an additional Nepomuk collection which could be used if the user did not want Amarok to index all their music files. Removing this Nepomuk collection does NOT remove any functionality from Amarok.
Making Amarok share their index with Baloo is not being considered at this time. It could be done in the future as a separate project.
With the latest Digikam, it allows tags/rating to be synchronized with Digikam's database. This is done by running a process which continuously monitors the Digikam and Nepomuk database and performs 2 way synchronization. Considering that Baloo uses extended attributes to store tags, it might be easier to integrate this with Digikam.
Conquiere heavily depended on Nepomuk as its primary storage mechanism. It will need to be reworked to have a new storage medium.
Needs porting. Just using tags, should be very simple.
Uses Nepomuk to store the license information of a file. It's not integral to the application, and is just a nice addon. Considering that this requires Nepomuk to be running, it does not seem like a big loss.
Will need to be reworked.