[UCR] Coverage

MITRE members had the following observations regarding coverage (also
included in my comments on the Straw Poll):
 
(1) We would like RIF to address how to map the entities over which
rules operate. This is a key question for this format. For example, if
a rule says "if a customer is valued" - how do we define what
"customer" means ? What does "valued" mean? Rules without an understood
data model seem like they would have limited value. It is not clear
that this is addressed by either 2.1 or 2.8, though those cases have
related concerns. Also, we note that use case 2.6 presents an
alternative of using mapping rules which could replace a common data
model.
(2) One use case they didn't cover is the use of rules for dynamic
service behavior. They may be thinking that BPEL and others support
that. But we are not talking about the external interaction between
rules (like choreography) but instead, rules for internal service
behavior. If we can push the behavior of services to data (to the
extent that it makes sense), then we can build agile systems, setting
the stage for autonomous entities. 	
 
Deborah