(Removed Development status) |
(→Documentation) |
||
| Line 17: | Line 17: | ||
The following links provide good reads for getting used to the Nepomuk system and its APIs. | The following links provide good reads for getting used to the Nepomuk system and its APIs. | ||
* [[Development/Tutorials/Metadata/Nepomuk|Development Tutorials]] | * [[Development/Tutorials/Metadata/Nepomuk|Development Tutorials]] | ||
| − | * | + | * [[Development/Tutorials/Metadata/Nepomuk/TipsAndTricks|Nepomuk Tips and Tricks]] |
* [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/index.html Nepomuk API Documentation] | * [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/index.html Nepomuk API Documentation] | ||
* [http://soprano.sourceforge.net/apidox/trunk/index.html Soprano (RDF storage) API] | * [http://soprano.sourceforge.net/apidox/trunk/index.html Soprano (RDF storage) API] | ||
Contents |
Nepomuk serves as a cross application semantic storage backend. It aims at collecting data from various sources - file indexing, the web, applications, etc, and linking them all together to form a cohesive map of data.
To know more about Nepomuk from a user's point of view, head over to the Nepomuk page on UserBase. To know more about the Nepomuk community and getting involved in Nepomuk, head over to Nepomuk page on Community. This page is dedicated to 3rd party documentation for Nepomuk.
The following links provide good reads for getting used to the Nepomuk system and its APIs.
As Nepomuk is highly dependent on its data in the RDF store and the used ontologies, one might consider to read up on RDF and the Nepomuk ontogies:
KDE TechBase 