I still have this issue with version 4.1. Paul
On Wednesday, August 15, 2012 6:00:29 PM UTC+2, Gokhan Soydan wrote: > > 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 <pa...@proxml.be <javascript:>>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:8888/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:8888/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.com>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> 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&<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 >>>>> >>>>> 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=en<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 >> 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
