Tim; I'm happy to hear you got the AllegroGraph issue resolved. I noticed you were running the AllegroGraph server on localhost and wanted to make sure you were aware that Using AllegroGraph as a SPARQL Endpoint is not necessary. Composer supports allegro as as data back- end, so all that is needed is to create a connection file (New > RDF/ OWL AllegroGraph Database Connection) and you can access the contents directly in Composer, use it on owl:imports, etc. This will also be much more efficient than the level of indirection caused by calling the back-end as a SPARQL Endpoint.
-- Scott On Sep 11, 10:46 pm, Tim Harsch <[email protected]> wrote: > Turns out the problem was that I did not have a file loaded. I was running > the query in a new workspace with no files loaded. > > The SERVICE keyword worked like a charm. > > On Sat, Sep 11, 2010 at 8:36 PM, Tim Harsch <[email protected]> wrote: > > I forgot to mention I was using TBC Free Edition -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. 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-users?hl=en
