Difference between revisions of "Projects/Nepomuk/SparqlQueries"

Jump to: navigation, search
(Sparql Prefixes)
(Prepare for translation)
Line 1: Line 1:
 +
<languages />
 +
<translate>
 +
 +
== Running Sparql Queries ==
 +
 
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 =
+
'''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]:
+
  
 
<syntaxhighlight lang="cpp-qt">
 
<syntaxhighlight lang="cpp-qt">
Line 21: Line 25:
  
  
== Sparql Prefixes ==
+
=== Sparql Prefixes ===
 +
 
 
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 32:
 
select ?r ?name where { ?r a nco:Contact . ?r nco:fullname ?name . }
 
select ?r ?name where { ?r a nco:Contact . ?r nco:fullname ?name . }
 
</syntaxhighlight>
 
</syntaxhighlight>
 
  
 
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. In the future we will try to make virtuoso automatically understand all prefixes.
  
== Full Text Indexing ==
+
=== Full Text Indexing ===
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.  
  
 
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:
Line 49: Line 54:
 
                   ?label bif:contains "'nepomuk*'" . }
 
                   ?label bif:contains "'nepomuk*'" . }
 
</syntaxhighlight>
 
</syntaxhighlight>
 
  
 
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.
 +
 +
[[Category:Documentation]]
 +
[[Category:Development]]
 +
[[Category:Tutorials]]
 +
</translate>

Revision as of 14:42, 12 December 2012

Other languages:English 100%

Running Sparql Queries

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

Nepomuk uses one main Soprano model which is accessed through the ResourceManager:

    Soprano::Model* model = Nepomuk::ResourceManager::instance()->mainModel();


The queries can be run via this model -

    QString query = QString::fromLatin1("select ?r where { ?r a nco:Contact . }");
    Soprano::Model* model = Nepomuk2::ResourceManager::instance()->mainModel();
    Soprano::QueryResultIterator it = model->executeQuery( query, Soprano::Query::QueryLanguageSparql );
 
    while( it.next() ) {
        kDebug() << it["r"].uri();
    }


Sparql Prefixes

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

PREFIX nco: <http://www.semanticdesktop.org/ontologies/2007/03/22/nco#> .
select ?r ?name where { ?r a nco:Contact . ?r nco:fullname ?name . }

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:

select ?r where { ?r nao:prefLabel ?label .
                  ?label bif:contains 'nepomuk' . }

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

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

select ?r where { ?r nao:prefLabel ?label .
                  ?label bif:contains "'nepomuk*'" . }

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


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal