Projects/Nepomuk: Difference between revisions

From KDE TechBase
(Move away from Basic and Advanced)
(Added tag lines)
Line 7: Line 7:
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.
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 3rd party documentation for Nepomuk. To know more about Nepomuk from a user's point of view, head over to the [http://userbase.kde.org/Nepomuk Nepomuk page on UserBase]. Or to know more about the Nepomuk community and getting involved in Nepomuk, head over to the [http://community.kde.org/Projects/Nepomuk Nepomuk Community Page].
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 [http://userbase.kde.org/Nepomuk Nepomuk page on UserBase]. Or to know more about the Nepomuk community and getting involved in Nepomuk, head over to the [http://community.kde.org/Projects/Nepomuk Nepomuk Community Page].
 
== Documentation ==
 
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/TipsAndTricks|Nepomuk Tips and Tricks]]
*
* [http://soprano.sourceforge.net/apidox/trunk/index.html Soprano (RDF storage) API]
* [http://trueg.wordpress.com/2009/06/02/nepomuk-and-some-cmake-magic/ 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:
* [http://www.w3.org/TR/REC-rdf-syntax/ RDF Primer]
* [http://www.semanticdesktop.org/ontologies Nepomuk Ontologies]
* [http://dev.nepomuk.semanticdesktop.org/wiki/OntologyMaintenance Experimental Nepomuk Ontologies and Ideas for new ones]
 
=== Introductory Material ===
If you're just getting started with Nepomuk and want to know a quick way to fetch some data.


== Introduction ==
* [[Development/Tutorials/Metadata/Nepomuk/Quickstart| Quick Start]]
* [[Development/Tutorials/Metadata/Nepomuk/Quickstart| Quick Start]]
* [[Projects/Nepomuk/OntologyBasics| Basic Ontology concepts]]
* [[Projects/Nepomuk/OntologyBasics| Basic Ontology concepts]]


== Managing Data ==
=== Managing Data ===
* [[Projects/Nepomuk/Resources| Resources]]
This section includes more in-depth articles on how manage the data in Nepomuk. As a starting point you should probably open up the [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/index.html Nepomuk API Documentation]. It is generally more up to date than the articles mentioned below.
 
* [[Projects/Nepomuk/Resources| Managing Resources]]
* [[Projects/Nepomuk/ResourceWatcher| Monitoring Changes]]
* [[Projects/Nepomuk/ResourceWatcher| Monitoring Changes]]
* [[Projects/Nepomuk/BulkChanges| Bulk Changes]]
* [[Projects/Nepomuk/BulkChanges| Bulk Changes]]
* [[Projects/Nepomuk/DataFeeders| Data Feeders]]
* [[Projects/Nepomuk/DataFeeders| Data Feeders]]


== Querying ==
=== Querying ===
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.
 
* [[Projects/Nepomuk/QueryingMethods| Different ways to Query Nepomuk]]
* [[Projects/Nepomuk/QueryingMethods| Different ways to Query Nepomuk]]
* [[Projects/Nepomuk/QueryLibrary| Nepomuk Query Library]]
=== Architectural Overview ===
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.


== Architectural Overview ==
* [[Projects/Nepomuk/Repositories| Nepomuk Repositories]]
* [[Projects/Nepomuk/Repositories| Nepomuk Repositories]]
* [[Projects/Nepomuk/ComponentOverview| Nepomuk Architectural Overview]]
* [[Projects/Nepomuk/ComponentOverview| Nepomuk Architectural Overview]]


== Nepomuk Internals ==
=== Nepomuk Internals ===
When you decide to dig even deeper.
 
* [[Projects/Nepomuk/GraphConcepts| Graph handling]]
* [[Projects/Nepomuk/GraphConcepts| Graph handling]]
* [[Projects/Nepomuk/VirtuosoInternal| Virtuoso Internals]]
* [[Projects/Nepomuk/VirtuosoInternal| Virtuoso Internals]]
* [[Projects/Nepomuk/OntologyExtention| Extending the Ontologies]]
* [[Projects/Nepomuk/OntologyExtention| Extending the Ontologies]]


== Miscellaneous ==
=== Miscellaneous ===
* [[Projects/Nepomuk/Nepomuk2Port| Porting to Nepomuk2]]
* [[Projects/Nepomuk/Nepomuk2Port| Porting to Nepomuk2]]
== Documentation ==
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/TipsAndTricks|Nepomuk Tips and Tricks]]
* [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://trueg.wordpress.com/2009/06/02/nepomuk-and-some-cmake-magic/ 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:
* [http://www.w3.org/TR/REC-rdf-syntax/ RDF Primer]
* [http://www.semanticdesktop.org/ontologies Nepomuk Ontologies]
* [http://dev.nepomuk.semanticdesktop.org/wiki/OntologyMaintenance Experimental Nepomuk Ontologies and Ideas for new ones]


== Subpages of {{FULLPAGENAME}}==
== Subpages of {{FULLPAGENAME}}==
{{Special:PrefixIndex/{{FULLPAGENAME}}/}}
{{Special:PrefixIndex/{{FULLPAGENAME}}/}}

Revision as of 12:14, 23 August 2012


About Nepomuk

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.

Documentation

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:

Introductory Material

If you're just getting started with Nepomuk and want to know a quick way to fetch some data.

Managing 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.

Querying

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.

Architectural Overview

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.

Nepomuk Internals

When you decide to dig even deeper.

Miscellaneous

Subpages of Projects/Nepomuk