From KDE TechBase
    Other languages:
    • English

    Using ontology URIs in your code

    One often needs the URI of a specific class or a specific property in ones code. And not all ontologies are provided by the very convenient Soprano::Vocabulary namespace.

    The solution is rather simple: create your own vocabulary namespaces by using Soprano's own onto2vocabularyclass command line tool. It can generate convenient vocabulary namespaces for you. The Soprano documentation shows how to use it manually or even simpler with a simple CMake macro.

    Mind the Difference between QString and QUrl

    Nepomuk::Resource provides two constructors: one taking a QString as identifier or URI and one taking a QUrl.

    The latter one is really simple: the given URI is used as the resource URI. If the resource exists, its data is used, otherwise it will be created with exactly that URI.

    The QString one is a bit trickier. It will try to be clever about the parameter and see if it is a URI. If no resource with that URI (if it is a URI) exists, it is interpreted as an identifier (nao:identifier). Resource checks if a resource with that identifier exists. If so, its data is loaded, if not, a new resource with a random URI and that string as identifier is created.

    However, be aware that nothing is written to Nepomuk until the first writing call to Resource such as setProperty or addType.

    Debugging the created data

    Soprano provides a command line client to connect to the storage service. It's called sopranocmd. It provides all the features one needs to debug data. It is recommended that you only use sopranocmd for running queries.

    Running sopranocmd is cumbersome because of the large number of arguments it requires. This can be made simpler by adding the following alias -

    alias nepomukcmd="sopranocmd --socket `kde4-config --path socket`nepomuk-socket --model main --nrl"

    For example -

    # nepomukcmd query \
        "select ?r where { ?r nao:hasTag ?tag . \
                           ?tag nao:prefLabel 'foobar'^^xsd:string . }"

    Using Konqueror

    In the Nepomuk playground repository lives a KIO slave which can handle the nepomuk:/ protocol. It will display all properties of a Nepomuk resource including its links to other resources and the backlinks. This is a convenient way of looking at the Nepomuk data. The KIO slave even support removal of resources.

    Using NepomukShell

    NepomukShell is a maintenance and debugging tool, which lives in its own git repository at nepomukshell. It is a simple tool that let's one browse all resources in Nepomuk. Additionally it allows to create subclasses and properties and remove resources.

    Do only create subclasses and properties from PIMO classes and properties!

    Constructing SPARQL queries

    In most cases the Nepomuk Query API should be enough and prevent you from writing your own SPARQL which is hard to debug.

    Whenever doing something a bit fancier with Nepomuk one has to use SPARQL queries via

        ->executeQuery( myQueryString, 
                        Soprano::Query::QueryLanguageSparql );

    Constructing these queries can be a bit cumbersome since one has to use a lot of class and property URIs from different ontologies. Also literals have to be formatted according to the N3 syntax used in SPARQL. Luckily Soprano provides the necessary tools to do exactly that:
    Soprano::Node::resourceToN3, and
    Soprano::Node::literalToN3 take care of all formatting and percent-encoding you need. Using those methods the code to create queries might look ugly but the resulting queries are more likely to be correctly encoded and introduce less code duplication.

    Typically one would use QString::arg like so (be aware that the standard prefixes are NOT supported out-of-the-box as with sopranocmd):

    using namespace Soprano;
    QString myQuery
         = QString("select ?r where { "
                   "?r %1 ?v . "
                   "?v %2 %3 . }")

    This will create the same query we used above only using no hard-coded components whatsoever.

    Debugging virtuoso-t

    If virtuoso-t consumes a lot of CPU resources but there are no active queries analysis has to go a bit deeper. Virtuoso is started through Soprano with certain parameters which are set in a temporary ini-file (/tmp/virtuoso_XXXX.ini). Soprano needs to be modified manually to start Virtuoso with different parameters in the ini-file, e.g. to improve virtuoso-t's behaviour by modifying backends/virtuoso/virtuosocontroller.cpp (Soprano) and setting NumberOfBuffers to 40000 (line 344) and SchedulerInterval to 0 (line 350).

    After re-compiling soprano one has to attach gdb to virtuoso-t as soon as it starts consuming CPU and create a full threaded backtrace:

    set logging file /tmp/virtuoso-t.out
    set logging on
    thread apply all bt full

    Note: The above settings should only be used for debugging!