There are three ways to populate the grid: 1. By providing a property that connects some resource that is passed to the grid component to resources to be shown in the grid. For example, resource being passed could be kennedys:Person, and property could be rdf:type, when configured like this, grid will display all people. Or it could be :JohnKennedy and property could be :almaMatter. Then grid will display all colleges JFK went to. You can differentiate between the resource being passed is a subject or an object of the triple.
One can also indicate what columns to display by configuring the class that is being used to determine the display columns. This is called Column Resource. When property is rdf:type and a column class is not specified, TBE uses the passed resource (in our example, class Person), when a property is not rdf:type, column resource should be specified in the configuration. In the second example, one would have to explicitly say in the configuration that we are using for display :College class (or any other class that make sense). As Scott explained, data for the columns should already exist. If it is not there, the columns can not be populated. If the data needs to be inferred, then inferencing process should be run first by invoking, for example, SM script. 2. By specifying search criteria in the search form or visual query editor. With these options application end user could select what columns to display. Again, data needs to be already there 3. By specifying a query template to populate the grid. With it, one would also specify a query template variable. This is an alternative grid configuration to #1 above. I believe it should be possible to use magic properties in the query template and their values could then show up in the grid, but I have not tried doing this. Regards, Irene -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Scott Henninger Sent: Monday, April 26, 2010 6:38 PM To: TopBraid Suite Users Subject: [topbraid-users] Re: magic properties as columns in composer instances pane or ensemble results grid Arthur; There may be an expectation mismatch with what is meant by "magic property" - see http://composing-the-semantic-web.blogspot.com/2009/11/magic-properties-with -spin.html. Magic properties are best thought of as a kind of SPIN function that returns more than one value, ala a graph match instead of a function return. It may or may not define values for the property used in the definition. This depends on the definition in the magic property's spin:body. The Ensemble grid will display values of properties for each instance of the grid. You can infer these values, but you will need a direct triple - i.e. "<instance> <property> <value>", where <property> is the property in the Grid column. I.e. you can populate the property from a magic property definition, but you will need to run a query to compute the values and assert them as values of the properties you are displaying in the Grid. A more concrete example may be needed... -- Scott On Apr 26, 5:16 pm, Arthur Keen <[email protected]> wrote: > I need to display the status of a parent object in columns in the Ensemble Grid, where the status of the parent is derived from the status of it's children. > > I assumed that the instance view and ensemble grid use sparql under the covers to query for the tabular data displayed, so I decided to use magic properties and created a set of magic properties that summarize the status of a parent object based on status property values on it's children. I verified that they worked, and then added the magic properties to columns of the instance panel. The columns show up in the instance panel and the Ensemble grid, however the values returned by the magic property do not make it into the instances panel or grid. Do magic properties work on the instance panel and ensemble grid view components? > > Arthur > > -- > 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 athttp://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 -- 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
