Re: [topbraid-users] Re: import SPARQL endpoint
Hello Paul, I found where the bug was. For default graph URI and named graph URI, our code generated an empty string literal, which got passed into the SPARQL endpoint call. As a fix, the code is now filtering out empty string literals to prevent them being passed in the call. This fixes both of the issues you encountered - calling Sesame SPARQL endpoint with a default graph URI and calling the same endpoint with no graph URIs at all - i.e. returning all triples in the repository. The fix will be most likely available in the TBC 3.6.2 release. Gokhan On Mon, Aug 13, 2012 at 2:02 PM, PaulZH p...@proxml.be wrote: Hi Gokhan, 2 remarks in this context: a) in TBC's user interface the field for indicating the default graph is indicated as optional b) Sesame can be used as a triple store not using the fourth slot for indicating the graph the triple belongs, e.g. having the null context. Hence http://localhost:/openrdf-sesame/repositories/OWMS?query=SELECT++*%0AWHERE%0A++%7B+%3Fs+%3Chttp%3A%2F%2Fwww.w3.org%2F1999%2F02%2F22-rdf-syntax-ns%23type%3E+%3Fo+%7D%0ALIMIT+++1%0A *default-graph-uri=* as generated by TBC is not working where http://localhost:/openrdf-sesame/repositories/OWMS?query=SELECT++*%0AWHERE%0A++%7B+%3Fs+%3Chttp%3A%2F%2Fwww.w3.org%2F1999%2F02%2F22-rdf-syntax-ns%23type%3E+%3Fo+%7D%0ALIMIT+++1%0A does But I have to agree that the differences between tools in what the default graph is and does, make this a rather messy chapter. Paul On Monday, August 13, 2012 12:38:17 AM UTC+2, Gokhan Soydan wrote: Paul, This looks strange although I think at least the default graph URI should have been provided. Gokhan On Mon, Aug 13, 2012 at 1:37 AM, Gokhan Soydan gso...@topquadrant.comwrote: Paul, This looks strange although at least the default graph URI Gokhan On Thu, Aug 9, 2012 at 1:00 PM, PaulZH pa...@proxml.be wrote: Additional info on this issue. When not filling in the optional connection parameters 'Default Graph URI' and 'Named Graph URI' TBC composes following query to the endpoint. GET http://localhost:3030/ds/**query?query=SELECT++*%0AWHERE%** 0A++%7B+%3Fs+%3Chttp%3A%2F%**2Fwww.w3.org%2F1999%2F02%2F22-** rdf-syntax-ns%23type%3E+%3Fo+%**7D%0ALIMIT+++1%0Ahttp://localhost:3030/ds/query?query=SELECT++*%0AWHERE%0A++%7B+%3Fs+%3Chttp%3A%2F%2Fwww.w3.org%2F1999%2F02%2F22-rdf-syntax-ns%23type%3E+%3Fo+%7D%0ALIMIT+++1%0A; *default-graph-uri=named-graph-uri=* In the case of fuseki it generates warnings: 11:52:47 WARN Fuseki :: SPARQL Query: Unrecognize request parameter (ignored): default-graph-uri 11:52:47 WARN Fuseki :: SPARQL Query: Unrecognize request parameter (ignored): named-graph-uri But in the case of Sesame I get: HTTP/1.1 400 Bad Request Content-Length: 31 Server: Apache-Coyote/1.1 Content-Type: text/plain;charset=UTF-8 Content-Language: en-US Date: Thu, 09 Aug 2012 09:44:50 GMT Connection: close Illegal URI for default graph. Paul -- -- 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 topbrai...@googlegroups.**com To unsubscribe from this group, send email to topbraid-user...@**googlegroups.com For more options, visit this group at http://groups.google.com/**group/topbraid-users?hl=enhttp://groups.google.com/group/topbraid-users?hl=en -- -- 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 topbraid-users@googlegroups.com To unsubscribe from this group, send email to topbraid-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en -- -- 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 topbraid-users@googlegroups.com To unsubscribe from this group, send email to topbraid-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en
Re: [topbraid-users] Re: import SPARQL endpoint
Hi Gokhan, 2 remarks in this context: a) in TBC's user interface the field for indicating the default graph is indicated as optional b) Sesame can be used as a triple store not using the fourth slot for indicating the graph the triple belongs, e.g. having the null context. Hence http://localhost:/openrdf-sesame/repositories/OWMS?query=SELECT++*%0AWHERE%0A++%7B+%3Fs+%3Chttp%3A%2F%2Fwww.w3.org%2F1999%2F02%2F22-rdf-syntax-ns%23type%3E+%3Fo+%7D%0ALIMIT+++1%0A *default-graph-uri=* as generated by TBC is not working where http://localhost:/openrdf-sesame/repositories/OWMS?query=SELECT++*%0AWHERE%0A++%7B+%3Fs+%3Chttp%3A%2F%2Fwww.w3.org%2F1999%2F02%2F22-rdf-syntax-ns%23type%3E+%3Fo+%7D%0ALIMIT+++1%0A does But I have to agree that the differences between tools in what the default graph is and does, make this a rather messy chapter. Paul On Monday, August 13, 2012 12:38:17 AM UTC+2, Gokhan Soydan wrote: Paul, This looks strange although I think at least the default graph URI should have been provided. Gokhan On Mon, Aug 13, 2012 at 1:37 AM, Gokhan Soydan gso...@topquadrant.comjavascript: wrote: Paul, This looks strange although at least the default graph URI Gokhan On Thu, Aug 9, 2012 at 1:00 PM, PaulZH pa...@proxml.be javascript:wrote: Additional info on this issue. When not filling in the optional connection parameters 'Default Graph URI' and 'Named Graph URI' TBC composes following query to the endpoint. GET http://localhost:3030/ds/query?query=SELECT++*%0AWHERE%0A++%7B+%3Fs+%3Chttp%3A%2F%2Fwww.w3.org%2F1999%2F02%2F22-rdf-syntax-ns%23type%3E+%3Fo+%7D%0ALIMIT+++1%0A; *default-graph-uri=named-graph-uri=* In the case of fuseki it generates warnings: 11:52:47 WARN Fuseki :: SPARQL Query: Unrecognize request parameter (ignored): default-graph-uri 11:52:47 WARN Fuseki :: SPARQL Query: Unrecognize request parameter (ignored): named-graph-uri But in the case of Sesame I get: HTTP/1.1 400 Bad Request Content-Length: 31 Server: Apache-Coyote/1.1 Content-Type: text/plain;charset=UTF-8 Content-Language: en-US Date: Thu, 09 Aug 2012 09:44:50 GMT Connection: close Illegal URI for default graph. Paul -- -- 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 topbrai...@googlegroups.com javascript: To unsubscribe from this group, send email to topbraid-user...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en -- -- 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 topbraid-users@googlegroups.com To unsubscribe from this group, send email to topbraid-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en
Re: [topbraid-users] Re: import SPARQL endpoint
Paul, This looks strange although at least the default graph URI Gokhan On Thu, Aug 9, 2012 at 1:00 PM, PaulZH p...@proxml.be wrote: Additional info on this issue. When not filling in the optional connection parameters 'Default Graph URI' and 'Named Graph URI' TBC composes following query to the endpoint. GET http://localhost:3030/ds/query?query=SELECT++*%0AWHERE%0A++%7B+%3Fs+%3Chttp%3A%2F%2Fwww.w3.org%2F1999%2F02%2F22-rdf-syntax-ns%23type%3E+%3Fo+%7D%0ALIMIT+++1%0A; *default-graph-uri=named-graph-uri=* In the case of fuseki it generates warnings: 11:52:47 WARN Fuseki :: SPARQL Query: Unrecognize request parameter (ignored): default-graph-uri 11:52:47 WARN Fuseki :: SPARQL Query: Unrecognize request parameter (ignored): named-graph-uri But in the case of Sesame I get: HTTP/1.1 400 Bad Request Content-Length: 31 Server: Apache-Coyote/1.1 Content-Type: text/plain;charset=UTF-8 Content-Language: en-US Date: Thu, 09 Aug 2012 09:44:50 GMT Connection: close Illegal URI for default graph. Paul -- -- 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 topbraid-users@googlegroups.com To unsubscribe from this group, send email to topbraid-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en -- -- 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 topbraid-users@googlegroups.com To unsubscribe from this group, send email to topbraid-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en
Re: [topbraid-users] Re: import SPARQL endpoint
Paul, This looks strange although I think at least the default graph URI should have been provided. Gokhan On Mon, Aug 13, 2012 at 1:37 AM, Gokhan Soydan gsoy...@topquadrant.comwrote: Paul, This looks strange although at least the default graph URI Gokhan On Thu, Aug 9, 2012 at 1:00 PM, PaulZH p...@proxml.be wrote: Additional info on this issue. When not filling in the optional connection parameters 'Default Graph URI' and 'Named Graph URI' TBC composes following query to the endpoint. GET http://localhost:3030/ds/query?query=SELECT++*%0AWHERE%0A++%7B+%3Fs+%3Chttp%3A%2F%2Fwww.w3.org%2F1999%2F02%2F22-rdf-syntax-ns%23type%3E+%3Fo+%7D%0ALIMIT+++1%0A; *default-graph-uri=named-graph-uri=* In the case of fuseki it generates warnings: 11:52:47 WARN Fuseki :: SPARQL Query: Unrecognize request parameter (ignored): default-graph-uri 11:52:47 WARN Fuseki :: SPARQL Query: Unrecognize request parameter (ignored): named-graph-uri But in the case of Sesame I get: HTTP/1.1 400 Bad Request Content-Length: 31 Server: Apache-Coyote/1.1 Content-Type: text/plain;charset=UTF-8 Content-Language: en-US Date: Thu, 09 Aug 2012 09:44:50 GMT Connection: close Illegal URI for default graph. Paul -- -- 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 topbraid-users@googlegroups.com To unsubscribe from this group, send email to topbraid-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en -- -- 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 topbraid-users@googlegroups.com To unsubscribe from this group, send email to topbraid-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en
Re: [topbraid-users] Re: import SPARQL endpoint
Additional info on this issue. When not filling in the optional connection parameters 'Default Graph URI' and 'Named Graph URI' TBC composes following query to the endpoint. GET http://localhost:3030/ds/query?query=SELECT++*%0AWHERE%0A++%7B+%3Fs+%3Chttp%3A%2F%2Fwww.w3.org%2F1999%2F02%2F22-rdf-syntax-ns%23type%3E+%3Fo+%7D%0ALIMIT+++1%0A; *default-graph-uri=named-graph-uri=* In the case of fuseki it generates warnings: 11:52:47 WARN Fuseki :: SPARQL Query: Unrecognize request parameter (ignored): default-graph-uri 11:52:47 WARN Fuseki :: SPARQL Query: Unrecognize request parameter (ignored): named-graph-uri But in the case of Sesame I get: HTTP/1.1 400 Bad Request Content-Length: 31 Server: Apache-Coyote/1.1 Content-Type: text/plain;charset=UTF-8 Content-Language: en-US Date: Thu, 09 Aug 2012 09:44:50 GMT Connection: close Illegal URI for default graph. Paul -- -- 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 topbraid-users@googlegroups.com To unsubscribe from this group, send email to topbraid-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en
Re: [topbraid-users] Re: import SPARQL endpoint
OK, have to wait then.
In the meantime, you can use the Sesame connector to get to Sesame
data. This has the advantage of being more efficient because it calls
the APIs directly instead of going through the serialization process
of the endpoint protocol.
Was looking into this road, since there are some issues with the Sesame
connector.
Hopefully also being addressed in 3.6.2.
-- Scott
On Jun 29, 2:35 am, PaulZH p...@proxml.be wrote:
Scott,
Unfortunatily indicating the default graph for a Sesame connection gives
the same error: No graph defined at the endpoint
Paul
On Friday, June 29, 2012 4:02:22 AM UTC+2, Scott Henninger wrote:
Paul; Try specifying the graph you are trying to query in Sesame in
the Default graph area for the connector. I.e. sml:defaultGraphURI.
If you want to get to the default graph for your repository, then it
will be whatever URI Sesame knows the default graph as.
-- Scott
On Jun 28, 6:52 am, PaulZH p...@proxml.be wrote:
Scott,
It is an announced new feature of TBCME 3.6.1, see release notes:
TopBraid Composer - Maestro Edition
- Feature: SPARQL end point connector was brought back with
authentication support.
It's about importing (cf. import menuitem), not about using this from
SPARQLMotion.
From the Help file.
Import SPARQL Endpoints
This feature is available in TopBraid Composer - Maestro Edition
http://topquadrant.com/products/TB_Composer.html#maestroonly.
You can import SPARQL endpoints in TopBraid Composer - Maestro Edition.
Paul
On Wednesday, June 27, 2012 9:55:30 PM UTC+2, Scott Henninger wrote:
Paul; What version of TBC or TBL are you using? Currently,
sml:ImportSPARQLEndpoint is not a supported module (see Help
Reference SPARQLMotion Module Library Reference). We are looking to
create new features for using SPARQL endpoints in a future release of
TBC. but for now, it is sufficient to use the SERVICE keyword in an
ApplyConstruct, PerformUpdate, or SELECT query modules.
-- Scott
On Jun 27, 10:23 am, PaulZH p...@proxml.be wrote:
Hi,
I connected succesfully to a Fuseki SPARQL endpoint using following
settings:
[]rdf:type sml:ImportSPARQLEndpoint ;
sml:baseURI http://import.org/fuseki; ;
sml:defaultGraphURI ;
sml:imports () ;
sml:namedGraphURI ;
sml:url http://localhost:3030/ds/query; ;
sml:userName .
Now I want to do the same for a Sesame endpoint:
[]rdf:type sml:ImportSPARQLEndpoint ;
sml:baseURI http://import.org/sesame; ;
sml:defaultGraphURI ;
sml:imports () ;
sml:namedGraphURI ;
sml:url
http://localhost:/openrdf-sesame/repositories/OWMS;
;
sml:userName .
but I get following error:
Reason:
java.io.IOException: java.lang.Exception: No graph defined at the
endpoint
defined by the file L/Test/tosesame.sparqlep
I am able to query this SPARQL endpoint from outside TBC and from
within
TBC using the SERVICE keyword
SELECT *
WHERE {
SERVICE http://localhost:/openrdf-sesame/repositories/OWMS
{ ?subject rdfs:subClassOf ?object .}
}
-- 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
topbraid-users@googlegroups.com
To unsubscribe from this group, send email to
topbraid-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
Kind Regards,
Paul Hermans
-
ProXML bvba
XML and OWL/RDF services
(w) www.proxml.be
(b) experiences and opinions
(e) p...@proxml.be
(t) +32 15 23 00 76
(m) +32 473 66 03 20
Narcisweg 17
3140 Keerbergen
Belgium
-- 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
topbraid-users@googlegroups.com
To unsubscribe from this group, send email to
topbraid-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
