Updated README

1 files changed, 23 insertions, 28 deletions

diff --git a/README b/README
index 85b842d03..939302dc2 100644
--- a/README
+++ b/README
@@ -1,33 +1,28 @@
 1 Introduction
 
-  Tracker is a powerful desktop-neutral first class object
-  database, tag/metadata database, search tool and indexer.
-
-  Tracker is also extremely fast and very memory-efficient
-  when compared with some other competing frameworks and has by
-  far the fastest and most memory-efficient Nautilus search and
-  Deskbar backends currently available.
-
-  It consists of a common object database that allows entities to
-  have an almost infinte number of properties, metadata (both
-  embedded/harvested as well as user definable), a comprehensive
-  database of keywords/tags and links to other entities.
-
-  It provides additional features for file-based objects
-  including context linking and audit trails for a file object.
-
-  It has the ability to index, store, harvest metadata, retrieve
-  and search all types of files and other first class objects.
-
-  Supported first class objects include:
-
-  * Files, Documents, Music, Images, Videos, Applications, Emails,
-    Conversations, Playlists
-
-  Planned support:
-
-  * Appointments, Contacts, Projects, Tasks, Bookmarks, Notes,
-    Firefox Web History
+  Tracker is a search engine and that allows the user to find their
+  data as fast as possible. Users can search for their files and
+  search for content in their files too.  
+
+  Tracker is a semantic data storage for desktop and mobile devices.
+  Tracker uses W3C standards for RDF ontologies using Nepomuk with
+  SPARQL to query and update the data.
+
+  Tracker is a central repository of user information, that provides
+  two big benefits for the desktop; shared data between applications
+  and information which is relational to other information (for
+  example: mixing contacts with files, locations, activities and
+  etc.).
+
+  This central repository works with a well defined data model that
+  applications can rely on to store and recover their information.
+  That data model is defined using a semantic web artifact called
+  ontology. An ontology defines the relationships between the
+  information stored in the repository.
+
+  An EU-funded project called Nepomuk was started to define some of
+  the core ontologies to be modelled on the Desktop. Tracker uses this
+  to define the data's relationships in a database.
 
   All discussion related to tracker happens on the Tracker
   mailing list