Hello, John; Since Composer is not intended as a user interface, some features, such as choosing the form class isn't available in Composer.
Enumerated classes (owl:oneOf) are often used for grouping items that belong in a list. In that case, the List class is an enumerated class whose members can change dynamically at run time to be whatever set of resources needed. Another idea is to use some property, such as :inList and have the custom ui query for all members of :inList that are 'true' to populate the list. I found the statement "it needs to know the type of the class". This is always known - owl:Class. Perhaps there is a terminology mismatch here? -- Scott On Aug 9, 11:42 am, John Perdoni <[email protected]> wrote: > Hello Scott ,thanks again for the continued help. > > To clarify ,i am not using ensemble, the question re viewing forms was for > tbc. > > With regard to just adding the sectionHeading instance to the List class, > the ui is custom written, and in order for it to differentiate between a > standalone heading or one that is included in a list ,it needs to know the > type of the class, ie to display/create on the fly a list it has to be > listItem , and visa versa for a standalone heading hence the reason is a > member of both classes. > > I still struggle greatly with the actual modelling , so any further pointers > would be helpfull, although not critical > > Regards > > John -- 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
