Andriy; The label will be a problem for identifying the component, particularly if the "Update Label Automatically" attribute is set to true. A suggestion is to create a property for uniquely identifying the component. The property can be defined in <http://tb-dag> so it is not displayed in your application. Assign the unique value when creating a component and query for it when you need to uniquely identify the component.
-- Scott On Apr 12, 8:56 am, Andriy Sokolov <[email protected]> wrote: > One option I've found is to use the rdfs:label property of the > component instance. Then on load I use a SPARQL-select query with > FILTER on label. But if multiple instances of a component have equal > labels, all instances will be retrieved from configGraph. Is there > another way to distinguish between them? > > On 12 Apr., 14:30, Andriy Sokolov <[email protected]> wrote: > > > Hallo TB-Team, > > I want to store in the configGraph of a TB-Application config data of > > my component. How can I manage multiple components in the configGraph? > > As I know, every component instance becomes random anonymous URI. How > > do I identify and differenciate them? > > Regards, > > Andriy -- 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
