Scott, When I run inferencing with SwiftOWLIM it doens't infer the tripples that I need. Is there a different engine that I need to use or a configuration to change?
I know that Ensemble is targeted at end users, but the functionality that we are looking for is something that our end users want. I'm a little curious how Composer works under the hood in this regard compared to Ensemble. Composer is able to recursively look down into sub classes without needing the inferred tripples. It would be nice in the configuration of a tree component you could specify wether or not it would recurse into sub classes. Chris On Wed, Feb 9, 2011 at 1:40 PM, Scott Henninger <[email protected]>wrote: > Chris; The Ensemble tree is not designed to work like Composer's. You > can define what property is used for the count by editing the "Counts > Property" attribute for the tree view. But to get a count of all > instances subsubmed (entailed by RDFS reasoning), you would first need > to run RDFS inferences, either on the file in the server (you can save > inferred triples and re-import them) or via a server-side SPARQLMotion > script, etc. > > Running RDFS inferences would also address the problem with showing > all subsumed instances for a class in a Grid component. > > Just so there aren't other expectation mismatches, the target audience > of Composer and Ensemble are different. Composer is targeted for > ontology experts and therefore provide for a full range of ontology > editing features, from reasoning profiles to modeling tools such as > creating local class restrictions in OWL. Ensemble's target audience > is end users, some of whom may not know anything about RDF, RDFS or > OWL. A full set of ontology editing tools is not expected for this > audience, as their concern is to work with data that has been designed > by ontologists/data specialists. > > As stated, you can write a SPARQLMotion script that runs whatever > reasoning profile you want, along with other rules and data > manipulations, that places data in the Ensemble application for the > end users to edit, view, etc. But the ontology work is expected to > occur in the ontology editor, Composer. > > If your use cases are different, please let us know some details, and > we can look into potential enhancements. > > -- Scott > > -- Scott > > On Feb 9, 10:34 am, Chris Shaw <[email protected]> wrote: > > I'm trying to configure the tree component in Ensemble to behave more > like > > the tree in Composer. I would like the number of elements to display the > > entire number of instances for not only that class, but also its > > sub-classes. There is a property for configuring the count, but I > haven't > > found anything that will produce the results that I'm looking for. > > > > I'd also like to change the behavior of the results grid to that of the > > instance view in Composer. When a higher level class is selected, I'd > like > > the results grid to populate with not only the results at that level, but > > its sub-classes as well. > > > > Thanks for any help > > Chris > > -- > You received this message because you are subscribed to the Google > Group "TopBraid Suite Users", the topics of which include TopBraid > Composer, > TopBraid Live, TopBraid Ensemble, SPARQLMotion 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 Group "TopBraid Suite Users", the topics of which include TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion 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
