Dynamic Evidence has certain expectations for the required structure of Summary Rule Sets in terms of the Rule Classes and Attributes that they should contain. Having said this, the generic CER infrastructure does not have any Evidence Processing concepts. So in order to make sure handcrafted Summary Rule Sets meet these expectations, the following restrictions are enforced on them:
- Summary Rule Sets must contain one Concrete Rule Class which extends from DefaultEvidenceSummary Rule Class in the EvidenceSummaryRuleSet.
- This Rule Class must contain a Rule Attribute named "evidence". The type of this Rule Attribute should be the generated Processing Rule Class, and the derivation of this Attribute should use the specified expression. The specified expression is the default derivation when an Attribute is defined in the CER Editor. So, for example, if the logical name of a Dynamic Evidence Type is "Alien", a Rule Set named "AlienRuleSet" with a Rule Class named "Alien" would be generated. In this case, the concrete Rule Class in the Summary Rule Set for this Dynamic Evidence Type must contain an Attribute named "evidence" whose type is the "Alien" Rule Class in the "AlienRuleSet".