I know this goes against how a ontology runs but is there a way to force priorty on spin rules.
Example(Bad). I have 3 classes ABC A and B have a spin rule to generate there label C generates its label out of A's and B's Label. So when I run i get a version of C's label with A and B having no label and version with A and B having a label. Although both are correct, i really only care about the longer C label. So either i say run these rules first somehow. Or I filter out the shorter of 2 labels when their are 2. But then I would probably hit a infinite loop. I can do this with sparql motion but I'm trying to avoid it. I know the inference engine loops over until there are no new triples. Thanks for any help. you can provide -- 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.
