Paul,
I did further testing. TBC 3.5.4 works fine using Sesame 2.5 with
regards to editing the anonymous nodes.
However, when I hover around the anonymous nodes in the form, TBC
becomes unresponsive for a while, and then produces several warning like
"Failed to convert node: @node.......". This happens both in TBC 3.5.4
and 3.6.0B. Was it this issue that you experienced?
This might be a TBC-related warning, so I will look into it.
Thanks,
Gokhan
On 2/28/2012 3:22 AM, PaulZH wrote:
Hi Gokhan,
It was with TBC 3.5.4 and Sesame 2.5.
It is good to know that using the upcoming TBC version with Sesame 2.6
works within acceptable timespans.
Thanks for checking this out.
Paul
On Feb 28, 10:04 am, Gokhan Soydan<gsoy...@topquadrant.com> wrote:
Paul,
Sorry it took me a while to work on the file that you sent. I tried it
in Sesame 2.6.2 (in a memory-store type repository) with TBC-ME 3.6.0B.
It took me at most 5 - 10 seconds to edit eu:language or eu:noteLiteral
literals inside the anonymous nodes.
What version of Sesame did you use? I know that TBC 3.5.4 cannot run
with Sesame version 2.6 or above.
Gokhan
On 2/23/2012 1:27 PM, Gokhan Soydan wrote:
Paul,
As of TBC 3.6.0B, we support Sesame 2.6 and above as well. Maybe you
can try TBC 3.6.0B and see if it is more responsive with anonymous
nodes there.
In the meanwhile, you can send the file to us, and we can test it as
well.
Thanks,
Gokhan
On 2/23/2012 8:00 AM, PaulZH wrote:
Context: Windows 7 32-bit
TBCME 3.5.4
Having a skos with some extensions thesaurus with 2.657.262 triples.
Loaded these in Sesame.
TBC connected to Sesame.
Opening the file takes 50 seconds, which is much better than trying to
open the file directly in TBC (more than 25 minutes).
Everything works fluently except for editing anonymous nodes.
E.g. every skos:Concept has a skos:scopeNote for every language used
in the european union (25 scopeNotes per concept).
Every scopeNote is anonymous with 2 properties: eu:language and
eu:noteLiteral.
When editing a skos Concept and changing something related to these
anonymous nodes makes the system unresponsive for about a minute.
This is not the case when editing other properties.
Anything that can be done?
If needed, I can send the file.
--
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
topbraid-users@googlegroups.com
To unsubscribe from this group, send email to
topbraid-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
