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.
This page is dedicated to third party documentation for Nepomuk. To know more about Nepomuk from a user's point of view, head over to the Nepomuk page on UserBase. Or to know more about the Nepomuk community and getting involved in Nepomuk, head over to the Nepomuk Community Page.
The following links provide good reads for getting used to the Nepomuk system and its APIs.
- Development Tutorials
- Nepomuk Tips and Tricks
- Soprano (RDF storage) API
- Using the Nepomuk Resource Code generator and the Soprano Ontology class generator in cmake
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:
If you're just getting started with Nepomuk and want to know a quick way to fetch some data.
This section includes more in-depth articles on how manage the data in Nepomuk. As a starting point you should probably open up the Nepomuk API Documentation. It is generally more up to date than the articles mentioned below.
As you advance into Nepomuk, you'll want to move beyond just fetching and pushing data and will want to query Nepomuk for specialized data. One can query Nepomuk is many different ways, the important part is to optimize your queries and make sure they run well on production systems where the database sizes may way very large.
If you're looking to get more involved with Nepomuk development process, you should probably need to need to figure out our basic architecture and where you can find all the relevant code.
When you decide to dig even deeper.
Subpages of Projects/Nepomuk
- Projects/Nepomuk/Qualified Relations Idea