|
Tim, the issue is that Composer displays the classes
and properties. If you have an ontology with a few classes and
properties, Composer works well. Getting the first n instances
(1000 out-of-the-box) when choosing the Instances view, etc. But
if you have an ontology with 20k class definitions, then all need
to be cached to display the tree. Same for properties. -- Scott On 4/11/2014, 11:32 AM, Tim Smith
wrote:
-- -- 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. |
- Re: [topbraid-users] How to NOT cache all triples from da... Mark Graham
- Re: [topbraid-users] How to NOT cache all triples fr... Tim Smith
- Re: [topbraid-users] How to NOT cache all triple... Scott Henninger
- Re: [topbraid-users] How to NOT cache all tr... Tim Smith
- RE: [topbraid-users] How to NOT cache al... Irene Polikoff
- Re: [topbraid-users] How to NOT cac... Tim Smith
- RE: [topbraid-users] How to NOT... Irene Polikoff
- Re: [topbraid-users] How to NOT cache all triples fr... Holger Knublauch
