Hi Chimezie, good point - I had observed this problem in the past as well. I will add such an option to a future release.
Holger On Mar 31, 2009, at 2:53 PM, Chimezie Ogbuji wrote: > > Hello Scott. > > Sounds good. That works, Thanks! One comment though: > > I noticed the query that gets sent to the endpoint still includes the > FROM statement. For some services this might be problematic since > they may have a 'default' behavior (like the one I was targetting) > that actually tries to fetch the representation of an RDF graph from > that URI to use as the default graph for the query rather than ignore > a FROM IRI that points to itself. Luckily, I'm the author of the > SPARQL service I was testing this against, so I was just able to make > the appropriate change :) > > However, it might be best to have the option of where to send the > query be a function of the application and not embedded in the query > > -- Chimezie > > On Mar 27, 2:12 pm, Scott Henninger <[email protected]> > wrote: >> Chimezie; The best way to do this is through the SPARQL syntax >> itself. For example: >> >> SELECT ?child >> FROM <http://dbpedia.org/sparql> >> WHERE >> { <http://dbpedia.org/resource/Rose_Fitzgerald_Kennedy> >> <http://dbpedia.org/property/children> >> ?child >> >> } >> >> ...wherehttp://dbpedia.org/sparqlis the sparql endpoint. >> >> -- Scott >> >> On Mar 27, 12:40 pm, Chimezie Ogbuji <[email protected]> wrote: >> >>> Hello, excellent work with TopBraid. >> >>> I have a basic question on the SPARQL support. I have a live SPARQL >>> server with an endpoint that implements the SPARQL query protocol >>> and >>> would like to (if possible) use TopBraid to compose SPARQL queries >>> using the OWL associated with the RDF dataset served by the endpoint >>> (for autocompletion, etc..) and dispatch them against the endpoint >>> (i.e., not one of the database connections supported, but a *pure* >>> SPARL server). >> >>> It is not clear how this is done. I tried Import->SPARQL Endpoint >>> Connection and it asks for 3 things: >> >>> 1) file name (i'm guessing it is the file where the connection >>> information is stored) >>> 2) Base URI for imports (I'm not sure if this is the base uri for >>> the >>> OWL used to drive composition of SPARQL and if so, why the normal >>> base >>> URI mechanisms don't already cover this: URL of the OWL document, >>> xml:base in content, etc..) >>> 3) Endpoint URL >> >>> However, having done that , I'm not sure how to proceed with >>> composing >>> SPARQL queries to evaluate the defined SPARQL endpoint connection. >> >>> Thanks > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
