Rich; The blue links (edges) are inferred and the black ones are
asserted. One way clean things up is to not infer the inverses. You
can read the graph either way, as evidenced by the incoming and
outgoing connections for any resource. SPARQL can also read the graph
either way, so there really isn't a reason to compute inverses. This
will at least reduce clutter a bit.
Insofar as the Graph View is concerned, it is intended to help people
explore their data, not as a visualization tool. Currently we are not
planning on updating this feature, but we will be reviewing Composer
features this fall and your request will be considered.
-- Scott
On Aug 8, 1:42 pm, Rich Keller rich.m.kel...@gmail.com wrote:
I find the graphing function very useful, but I am annoyed that the edge
labels and their inverses are displayed on top of one another. This makes
the graph unreadable. I don't see any way around this short of deleting
inverses or turning off edge labels altogether. Am I wrong? Certainly
there is a better way to handle this in the graph display code.
An unrelated question is the difference between blue links and black links
in the graph.
Thanks for your help. I am using SE v3.5.2.
--
-- 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, SPARQL Web Pages 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
