On 6/27/2012 19:20, PaulZH wrote:
Thanks Holger for the clarification.
Indeed, it is paging that I'm after.
Any suggestion for a possible approach in TBCME is welcome.
If you're OK with the usual SPARQL result set format (e.g. in JSON) then
you could use the built-in SPARQL end point and construct the query
string (with LIMIT and OFFSET) by hand as a string. If you want more
flexibility in the output, e.g. a custom JSON for a grid component, then
SWP can be used. I have just added a paragraph on this to the SWP online
help
*Query modifiers (Advanced Topic):* SWP supports four system properties
|ui:queryLimit|, |ui:queryOffset|, |ui:queryOrderBy| and
|ui:queryOrderByDir| that can be used to modify the SELECT queries found
within the same surrounding element. They can be used to specify values
for the SPARQL keywords |LIMIT|, |OFFSET| and |ORDER BY| that must be
fixed values in standard SPARQL syntax. An example use case of these
properties is callbacks for user interface components that require
paging through large result sets.
Holger
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary
Network (EVN), TopBraid Composer, TopBraid Live,
TopBraid Ensemble, SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
