<2.Most restrictions we declare in TBC are cardinality restrictions. If we port them to TBE via the SPARQLMotion module, starting from the assumption we have a number of forms with 20 or more properties, can we still use “selectedResource” as input for the cardinality check or should we define the cardinality check with each property separately for the form ? We would end up with 20 X 2 (min and max cardinality found in function modules) to be executed for any single form in that case.>
This may need some clarification. By the reference to "form", I take it you mean you are defining cardinality constraints on an RDF resource. I'm also assuming that you have created a SPIN function that is to operate on a resource (via the parameter "selectedResource"). The advantage of SPIN is that you can define a single constraint rule, specified in SPARQL, that applies to all instances of a class (all resources if the constraint is defined for rdfs:Resource). In this way, it seems that your cardinality checks could be created with just a handful of constraint rules. But perhaps I am misunderstnding the specifics of your application? -- Scott --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. 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-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
