Depending on the needs of your application you may need to directly run sparql queries.

Depending on the needs of your application you may need to directly run sparql queries.

−

= Running Sparql Queries =

+

<!--T:3-->

−

Nepomuk uses one main [http://soprano.sourceforge.net/apidox/stable/classSoprano_1_1Model.html Soprano model] which is accessed through the [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/classNepomuk_1_1ResourceManager.html ResourceManager]:

+

'''Nepomuk''' uses one main [http://soprano.sourceforge.net/apidox/stable/classSoprano_1_1Model.html Soprano model] which is accessed through the [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/classNepomuk_1_1ResourceManager.html ResourceManager]:

When writing SPARQL queries, according to the standard one needs to prepend the queries with the prefixes that have been used. For example -

When writing SPARQL queries, according to the standard one needs to prepend the queries with the prefixes that have been used. For example -

<syntaxhighlight lang="text">

<syntaxhighlight lang="text">

Line 27:

Line 40:

</syntaxhighlight>

</syntaxhighlight>

+

<!--T:9-->

+

When running queries in Nepomuk, you do not need to explicitly add the prefix. The prefix will automatically be added by the storage service. In the future we will try to make virtuoso automatically understand all prefixes.

−

When running queries in Nepomuk, you do not need to explicitly add the prefix. The prefix will automatically be added by the storage service.

+

=== Full Text Indexing === <!--T:10-->

−

== Full Text Indexing ==

+

<!--T:11-->

−

Nepomuk depends on [http://soprano.sourceforge.net/apidox/trunk/soprano_backend_virtuoso.html Virtuoso] for data storage. Virtuoso brings a lot of nice [http://docs.openlinksw.com/virtuoso/rdfsparql.html#sparqlextensions extensions to SPARQL]. Most importantly the full text search which is used through the artificial ''bif:contains'' property.

+

'''Nepomuk''' depends on [http://soprano.sourceforge.net/apidox/trunk/soprano_backend_virtuoso.html Virtuoso] for data storage. '''Virtuoso''' brings a lot of nice [http://docs.openlinksw.com/virtuoso/rdfsparql.html#sparqlextensions extensions to SPARQL]. Most importantly the full text search which is used through the artificial ''bif:contains'' property.

+

<!--T:12-->

This allows to combine graph queries with full text queries in a nice way:

This allows to combine graph queries with full text queries in a nice way:

+

<!--T:13-->

<syntaxhighlight lang="text">

<syntaxhighlight lang="text">

select ?r where { ?r nao:prefLabel ?label .

select ?r where { ?r nao:prefLabel ?label .

Line 40:

Line 57:

</syntaxhighlight>

</syntaxhighlight>

+

<!--T:14-->

The query above will find any resources that contain ''nepomuk'' in their label.

The query above will find any resources that contain ''nepomuk'' in their label.

+

<!--T:15-->

Of course wildcards are supported, too. However, be aware that when using wildcards the expression itself needs to be enclosed in quotes as follows:

Of course wildcards are supported, too. However, be aware that when using wildcards the expression itself needs to be enclosed in quotes as follows:

+

<!--T:16-->

<syntaxhighlight lang="text">

<syntaxhighlight lang="text">

select ?r where { ?r nao:prefLabel ?label .

select ?r where { ?r nao:prefLabel ?label .

Line 49:

Line 69:

</syntaxhighlight>

</syntaxhighlight>

−

+

<!--T:17-->

Please note the virtuoso '''requires a minimum of 4 leading characters''' in order to use wildcards.

Please note the virtuoso '''requires a minimum of 4 leading characters''' in order to use wildcards.

When running queries in Nepomuk, you do not need to explicitly add the prefix. The prefix will automatically be added by the storage service. In the future we will try to make virtuoso automatically understand all prefixes.

Full Text Indexing

Nepomuk depends on Virtuoso for data storage. Virtuoso brings a lot of nice extensions to SPARQL. Most importantly the full text search which is used through the artificial bif:contains property.

This allows to combine graph queries with full text queries in a nice way: