On 5/30/2012 23:03, PaulZH wrote:
Hi Holger,
On May 30, 7:24 am, Holger Knublauch<[email protected]> wrote:
Hi Paul,
do you know when the slowness started for you?
From the first moment already.
Is not surprising since the workflow is as follows.
Read in csv in Google Refine, clean, reconcile and export to RDF ttl.
Then import the ttl file into Sesame via the Sesame Workbench.
Connect to Sesame from TBC to do some additional editing and
constraint checking.
If you have time, an option worth trying would be to do the import of
the ttl file from TBC or SPARQLMotion, and not via Sesame directly. The
difference would be that it will then use Jena bnode identifiers and
these may be easier to round-trip. Sorry we are a bit short on time with
SemTech preparations right now so may not be able to look into this
issue ourselves for a while.
Holger
--
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 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
