On 28/03/2017 4:12, Jack Hodges wrote:
Frequently I end up with errors resulting from a graph not being able
to import another graph. Tracking down these errors is often quite
time consuming and the error log isn't helpful at all. Since the error
is well known to TBC, why can't the log tell us which graph was trying
to perform the import when the error occurred? On the TBC imports tab,
the inability to import a graph shows up as a world, which can be
associated with an error or with an external graph. It would be easier
to identify a problem if it had a distinctive icon (maybe a red
world), but much more importantly it would be easier if the
troublesome import was expanded in the import list so I wouldn't have
to open each and every import (sometimes nested very deeply).
Improving the error log is probably the fastest and easiest, and would
save a lot of time.
Yes, that makes a lot of sense. I have just added the URI of the file
that is attempting the import (i.e. the subject of the owl:imports
statement) to the error messages produced by TBC. These are now shown
both in the error dialog and the log.
Pro tip: If you have TBC-ME, go to
http://localhost:8083/tbl/admin/baseURIMgmt
This page will highlight any files that have missing imports, i.e.
references to graphs that are not in the current workspace.
In the inferences tab it is often difficult to locate items of
interest in a long list and it would be helpful if there was some
filtering that could be applied. For example, if you are looking for
inferences on a particular class or graph and could filter out all
those that don't apply to that class or graph it would simplify work
so much.
Hmm, that's much harder. I don't yet see how this could be done without
a lot of supporting infrastructure. The only real way to support all the
different scenarios that people may want to request is through SPARQL or
a generic search capability (that we don't have in TBC). The currently
best approximation might be to use "Assert all to graph..." from the
Inferences view's context menu, following by SPARQL queries against that
named graph.
Holger
--
You received this message because you are subscribed to the Google Group "TopBraid
Suite Users", the topics of which include the TopBraid Suite family of products and
its base technologies such as SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to [email protected]
---
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
