Version: (using KDE 4.2.4) OS: Linux Synpnosis: A way of interacting with your computer, through natural langauge processing with semantic knowledge of users files and interests. Nowadays, we have a lot of information to process, be it bug reports, emails, news...the list goes on. We talk with our friends, arrange meetings and appointments. As the amount of information we process gets bigger, our tools for finding, processing and delivering that information must evolve. The only way for our tools to 'evolve' into more useful tools, is to embed them with Artificial Intelligence. Thus, I propose K.I.I.M (KDE's Intelligent Information Manager) Kiim's function is to get your computer to work WITH you, rather then you working on it. (thread on the forums can be found here: http://forum.kde.org/viewtopic.php?f=83&t=61978 K.I.I.M can either be an app, a new desktop metaphor or a project to increase the usefulness of KDE apps. Example uses: Optical Character Recognition in Okular (allowing Okular to copy text, as well as allowing speech synthesis to read the files out) Natural language queries and commands: "Send all the documents I was working on yesterday to Jack." (This would work by finding all document files whose creation date/modification date was yesterday and sending them via email to a contact named Jack in the address book) "Give me a report on nuclear fission" (This would assemble data from numerous online sources into a document, allowing people to be brought up to speed quite easily, instead of digging around for it manually.) Also, Kiim could keep track of conversations made through Kopete, so if a particular set of keywords comes up ("Dan, do you wanna go to the cinema tomorrow?") Kiim could automatically make that an appointment and remind you later. The code already exists in FOSS compatible terms. It just all needs to be linked in together. I first thought of Kiim as a desktop of the future, a way of giving your computer a personality. I would love to see Kiim take such a form.
*** This bug has been marked as a duplicate of bug 213452 ***