Projects/Nepomuk/QueryLibrary - Revision history

AnneW: Marked this version for translation

2012-12-12T13:38:31Z

Marked this version for translation

AnneW: Prepare for translation

2012-12-12T13:37:41Z

Prepare for translation

Vishesh at 13:09, 23 August 2012

2012-08-23T13:09:58Z

Vishesh at 13:07, 23 August 2012

2012-08-23T13:07:21Z

Vishesh: Created page with "Nepomuk provides a Query Library which is a part of the nepomuk-core library. It can be user to dynamically create queries. This Query Library eventually compiles the queries ..."

2012-08-23T13:06:30Z

Created page with "Nepomuk provides a Query Library which is a part of the nepomuk-core library. It can be user to dynamically create queries. This Query Library eventually compiles the queries ..."

New page

Nepomuk provides a Query Library which is a part of the nepomuk-core library. It can be user to dynamically create queries. This Query Library eventually compiles the queries into Sparql which is then run on our database - virtuoso.

It is recommended that you use the Query Library when you're searching for resources which have some direct properties. If the queries are too complex, maybe you should be directly using SPARQL. It all depends on your use case. The only advantage of using the QueryLibrary is that with improvements in the query library, your queries should get faster.

= Creating Queries =

The entire Query Library resides in the Nepomuk2::Query namespace. It consists of a number of terms which can be combined together to create larger terms. Eventually when you've have created the final term, you can pass it to <code>Nepomuk2::Query::Query</code> and [[Projects/Nepomuk/QueryingMethods| run the query]]

The different kinds of terms are -

* [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/classNepomuk2_1_1Query_1_1AndTerm.html AndTerm]
* [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/classNepomuk2_1_1Query_1_1OrTerm.html OrTerm]
* [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/classNepomuk2_1_1Query_1_1NegationTerm.html NegationTerm]
* [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/classNepomuk2_1_1Query_1_1ComparisonTerm.html ComparisionTerm]
* [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/classNepomuk2_1_1Query_1_1LiteralTerm.html LiteralTerm]
* [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/classNepomuk2_1_1Query_1_1ResourceTerm.html ResourceTerm]
* [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/classNepomuk2_1_1Query_1_1ResourceTypeTerm.html ResourceTypeTerm]

@@ Line 2: / Line 2: @@
 <translate>
-== The Query Library ==
+== The Query Library == <!--T:1-->
 '''Nepomuk''' provides a Query Library which is a part of the nepomuk-core library. It can be user to dynamically create queries. This Query Library eventually compiles the queries into Sparql which is then run on our database - virtuoso.
 It is recommended that you use the Query Library when you're searching for resources which have some direct properties. If the queries are too complex, maybe you should be directly using SPARQL. It all depends on your use case. The only advantage of using the QueryLibrary is that with improvements in the query library, your queries should get faster.
-== Creating Queries ==
+== Creating Queries == <!--T:4-->
 The entire Query Library resides in the Nepomuk2::Query namespace. It consists of a number of terms which can be combined together to create larger terms. Eventually when you've have created the final term, you can pass it to <tt>Nepomuk2::Query::Query</tt> and [[Projects/Nepomuk/QueryingMethods| run the query]]
 The different kinds of terms are -
 * [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/classNepomuk2_1_1Query_1_1AndTerm.html AndTerm]
 * [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/classNepomuk2_1_1Query_1_1OrTerm.html OrTerm]
@@ Line 22: / Line 27: @@
 * [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/classNepomuk2_1_1Query_1_1ResourceTypeTerm.html ResourceTypeTerm]
-=== Examples ===
+=== Examples === <!--T:8-->
 Imagine we wanted to find all files that are tagged with a certain tag:
 <syntaxhighlight lang="cpp">
 Nepomuk::Tag myTag = someFancyMethod();
 // term matching the tag
 Nepomuk::Query::ResourceTerm tagTerm( myTag );
 // term matching tagged resource
 Nepomuk::Query::ComparisonTerm term( Soprano::Vocabulary::NAO::hasTag(),
@@ Line 37: / Line 46: @@
                                       Nepomuk::Query::ComparisonTerm::Equal );
 // build the query
 Nepomuk::Query::Query query( term );
 </syntaxhighlight>
