I am using Sesame 2.2.4 with BigOWLIM.

Jim 





Holger Knublauch <[email protected]> 
Sent by: [email protected]
05/25/2009 02:04 PM
Please respond to
[email protected]


To
[email protected]
cc

Subject
[tbc-users] Re: Import Remote Sesame in SparqlMotion







Do you know which Sesame version is used by your BigOWLIM store? 
TopBraid uses Sesame 2, but the last time I looked, OWLIM was still 
using Sesame 1.x

Holger


On May 25, 2009, at 10:55 AM, Jim wrote:

>
> I am apparently not using ImportSesameRemoteRepository correctly in my
> SparqlMotion script.
>
> I executed the Import in debug mode, and nothing appears in the
> Results panel.  I changed the script so that the Import feeds directly
> into a Construct {?a ?b ?c} where {?a ?b ?c}, and still I see no
> data.
>
> I changed the connection URL to an invalid one, and got an error
> message, and tried it again with a bogus modelName, which also
> failed.  So it appears to be connecting to my BigOWLIM store; I just
> don't get any data.  I checked the store's contents via the sesame
> workbench, and there is a lot of data there.
>
> Should I see triples directly from the ImportSesameRemoteRepository
> module?  Any ideas what could be going on here?  (I am not using
> contexts)
>
> Jim
>
> >




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.146.164; 
e-from=grbounce--o7mwauaaadwl_g2bqlyhjkrnqovtno4=james_a_miller=raytheon....@googlegroups.com;
 
[email protected]; date=May 25, 2009 6:04:48 PM; 
subject=[tbc-users] Re: Import Remote Sesame in SparqlMotion)




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