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.
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. Respectfully submitted, Jack Hodges -- 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.
