Hi,
I'm enjoying TBC 4.6 a lot (I really like the features and the UI), as well
as the SPIN java API which is a great companion for automating some tasks.
But there are a couple of (minor) things I've noticed which, at least from
my perspective, would be useful to fix/enhance:
- In TBC, when using sp:text only to specify rules (and no RDF syntax),
the comments don't get extracted from the TBC Rule field. This makes
monitoring the inferencing progress very verbose, as the whole query -
including prefixes - gets displayed. I can add the rdfs:comment field
manually in TBC ("Add widget for property..."), but then the TBC Rule field
doesn't display the rule properly anymore.
- When I specify rules in TBC that contain nodes of the default
namespace (i.e. :myNode instead of myNS:myNode) then SPIN API complains
about these rules. Don't know if this is a problem of TBC (should sp:text
only contain fully qualified nodes?) or of SPIN API.
- It would be nice if more "useable" information is sent to the SPIN API
ProgressMonitor, such as the iteration number as an integer and rule name
as a string. Now the only way to extract this information, seems to parse
the so-called subtask label.
- Inferencing with SPIN API is a lot faster than inferencing with TBC
(factor 8 or so). Perhaps the constant updating of the TBC progress widget
is the culprit? If this is the case, maybe it makes sense to provide the
possibility to turn off these widget updates? Or better yet, perhaps a more
advanced progress widget would allow the possibility to show only "high
level" information such as the current iteration number, and would show
additional information such as a progress bar, busy time, etc.?
- In TBC, suppose you create a new ontology that imports other
ontologies, and you create subclasses of existing (imported) classes. In
this case, it would be nice to visualize in the Classes View which "paths"
contain subclasses of the currently active ontology, and which don't. Just
like individuals can be found very easily due to the "(<number>)" suffix,
it would be nice to see which classes lead to subclasses of the currently
active ontology, and which don't. Perhaps the imported classes that don't
contain subclasses of the currently active ontology could have a gray font
instead of a black one?
- In TBC, it would be nice to be able to (briefly) filter the Properties
View and the Classes View, so that they only show the properties and
classes of the currently active ontology. If your ontology imports some
other ontologies, you may end up with a very long or deeply nested list of
properties and classes, and you lose the overview. A simple checkbox next
to the "Classes" or "Properties" tab would allow to quickly switch between
the "full" view and the "active ontology only" view.
- Not sure if it's a legitimate remark or not, but I for one wouldn't be
unhappy to see SPIN API appearing on GitHub...
Not expecting any feedback on these remarks of course, just wanted to
mention them.
Kind regards,
Wim
--
-- 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 Insight,
SPARQLMotion, SPARQL Web Pages 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
---
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.
