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
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
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
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
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
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
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
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
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,
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
10 matches
Mail list logo