-=== Introspecting Queries ===
+=== Introspecting Queries === <!--T:14-->
 The <tt>Query</tt> class provides convenient methods to convert the query into its relevant sparql query, which can then easily be read. Additionally, it also provides a <tt>toSearchUrl</tt> method.
 * toSparqlQuery() - Creates a SPARQL query to be used in Soprano::Model::executeQuery
 * toSearchUrl() - Creates a URL that can be listed via KIO.
 [[Category:Documentation]]
 [[Category:Development]]
 [[Category:Tutorials]]
 </translate>

@@ Line 1: / Line 1: @@
-Nepomuk provides a Query Library which is a part of the nepomuk-core library. It can be user to dynamically create queries. This Query Library eventually compiles the queries into Sparql which is then run on our database - virtuoso.
+<languages />
 It is recommended that you use the Query Library when you're searching for resources which have some direct properties. If the queries are too complex, maybe you should be directly using SPARQL. It all depends on your use case. The only advantage of using the QueryLibrary is that with improvements in the query library, your queries should get faster.
-= Creating Queries =
+== Creating Queries ==
-The entire Query Library resides in the Nepomuk2::Query namespace. It consists of a number of terms which can be combined together to create larger terms. Eventually when you've have created the final term, you can pass it to <code>Nepomuk2::Query::Query</code> and [[Projects/Nepomuk/QueryingMethods| run the query]]
+The entire Query Library resides in the Nepomuk2::Query namespace. It consists of a number of terms which can be combined together to create larger terms. Eventually when you've have created the final term, you can pass it to <tt>Nepomuk2::Query::Query</tt> and [[Projects/Nepomuk/QueryingMethods| run the query]]
 The different kinds of terms are -
@@ Line 36: / Line 41: @@
 </syntaxhighlight>
-== Introspecting Queries ==
+=== Introspecting Queries ===
-The <code>Query</code> class provides convenient methods to convert the query into its relevant sparql query, which can then easily be read. Additionally, it also provides a <code>toSearchUrl</code> method.
+The <tt>Query</tt> class provides convenient methods to convert the query into its relevant sparql query, which can then easily be read. Additionally, it also provides a <tt>toSearchUrl</tt> method.
 * toSparqlQuery() - Creates a SPARQL query to be used in Soprano::Model::executeQuery
 * toSearchUrl() - Creates a URL that can be listed via KIO.

← Older revision		Revision as of 13:09, 23 August 2012
Line 35:		Line 35:
	Nepomuk::Query::Query query( term );		Nepomuk::Query::Query query( term );
	</syntaxhighlight>		</syntaxhighlight>
		+
		+	== Introspecting Queries ==
		+
		+	The <code>Query</code> class provides convenient methods to convert the query into its relevant sparql query, which can then easily be read. Additionally, it also provides a <code>toSearchUrl</code> method.
		+
		+	* toSparqlQuery() - Creates a SPARQL query to be used in Soprano::Model::executeQuery
		+	* toSearchUrl() - Creates a URL that can be listed via KIO.

← Older revision		Revision as of 13:07, 23 August 2012
Line 16:		Line 16:
	* [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/classNepomuk2_1_1Query_1_1ResourceTerm.html ResourceTerm]		* [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/classNepomuk2_1_1Query_1_1ResourceTerm.html ResourceTerm]
	* [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/classNepomuk2_1_1Query_1_1ResourceTypeTerm.html ResourceTypeTerm]		* [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/classNepomuk2_1_1Query_1_1ResourceTypeTerm.html ResourceTypeTerm]
		+
		+	=== Examples ===
		+
		+	Imagine we wanted to find all files that are tagged with a certain tag:
		+
		+	<syntaxhighlight lang="cpp">
		+	Nepomuk::Tag myTag = someFancyMethod();
		+
		+	// term matching the tag
		+	Nepomuk::Query::ResourceTerm tagTerm( myTag );
		+
		+	// term matching tagged resource
		+	Nepomuk::Query::ComparisonTerm term( Soprano::Vocabulary::NAO::hasTag(),
		+	tagTerm,
		+	Nepomuk::Query::ComparisonTerm::Equal );
		+
		+	// build the query
		+	Nepomuk::Query::Query query( term );
		+	</syntaxhighlight>