Compliant applications must handle any valid RIF document in a predictable way
Full Statement
A RIF (Core, Standard, etc) compliant application MUST be able to handle any valid RIF (Core, Standard, etc, resp.) document in a predictable way.
A correlate is that a RIF (Core, Standard, etc) compliant application MUST produce only valid RIF (Core, Standard, etc, resp.) documents, but this is probably obvious and need maybe not be stated as an explicit design constraint.
Position in the DC structure
Level: Critical Success Factor [PROPOSED]
Dependencies
This DC depends on the following DCs:
Motivation
This comes from the charter, I guess. The point is that there will always be a use case for an application that cannot process all the rules that can be covered by a RIF, however poor its expressiveness: if the expressiveness of RIF Core is Horn logic, Datalog applications will not be able to process all the rules or rulesets covered by RIF Core; if the expressiveness of RIF Core is Datalog, propositional calculus applications will not be able to process all the rules or rulesets covered by RIF Core etc. Same for Standard RIF etc.
Therefore, compliance cannot be expressed in terms of how a compliant application processes rules or rulesets covered by the RIF, but only in terms of how it processes a valid RIF document.
Urgency
A RIF without that is probably of limited use for most stakeholders