I had moved on to other issues.  I just tried this again (with BigOWLIM), 
and I still see only the "base" triples, not any of mine.  (They do appear 
in the Sesame Workbench).

Jim




From:
PaulZH <[email protected]>
To:
TopBraid Composer Users <[email protected]>
Date:
10/05/2009 06:16 AM
Subject:
[tbc-users] Problem connecting to a Sesame 2 remote repository
Sent by:
[email protected]




Having successfully Sesame 2.2.4 running on localhost.
Created a repository, loaded some triples which I can see and query in
the Sesame Workbench.

Connecting now from TBC-ME 3.1.1 using the wizard.
Using Sesame's service URL I'm able to fetch the list of repositories,
so I think the connection works.
Choosing a repository then opens TBC, but no custom triples to be seen
or found.

A similar issue was reported by James A Miller end of May, but I was
not able to find more info.

>I am able to successfully connect to the Sesame 2 remote repository, but
>I don't see triples.  I don't get any error messages.  I was able
>to Fetch Repositories successfully--my store was in the list.

>I ran a SELECT * WHERE {?a ?b ?c} query, and I get results--but only the
>standard OWL, RDF, XSD  triples:  none of my 'custom' triples that I see
>in the Sesame workbench.

Paul



The following line is added for your protection and will be used for 
analysis if this message is reported as spam: (Raytheon Analysis: 
IP=209.85.221.140; 
e-from=grbounce--o7mwauaaadwl_g2bqlyhjkrnqovtno4=james_a_miller=raytheon....@googlegroups.com;
 
[email protected]; date=Oct 5, 2009 9:31:40 AM; subject=[tbc-users] 
Problem connecting to a Sesame 2 remote repository)


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to