Re: Nepomuk use case

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: Nepomuk use case
by Robert Knight on Saturday 09/Feb/2008, @05:22

> Nepomuk has been HUGELY undersold, imho.

I think one important lesson from development leading up to KDE 4.0 is that it is best to keep mum until there is something cool to show.

Sure, the semantic desktop does have a lot of potential, but right now, as far as the end user is concerned, it gives them simple tagging and rating of files in Dolphin.

Pitching to the developers is a different story. You want to get them fired up about the potential of a particular project and encourage them to use it to improve their own software. The difficulty is making sure that a pitch to developers or potential developers doesn't land on the front page of Slashdot as a promise that KDE version X will do Y.

Related Links

·   Articles on Developer
·   Also by Robert Knight
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: Nepomuk use case
by Lee on Sunday 10/Feb/2008, @13:21

Yep, agreed. It's a tough balance to find. Nepomuk's APIs have a really nice simplicity to them though, so I'm confident that development will catch up soon enough :) One thing that would really help though, is better documentation. The examples on techbase are great, but there aren't many of them, and they're fairly limited in terms of use cases. I haven't yet seen any examples of soprano/nepomuk use from python/ruby/kross -- don't even know if any of those bindings are implemented yet.

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"Feature freeze: You're allowed to add new bugs, but no new features." -- Richard J. Moore
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.