TopBraid Composer > User Interface Overview> SPARQL View Where is that information at? Is it in a pdf or on the webpage somewhere.
On May 29, 3:43 pm, Scott Henninger <[email protected]> wrote: > Matt; On the first, this has been reported in this forum (I believe > the post/response was hijacked so it is hard to find). It's a known > problem that will be fixed in the next release. The workaround is as > you state. > > On the second, Composer does have the means to build a query library. > See TopBraid Composer > User Interface Overview> SPARQL View and > scroll down to Query Libraries. > > -- Scott > > On May 29, 3:31 pm, Matt <[email protected]> wrote: > > > BUG 1: Changing a SPARQL query in the SPARQL View with Reasoning. > > > I have the button next to the "Execute SPARQL" button called "Use > > Currently Configured Inferences" pressed on the SPARQL view. Next, I > > modify the text in the "Query Editor". I get a > > "java.lang.NullPointerException" in the very bottom of Eclipse in the > > "status bar". There is no entry in the Error Log. I can not execute > > the new sparql query unless I: > > 1) Unclick "Use Currently Configured Inferences" > > 2) Cut and Paste the sparql query to "reset" things. > > 3) Click "Use Currently Configured Inferences" > > 4) Click "Execute SPARQL" > > > BUG 2: Close SPARQL View when all models are closed. > > > If I am in the TBC perspective in Eclipse, and I close all models; > > then it closes all SPARQL Views and opens up the default one. This > > causes all my sparql queries to be lost. Indeed, when the last model > > is closed most of the views close. I consider this a bug, because: > > (1) TBC doesn't support 2 models with the same base URI to be open at > > the same time; (2) If I close leave at least one model open, even if > > it isn't the same model that the query was done on, the SPARQL View > > remains; (3) TBC does't let you save common sparql queries even though > > the sparql queries can be uploaded to SPARQLpedia... > > > USE CASE: We find our selves needing to perform reasoning on models > > that are located on a backend server (Allegrograph/JenaDB/Oracle/ > > etc). Often we have to export those models to the file system to run > > reasoning on them locally. Essentially "caching" all of the results > > locally. Then, when we want to modify or interact with the model > > somehow, we have to close the reasoned filesystem version and open > > back up the backend server version. If I forget to leave up a random > > model, all my queries and such get wiped out. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. 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-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
