WARNING: This server provides a static reference view of the NetKernel documentation. Links to dynamic content do not work. For the best experience we recommend you install NetKernel and view the documentation in the live system .

Endpoint
Name:jena.RDFQueryModelSELECT
Description:performs an RDQL query on a Jena model
Id:jena.RDFQueryModelSELECT
Category:accessor
Identifier Syntax

jena.RDFQueryModelSELECT is an accessor using Active URI syntax with the following base identifiers:

Base
active:jRDFQueryModelSELECT

and the following arguments: (for more details on argument passing details see here)

ArgumentRulesTypingDescription
operand
Optional
Representation (java.lang.Object)Model to select from
operator
Mandatory
Representation (java.lang.Object)SPARQL SELECT statement
model
Optional
Representation (java.lang.Object)flag to indicate return a model rather than XML/RDF
Request Verbs

The following verb is supported:

Verb
SOURCE
Response

The response representation of this accessor for SOURCE requests is unknown.

This accessor throws no documented exceptions.

Import Requirements

To use jena.RDFQueryModelSELECT accessor you must import the module urn:org:netkernel:rdf:jena:

<import>
  <uri>urn:org:netkernel:rdf:jena</uri>
</import>

The jRDFQueryModel accessor performs an RDQL query on a Jena model and returns the results as an XML results set. If a model argument is provided (with an arbitrary value) then the results will be returned as a IRepJenaModel.

The operator specifies the SPARQL SELECT query, for example

SELECT ?x
WHERE { ?x  "value" }

The XML form of the results looks like...

<sparql xmlns="http://www.w3.org/2005/sparql-results#">
  <head>
    <variable name="x" />
  </head>
  <results>
    <result>
      <binding name="x">
        <uri>http://www.1060.org/bugxter/</uri>
      </binding>
    </result>
    <result>
      <binding name="x">
        <uri>http://www.1060.org/forum/</uri>
      </binding>
    </result>
  </results>
</sparql>

Optional Operand Argument

If the operand argument is provided the query will be made against the operand model.

If the operand argument is omitted it is assumed that the query references a resource in the FROM part of the query statement. Referenced resources will be SOURCEd from the ROC domain so that querys can be made from ROC domain resources, as well as external HTTP resources (if the http client module is resolvable in context).

For example, active resources are supported like this:

SELECT ?s ?p ?o
FROM 
WHERE { ?x  "value" }